Jetson nano boot failed: Starting CPU & Halting co-processor

Hi Nvidia,
There include multiple Jetson Nano EMMC modules on my Chassis, In most cases, All the modules startup normally, But sometimes there are several modules boot failed at the same time with the following errors.

[0000.232] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.237] Processing in cold boot mode Bootloader 2
[0000.242] A02 Bootrom Patch rev = 1023
[0000.245] Power-up reason: pmc por
[0000.249] No Battery Present
[0000.251] pmic max77620 reset reason
[0000.255] pmic max77620 NVERC : 0x80
[0000.258] RamCode = 0
[0000.260] Platform has DDR4 type RAM
[0000.264] max77620 disabling SD1 Remote Sense
[0000.268] Setting DDR voltage to 1125mv
[0000.272] Serial Number of Pmic Max77663: 0x12f49
[0000.279] Entering ramdump check
[0000.282] Get RamDumpCarveOut = 0x0
[0000.286] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.291] Last reboot was clean, booting normally!
[0000.295] Sdram initialization is successful
[0000.299] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.306] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.311] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.317] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.323] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.329] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.335] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.341] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.357] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.363] Platform-DebugCarveout: 0
[0000.366] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.372] Non secure mode, and RB not enabled.
[0000.376] *** Booting BFS0.
[0000.379] Initialize FailControl
[0000.382] Read PT from (0:3)
[0000.397] Csd NumOfBlocks=0
[0000.436] PT crc32 and magic check passed.
[0000.440] Using BFS PT to query partitions
[0000.444] PT: Partition LNX NOT found !
[0000.448] *** Booting KFS0.
[0000.450] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.456] BoardID = 3448, SKU = 0x2
[0000.459] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.465] Read GPT from (0:3)
[0000.473] Using GPT Primary to query partitions
[0000.478] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.485] Loading Tboot-CPU binary
[0000.491] Verifying TBC in OdmNonSecureSBK mode
[0000.501] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.508] Bootloader downloaded successfully.
[0000.512] Downloaded Tboot-CPU binary to 0xa0000258
[0000.517] MAX77620_GPIO5 configured
[0000.520] CPU power rail is up
[0000.523] CPU clock enabled
[0000.527] Performing RAM repair
[0000.530] Updating A64 Warmreset Address to 0xa00002e9
[0000.535] BoardID = 3448, SKU = 0x2
[0000.538] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.544] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.550] Loading NvTbootBootloaderDTB
[0000.567] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.639] Bootloader DTB Load Address: 0x83000000
[0000.643] BoardID = 3448, SKU = 0x2
[0000.647] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.652] Loading NvTbootKernelDTB
[0000.669] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.740] Kernel DTB Load Address: 0x83100000
[0000.744] BoardID = 3448, SKU = 0x2
[0000.747] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.753] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.760] Loading cboot binary
[0000.771] Verifying EBT in OdmNonSecureSBK mode
[0000.813] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.820] Bootloader downloaded successfully.
[0000.824] BoardID = 3448, SKU = 0x2
[0000.827] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.833] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.839] PT: Partition NCT NOT found !
[0000.843] Warning: Find Partition via PT Failed
[0000.847] Next binary entry address: 0x92c00258
[0000.852] BoardId: 3448
[0000.857] Overriding pmu board id with proc board id
[0000.861] Display board id is not available
[0000.866] BoardID = 3448, SKU = 0x2
[0000.869] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.875] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.888] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0000.944] /bpmp deleted
[0000.946] SC7EntryFw header found loaded at 0xff700000
[0001.130] OVR2 PMIC
[0001.132] Bpmp FW successfully loaded
[0001.135] BoardID = 3448, SKU = 0x2
[0001.138] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0001.144] NvTbootFailControlDoFailover: No failover; Continuing …
[0001.151] WB0 init successfully at 0xff780000
[0001.156] Verifying NvTbootWb0 in OdmNonSecureSBK mode
[0001.161] Set NvDecSticky Bits
[0001.164] GSC2 address ff53fffc value c0edbbcc
[0001.171] GSC MC Settings done
[0001.173] BoardID = 3448, SKU = 0x2
[0001.177] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0001.183] TOS Image length 53680
[0001.187] Monitor size 53680
[0001.189] OS size 0
[0001.195] Secure Os AES-CMAC Verification Success!
[0001.199] TOS image cipher info: plaintext
[0001.203] Loading and Validation of Secure OS Successful
[0001.219] SC7 Entry Firmware - 0xff700000, 0x4000
[0001.224] NvTbootPackSdramParams: start.
[0001.229] NvTbootPackSdramParams: done.
[0001.233] Tegraboot started after 161519 us
[0001.237] Basic modules init took 741103 us
[0001.241] Sec Bootdevice Read Time = 54 ms, Read Size = 3682 KB
[0001.246] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB
[0001.252] Next stage binary read took 7378 us
[0001.256] Carveout took -34772 us
[0001.259] CPU initialization took 387492 us
[0001.263] Total time taken by TegraBoot 1101201 us

[0001.268] Starting CPU & Halting co-processor

Are you telling that there are modules that would boot fail simultaneously? How is your system for each module here?

Why would one jetson nano affect the boot process of another one?

Yes. In my Chassis there are multiple Jetson Nano EMMC modules which have the same power and can work independently. They can power up simultaneously. And the boot process has no effect on each other. I suspect it’s a hardware problem. I wonder if I can see what caused this problem according the boot log above.

Please move your module to devkit and see if same issue would happen.

If it does not, then this is the hardware problem.