Error Logs

When an error is encountered in decoding CSI packets received at an SoC CSI interface and writing the raw frame data to memory, the VI hardware engine notifies these errors to RCE. The capture stack running on CCPLEX queries the capture status from RCE and displays:

  • The CSI stream ID (CSI brick).
  • VC ID for which the error occurred.
  • The type of error.
  • Detailed errors per the error type.

The error status provides a good starting point to determine the root cause and identify the next steps.

If the VI engine did not successfully capture a frame, and did not encounter and report an error to RCE, then the error message, as follows, or a similar one displays: 

Frame Start Timeout Error.

    EngineStatusError (2), Detailed Error Code: 00000001 at 
    StreamId:0 vcId:0 CSIFrameId:0 notified-bits:2000000or

Frame End Timeout Error

    EngineStatusError (2), Detailed Error Code: 00000002 at 
    StreamId:0 vcId:0 CSIFrameId:0 notified-bits:4000000

This can be due to one of two reasons:

  1. The deserializer is not streaming data.
  2. The VI channel is not configured to capture the correct data type/VC id.

The remainder of this document describes the root causes for these errors.