Jetson Nano corrupted bootloader and won't show up on SDK Manager

For context, I’m currently working on a uni project, in which we’re using 3 Jetson Nanos (4gb devkits b01) in 3 Jetbots. Because one of them wasn’t working properly due to some software problems, I decided to clone the SDCard that was in one of the working Jetsons, over to the SDCard of the non-working one. And this worked perfectly, the old, non-working jetson, was now functional.

The problems started when I tried to place the SDCard back on the working jetson, which would now not boot, and just show the green power LED. The problem is not from the SDCard, or so I think, since they both work on the previously non-working jetson.

I tried using SDK Manager, like suggested in some other topics, but the jetson doesn’t show up no matter what I do, even when placed into recovery mode by shorting the sys res pin. I don’t think it’s a problem with SDK Manager, since it detects the other 2 jetsons just fine.

To better understand what was happening, I tried reading the output from the UART pins and got this as the ouput, suggesting the bootloader is corrupted:

[0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.130] Processing in cold boot mode Bootloader 2
[0000.135] A02 Bootrom Patch rev = 1023
[0000.138] Power-up reason: pmc por
[0000.141] No Battery Present
[0000.144] pmic max77620 reset reason
[0000.147] pmic max77620 NVERC : 0x40
[0000.151] RamCode = 0
[0000.153] Platform has DDR4 type RAM
[0000.156] max77620 disabling SD1 Remote Sense
[0000.161] Setting DDR voltage to 1125mv
[0000.165] Serial Number of Pmic Max77663: 0xf1f45
[0000.172] Entering ramdump check
[0000.175] Get RamDumpCarveOut = 0x0
[0000.178] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.184] Last reboot was clean, booting normally!
[0000.188] Sdram initialization is successful
[0000.192] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.198] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.204] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.210] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.216] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.222] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.233] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.256] Platform-DebugCarveout: 0
[0000.259] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.265] Non secure mode, and RB not enabled.
[0000.269] BoardID = 3448, SKU = 0x0
[0000.272] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.276] Nano-SD: checking PT table on QSPI …
[0000.280] Read PT from (2:0)
[0000.296] Using BFS PT to query partitions
[0000.301] Loading Tboot-CPU binary
[0000.330] Verifying TBC in OdmNonSecureSBK mode
[0000.341] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.348] Bootloader downloaded successfully.
[0000.352] Downloaded Tboot-CPU binary to 0xa0000258
[0000.357] MAX77620_GPIO5 configured
[0000.360] CPU power rail is up
[0000.363] CPU clock enabled
[0000.367] Performing RAM repair
[0000.370] Updating A64 Warmreset Address to 0xa00002e9
[0000.375] BoardID = 3448, SKU = 0x0
[0000.378] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.382] Nano-SD: checking PT table on QSPI …
[0000.387] Loading NvTbootBootloaderDTB
[0000.453] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.524] Bootloader DTB Load Address: 0x83000000
[0000.529] BoardID = 3448, SKU = 0x0
[0000.532] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.536] Nano-SD: checking PT table on QSPI …
[0000.541] Loading NvTbootKernelDTB
[0000.607] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.680] Kernel DTB Load Address: 0x83100000
[0000.684] BoardID = 3448, SKU = 0x0
[0000.687] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.691] Nano-SD: checking PT table on QSPI …
[0000.697] Loading cboot binary
[0000.813] Verifying EBT in OdmNonSecureSBK mode
[0000.855] Bootloader is corrupted!
[0000.858] Error in NvTbootLoadBinary: 0x14 !
[0000.862] BoardID = 3448, SKU = 0x0
[0000.865] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.869] Nano-SD: checking PT table on QSPI …
[0000.874] PT: Partition RBL NOT found !
[0000.877] Warning: Find Partition via PT Failed
[0000.882] Error is 1

What can I do to try to fix this?

Hi,
This issue appears to be similar to the one described in the documentation. Regarding the SDK Manager, ensure it is installed on a physical machine running Ubuntu 18.04 (Not 20.04), rather than on a virtual machine (e.g., VirtualBox, VMware, or WSL).
To verify if the host detects the Jetson Nano, use the lsusb command. When connected normally, you should see something like:

Bus 001 Device 017: ID 0955:7020 NVIDIA Corp. L4T (Linux for Tegra) running on Tegra

After putting the device in recovery mode, the output should resemble:

Bus 001 Device 015: ID 0955:7f21 NVIDIA Corp. APX

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