SIPL get image error

Robotics & Edge Computing Jetson Systems Jetson Thor
1

We are attempting to capture images via the SIPL , but there is error report as follow:
nvsipl_camera: ERROR: Pipeline: 0, NOTIF_ERROR_ICP_EMB_DATA_PARSE_FAILURE
nvsipl_camera: ERROR: Pipeline: 0, NOTIF_ERROR_ICP_BAD_INPUT_STREAM
nvsipl_camera: ERROR: Pipeline: 0, NOTIF_ERROR_ICP_EMB_DATA_PARSE_FAILURE
nvsipl_camera: ERROR: Pipeline: 0, NOTIF_ERROR_ICP_BAD_INPUT_STREAM

Our hardware platform is Thor, software version: JP7.2. The full log is shown below. Could you advise methods to locate what is wrong?
log1.txt (18.4 KB)
log2.txt (22.8 KB)

4

The notifications mean ICP never produced a valid full frame.

  • NOTIF_ERROR_ICP_EMB_DATA_PARSE_FAILURE: a capture buffer was returned, but top embedded data could not be parsed. For AR0234 that parser expects a full top line (≥768 bytes) starting with header 0A AA 30 A5.
  • NOTIF_ERROR_ICP_BAD_INPUT_STREAM: VI reported a partial / short frame.
  • NOTIF_ERROR_ICP_CAPTURE_FAILURE and 0 fps are the result of those, not a separate GetImage issue.

Init is OK (AR0234 Init called). The failure starts immediately after Start.

Your RCE log programs VI 1920×1538. The JP7.2 HAWK single-camera config is 1920×1200, 2 embedded top lines, isEmbeddedDataTypeEnabled: true (embedded on CSI DT 0x12, not added into pixel height). 1920×1538 looks like 1920×1536+2, which does not match AR0234. If VI height / embedded DT do not match what the sensor+serializer actually send, you get exactly this pair of errors.

Please check:

  1. Confirm the module on CSI-A / link 0 is really NVIDIA HAWK AR0234 (MAX9295 + AR0234), not a 1920×1536 camera with this config name reused.

  2. Dump the live query (width, height, embeddedTopLines, isEmbeddedDataTypeEnabled):

    nvsipl_query -p -c AR0234CS_HAWK_SINGLE_CAMERA

    If you use a custom JSON/-t, please attach that file.

  3. Retry with subframe disabled (ISP is already off):

    sudo nvsipl_camera -H -R -0 -1 -2 -u -m "0x0001" -c AR0234CS_HAWK_SINGLE_CAMERA -r 15 -s -v 4

  4. Collect dmesg from the same run (tegra-capture-vi / nvcsi corr_err, short frame, err_data).

  5. Recapture rtcpu trace with VI notify errors enabled so CHANSEL / short-frame / DT mismatch show up. The attached 159-line trace only has stream config + vi_task_submit, no capture-complete or VINOTIFY error.

Operation returning failure: opcode = 0x5 on Stop is HSL write-verify during teardown after the pipeline already failed. Please ignore that until a full frame is captured.