information |
NOTIF_INFO_ICP_PROCESSING_DONE |
0 |
Pipeline event, indicates that ICP processing is
finished. |
Capturing frame from VI was successful. |
Every frame |
N/A |
N/A |
NOTIF_INFO_ISP_PROCESSING_DONE |
1 |
Pipeline event, indicates that ISP processing was requested
successfully. |
ISP Process task is submitted for the frame successfully. |
Every frame |
N/A |
N/A |
NOTIF_INFO_ACP_PROCESSING_DONE |
2 |
Pipeline event, indicates that auto control processing is
finished. |
Auto Control Alg processing on the frame finished
successfully. |
Every frame |
N/A |
N/A |
NOTIF_INFO_CDI_PROCESSING_DONE |
3 |
Pipeline event, indicates that CDI processing is
finished. |
Set sensor controls done. |
If triggered, immediately This event is triggered only if the
Auto Exposure and Auto White Balance algorithm produces new sensor
settings that need to be updated in the image sensor. |
N/A |
N/A |
|
NOTIF_INFO_ICP_AUTH_SUCCESS |
4 |
Pipeline event, indicates image authentication success. |
Image Authentication Success |
Every frame |
N/A |
N/A |
Warnings |
NOTIF_WARN_ICP_FRAME_DROP |
100 |
Pipeline event, indicates that the pipeline was forced to drop a
frame due to a slow consumer or system issues. |
Not enough free buffers in the SIPL capture buffer pool. |
Every time a frame was dropped |
YES |
Record |
NOTIF_WARN_ICP_FRAME_DISCONTINUITY |
101 |
Pipeline event, indicates that a discontinuity was detected in
parsed embedded data frame sequence number. |
Current frame index num not equal last frame index num +
1. |
Every time a frame was sequence number was not as
expected |
YES |
Record |
NOTIF_WARN_ICP_CAPTURE_TIMEOUT |
102 |
Pipeline event, indicates occurrence of timeout while
capturing. |
Cannot get data after in a duration of 10/frameRate. |
Everytime a frame was not retrieved from VI within duration
10/frameRate. Could occur during Deinit and it can be
ignored. |
YES |
Record |
Errors |
NOTIF_ERROR_ICP_BAD_INPUT_STREAM |
200 |
Pipeline event, indicates ICP bad input stream. |
The captured buffer is a partial frame. |
On demand |
Depends on the specific error |
Print the error and stop the pipeline. |
NOTIF_ERROR_ICP_CAPTURE_FAILURE |
201 |
Pipeline event, indicates ICP capture failure. |
If getting output buffer from VI fails. |
On demand |
NO |
Print the error and stop the pipeline, or try to recover from the
error when the auto recovery option is specified. |
NOTIF_ERROR_ICP_EMB_DATA_PARSE_FAILURE |
202 |
Pipeline event, indicates embedded data parsing failure. |
For full frame, it is a critical failure. For sub frame, it is a
critical failure if Parse Top data fails, but it is not critical if
Parse Bottom data fails. |
On demand |
NO |
Print the error and stop the pipeline. |
NOTIF_ERROR_ISP_PROCESSING_FAILURE |
203 |
Pipeline event, indicates ISP processing failure. |
If programming/processing request to ISP fails |
On demand |
NO |
Print the error and stop the pipeline. |
NOTIF_ERROR_ACP_PROCESSING_FAILURE |
204 |
Pipeline event, indicates auto control processing
failure. |
|
On demand |
NO |
Print the error and stop the pipeline. |
NOTIF_ERROR_CDI_SET_SENSOR_CTRL_FAILURE |
205 |
Pipeline event, indicates CDI set sensor control failure. |
|
On demand |
NO |
Print the error and stop the pipeline, or try to recover from the
error when the auto recovery option is specified. |
NOTIF_ERROR_DESER_LINK_FAILURE |
206 |
Deprecated |
N/A |
N/A |
N/A |
N/A |
NOTIF_ERROR_DESERIALIZER_FAILURE |
207 |
Device block event, indicates a deserializer failure. |
1. Config which gpios used for these device errors
via platform config. 2. Start an error monitor in a thread. 3.
Device driver calls low-level driver to wait for the specified GPIO
interrupts. 4. Once the specified GPIO interrupt occurs, translate
GPIO index num to these three error types, and then notify app to
handle it via callback. |
On demand |
NO |
Call GetDeserializerErrorInfo to get details. |
NOTIF_ERROR_SERIALIZER_FAILURE |
208 |
Device block event, indicates a serializer failure. |
On demand |
NO |
Call GetModuleErrorInfo to get details. |
NOTIF_ERROR_SENSOR_FAILURE |
209 |
Device block event, indicates a sensor failure. |
On demand |
NO |
NOTIF_ERROR_ISP_PROCESSING_FAILURE_RECOVERABLE |
210 |
Pipeline event, indicates an ISP process failure due to
recoverable errors. |
An ISP recoverable error has happened in the last ISP processed
frame for the specified pipeline. |
On demand |
YES |
Record |
NOTIF_ERROR_ICP_AUTH_FAILURE |
211 |
Pipeline event, indicates image authentication failure. |
If image authentication or the request to authenticate image
fails. |
On demand |
YES if it is an authentication failure; NO if it is an error from
the Security Engine |
Authentication failures can resolve on their own. Otherwise,
print the error and stop the pipeline. |
NOTIF_ERROR_INTERNAL_FAILURE |
300 |
Pipeline and device block event, indicates an unexpected internal
failure. |
When there are critical failures due to a) dependencies b) helper
functions c) failed to submit capture requests. |
On demand |
NO |
Print the error and stop the pipeline. |