Xavier NX boot failure of CPU

Hi,
I’m testing our custom Xavier NX board using L4TR35.3.1.
During the process of repeating the power cycle test of the board 456 times, there were 2 instances of very slow startup. Upon opening the serial port and printing logs, the following issue was discovered.
It seems the CPU get failure

[    0.010827] Tegra Revision: A02 SKU: 0xde CPU Process: 0 SoC Process: 0
[    0.011076] Remapping and enabling EFI services.
[    0.012758] smp: Bringing up secondary CPUs ...
[    5.111205] CPU1: failed to come online
[    5.111260] CPU1: failed in unknown state : 0x0
[   10.253360] CPU2: failed to come online
[   10.253404] CPU2: failed in unknown state : 0x0
[   15.394744] CPU3: failed to come online
[   15.394763] CPU3: failed in unknown state : 0x0
[   20.535897] CPU4: failed to come online
[   20.535936] CPU4: failed in unknown state : 0x0
[   25.674858] CPU5: failed to come online
[   25.674877] CPU5: failed in unknown state : 0x0
[   25.674971] smp: Brought up 1 node, 1 CPU
[   25.674984] SMP: Total of 1 processors activated.
[   25.674998] CPU features: detected: Privileged Access Never
[   25.675030] CPU features: detected: LSE atomic instructions
[   25.675042] CPU features: detected: User Access Override
[   25.675070] CPU features: detected: 32-bit EL0 Support
[   25.675083] CPU features: detected: RAS Extension Support
[   25.675095] CPU features: detected: CRC32 instructions
[   25.749712] CPU: All CPU(s) started at EL2

noarmal_bootlog.txt (66.9 KB)
err_bootlog.txt (72.0 KB)

What is the reason for this, is it due to hardware design or a bug in the L4T version?

Please move to latest version of L4T.

is that mean this is a known issues in R35.3.1? But we don’t have a plan to update the jetson version, is there any other solution to fix it?

It is just for debug purpose.

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