My Jetson Nano, which I have been using for about 6 months, has stopped running.
The operation when the power is turned on is as follows.
1.The green LED lights up and turns off after one second.
2.I have it connected to the display, but there is no signal.
Before this happened, I updated Jetpack to 4.6.
However, I don’t know if this is a direct cause or a physical failure.
I would appreciate it if someone could tell me what is going on and how to investigate the cause.
In this case, IMO, the best way you do is using debug console.
And post the logs here again.
Thanks for letting me know.
I don’t have a cable at hand right now, so I can’t get a log of the serial debugging console, but I will post the log when I get it.
I was able to get the logs from the console.
The log is pasted below.
[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: 0x150ff0
[0000.172] Entering ramdump check
[0000.175] Get RamDumpCarveOut = 0x0
[0000.179] 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.199] 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.234] 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.281] Read PT from (2:0)
[0000.296] Using BFS PT to query partitions
[0000.302] Loading Tboot-CPU binary
[0000.330] Verifying TBC in OdmNonSecureSBK mode
[0000.340] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.347] Bootloader downloaded successfully.
[0000.351] Downloaded Tboot-CPU binary to 0xa0000258
[0000.356] MAX77620_GPIO5 configured
[0000.359] CPU power rail is up
[0000.362] CPU clock enabled
[0000.366] Performing RAM repair
[0000.369] Updating A64 Warmreset Address to 0xa00002e9
[0000.374] BoardID = 3448, SKU = 0x0
[0000.377] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.381] Nano-SD: checking PT table on QSPI …
[0000.385] Loading NvTbootBootloaderDTB
[0000.452] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.523] Bootloader DTB Load Address: 0x83000000
[0000.528] BoardID = 3448, SKU = 0x0
[0000.531] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.535] Nano-SD: checking PT table on QSPI …
[0000.540] Loading NvTbootKernelDTB
[0000.606] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.679] Kernel DTB Load Address: 0x83100000
[0000.683] BoardID = 3448, SKU = 0x0
[0000.686] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.690] Nano-SD: checking PT table on QSPI …
[0000.696] Loading cboot binary
[0000.812] Verifying EBT in OdmNonSecureSBK mode
[0000.854] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.861] Bootloader downloaded successfully.
[0000.865] BoardID = 3448, SKU = 0x0
[0000.868] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.872] Nano-SD: checking PT table on QSPI …
[0000.876] PT: Partition NCT NOT found !
[0000.880] Warning: Find Partition via PT Failed
[0000.884] Next binary entry address: 0x92c00258
[0000.889] BoardId: 3448
[0000.893] Overriding pmu board id with proc board id
[0000.898] Display board id is not available
[0000.902] BoardID = 3448, SKU = 0x0
[0000.906] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.910] Nano-SD: checking PT table on QSPI …
[0001.015] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.071] /bpmp deleted
[0001.073] SC7EntryFw header found loaded at 0xff700000
[0001.269] OVR2 PMIC
[0001.271] Bpmp FW successfully loaded
[0001.274] BoardID = 3448, SKU = 0x0
[0001.278] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.281] Nano-SD: checking PT table on QSPI …
[0001.287] WB0 init successfully at 0xff780000
[0001.291] Set NvDecSticky Bits
[0001.295] GSC2 address ff53fffc value c0edbbcc
[0001.301] GSC MC Settings done
[0001.304] BoardID = 3448, SKU = 0x0
[0001.307] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.311] Nano-SD: checking PT table on QSPI …
[0001.316] TOS Image length 53680
[0001.319] Monitor size 53680
[0001.322] OS size 0
[0001.337] Secure Os Aes-CMAC Verification Failed!
[0001.342] Error in NvTbootValidateTOS 
[0001.346] Validation of secure os failed!
[0001.349] Device Shutdown called …
I think the topic is similar to the following error, so I will try writing the image to the SD card again and see what happens.
I recently tried updating jetpack from 4.5 to 4.6 but when I put in the SD card and boot up Jetson nano. It simply blinks the green light once and that’s it. Nothing comes on again, I’m confused at what happened since I’m currently using the barrel jack.
I need urgent assistance please
Unfortunately, I rebooted with a new SD image written to it, and the same thing happened.
Did you try the hint, end of the post
Flash the jetson using the SDK manager, but make sure you use ubuntu 18
If something is wrong in such early boot log, keep replacing the image on the sdcard won’ t help.
The sdcard only loads the kernel and rootfs. What need to gets re-flashed is the bootloader part.
So only sdkmanager can fix this kind of issue. Hope this can explain why you must use sdkm.
I was able to solve the problem by following these steps. Thank you for your help.
1.Short-circuit the FC REC to GND to boot in recovery mode.
2.Turn on the power, make sure it doesn’t go off, and make a USB connection to the Ubuntu 18.04 terminal.
3.Run the lsusb command in Terminal and confirm that the following log is displayed.
Bus 001 Device 004: ID 0955:7019 NVidia Corp.
4.Writing from SDK manager to USB-connected JetsonNano on Ubuntu 18.04LTS environment.
Everything You Need to Set Up Your Development Environment NVIDIA SDK Manager provides an end-to-end development environment setup solution for NVIDIA’s DRIVE, Jetson, Holoscan, Rivermax, DOCA and Ethernet Switch SDKs for both host and target...
As a result, we were able to confirm booting even after the recovery mode was released.
I have solved this problem, but I have a question.
What is the probable cause of this boot loader failure?
I want to know so that we can avoid as many failures as possible.
I am not sure what was your previous jetpack release version.
In some older release like jp4.5, we notice some issues that it would cause bootloader failure in some cases. And this should be fixed after jp4.6 release.
Thus, please upgrade the release version if possible.
The previous version of Jetpack was 4.2.3.
I was relieved to hear that Jetpack 4.6 would not cause the said incident.
Thank you very much for your support.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.