Tool/software:
When CRC error comes within a frame, this error callback will be immediately called, but this frame will be still captured in the memory, so there will still be frameCallback from the driver.
So the errors are received frames are reported asynchronously to each other?
Then, is there any reliable way to know which particular frame buffer returned corresponds to the erratic frame?
There is a documented FVID2 return code for CRC errors (FVID2_FRAME_STATUS_CRC_ERROR) however I can't find this error code ever returned in the csirx driver sources.
Perhaps can receive both frame notifications and error notification and assume that the next frame returned after the error is problematic, however:
(1) is the callback order guaranteed? can't it happen that notification about the error close to end of frame comes after notification about receive? or, can't notification about error close to the beginning of a frame come before notification about previous frame receive?
(2) in case of multiple frames (for different VCs) are received by the same CSIRX instance, how to know which particular one was received with an error?