Orin Nano does not boot anymore

Hi all,

I have flashed JetPack 6.0 on an NVMe on an Orin Nano through SDK Manager, and I have been using the device for the last two weeks without any issues. Yesterday, it stopped booting for some reason (the fan and power LED are working, but it only displays a blank screen—not even showing the initial logo screen).

I tried the following steps:

  1. Running it in headless mode and connecting through SSH - it didn’t work.
  2. Connecting to a host machine - SDK Manager detects the device but cannot flash it.
  3. Removing the NVMe disk and plugging it into an external USB interface - partitions and content seemed fine, I backed up my workspace and erased all the partitions.
  4. Plugging a monitor into the Orin Nano and running it without any disk - this time, it displayed the startup screen with the NVIDIA logo.
  5. Trying to flash it again with the formatted disk on the host machine using SDK Manager - it still gives errors (logs attached).

Strangely, now, when I plug in the peripherals and try to run it without the disk, even the startup screen does not appear anymore.

I am suspecting a hardware problem. I ordered a USB to TTY cable for further debugging through a serial connection. Meanwhile, could you please give me some direction on what to do?

Best wishes,
baris

SDKM_logs_JetPack_6.zip (191.6 KB)

Hi,

You are using a virtual machine on a Mac for flashing?
We don’t support virtual machines, and please use a real Ubuntu host PC.

Hi,

Thanks for your reply.

No, I used real machines. I did the initial working installation on Ubuntu 22.04. The unsuccessful flashing attempts were on Ubuntu 20.04

I asked this because I saw __MACOSX in the zip file, which should only appear on a Mac system.
Anyway, we still need the log:

Yes, I first copied the log file to my macbook before I sent it to the forum. I used my colleagues’ workstations for the installations.

I’ll do the debugging once I received the cable, thanks.

1 Like

Is this still an issue to support? Any result can be shared?

yes, please keep the topic open. I haven’t received the cable yet, once I get it I’ll share the results here.

Hi again,

I received the cable now and that’s the error message I get:

I/TC: Primary CPU switching to normal world boot
??
  Jetson UEFI firmware (version 36.2.0-gcid-34956989 built on 2023-11-30T18:35:35+00:00)


??ERROR: camera-ip/isp5/isp5.c:2031 [isp5_pm_init] "ERROR: Failed to turn isp1 power on"
BUG: core/init/init.c:86 [init_all] "*** FIRMWARE INIT FAILED AT LEVEL 95 ***"
??

  ??Admin Task Init
Admin Task Init complete
Print Task Init
RM Task Init
SHA Task Init
Admin Task Started
DCE SC7 SHA Enabled
??

  ??RM Task Started
??
  ??RM Task Running
??

Here is the full log:
log.txt (36.4 KB)

Do you have any idea about the problem?

Could you dump the uart log during flash process too?

I saw there is such log which should not happen on any of device.

FATAL ERROR [FILE=platform/drivers/emc/drv/emc-init-train.c, ERR_UID=2954]: EMC: training failed: -5\

Hi, thanks for your reply.

How can I get the uart log during flash process please? Should I set it to the force recovery mode and start a flash process again while keeping the serial connection (having two USB connections at the same time)?

How can I get the uart log during flash process please? Should I set it to the force recovery mode and start a flash process again while keeping the serial connection (having two USB connections at the same time)?

Yes.

I’ve attached the log file:
log_flash_attempt.txt (7.7 KB)

When I clicked the retry failed items button on SDKManager, I got the following message:
Screenshot from 2024-05-28 15-07-14

Hi again,

the following log from the 2nd flash attempt has more information:

log_flash_2.txt (35.0 KB)

SDKM_logs_JetPack_6.0_(rev._1)_Linux_for_Jetson_Orin_Nano_modules_2024-05-28_15-14-19.zip (406.2 KB)

Is there peripheral(camera, WiFi dongle, keyboard, mouse…) connected to the device during flashing?
Remove then if so and try again.

No, nothing was connected during flashing.

Then it is hardware issue. Please RMA the device.

ok, thanks for your help.

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