Boot failure Nano B01 -> no USB/HDMI

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
,
1

Hi all. Me and my daughter are assembling a Jetbot, based on the B01 developer board. While trying to initialize the board we’ve run in to a problem getting it to boot.

System is currently powered by a MW powersupply, rated 5V at 4A.

Have tried to jumper pins 9 and 10 on J50, to no avail.

I’ve tried multiple sd-cards and multiple images (jetbot images ranging from 4.4.1 to 4.5) and also vanilla jetpack 4.5 and 4.6. All give similar results :

  1. Nano is undetectable on USB (both Win10 and Ubuntu 18.04 bare metal installation).
  2. Serial USB output shows boot failure
  3. No output on HDMI (tried multiple screens and cables)
[0000.163] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.168] Processing in cold boot mode Bootloader 2
[0000.173] A02 Bootrom Patch rev = 1023
[0000.177] Power-up reason: pmc por
[0000.180] No Battery Present
[0000.182] pmic max77620 reset reason
[0000.186] pmic max77620 NVERC : 0x6f
[0000.189] RamCode = 0
[0000.191] Platform has DDR4 type RAM
[0000.195] max77620 disabling SD1 Remote Sense
[0000.199] Setting DDR voltage to 1125mv
[0000.203] Serial Number of Pmic Max77663: 0xd10ac
[0000.210] Entering ramdump check
[0000.213] Get RamDumpCarveOut = 0x0
[0000.217] RamDumpCarveOut=0x0,  RamDumperFlag=0xe59ff3f8
[0000.222] Last reboot was clean, booting normally!
[0000.226] Sdram initialization is successful
[0000.231] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.237] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.242] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.248] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.254] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.260] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.266] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.272] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.288] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.294] Platform-DebugCarveout: 0
[0000.297] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.303] Non secure mode, and RB not enabled.
[0000.307] BoardID = 3448, SKU = 0x0
[0000.311] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.314] Nano-SD: checking PT table on QSPI ...
[0000.319] Read PT from (2:0)
[0000.334] Using BFS PT to query partitions
[0000.338] PT: Partition TBC NOT found !
[0000.342] Warning: Find Partition via PT Failed
[0000.346] BoardID = 3448, SKU = 0x0
[0000.349] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.353] Nano-SD: checking PT table on QSPI ...
[0000.358] PT: Partition TBC NOT found !
[0000.361] Warning: Find Partition via PT Failed
[0000.366] Error is 1

Any ideas on how to fix this without being able to get the USB connection up and running?

2

You need put device into recovery mode and then use sdkmanager + your ubuntu 18.04 host to reflash this board.

Keep changing the sdcard won’t resolve this problem.

3

Faulty jumper on 9 and 10, tried another on and that seems to have done the trick. SDK Manager has detected the board now and is running!

4

SDK Manager stalls sadly enough :

11:17:06 INFO: Flash Jetson Nano - flash: [ 1.0702 ] Applet version 00.01.0000
11:17:06 INFO: Flash Jetson Nano - flash: [ 1.1521 ] tegrarcm --reboot recovery
11:17:06 INFO: Flash Jetson Nano - flash: [ 1.1533 ] Applet version 00.01.0000
11:17:08 INFO: Flash Jetson Nano - flash: [ 1.1559 ]
11:17:08 ERROR: Flash Jetson Nano - flash: Board ID(3448) version(401)
11:17:08 INFO: Flash Jetson Nano - flash: copying bctfile(/home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/t210ref/BCT/P3448_A00_lpddr4_204Mhz_P987.cfg)... done.
11:17:08 INFO: Flash Jetson Nano - flash: copying bootloader(/home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/t210ref/cboot.bin)... done.
11:17:08 INFO: Flash Jetson Nano - flash: copying initrd(/home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/l4t_initrd.img)... done.
11:17:08 INFO: Flash Jetson Nano - flash: Making Boot image... done.
11:17:08 INFO: Flash Jetson Nano - flash: Existing sosfile(/home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/nvtboot_recovery.bin) reused.
11:17:08 INFO: Flash Jetson Nano - flash: copying wb0boot(/home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/t210ref/warmboot.bin)... done.
11:17:08 INFO: Flash Jetson Nano - flash: Copying nv_boot_control.conf to rootfs
11:17:08 INFO: Flash Jetson Nano - flash: populating kernel to rootfs... done.
11:17:08 INFO: Flash Jetson Nano - flash: Making system.img...
11:17:17 INFO: Flash Jetson Nano - flash: populating rootfs from /home/eric/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/rootfs ... populating /boot/extlinux/extlinux.conf ... done.
11:17:22 INFO: Flash Jetson Nano - flash: Sync'ing system.img ... done.
11:17:30 INFO: Flash Jetson Nano - flash: system.img built successfully.
11:17:30 ERROR: Flash Jetson Nano - flash: command terminated with error
11:17:30 SUMMARY: DateTime Target Setup - target: Depends on failed component
11:19:33 SUMMARY: NVIDIA Nsight Systems - host: Install completed successfully.
11:19:51 SUMMARY: Drivers for Jetson - target_image: Install completed successfully.
11:22:31 SUMMARY: DateTime Target Setup - target: Depends on failed component
11:24:13 SUMMARY: NVIDIA Nsight Systems - host: Install completed successfully.
11:24:32 SUMMARY: Drivers for Jetson - target_image: Install completed successfully.
11:27:15 SUMMARY: DateTime Target Setup - target: Depends on failed component
5

please share the full log. There is a export log button on your sdkmanager GUI.

1 Like
6

SDKM_logs_JetPack_4.6_(rev.1)_Linux_for_Jetson_Nano_modules_2021-09-20_11-27-43.zip (249.4 KB)

7

Please run sudo apt-get install libxml2-utils on your host and then run sdkmanager to flash again.

8

Thanks. Faulty jumper and a missing package seem to have been the issues. Perhaps include install command for that package in the script for next release?

9

Yes, we already noticed this issue. SDKM will try to enhance this.