基于CX3的应用程序中出现错误触发

你好，
在我的基于CX3的应用程序中，我通过注册CYU3pPIN TrcButtBuffic函数与Cyu3pPIbReistalCalpCou后缀API实现了“PIB中断”回调：在任何情况下，我不需要这样做，除了在整个应用程序的调试阶段中检查意外情况之外。
令人惊讶的是，在明显的正常操作中，我调用了多次调用回调，CBType＝= Cyu3PyPiBi内错误和Cyu3PyGETY-GPIFYErrRoRyType（CBARG）= = CYU3PY-GPIIFEL RealEndiDySt.
即使我不确定这样做是合法的，但在这种情况下，我试图通过调用回调内部的CYU3PGPIFGETSMSTATE来理解哪个GPIF SM状态被认为是“无效的”。根据该过程，似乎触发错误的状态是：Cx3AIDLYESCK0/ 1，CX3WAITYOFFRIGHYSTARKSTARKSCK0/ 1，CX3SUPARALL BuffelSyIn SCK0/1和未记录状态131和132。
由于我正在使用CX3设备，所以我使用的是“固定”函数GPIF配置，这是由于调用CYU3PMIPICSIGIFFILLATE（CyuU3PYMIPICSIIB BuSU24，BuffrySead）导致的。
所描述的行为正常/预期吗？如果不是，什么会引起这些错误的触发？
请注意，我的应用程序目前有点奇怪，因为我正在编写一个自定义的DPHY/CSII传感器的图像帧组成的单行：因此，我目前保持线/帧率相当低（相比于传感器HW所支持的），以便能够在Cx3IDE，以跟上相应的中断率。
谢谢你，尼古拉。



     以下为原文
  Hello,

in my CX3-based application I enabled the 'PIB interrupt' callback, by registering my CyU3PPibIntrCb_t-compliant function with the CyU3PPibRegisterCallback API: I don't need this for any purpose apart checking for unexpected conditions while I'm in a debug phase for the entire application.
Surprisingly I'm having my callback called many times during apparently normal operation, with cbType == CYU3P_PIB_INTR_ERROR and CYU3P_GET_GPIF_ERROR_TYPE(cbArg) == CYU3P_GPIF_ERR_INVALID_STATE.
Even if I'm not sure that it is legal to do so, in those circumstances I'm trying to understand which GPIF SM state is considered 'invalid', by calling the CyU3PGpifGetSMState from inside the callback. According to that procedure the states that seem to trigger the error are: CX3_IDLE_SCK0/1, CX3_WAIT_FOR_FRAME_START_SCK0/1, CX3_PARTIAL_BUFFER_IN_SCK0/1 and undocumented states 131 and 132.
Since I'm working on the CX3 device, I'm using the 'fixed'function' GPIF configuration that results from the call to CyU3PMipicsiGpifLoad(CY_U3P_MIPICSI_BUS_24, buffer_size).
Is the described behavior normal/expected ? If not, what could be causing the triggering of those errors ?
Please note that my application is currently a bit peculiar because I'm programming a custom D-PHY/CSI-2 sensor for image frames composed of a single line: as a result I'm currently keeping the line/frame rate quite low (compared to what supported by the sensor HW) in order to be able, on the CX3 side, to keep up with the corresponding interrupt rate.

Thanks in advance and best regards, Nicola.