Jetson Nano (4GB) reboot cycle "EBT partition is corrupted"

[0000.125] [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: 0xc1ae6
[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] 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.324] 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.549] Bootloader DTB Load Address: 0x83000000
[0000.554] BoardID = 3448, SKU = 0x0
[0000.557] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.561] Nano-SD: checking PT table on QSPI …
[0000.565] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.571] Loading NvTbootKernelDTB
[0000.637] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.706] Kernel DTB Load Address: 0x83100000
[0000.710] BoardID = 3448, SKU = 0x0
[0000.714] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.717] Nano-SD: checking PT table on QSPI …
[0000.722] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.729] Loading cboot binary
[0000.845] Verifying EBT in OdmNonSecureSBK mode
[0000.887] Verification of EBT failed!
[0000.890] EBT partition is corrupted!
[0000.894] *** Set to failover in the next boot ***
[0000.898] NvTbootFailControlSetClobber:
[0000.902] *** 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: 0xc1ae6
[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.255] 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 0 is corrupted (ec=0x14).
[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.439] 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.457] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.460] Nano-SD: checking PT table on QSPI …
[0000.465] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 0 is corrupted (ec=0x14).
[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.628] Bootloader DTB Load Address: 0x83000000
[0000.632] BoardID = 3448, SKU = 0x0
[0000.636] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.640] Nano-SD: checking PT table on QSPI …
[0000.644] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 0 is corrupted (ec=0x14).
[0000.653] NvTbootFailControlDoClobber:
[0000.656] Current BFS=0
[0000.658] No write function to write to current BFS 0
[0000.663] Clobber: returns e=0x1
[0000.666] - failover failed; Continuing with bad image …
[0000.672] Loading NvTbootKernelDTB
[0000.738] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.807] Kernel DTB Load Address: 0x83100000
[0000.811] BoardID = 3448, SKU = 0x0
[0000.814] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.818] Nano-SD: checking PT table on QSPI …
[0000.822] NvTbootFailControlDoFailover: Doing failover: NvTboot partition 0 is corrupted (ec=0x14).
[0000.831] NvTbootFailControlDoClobber:
[0000.834] Current BFS=0
[0000.837] No write function to write to current BFS 0
[0000.842] Clobber: returns e=0x1
[0000.845] - failover failed; Continuing with bad image …
[0000.852] Loading cboot binary
[0000.967] Verifying EBT in OdmNonSecureSBK mode
[0001.009] Verification of EBT failed!
[0001.013] EBT partition is corrupted!
[0001.016] *** Set to failover in the next boot ***
[0001.021] NvTbootFailControlSetClobber:
[0001.024] *** Rebooting ***

I’ve flashes few times the SD card and i have the same trouble at every try :c

Many people using the Nano dev kit don’t realize that the SD card is not the container of boot content…that role falls to the QSPI memory on the dev kit itself. EBT is part of that boot content. For the most part that content changes only after a long period of time with multiple releases, but it does change, and when it does the SD card’s content becomes invalid if it was written for an older QSPI release.

To change (update) the QSPI so that it’ll work with a more recent SD card image you must use JetPack/SDK Manager to flash the Jetson Nano itself. You might also have to freshly create the SD card image again, but once you’ve flashed the QSPI with the current release (the one paired to that SD card image), then it should work again.

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