I’m having the issue of not being able to see anything on my xavier nx.
The jetson was booted up and was being worked on through ssh since I enabled that to work during boot rather than login. Everything was running fine and then all of a sudden the ssh connection disconnected. The ssh connection wouldn’t come back so I plugged in hdmi with a monitor and what popped up was a black screen with a small nvidia logo. I then power cycled the xavier and it outputted a blank black display so I waited a bit and it still stayed on that. I then disconnected both the hdmi and the power and then reconnected them both and then it it said there was no hdmi connection found. I am on an almost brand new xavier nx.
I then took the sd card of the xavier nx and plugged it into my jetson nano. This resulted in the jetson powering on but it didn’t boot correctly which is expected, but it still did display to the monitor. I then put the sd card back into the xavier and it had the same no hdmi connection found error.
When I boot my nano without any sd card it outputs a white screen with an nvidia logo. When I boot my xavier without any sd card it just says no hdmi connection found again.
Any ideas as to what is happening or any solutions? My next step is to reflash the xavier sd card but I would prefer to avoid that if possible.
Thanks!
Dumping the log will tell more detail.
This is the serial dump.
[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Chip revision : A02P
[0000.044] I> Bootrom patch version : 15 (correctly patched)
[0000.049] I> ATE fuse revision : 0x200
[0000.053] I> Ram repair fuse : 0x0
[0000.056] I> Ram Code : 0x0
[0000.058] I> rst_source : 0x0
[0000.061] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.067] I> Qspi flash params source = brbct
[0000.071] I> Qspi using bpmp-dma
[0000.074] I> Qspi clock source : pllp
[0000.078] I> QSPI Flash Size = 32 MB
[0000.081] I> Qspi initialized successfully
[0000.085] I> Active Boot chain : 0
[0000.088] I> Boot-device: QSPI
[0000.091] I> Qspi flash params source = brbct
[0000.097] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.105] I> Temperature = 25000
[0000.108] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.112] W> Skipping boost for clk: BPMP_APB
[0000.116] W> Skipping boost for clk: AXI_CBB
[0000.120] W> Skipping boost for clk: AON_CPU_NIC
[0000.124] W> Skipping boost for clk: CAN1
[0000.128] W> Skipping boost for clk: CAN2
[0000.132] I> Boot-device: QSPI
[0000.135] I> Boot-device: QSPI
[0000.138] I> Qspi flash params source = mb1bct
[0000.142] I> Qspi using bpmp-dma
[0000.145] I> Qspi clock source : pllc_out0
[0000.149] I> Qspi reinitialized
[0000.152] I> Qspi flash params source = mb1bct
[0000.157] I> ECC region[0]: Start:0x0, End:0x0
[0000.161] I> ECC region[1]: Start:0x0, End:0x0
[0000.165] I> ECC region[2]: Start:0x0, End:0x0
[0000.170] I> ECC region[3]: Start:0x0, End:0x0
[0000.174] I> ECC region[4]: Start:0x0, End:0x0
[0000.178] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.184] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.188] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.192] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.197] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.202] E> FAILED: Thermal config
[0000.210] E> FAILED: MEMIO rail config
[0000.219] E> Task 50 failed (err: 0x7979061c)
[0000.223] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reason: 0x1c, aux_info: 0x06
[0000.232] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
0000000000011111111110111111111111111111111100111110000000000000000000000000000000000000000000000000000000000000000000000000000011011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0000.262] I> Reset to recovery mode
Weird, the board enter the recovery mode by itself.
Do you have other xavier NX module or carrier board that can do a comparison here? For example, switch the module to other carrier board and see if issue is still.
Also, what will be printed if you jumper the reset pin when you see this log? Will the reboot log also says it enters the recovery mode?
I don’t have another module or carrier board. I tried the jumper reset pin and the log shows the exact same output. Should I reflash my module? Thanks.
If you don’t want the data on your sd card is gone, I would suggest you can
-
Find another fresh sdcard
-
Plug this sdcard to jetson NX
-
Use sdkamnager to flash his fresh sdcard
-
Check if the board can work or not
-
Move out this second sdcard and plug your original sdcard back
-
Check if the board can work or not.
Please note that sdkamanger is required here and it cannot be replaced by sdcard image.
Sdcard image is not really “flashing” anything on the board.
Ok I will go ahead and flash my SDCard using the sdkmanager. Just curious, why does the sd card image method not work? Thanks!
There is a QSPI device on jetson NX and jetson Nano. This device includes some bootloader binaries.
When you replace the jetpack version on sdcard image, what you changed is only on sdcard.
The version on QSPI does not get upgrade/updated. For example, if you always use sdcard image but never try sdkmanager, then no matter what you’ve installed to your card, the bootloader on your NX QSPI is always that one flashed in factory. We don’t guarantee the version from the factory. Maybe it is from jetpack4.2.2, jetpack4.3 or 4.4.1.
Theoretically, even old bootloader shall work with new kernel from sdcard image. However, if the software on QSPI is corrupted, then replacing sdcard will not bring it back.
But just remember that this is just a try from software. I also asked to switch the board too because we cannot guarantee if this is a hardware defect.
Oh that makes a lot of sense, thanks! I’ll let you know my results once I get to it.
1 Like
I am connecting to the xavier nx using microusb to usb and my sdkmanager says no device connected. Does the IO work in the current state of the jetson?
Edit: Due to a faulty microUSB cable. This is no longer a problem.
1 Like
Ok i tried flashing using the sdkmanager and it results in an error with both automatic and manual installs. The error I recieve is the following for the last few lines.
23:21:22 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.6785 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_coldboot_sigheader.bct.encrypt mem_coldboot_sigheader.bct.hash zerosbk
23:21:22 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.6820 ] tegrabct_v2 --chip 0x19 0 --sdram /home/vatsal/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_XAVIER_NX_DEVKIT/Linux_for_Tegra/bootloader/20225/tmpltq3x4ou1.cfg --membct /home/vatsal/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_XAVIER_NX_DEVKIT/Linux_for_Tegra/bootloader/20225/tmpltq3x4ou1_1.bct /home/vatsal/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_XAVIER_NX_DEVKIT/Linux_for_Tegra/bootloader/20225/tmpltq3x4ou1_2.bct /home/vatsal/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_XAVIER_NX_DEVKIT/Linux_for_Tegra/bootloader/20225/tmpltq3x4ou1_3.bct /home/vatsal/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_XAVIER_NX_DEVKIT/Linux_for_Tegra/bootloader/20225/tmpltq3x4ou1_4.bct
23:21:23 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.7191 ] Packing sdram param for instance[1]
23:21:23 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.8024 ] tegrahost_v2 --chip 0x19 --align mem_rcm.bct
23:21:23 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.8047 ] adding BCH for mem_rcm.bct
23:21:23 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.8099 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_rcm_sigheader.bct.encrypt mem_rcm_sigheader.bct.hash zerosbk
23:21:26 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 4.8126 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
23:21:26 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 8.2090 ] RCM version 0X190001
23:21:27 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 8.2094 ] Boot Rom communication completed
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 10.2298 ] tegrarcm_v2 --isapplet
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 10.2466 ] Sending bct_mb1
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 10.2510 ] [...] 100%
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 10.2553 ] Sending bct_mem
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ 10.3027 ] [...] 100%
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: Command tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem mem_rcm_sigheader.bct.encrypt
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: Failed flashing t186ref.
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [ Component Install Finished with Error ]
23:21:28 INFO: Flash Jetson Xavier NX (Devkit) - flash: [host] [ 668.00 KB used. Disk Avail: 845.38 GB ]
23:21:28 ERROR: Flash Jetson Xavier NX (Devkit) - flash: command terminated with error
23:21:30 SUMMARY: NVIDIA Nsight Systems - target: Depends on failed component
During the flash is doing, the uart connected on jetson NX should dump some log too.
Could you share those logs too so that we can know why flash got stuck?
Sure thing.
[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Chip revision : A02P
[0000.044] I> Bootrom patch version : 15 (correctly patched)
[0000.049] I> ATE fuse revision : 0x200
[0000.053] I> Ram repair fuse : 0x0
[0000.056] I> Ram Code : 0x0
[0000.058] I> rst_source : 0x0
[0000.061] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.067] I> Qspi flash params source = brbct
[0000.071] I> Qspi using bpmp-dma
[0000.074] I> Qspi clock source : pllp
[0000.078] I> QSPI Flash Size = 32 MB
[0000.081] I> Qspi initialized successfully
[0000.085] I> Active Boot chain : 0
[0000.088] I> Boot-device: QSPI
[0000.091] I> Qspi flash params source = brbct
[0000.097] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.105] I> Temperature = 31000
[0000.108] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.112] W> Skipping boost for clk: BPMP_APB
[0000.116] W> Skipping boost for clk: AXI_CBB
[0000.120] W> Skipping boost for clk: AON_CPU_NIC
[0000.124] W> Skipping boost for clk: CAN1
[0000.128] W> Skipping boost for clk: CAN2
[0000.132] I> Boot-device: QSPI
[0000.135] I> Boot-device: QSPI
[0000.138] I> Qspi flash params source = mb1bct
[0000.142] I> Qspi using bpmp-dma
[0000.145] I> Qspi clock source : pllc_out0
[0000.149] I> Qspi reinitialized
[0000.152] I> Qspi flash params source = mb1bct
[0000.157] I> ECC region[0]: Start:0x0, End:0x0
[0000.161] I> ECC region[1]: Start:0x0, End:0x0
[0000.165] I> ECC region[2]: Start:0x0, End:0x0
[0000.170] I> ECC region[3]: Start:0x0, End:0x0
[0000.174] I> ECC region[4]: Start:0x0, End:0x0
[0000.178] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.184] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.188] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.192] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.197] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.202] E> FAILED: Thermal config
[0000.210] E> FAILED: MEMIO rail config
[0000.219] E> Task 50 failed (err: 0x7979061c)
[0000.223] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reason: 0x1c, aux_info: 0x06
[0000.232] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
0000000000011111111110111111111111111111111100111110000000000000000000000000000000000000000000000000000000000000000000000000000011011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0000.262] I> Reset to recovery mode
⸮⸮
[0375.786] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0375.794] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0375.800] I> Boot-mode: Platform RCM
[0375.803] I> Chip revision : A02P
[0375.806] I> Bootrom patch version : 15 (correctly patched)
[0375.811] I> ATE fuse revision : 0x200
[0375.815] I> Ram repair fuse : 0x0
[0375.818] I> Ram Code : 0x0
[0375.821] I> rst_source : 0xb
[0375.823] I> rst_level : 0x1
[0375.827] I> USB configuration success
[0377.852] I> mb2 image downloaded
[0377.860] I> Recovery boot mode 0
[0377.864] I> Boot-device: QSPI
[0377.869] I> UPHY full init done
[0377.873] I> MB1 done
[0377.878] W> Profiler not initialized
[0377.882] I> Welcome to MB2(TBoot-BPMP) Applet (version: 00.00.2018.32-mobile-e677d209)
[0377.890] W> Profiler not initialized
[0377.893] I> DMA Heap @ [0x40020000 - 0x40065800]
[0377.898] I> Default Heap @ [0xd486400 - 0xd48a400]
[0377.903] W> Profiler not initialized
[0377.906] W> Profiler not initialized
[0377.910] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0377.915] W> device prod register failed
[0377.919] W> Profiler not initialized
[0377.923] E> Error in command_complete 18000 int_status
[0377.929] E> OCR failed, error = f0f0706
[0377.932] I> SDMMC is not present.
[0377.936] I> QSPI Flash Size = 32 MB
[0377.944] I> Qspi initialized successfully
[0377.996] E> Link startup dme_set failed
[0377.999] E> UFS initialization failed
[0378.003] I> UFS is not present
[0378.006] W> Profiler not initialized
[0378.011] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0378.017] W> Profiler not initialized
[0378.020] W> Profiler not initialized
[0378.024] W> Profiler not initialized
[0378.027] I> Entering 3p server
[0378.031] I> USB configuration success
[0378.904] I> Populate chip info
[0378.916] I> Populate eeprom info
[0378.920] I> Populate eeprom info for module cvm
[0378.963] I> Rebooting : reboot-recovery
[037⸮⸮
[0002.320] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0002.329] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0002.334] I> Boot-mode: Platform RCM
[0002.337] I> Chip revision : A02P
[0002.340] I> Bootrom patch version : 15 (correctly patched)
[0002.346] I> ATE fuse revision : 0x200
[0002.349] I> Ram repair fuse : 0x0
[0002.352] I> Ram Code : 0x0
[0002.355] I> rst_source : 0xb
[0002.357] I> rst_level : 0x1
[0002.361] I> USB configuration success
[0004.367] I> mb2 image downloaded
[0004.377] I> Recovery boot mode 0
[0004.381] I> Boot-device: QSPI
[0004.385] I> UPHY full init done
[0004.390] I> MB1 done
[0004.394] W> Profiler not initialized
[0004.398] I> Welcome to MB2(TBoot-BPMP) Applet (version: 00.00.2018.32-mobile-e677d209)
[0004.406] W> Profiler not initialized
[0004.409] I> DMA Heap @ [0x40020000 - 0x40065800]
[0004.414] I> Default Heap @ [0xd486400 - 0xd48a400]
[0004.419] W> Profiler not initialized
[0004.422] W> Profiler not initialized
[0004.426] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0004.431] W> device prod register failed
[0004.435] W> Profiler not initialized
[0004.439] E> Error in command_complete 18000 int_status
[0004.445] E> OCR failed, error = f0f0706
[0004.448] I> SDMMC is not present.
[0004.452] I> QSPI Flash Size = 32 MB
[0004.460] I> Qspi initialized successfully
[0004.512] E> Link startup dme_set failed
[0004.515] E> UFS initialization failed
[0004.519] I> UFS is not present
[0004.522] W> Profiler not initialized
[0004.527] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0004.533] W> Profiler not initialized
[0004.536] W> Profiler not initialized
[0004.540] W> Profiler not initialized
[0004.543] I> Entering 3p server
[0004.547] I> USB configuration success
[0005.421] I> Populate chip info
[0005.433] I> Populate eeprom info
[0005.437] I> Populate eeprom info for module cvm
[0005.484] I> Rebooting : reboot-recovery
[000⸮⸮
[0393.236] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0393.244] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0393.250] I> Boot-mode: RCM
[0393.252] I> Chip revision : A02P
[0393.255] I> Bootrom patch version : 15 (correctly patched)
[0393.260] I> ATE fuse revision : 0x200
[0393.264] I> Ram repair fuse : 0x0
[0393.267] I> Ram Code : 0x0
[0393.270] I> rst_source : 0xb
[0393.272] I> rst_level : 0x1
[0393.276] I> USB configuration success
[0395.251] I> bct_bootrom image downloaded
[0395.260] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0395.267] I> Temperature = 40000
[0395.270] W> Skipping boost for clk: BPMP_CPU_NIC
[0395.274] W> Skipping boost for clk: BPMP_APB
[0395.278] W> Skipping boost for clk: AXI_CBB
[0395.282] W> Skipping boost for clk: AON_CPU_NIC
[0395.286] W> Skipping boost for clk: CAN1
[0395.290] W> Skipping boost for clk: CAN2
[0395.295] I> Boot-device: QSPI
[0395.297] I> Boot-device: QSPI
[0395.300] I> Qspi flash params source = mb1bct
[0395.304] I> bct_mb1 image downloaded
[0395.314] I> ECC region[0]: Start:0x0, End:0x0
[0395.318] I> ECC region[1]: Start:0x0, End:0x0
[0395.322] I> ECC region[2]: Start:0x0, End:0x0
[0395.326] I> ECC region[3]: Start:0x0, End:0x0
[0395.331] I> ECC region[4]: Start:0x0, End:0x0
[0395.335] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0395.341] I> Non-ECC region[1]: Start:0x0, End:0x0
[0395.345] I> Non-ECC region[2]: Start:0x0, End:0x0
[0395.349] I> Non-ECC region[3]: Start:0x0, End:0x0
[0395.354] I> Non-ECC region[4]: Start:0x0, End:0x0
[0395.360] E> FAILED: Thermal config
[0395.368] E> FAILED: MEMIO rail config
[0395.377] E> Task 50 failed (err: 0x7979061c)
[0395.381] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reason: 0x1c, aux_info: 0x06
[0395.390] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
0000000000011111111110000111111111111110011000111110000000000000000000000000000000000000000000000000000000000000000000000000000011001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0395.420] I> Reset to recovery mode
Looks like a hardware issue. If this is nv devkit, please file a RMA request.