I2C Master卡住：MCSR卡在START_GEN设置中

在我的CY8C588FNI设计中，使用固定功能的主I2C接口（IP版本3.5），我很少看到（按每秒一次访问一次的顺序），该接口在调用SDENSTATE（）API函数后会被卡住。在调用SeNestSistar（）之前，我检查MCSR以确保它是0，它是。通常，在该调用之后，MCSR转到0x0C（Buth-Woad和MSTRUX模式）。但是，在卡住的情况下，我看到它被设置为0x01（StaskGEN）——这是调用所断言的比特。没有多少等待帮助-寄存器停留在0x1。SeNestStar（）完成无错误（NONError），但对I2C API函数的后续调用在NoTyRead中失败。
也就是说，在失败的情况下，I2C接口开始空闲，SeNSTART似乎完成了OK（它等待CSR WaITyByTeTeExcel完成），但是MCSR卡在StaskGEN中，并且从未完成。
这是当务之急，请帮忙。
---
顺便说一下，我还观察到，调用sEdTestSug（）API后，MCSR很少会在0xC停留一段时间，但是这是一个过渡状态，最终它会变成0x0。不过，这似乎是一个不正确的API实现——我希望sEntStutter（）在接口和总线空闲之前旋转。



     以下为原文
  In my CY8C5888FNI design with fixed-function master I2C interface (IP version 3.5), I see that very infrequently (on the order of once per hour under once-per-second accesses), the interface gets stuck after the SendStart() API function is called. Before calling SendStart(), I check the MCSR to make sure it is 0, which it is. Normally, after that call, the MCSR goes to 0x0C (BUS_BUSY and MSTR_MODE). However, in the stuck case, I see it set to 0x01 (START_GEN) - which is the bit that the call asserts. No amount of waiting helps - the register stays at 0x1.  SendStart() completes without error (NO_ERROR), but subsequent calls to I2C API functions fail with NOT_READY.

I.e., it appears that in the failing scenario, I2C interface starts out as idle, SendStart seemingly completes OK (its wait for CSR WAIT_BYTE_COMPLETE succeeds), yet the MCSR gets stuck in START_GEN and never completes.

This is quite an urgent matter, please help.

---

BTW, separately I've also observed that after calling SendStop() API, MCSR infrequently stays at 0xC for some time - however this is a transient condition, where it eventually changes to 0x0. Still, seems like this an incorrect API implementation - I'd expect SendStop() to spin until the interface and the bus go idle.