The camera reports the following problem. What is going on? Can you help me solve it?thanks

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hi All：
The camera reports the following problem. What is going on? Can you help me solve it?

[11286.768337] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 256=0x100, vc: 0.2024-08-12.
[11286.877578] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: flags 2, err_data 0
[11286.897643] [RCE] VM0 deactivating.VM0 activating.ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=11307825317184 sof_ts=11307839738912 gerror_code=2 gerror_data=400062 notify_bits=20000"
[11289.565616] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[11289.574765] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[11289.584356] (NULL device *): vi_capture_control_message: NULL VI channel received
[11289.592089] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[11289.602763] (NULL device *): vi_capture_control_message: NULL VI channel received
[11289.611603] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

Block Diagram

image
image689×738 13.6 KB

version:

root@tegra:/home/robot# more /etc/nv_tegra_release
# R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug  1 19:57:35 UTC 2023

trace.log:
trace.log (28.7 MB)

dts:
dts.txt (478.1 KB)

3

hello wxsrite,

did you meant such failure only reported by running d430 at port-index=<2>?
had you confirm it’s actually output validate frame packets to CSI channel as well?

4

hi JessyChang,

yes.

The problem is that when the device is running, an error message is displayed. When the device is turned off and then turned on again, there is no problem. There is no way to capture the status of the serializer and deserializer in time when the problem occurs.

5

hello wxsrite,

I assume you’re saying keep the v4l2 or gst pipeline running, then restart d430 stream, right?

6

No, disconnect the stream and use the v4l2 or gst command again.

7

hello wxsrite,

just double check, had you apply this RCE firmware update from Topic 268833 to update deskew algorithm, and also stability fixes?

8

hi，JerryChang,
Can I put it directly in the device and flash the partition directly? Because the device has been sold, it is not easy to flash it.

9

hello wxsrite,

it’s doable, you may use the OTA payload to update bootloader remotely.
we’ve also tested and verified it could update rce-fw remotely.
for instance,
(1) Please update rce-fw on your host machine, i.e. update $OUT/Linux_for_Tegra/bootloader/camera-rtcpu-t234-rce.img with the updated firmware binary.
(2.1) You should also visit L4T page, jetson-linux-r3541 to download the same release version [OTA Tools] package.
(2.2) You may refer to developer guide for Preparing the OTA Payload Package section to prepare the OTA payload.
(3) Running below commands to generate an OTA payload package to only update Bootloader for your Orin Nano DevKit.
$ sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 -b jetson-orin-nano-devkit R35-4
(4) Here’s created OTA payload, you may deliver this ota_payload to your remote targets for running bootloader update.
$ ls $OUT/Linux_for_Tegra/bootloader/jetson-orin-nano-devkit/ota_payload_package.tar.gz

10

Hi，JerryChang：

Please help me check if it works, thank you!

I am using Debug_camera-rtcpu-t234-rce.img

Procedure：
camera-rtcpu-t234-rce(OTA log).txt (641.4 KB)

Device Log：
dmesg.txt (127.3 KB)

11

hello wxsrite,

that’s outputting RCE debug logs, you may check those kernel logs with [RCE] in the beginning.

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.