Failed to Flash Jetson Orin NX ERROR: failed to read rcm_state

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

I have a new Jetson Orin devkit, and I am trying to flash it for the first time using windows WSL, Ubuntu 20.04, flashing jetpack6.0 (rev2) to EMMC however even tho everything is connected and seems to be working fine, it just won’t flash showing error 21:30:19 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.however looking at the logs show this error ERROR: failed to read rcm_state or JETSON_ORIN_NX_TARGETS - error code is: 1011
orinNX error log.txt (38.1 KB)
so now looking on the forum I can find this is associated to not having the correct base board, but I have the Orin NX devkit? So I’m confused and need some help trying to resolve this - attached is the end of error log


21:30:09.213 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: *** Reading EEPROM ... 
21:30:09.215 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: "/home/rob/nvidia/nvidia_sdk/JetPack_6.0_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py" --chip 0x23 --applet "/home/rob/nvidia/nvidia_sdk/JetPack_6.0_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins "mb2_applet applet_t234.bin" --skipuid --cmd "dump eeprom cvm cvm.bin; reboot recovery" 
21:30:09.215 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: 
21:30:09.271 - error: Failed to validate GA4 event. Validation errors: [{"fieldPath":"measurement_id","description":"Unable to find non-empty parameter [measurement_id] value in request.","validationCode":"VALUE_REQUIRED"},{"fieldPath":"firebase_app_id","description":"Unable to find non-empty parameter [firebase_app_id] value in request.","validationCode":"VALUE_REQUIRED"}]
21:30:09.285 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Welcome to Tegra Flash
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: version 1.0.0
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Type ? or help for help and q or quit to exit
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Use ! to execute system commands
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS:  
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.0336 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.0341 ] File rcm_state open failed
21:30:09.286 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.0341 ] ERROR: failed to read rcm_state
21:30:09.286 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [   0.0341 ] ERROR: failed to read rcm_state
21:30:09.286 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.0341 ]
1 Like
3 
21:30:09.344 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1017 ] S
21:30:09.344 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: ending bct_br
21:30:09.344 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: 
21:30:19.446 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1017 ] E
21:30:19.447 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: RROR: might be timeout in USB write.
21:30:19.447 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: 
21:30:19.451 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Error: Return value 3
21:30:19.451 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: Error: Return value 3
4

Hi DaveYYY

Thanks for the advice, however it has not worked unfortunately i tried many ways to see if it was USB autosuspend, but it seems the WSL environment restricts access to modifying the kernel parameters directly, so I don’t know what I can do in this situation apart from getting a dedicated Linux computer, I thought usbipd auto-attach was the fix for usb autosuspend?

01:51:27 INFO: Flash Jetson Linux - flash: RROR: might be timeout in USB write.
01:51:27 ERROR: Flash Jetson Linux - flash: Error: Return value 3
01:51:27 INFO: Flash Jetson Linux - flash: Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
01:51:27 ERROR: Flash Jetson Linux - flash: --- Error: Reading board information failed.
01:51:27 ERROR: Flash Jetson Linux - flash: *** ERROR: Parsing boardid failed
01:51:27 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.rob.sh; [error]: *** ERROR: Parsing boardid failed
01:51:27 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
01:51:27 INFO: Flash Jetson Linux - flash: [host] [ Disk Avail on Partition : 0.00 B ]
01:51:27 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 11s ]
01:51:27 ERROR: Flash Jetson Linux - flash: command terminated with error
01:51:27 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.
5

YES, drivers on WSL somehow does not support this option, so please avoid using WSL if you keep hitting this issue.

1 Like
6

cool thanks for your help

8

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