Hello Jerry,
To re-flash I use Orin Nano and tc358743 capture issue - #10 by anomad ( full creation process linked in this comment - Orin Nano and tc358743 capture issue - #12 by anomad )
When will the next public release be available to try?
hello anomad,
is this a fused device? for instance, is it has secure boot enabled with PKC+SBK.
if yes… it might be the same issue with Topic 266849.
sorry, I don’t have rough ETA at the moment.
Hello Jerry,
I’m not sure – is the Xavier NX DevKit a fused device? I didn’t set up any kind of encryption or code signing.
I see in your link locations like ‘uefi_keys/keys’ when I haven’t used before in OS generation/compilation.
Do I have to enable secure boot to use the patch you provided ?
hello anomad,
it seems partition update did not support with p3509+p3767.
please try update the rce-fw and perform a full-flash.
steps as following…
(1) update the binary file under… $OUT/Linux_for_Tegra/bootloader/camera-rtcpu-t234-rce.img
(2) $ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" -p --showlogs --network usb0 jetson-orin-nx-devkit-16gb internal
(3) $ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
(4) Flash images into the both storage devices:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only
Hello Jerry,
I received an error on step 2:
parallels@orindev:~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" -p --showlogs --network usb0 jetson-orin-nx-devkit-16gb internal
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml -p --showlogs --network usb0 jetson-orin-nx-devkit-16gb internal
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh: line 47: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/jetson-orin-nx-devkit-16gb.conf: No such file or directory
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash.func: line 215: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/jetson-orin-nx-devkit-16gb.conf: No such file or directory
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 366: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/jetson-orin-nx-devkit-16gb.conf: No such file or directory
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 558: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/jetson-orin-nx-devkit-16gb.conf: No such file or directory
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs jetson-orin-nx-devkit-16gb internal
Error: Invalid target board - jetson-orin-nx-devkit-16gb.
In searching for a solution, I found this link : Jetson Orin NX - #4 by Ursula which had the same error. It appears they were missing that files as well.
I did not see ‘jetson-orin-nx-dvkit-16gb’ in ~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra
Was that .conf file supposed to be released with 5.1.2 ?
Where can I get a copy of that file ?
please update the board name for using p3509-a02+p3767-0000 as it’s Orin SOM on Xavier NX Carrier.
Hello Jerry,
Didn’t we try this on 11.07.23 ? - Orin Nano and tc358743 capture issue - #9 by JerryChang
we’ve tested this locally. it indeeds an issue with p3509+p3767 doesn’t support partition update.
however, we could update rce-fw correctly by full flash the target.
Hello Jerry,
I changed the name of the conf file used and got:
Error: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Where can I find the process to sign/secure and create ‘flash.idx’ (and all the other necessary files) ?
I see flash.idx in my JetPack_5.1.1 directory, but can not find my notes on how I created it.
it’s created by initrd flash script file.
how you flash your target in the beginning? you may only perform the same the re-flash your device.
Hello Jerry,
The command I had used to flash the Orin was
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal
Upon close inspection, I see the command in step (2) had an extra “-p” in the parameters (before --showlogs). Could that be the source of the errors I was getting ?
That successfully reflashed my Orin. Is there a way to confirm I have the patch? I will apply my updates and files and report back in a day or two.
Hello Jerry,
Recently flashed Orin back to the non-working state is was in before. I ran the command you suggested above (adding ROOTFS_ENC=1 and the ekb.key to the flash command) - and it failed looking for -i.conf ??
parallels@orindev:~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external -i ./ekb.key
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external -i ./ekb.key
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh: line 47: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/-i.conf: No such file or directory
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash.func: line 215: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/-i.conf: No such file or directory
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 366: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/-i.conf: No such file or directory
/home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 558: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/-i.conf: No such file or directory
Create folder to store images to flash
Generate image for external storage devices
Generate images to be flashed
BOOTDEV=nvme0n1p1 ADDITIONAL_DTB_OVERLAY="" /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign --external-device -c "./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml" -i "./ekb.key" -i nvme0n1p1
Error: Invalid target board - -i.
Usage: sudo ./flash.sh [options] <target_board> <rootdev>
Where,
target board: Valid target board name.
rootdev: Proper root device.
options:
-c <cfgfile> ---------- Flash partition table config file.
[...]
--uda-dir-------------- Directory to store user data that will be encrypted in UDA partition.
Error: /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...
Why is it parsing -i as a target board ?
the last column is always determine as board configuration,
please moving this options forward, you may see-also below command-line as an example for disk encryption.
$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -i ./ekb.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
Hello Jerry,
I fixed the command to be :
sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -i ./ekb.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
And it appeared to run fine (after installing cryptsetup)
At the completion it says to run the command with “–flash-only” so I ran :
sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --flash-only --external-device nvme0n1p1 -i ./ekb.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
And received this error : (full command line and console logs available if needed)
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Starting to create gpt for external device
Active index file is /mnt/external/flash.idx
Number of lines is 19
max_index=18
writing item=1, 9:0:primary_gpt, 512, 19968, gpt_primary_9_0.bin, 16896, fixed-<reserved>-0, 23bdee126c2bfefb07468c55fee1daa9f8e544b2
Error: Could not stat device /dev/nvme0n1 - No such file or directory.
Flash failure
Cleaning up...
Where is it getting /dev/nvme0n1 from ?
hello anomad,
it’s your external storage.
Hello Jerry,
I see my mistake - I picked “nvme0n1p1” up from a previous example. Will try running w/correct --external-device.
Hello Jerry,
Attempted flash and now the unit only reboots w/a kernel panic.
hello anomad,
it looks you did not update EKS image correctly.
there shows an error to unlock the encrypted partition.
for example, [ 15.583687] ERROR: fail to unlock the encrypted dev /dev/mmcblk1p2.
please refer to this topic for the steps.
Hello Jerry,
Thank you for the link to the signing process - that filled in the blanks in my process to get to where I am successfully booting my signed image. I ran :
sudo ./apply_binaries.sh
# Reconnect Jetson in RM
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --no-flash --network usb0 jetson-orin-nano-devkit internal
echo "f0e0d0c0b0a001020304050607080900" > ekb.key
# Reconnect Jetson in RM
sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device mmcblk1p1 -i ./ekb.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
# Reconnect Jetson in RM
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only
How do I verify that I am using the updated camera-rtcpu-t234-rce.img ? I created mine on Nov 6.
-rwxrwxr-x 1 parallels parallels 531808 Nov 6 21:08 /home/parallels/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/camera-rtcpu-t234-rce.img
When I try my capture command
v4l2-ctl --device /dev/video0 --stream-mmap --set-fmt-video=width=1280,height=720,pixelformat=UYVY --stream-to=frame.raw --stream-count=10 --verbose
I am still getting the “vi_capture_control_message: NULL VI channel received” error. Last part of dmesg (let me know if you need the full capture).
[ 366.197031] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:
[ 5666.699172] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffcf0800, fsynr=0xb0003, cbfrsynra=0x405, cb=3
[ 5666.714752] mc-err: (255) csr_pcie1r: EMEM address decode error
[ 5666.721198] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[ 5666.729509] mc-err: secure: yes, access-type: read
[16628.554088] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd2c000, fsynr=0xb0003, cbfrsynra=0x5, cb=3
[16628.569402] mc-err: (255) csr_pcie1r: EMEM address decode error
[16628.575787] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[16628.584060] mc-err: secure: yes, access-type: read
[22436.182186] tc358743 9-000f: tc358743_set_pll:
[22436.186916] tc358743 9-000f: tc358743_set_csi_color_space: YCbCr 422 16-bit
[22436.188657] tc358743 9-000f: tc358743_g_input_status: status = 0x0
[22436.189048] tc358743 9-000f: jc - FOUND signal and sync!
[22436.191175] tc358743 9-000f: tc358743_query_dv_timings: 1280x720p60.00 (1650x750)
[22436.191204] tc358743 9-000f: tc358743_s_dv_timings: 1280x720p60.00 (1650x750)
[22436.192134] tc358743 9-000f: tc358743_set_pll:
[22436.213817] bwmgr API not supported
[22438.819386] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[22438.832141] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[22438.842582] (NULL device *): vi_capture_control_message: NULL VI channel received
[22438.850351] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[22438.861068] (NULL device *): vi_capture_control_message: NULL VI channel received
[22438.868809] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[22438.879715] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[22441.411060] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[22441.420211] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[22441.430774] (NULL device *): vi_capture_control_message: NULL VI channel received
[22441.438526] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[22441.449187] (NULL device *): vi_capture_control_message: NULL VI channel received
[22441.456915] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[22441.467863] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[22441.485153] bwmgr API not supported
[36032.217309] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd64000, fsynr=0x380003, cbfrsynra=0x805, cb=3
[36032.233526] mc-err: (255) csr_pcie1r: EMEM address decode error
[36032.239758] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[36032.248254] mc-err: secure: yes, access-type: read
[73894.670859] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd32000, fsynr=0x380003, cbfrsynra=0x5, cb=3
[73894.683315] mc-err: (255) csr_pcie1r: EMEM address decode error
[73894.689570] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[73894.697836] mc-err: secure: yes, access-type: read
[77674.572296] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc29000, fsynr=0xb0003, cbfrsynra=0x805, cb=3
[77674.587800] mc-err: Too many MC errors; throttling prints
[86683.434131] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffa5e000, fsynr=0x380003, cbfrsynra=0x805, cb=3
[86683.446907] mc-err: (255) csr_pcie1r: EMEM address decode error
[86683.453054] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[86683.461309] mc-err: secure: yes, access-type: read
[87376.443257] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffa9e800, fsynr=0xb0003, cbfrsynra=0x805, cb=3
[87376.458773] mc-err: (255) csr_pcie1r: EMEM address decode error
[87376.465119] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[87376.473459] mc-err: secure: yes, access-type: read
[91408.406035] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc0e800, fsynr=0x380003, cbfrsynra=0xc05, cb=3
[91408.418818] mc-err: (255) csr_pcie1r: EMEM address decode error
[91408.425072] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[91408.433415] mc-err: secure: yes, access-type: read
[105016.145648] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc35800, fsynr=0xb0003, cbfrsynra=0x405, cb=3
[105016.161176] mc-err: (255) csr_pcie1r: EMEM address decode error
[105016.167673] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[105016.176012] mc-err: secure: yes, access-type: read
[127191.789243] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffa7c800, fsynr=0x380003, cbfrsynra=0x805, cb=3
[127191.801862] mc-err: Too many MC errors; throttling prints
[128514.770093] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffb8d000, fsynr=0x380003, cbfrsynra=0x405, cb=3
[128514.782797] mc-err: (255) csr_pcie1r: EMEM address decode error
[128514.789096] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[128514.797437] mc-err: secure: yes, access-type: read
[130278.768133] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffb48000, fsynr=0x380003, cbfrsynra=0x405, cb=3
[130278.780828] mc-err: (255) csr_pcie1r: EMEM address decode error
[130278.787237] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[130278.795587] mc-err: secure: yes, access-type: read
[163227.223593] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc95800, fsynr=0x380003, cbfrsynra=0x405, cb=3
[163227.236281] mc-err: (255) csr_pcie1r: EMEM address decode error
[163227.242599] mc-err: status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[163227.250932] mc-err: secure: yes, access-type: read
[179485.959015] tc358743 9-000f: tc358743_set_pll:
[179485.963541] tc358743 9-000f: tc358743_set_csi_color_space: YCbCr 422 16-bit
[179485.965044] tc358743 9-000f: tc358743_g_input_status: status = 0x0
[179485.965424] tc358743 9-000f: jc - FOUND signal and sync!
[179485.967390] tc358743 9-000f: tc358743_query_dv_timings: 1280x720p60.00 (1650x750)
[179485.986723] bwmgr API not supported
[179488.519417] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[179488.532364] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[179488.542569] (NULL device *): vi_capture_control_message: NULL VI channel received
[179488.550437] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[179488.561237] (NULL device *): vi_capture_control_message: NULL VI channel received
[179488.569066] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[179488.580044] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[179491.111393] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[179491.120642] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[179491.130570] (NULL device *): vi_capture_control_message: NULL VI channel received
[179491.138424] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[179491.149198] (NULL device *): vi_capture_control_message: NULL VI channel received
[179491.157133] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[179491.168082] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
Thank you
hello anomad,
you may review the checksum in the booting messages.
for example,
on r35.4.1/AGX-Orin, the checksum of default camera firmware is.
tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=6 sha1=8676d22a01443bdbc66581b7dde3b6d6828cc925
here’s checksum after you update camera firmware with deskew fix.
tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=6 sha1=73154acbae92fa621c3d5e1b2a6e10f1075059aa