Hi There, Developer Forum!
I’ve been using a brand new Jetson nano board for about a week, and it was working perfectly fine.
Just now I had to flash a new SD card with JetPack 4.6 (since I’m having another unrelated issue with launching eclipse and nsight), and the installation completed on the jetson.
After that, I rebooted the device, and it will not turn on anymore: When I plug in the power supply, the PWR green LED lights up and the immediately turns off. There is no monitor output via DP. The device remains unresponsive, until I unplug it and replug it. When doing so, the scenario repeats itself.
This behavior persists when powered either via the DC barrel jack (with the jumper connected) or via the micro USB port (with the jumper removed).
I’d be happy to get some assistance with what I could do to solve this problem.
Thank you in advance,
It could be some connected device has an issue, e.g., something drawing too much power to a USB device. Probably though it is a hardware failure of the carrier board. If you still get the same LED power light up then off using both power sources which previously worked, while nothing else is connected, then you might consider RMA. See:
I am having the same issue. Were you able to find any solution?
Are you using the dev kit’s supplied power supply? What else is connected? Which release was it flashed with, and which model (SD card versus eMMC module)?
I am using a 5V 3A power supply. I meauserd output, which seems OK. I used the nano with the same power supply this morning with no problem.
It has a freshly flashed SDK from Nvidia.
I got the following messages from the serial port of Jetson Nano when just connected to the power. The green light turns of a few seconds and turns off:
[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 …
Total current available is rarely the issue. The issue is one of regulation quality. Jetsons are particularly sensitive to power fluctuations. I suggest trying other power sources known for high regulation quality, even if just for testing.
I don’t know enough about the boot log to answer, but someone more familiar with that stage of boot should be able to answer. In particular, I am wondering if you have enabled any kind of secure boot or performed any fuse burn.
Thanks for the reply.
I didn’t change any setting on dev kit, including the secure boot and fuses.
This issue happened just after I received the dev kit. I flashed the sd card with the latest image release from nvidia website. It had started up normally on the first boot, and it didn’t boot up on the second one. I just did the location, language etc. regional settings, then shutdown the dev kit on the first boot
There seems to be no error about power on boot log, can power still be the issue? Also, I tried all the 5v adapters I have, still looking for better ones though.
Power could still be the issue, but if the previous release used was not compatible in QSPI memory (SD card models have this), then it might just need flashing of QSPI via JetPack/SDK Manager. I couldn’t say for sure, but likely flashing the unit in recovery mode would be the next test anyway. If it is then still an issue, perhaps it is power.