NVIDIA Orin NX Boot Stuck at I/TC: Secondary CPU 11 switching to normal world boot

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

Hello, we are using a custom carrier board with NVIDIA Orin NX mounted onto it and it is currently stuck during boot (it was working previously, before we accidentally installed bad packages). The serial debug output gets stuck at :

EFI stub: Exiting boot services and installing virtual address map…
��I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
I/TC: Secondary CPU 8 initializing
I/TC: Secondary CPU 8 switching to normal world boot
I/TC: Secondary CPU 9 initializing
I/TC: Secondary CPU 9 switching to normal world boot
I/TC: Secondary CPU 10 initializing
I/TC: Secondary CPU 10 switching to normal world boot
I/TC: Secondary CPU 11 initializing
I/TC: Secondary CPU 11 switching to normal world boot

Here is the full boot log.

log.txt (34.5 KB)

Is there anything we can do to resolve this issue?

Thanks!

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that the NVIDIA Orin NX module on your custom carrier board is experiencing a boot issue. The serial debug output is stuck at a specific point, indicating a potential problem with the boot process.

To resolve this issue, I would recommend the following steps:

  1. Review the boot log: Carefully examine the full boot log (log.txt) to identify any error messages or warnings that may indicate the cause of the issue.
  2. Check the boot configuration: Verify that the boot configuration is correct and that the boot order is set to boot from the correct device (e.g., SD card or eMMC).
  3. Disable console printing over UART: As mentioned in the provided context, console printing over UART can be a bottleneck in kernel boot time. Try disabling console printing over UART by removing the console setting from the platform configuration file (e.g., p3767.conf.common for Orin NX).
  4. Verify the kernel device tree: Ensure that the kernel device tree is correctly configured and that it matches the hardware configuration of your custom carrier board.
  5. Check for firmware updates: Verify that the firmware on your Orin NX module is up-to-date. You can check for firmware updates using the NVIDIA SDK Manager or by contacting NVIDIA support.
  6. Try a different boot mode: Try booting the module in a different mode, such as recovery mode or safe mode, to see if the issue persists.
  7. Reflash the module: If none of the above steps resolve the issue, you may need to reflash the Orin NX module with a new image. This can be done using the NVIDIA SDK Manager or by contacting NVIDIA support.

In comparison to other issues mentioned in the provided context, this issue appears to be related to the boot process and kernel configuration, rather than issues with camera functionality or CUDA compilation.

Some similar issues mentioned in the context include:

  • “Boot failed” on Jetson Xavier NX, which may indicate a similar boot issue.
  • “Cannot cross compile CUDA samples and cutlass3.1.0 with JetPack Cross Compilation container” on Jetson AGX Orin, which is unrelated to the boot issue.
  • “My jetson orin nx 16g won’t shut down properly” on Jetson Orin NX, which may indicate a power management issue rather than a boot issue.

Overall, the issue appears to be specific to the boot process on the NVIDIA Orin NX module, and resolving it will likely require a combination of troubleshooting and configuration adjustments.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi eightfingers123,

What’s the Jetpack version in use? JP5.1.4(r35.6.0)?

It seems booting failed during kernel loading.

What bad package do you install?
Have you tried booting into recovery kernel and remove your package to check if it could help?

5

We are using L4T 35.6.0 [ JetPack 5.1.4 ].
We tried installing anydesk for remote desktop and i think something broke during its installation.
How do i boot into recovery kernel ? Can I do it through the UEFI shell ?

6

Please configure it through UEFI menu.
Device Manager → NVIDIA Configuration → L4T Configuration → L4T Boot Mode → recovery kernel

7

I tried configuring it to recovery kernel but it boots into UEFI shell instead. I think the recovery partition is missing.

image
image533×235 37.1 KB

8

Can your NVMe SSD be recognized in UEFI menu?