Hey I’ve got an AGX Orin dev kit. I’ve been using it for development successfully for many weeks. Recently however, it will no longer boot. When powered on, the power light will turn on but the display receives no image, and the keyboard does nothing. No other variables have changed.
It’s encouraging that the UART serial port still works. Here’s an excerpt from the logs during power on:
In my troubleshooting, I went to re-flash the image in recovery mode. Unfortunately, that’s broken too. My host is a clean install of Ubuntu 20.04.5. I’m using sdkmanager to flash Jetpack 5.0.2 (Rev. 1) in manual mode. It fails really quickly, with the following log excerpt:
15:37:27 ERROR: Flash Jetson AGX Orin - flash: [ 0.1556 ] ERROR: might be timeout in USB write.
15:37:27 INFO: Flash Jetson AGX Orin - 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
15:37:27 ERROR: Flash Jetson AGX Orin - flash: --- Error: Reading board information failed.
15:37:27 ERROR: Flash Jetson AGX Orin - flash: command terminated with error
15:37:27 SUMMARY: DateTime Target Setup - target: Depends on failed component
Thanks for the quick response. I have not used sdkmanager to flash this Orin before. I’ve been using the Orin as it was shipped, and I installed the SDKs I needed manually. I only busted out sdkmanager as a troubleshooting step because my box stopped booting.
I ran the flash.sh script manually as requested. Here’s an excerpt from the output:
[ 0.1631 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1634 ] Added Platform Config 9 data with size :- 80
[ 0.1634 ]
[ 0.1634 ] Updating mb1-bct with firmware information
[ 0.1650 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1688 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.1721 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.1736 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.1753 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1756 ] Assuming zero filled SBK key
[ 0.1782 ] Warning: pub_key.key is not found
[ 0.1795 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1818 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1818 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1819 ] Copying signatures
[ 0.1834 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1920 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1923 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1923 ] Boot Rom communication
[ 0.1937 ] 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.1951 ] BR_CID: 0x80012344705DD5C72800000009018280
[ 0.2239 ] Sending bct_br
[ 0.2671 ] 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 did try various configurations of USB cables and hubs, including using the cable that came in the box.
My host machine is a fresh install. I can certainly try downgrading to ubuntu 18.04, but I would like to know what troubleshooting step you are hoping to accomplish with that. From my perspective the problems flashing are secondary to the fact that the machine won’t boot.
Maybe we can first focus on the meaning of the UART messages? Specifically, I’d like to know what this section means:
The log does not provide much help because the UEFI log is in silent mode. To enable full log, you need to rebuild the UEFI from the website and then reflash the UEFI debug binary to your board.
However, if you understand above comment, you shall know that problem is back to the issue that you cannot flash your jetson with current host…
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
Could you also share the serial console log when you got flash error?