While I was using the Jetson Orin with the out of the box set up I executed by mistake a “sudo rm -r *” command. I stopped right after entering it but the damage was already done.
After that point, the system stopped working and not even a restart would solve it. This brings me to the conclusion that some relevant system files must have been erased.
When restarting the Jetson Orin I get the message in the booting screen as shown in the following image.
Then, I tried to flash the the OS again using the SDK Manager but I am getting the same issues as other people has been facing in older posts. I tried running the command ./flash.sh but also failed. My issue is that there is no way I can access the Jetson Orin.
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 1.0
###############################################################################
# Target Board Information:
# Name: jetson-agx-orin-devkit, Board Family: t186ref, SoC: Tegra 234,
# OpMode: production, Boot Authentication: NS,
# Disk encryption: disabled ,
###############################################################################
copying emc_fuse_dev_params(/home/jgc/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/jgc/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/jgc/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/jgc/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --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" --cmd "dump eeprom cvm cvm.bin; dump custinfo custinfo_out.bin; reboot recovery"
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0074 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0080 ] File rcm_state open failed
[ 0.0083 ] ERROR: failed to read rcm_state
[ 0.0083 ]
[ 0.0091 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0093 ] Assuming zero filled SBK key
[ 0.0086 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[ 0.0135 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[ 0.0202 ] Parsing partition layout
[ 0.0210 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0223 ] Parsing partition layout
[ 0.0230 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0238 ] Creating list of images to be signed
[ 0.0245 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[ 0.0251 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0258 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0261 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0302 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0305 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0343 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0346 ] adding BCH for mb2_t234_aligned.bin
[ 0.0370 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0490 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0493 ] adding BCH for mb2_t234_aligned.bin
[ 0.0633 ] Generating signatures
[ 0.0641 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0643 ] Assuming zero filled SBK key
[ 0.0737 ] Warning: pub_key.key is not found
[ 0.0731 ] Parsing dev params for multi chains
[ 0.0781 ] Generating br-bct
[ 0.0788 ] Updating dev and MSS params in BR BCT
[ 0.0788 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.0797 ] Updating bl info
[ 0.0804 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.0810 ] WARNING: boot chain is not completed. set to 0
[ 0.0816 ] Get Signed section of bct
[ 0.0823 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.0830 ] Signing BCT
[ 0.0838 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0840 ] Assuming zero filled SBK key
[ 0.0861 ] Sha saved in br_bct_BR.sha
[ 0.0864 ] Warning: pub_key.key is not found
[ 0.0857 ] Updating BCT with signature
[ 0.0863 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.0869 ] Offset :4608 Len :3584
[ 0.0872 ] Generating SHA2 Hash
[ 0.0880 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.0881 ] Assuming zero filled SBK key
[ 0.0882 ] Assuming zero filled SBK key
[ 0.0902 ] Sha saved in br_bct_BR.sha
[ 0.0897 ] Updating BCT with SHA2 Hash
[ 0.0904 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.0910 ] Offset :4608 Len :3584
[ 0.0912 ] Offset :68 Len :8124
[ 0.0914 ] Generating coldboot mb1-bct
[ 0.0921 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.0927 ] MB1-BCT version: 0.9
[ 0.0938 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.0940 ] Added Platform Config 9 data with size :- 80
[ 0.0940 ]
[ 0.0940 ] Updating mb1-bct with firmware information
[ 0.0946 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.0963 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.0978 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.0985 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1000 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1002 ] Assuming zero filled SBK key
[ 0.1016 ] Warning: pub_key.key is not found
[ 0.1016 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1026 ] Generating recovery mb1-bct
[ 0.1032 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1039 ] MB1-BCT version: 0.9
[ 0.1049 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1051 ] Added Platform Config 9 data with size :- 80
[ 0.1051 ]
[ 0.1051 ] Updating mb1-bct with firmware information
[ 0.1058 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1073 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.1087 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.1093 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.1107 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1108 ] Assuming zero filled SBK key
[ 0.1121 ] Warning: pub_key.key is not found
[ 0.1121 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1132 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1132 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1132 ] Copying signatures
[ 0.1139 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1179 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1181 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1181 ] Boot Rom communication
[ 0.1188 ] 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
[ 0.1195 ] BR_CID: 0x80012344705DD5176C00000006FE0080
[ 0.2737 ] Sending bct_br
[ 0.4198 ] ERROR: might be timeout in USB write.
Error: Return value 3
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
Reading board information failed.
I also tried from the SDK and this is the following error I get when I use the Automatic Setup.
I all cases I was running the Jetson Orin in Recovery Mode pressing the reset button and while that pressing the restart and releasing both at the same time.
I don’t know what else can I try to flash it or to have the Orin working again.
I hope I have provided enough information to solve this issue.
I have similar situation as your, change port, change cable still “ERROR: might be timeout in USB write.”
I tried this and can flash, hope it may help you :
Hold Recovery button, plug in your TypeC cable to an USB2 port
Plugin power, it may boot your Orin, if not press Power to boot it. Check lsusb if see 7023 device
Here is the step i done after the above two steps still failed . Hold the Recovery button and press Reset, keep holding Recovery button for maybe 3s. Then try again, this help me flash my Orin AGX devkit
Could you provide the full flash log and serial console log at the same time for further check?
We found some users getting this issue (timeout in USB write) with Ubuntu 20.04. Some users could resolve with newer kernel version (5.15.0 as you updated), but some users not.
This release (Ubuntu 20.04) should be available for flashing the board with Jetpack 5.0.2.
We could not reproduce this issue at our side and still figure out if it might relate to the specific USB driver of host PC.
Do you have other host PC (different brand/vendor) with Ubuntu 20.04?
I have shared all the possible logs that I could find.
Inside the company we all have DELL computers, but in the next days I should get a new PC from a different brand which I will try. It will come with Ubuntu20.04 as well but hopefully it will not be a problem. If not Next step will be to build a PC with Ubuntu18.04.
I managed to get a spare PC and install Ubuntu 18.04 in it.
After flashing the JetPack on the orin I could see that some packages were skipped as you can see in he attached image. Is this normal or they should have been installed?
After flash the Jetson reboots. Once first boot account setup is complete those extra packages are flashed via ssh over the network. The message you are seeing suggests the network is not configured correctly and networking does not succeed. I don’t know if this is a misleading message or not, but network failure would account for the packages not reaching the Jetson.
That default address of 192.168.55.1 is via a virtual ethernet device. The recovery mode Jetson does not have this, but after flash and reboot, the USB cable provides a virtual network device with a DHCP server. That device creates address 192.168.55.100 on the host PC, and address 192.168.55.1 on the Jetson (thus the default in the GUI). In theory the host PC could:
ping 192.168.55.1 (to ping the Jetson)
ping 192.168.55.100 (to ping itself)
And the Jetson could:
ping 192.168.55.1 (to ping itself)
ping 192.168.55.100 (to ping the host PC)
Ping could be replaced by ssh. However, this only works if:
The Jetson rebooted to provide the virtual device.
The Jetson’s first boot account setup completed (to give an admin login).
The PC accepts this device, allowing configuration.
The PC is not firewalled against this.
Most of the time those requirements work without issue. I’ve not seen the error message you mention though. It makes me think there might be more than one device at address 192.168.55.1. If the Jetson has wired ethernet attached to the same switch/router that the host PC has, then you could use that address instead of 192.168.55.1 (and it’d even be faster if it is gigabit).
Do note that you can run sdkmanager again, deselect flash, and deselect adding host PC components. And then just attempt install of the other components without flashing. Can you log in to the Jetson, and see what it says from:
