The Jetson Nano Developer Kit (with 4GB memory)

The The Jetson Nano Developer Kit (with 4GB memory) keeps restarting after being powered on;
start log:
[L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[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: 0x2ecd
[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.227] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.233] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.249] 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] Initialize FailControl
[0000.283] Read PT from (2:0)
[0000.314] PT crc32 and magic check passed.
[0000.318] Using BFS PT to query partitions
[0000.323] Loading Tboot-CPU binary
[0000.352] Verifying TBC in OdmNonSecureSBK mode
[0000.362] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.369] Bootloader downloaded successfully.
[0000.373] Downloaded Tboot-CPU binary to 0xa0000258
[0000.378] MAX77620_GPIO5 configured
[0000.381] CPU power rail is up
[0000.384] CPU clock enabled
[0000.388] Performing RAM repair
[0000.391] Updating A64 Warmreset Address to 0xa00002e9
[0000.396] BoardID = 3448, SKU = 0x0
[0000.399] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.403] Nano-SD: checking PT table on QSPI …
[0000.407] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.413] Loading NvTbootBootloaderDTB
[0000.480] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.551] Bootloader DTB Load Address: 0x83000000
[0000.556] BoardID = 3448, SKU = 0x0
[0000.559] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.563] Nano-SD: checking PT table on QSPI …
[0000.567] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.573] Loading NvTbootKernelDTB
[0000.639] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.711] Kernel DTB Load Address: 0x83100000
[0000.715] BoardID = 3448, SKU = 0x0
[0000.718] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.722] Nano-SD: checking PT table on QSPI …
[0000.726] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.734] Loading cboot binary
[0000.850] Verifying EBT in OdmNonSecureSBK mode
[0000.892] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.899] Bootloader downloaded successfully.
[0000.903] BoardID = 3448, SKU = 0x0
[0000.906] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.910] Nano-SD: checking PT table on QSPI …
[0000.914] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.920] PT: Partition NCT NOT found !
[0000.924] Warning: Find Partition via PT Failed
[0000.928] Next binary entry address: 0x92c00258
[0000.933] BoardId: 3448
[0000.937] Overriding pmu board id with proc board id
[0000.942] Display board id is not available
[0000.946] BoardID = 3448, SKU = 0x0
[0000.950] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.954] Nano-SD: checking PT table on QSPI …
[0000.958] NvTbootFailControlDoFailover: No failover; Continuing …
[0001.065] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.121] /bpmp deleted
[0001.123] SC7EntryFw header found loaded at 0xff700000
[0001.311] OVR2 PMIC
[0001.313] Bpmp FW successfully loaded
[0001.316] BoardID = 3448, SKU = 0x0
[0001.319] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.323] Nano-SD: checking PT table on QSPI …
[0001.328] NvTbootFailControlDoFailover: No failover; Continuing …
[0001.335] WB0 init successfully at 0xff780000
[0001.339] Verifying NvTbootWb0 in OdmNonSecureSBK mode
[0001.344] Set NvDecSticky Bits
[0001.348] GSC2 address ff53fffc value c0edbbcc
[0001.354] GSC MC Settings done
[0001.357] BoardID = 3448, SKU = 0x0
[0001.360] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.364] Nano-SD: checking PT table on QSPI …
[0001.368] NvTbootFailControlDoFailover: No failover; Continuing …
[0001.375] TOS Image length 53680
[0001.378] Monitor size 53680
[0001.381] OS size 0
[0001.396] Secure Os Aes-CMAC Verification Failed!
[0001.401] Error in NvTbootValidateTOS [18]
[0001.405] Validation of secure os failed!
[0001.408] TOS partition is corrupted!
[0001.412] *** Set to failover in the next boot ***
[0001.416] NvTbootFailControlSetClobber:
[0001.420] *** Rebooting ***
[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.162] Processing in cold boot mode Bootloader 2
[0000.167] A02 Bootrom Patch rev = 1023
[0000.171] Power-up reason: software reset
[0000.174] No Battery Present
[0000.177] pmic max77620 reset reason
[0000.180] pmic max77620 NVERC : 0x0
[0000.184] RamCode = 0
[0000.186] Platform has DDR4 type RAM
[0000.189] max77620 disabling SD1 Remote Sense
[0000.193] Setting DDR voltage to 1125mv
[0000.197] Serial Number of Pmic Max77663: 0x2ecd
[0000.205] Entering ramdump check
[0000.208] Get RamDumpCarveOut = 0x0
[0000.211] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.216] Last reboot was clean, booting normally!
[0000.221] Sdram initialization is successful
[0000.225] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.231] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.237] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.243] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.249] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.254] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.260] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.266] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.282] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.288] Platform-DebugCarveout: 0
[0000.292] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.297] Non secure mode, and RB not enabled.
[0000.302] BoardID = 3448, SKU = 0x0
[0000.305] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.309] Nano-SD: checking PT table on QSPI …
[0000.313] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0000.322] NvTbootFailControlDoClobber:
[0000.325] Current BFS=0
[0000.328] No write function to write to current BFS 0
[0000.332] Clobber: returns e=0x1
[0000.335] - failover failed; Continuing with bad image …
[0000.341] Read PT from (2:0)
[0000.371] PT crc32 and magic check passed.
[0000.375] Using BFS PT to query partitions
[0000.381] Loading Tboot-CPU binary
[0000.409] Verifying TBC in OdmNonSecureSBK mode
[0000.419] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.426] Bootloader downloaded successfully.
[0000.430] Downloaded Tboot-CPU binary to 0xa0000258
[0000.435] MAX77620_GPIO5 configured
[0000.438] CPU power rail is up
[0000.441] CPU clock enabled
[0000.445] Performing RAM repair
[0000.448] Updating A64 Warmreset Address to 0xa00002e9
[0000.453] BoardID = 3448, SKU = 0x0
[0000.456] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.460] Nano-SD: checking PT table on QSPI …
[0000.465] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0000.473] NvTbootFailControlDoClobber:
[0000.477] Current BFS=0
[0000.479] No write function to write to current BFS 0
[0000.484] Clobber: returns e=0x1
[0000.487] - failover failed; Continuing with bad image …
[0000.492] Loading NvTbootBootloaderDTB
[0000.559] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.630] Bootloader DTB Load Address: 0x83000000
[0000.635] BoardID = 3448, SKU = 0x0
[0000.638] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.642] Nano-SD: checking PT table on QSPI …
[0000.646] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0000.655] NvTbootFailControlDoClobber:
[0000.658] Current BFS=0
[0000.661] No write function to write to current BFS 0
[0000.665] Clobber: returns e=0x1
[0000.668] - failover failed; Continuing with bad image …
[0000.674] Loading NvTbootKernelDTB
[0000.740] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.811] Kernel DTB Load Address: 0x83100000
[0000.815] BoardID = 3448, SKU = 0x0
[0000.819] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.823] Nano-SD: checking PT table on QSPI …
[0000.827] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0000.836] NvTbootFailControlDoClobber:
[0000.839] Current BFS=0
[0000.841] No write function to write to current BFS 0
[0000.846] Clobber: returns e=0x1
[0000.849] - failover failed; Continuing with bad image …
[0000.856] Loading cboot binary
[0000.972] Verifying EBT in OdmNonSecureSBK mode
[0001.014] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0001.021] Bootloader downloaded successfully.
[0001.025] BoardID = 3448, SKU = 0x0
[0001.028] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.032] Nano-SD: checking PT table on QSPI …
[0001.036] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0001.045] NvTbootFailControlDoClobber:
[0001.049] Current BFS=0
[0001.051] No write function to write to current BFS 0
[0001.056] Clobber: returns e=0x1
[0001.059] - failover failed; Continuing with bad image …
[0001.064] PT: Partition NCT NOT found !
[0001.068] Warning: Find Partition via PT Failed
[0001.072] Next binary entry address: 0x92c00258
[0001.077] BoardId: 3448
[0001.081] Overriding pmu board id with proc board id
[0001.086] Display board id is not available
[0001.090] BoardID = 3448, SKU = 0x0
[0001.094] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.097] Nano-SD: checking PT table on QSPI …
[0001.102] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0001.111] NvTbootFailControlDoClobber:
[0001.114] Current BFS=0
[0001.116] No write function to write to current BFS 0
[0001.121] Clobber: returns e=0x1
[0001.124] - failover failed; Continuing with bad image …
[0001.230] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.286] /bpmp deleted
[0001.288] SC7EntryFw header found loaded at 0xff700000
[0001.476] OVR2 PMIC
[0001.478] Bpmp FW successfully loaded
[0001.482] BoardID = 3448, SKU = 0x0
[0001.485] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.489] Nano-SD: checking PT table on QSPI …
[0001.493] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0001.502] NvTbootFailControlDoClobber:
[0001.505] Current BFS=0
[0001.508] No write function to write to current BFS 0
[0001.512] Clobber: returns e=0x1
[0001.515] - failover failed; Continuing with bad image …
[0001.522] WB0 init successfully at 0xff780000
[0001.526] Verifying NvTbootWb0 in OdmNonSecureSBK mode
[0001.531] Set NvDecSticky Bits
[0001.535] GSC2 address ff53fffc value c0edbbcc
[0001.541] GSC MC Settings done
[0001.544] BoardID = 3448, SKU = 0x0
[0001.547] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.551] Nano-SD: checking PT table on QSPI …
[0001.555] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 1 is corrupted (ec=0x12).
[0001.564] NvTbootFailControlDoClobber:
[0001.568] Current BFS=0
[0001.570] No write function to write to current BFS 0
[0001.575] Clobber: returns e=0x1
[0001.578] - failover failed; Continuing with bad image …
[0001.584] TOS Image length 53680
[0001.587] Monitor size 53680
[0001.590] OS size 0
[0001.605] Secure Os Aes-CMAC Verification Failed!
[0001.609] Error in NvTbootValidateTOS [18]
[0001.613] Validation of secure os failed!
[0001.617] TOS partition is corrupted!
[0001.621] *** Set to failover in the next boot ***
[0001.625] NvTbootFailControlSetClobber:
[0001.629] *** Rebooting ***
[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.162] Processing in cold boot mode Bootloader 2
[0000.167] A02 Bootrom Patch rev = 1023
[0000.171] Power-up reason: software reset

By comparing with successful startup logs:
error log is:
[0001.605] Secure Os Aes-CMAC Verification Failed!
[0001.609] Error in NvTbootValidateTOS [18]
[0001.613] Validation of secure os failed!
[0001.617] TOS partition is corrupted!
[0001.621] *** Set to failover in the next boot ***
[0001.625] NvTbootFailControlSetClobber:

Can anyone help me discover the reason?

Have you tried re-flashing with SDK Manager?

I haven’t tried using SDK Manager to flash images yet,How should I use this method to burn images?
But I use SD Card Formatter to format the SD card
Then use BalenaEtcher to burn the image downloaded from the official website, completely following the manual to burn it
I guess it’s because the TOS image during firmware initialization broke, causing my Uboot image to fail to start. Is there any way to help me solve this problem?
The current situation of the Jetson Nano Developer Kit (with 4GB memory) board is that the power supply keeps resetting and restarting,
Keep reporting this log until repeated restarts:
[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.162] Processing in cold boot mode Bootloader 2

[0001.605] Secure Os Aes CMAC Verification Failed!
[0001.609] Error in NvTbootValidateTOS [18]
[0001.613] Validation of secure os failed!
[0001.617] TOS partition is corrupt!
[0001.621] * * * Set to fail over in the next boot***
[0001.625] NvTbootFailControlSe
[0001.629] *** Rebooting ***
[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.162] Processing in cold boot mode Bootloader 2

[0001.605] Secure Os Aes CMAC Verification Failed!
[0001.609] Error in NvTbootValidateTOS [18]
[0001.613] Validation of secure os failed!
[0001.617] TOS partition is corrupt!
[0001.621] * * * Set to fail over in the next boot***
[0001.625] NvTbootFailControlSe
[0001.629] *** Rebooting ***

Is it that my Jetson Nano Developer Kit (with 4GB memory) board hardware is broken?

https://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html

This won’t be solved with the SD card image, and that’s why I told you to use SDK Manager.

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