Jetson Orin Nano does not boot after flashing Jetpack 6

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
,
1

Hello world, today I flashed my Orin Nano 4GB with JetPack 6.0 DP successfully, but the Orin Nano does not boot anymore.

The specs:

  • Host Machine: dedicated Ubuntu 22.04
  • JetPack: 6.0 DP
  • Original JetPack installed: I can’t recall exactly but it must be JetPack 5
  • Method: SDKManager
  • Carrier Board: Custom Jetson Orin Nano SUB carrier board by Yahboom. Yahboom mentions this carrier board is not very different from the original Nvidia carrier board. In their manual they show how SDKM is used with standard settings.
  • Storage device: It should be flashed to the NVMe SSD
  • Host log: flash_1-1_0_20231210-203944.log (51.3 KB)

How I flashed:
I booted the Orin in Force Recovery Mode. Then I start SDKM and everything looks OK. JetPack 6.0 is downloaded correctly and I chose to skip Jetson SDK Components. The target is successfully recognized as Orin Nano 4GB. I choose NVMe as Storage Device. The flashing takes about 12 minutes and when it’s done it says it has been successful. During flashing it reboots a couple of times.
During one reboot (maybe the first) it shows the Nvidia logo and Boot-options very quickly. After this reboot the display shows only a dash-sign in the top-left corner flashing for about 5 minutes during the last part of flashing. After the final reboot the display does not show anything anymore. After power off/power on nothing happens on the display.

What I tried:
During one of the reboots the display shows the Nvidia logo and boot-options very shortly. I pressed Esc on the keyboard to enter the boot-options. I noticed that the NVMe was number 5 in the boot-order. I moved it up to position 1 and booted from the NVMe. Ubuntu actually booted after this! The problem is that when I restart the system, it boots into a totally black display again without boot options. Since I have no option to enter boot-options anymore, the only way to access boot-options is to flash and wait until 73% when there is a brief moment the display fires up and I can press Esc to enter boot options.

What is weird:
I’m pretty sure that I use the right method to enter Force Recovery Mode–> 1. Power off, 2 Place jumper between FRM-pin and ground-pin and 3. Power on. The weird thing is that even without FRM the SDKM recognizes the target.

1 Like
3

Hi,

Please dump serial console log so we know what’s going on behind the black screen:

4

Ok, the fire extinguisher is on my table (better be safe haha) and I have ordered the USB<>TTL cable. Hopefully I can upload the console log within 2 days.

5

Hi @DaveYYY,

I received the USB<>TTL-cable and logged the host and the console at the same time during flashing. See the logs below. When I log the console during booting it does not show anything at all! Any idea what’s going wrong during the flashing?

(I skipped flashing the Runtime/SDK components by the way)

6

I don’t see anything abnormal with your flashing log.
So what’s the issue now?

You should capture the log after flashing is done and when it’s booting up.

7

Hi @DaveYYY,

The problem is that nothing shows up on the serial connection during booting up after the flashing.
There are some errors in the console log (see below). They seem ‘normal’?

I> Applet do storage init
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : clk_m
I> QSPI Flash: Macronix 64MB
I> QSPI-0l initialized successfully
I> Secondary storage device: SDMMC_BOOT instance: 3
E> Error in command_complete 18000 int_status
E> OCR failed, error = 39390706
E> STORAGE: Failed to open SDMMC: 3.
W> Ignoring init failure for device 0-3
I> Secondary storage device: SDMMC_USER instance: 3
E> Error in command_complete 18001 int_status
E> OCR failed, error = 39390706
E> STORAGE: Failed to open SDMMC: 3.
W> Ignoring init failure for device 1-3
I> Secondary storage device: QSPI_FLASH instance: 0
I> Task: I2C register
8

Well, sorry I didn’t notice it.
I just knew you were using a third-party carrier board, then please contact the board vendor if it’s still compatible with the default BSP from SDK Manager on JetPack 6.
Or find a DevKit for verification.

9

Hi @DaveYYY,

I’m on it.

Another question: Maybe I will buy an original Nvidia carrier board, but I read somewhere that the carrier board cannot be bought separately from the Orin Nano module. Is this true? If yes, can you you recommend a 3rd party carrier board that is compatible with the Nivida original?

10

YES, DevKits are sold along with modules.
We don’t have any recommendation on it.

11

I think this issue seems very similar to the issue I was facing and @DaveYYY was helping me as well on this thread Jetson Orin Nano not booting up - #12 by DaveYYY. I was trying the SD card flashing and booting method though. I am still waiting to get my USB<>TTL-cable to get the logs. But from this discussions in this thread, did we buy a wrong board “third party board” instead of the original NVIDIA board ? I ordered from Amazon.com , there were 2 options one for 499$ and other was 599$. I bought the 499$ development kit as it had good reviews and “Amazon Choice” label on it. Now I am worried I probably bought the wrong development kit.

12

The point here is jetpack6 is just released out for about a week.

The vendor who provided the 3rdparty board may not be ready to provide a compatible BSP for jetpack6 + this 3rd party board.

Thus, if you are worried about wrong board things, you can try jetpack5 first. And come back once the vendor has released their software for jp6.

13

Hi @WayneWWW,

What I don’t understand is that my 3rd party carrier board can be flashed with JetPack 5 with the standard BSP. Why would JetPack 6 require a custom BSP?

I will try to flash with JetPack 5 and let you know if it works. The problem is that I have a dedicated Ubuntu 22.04 host which is not compatible with JetPack 5. That is pretty annoying I have to admit.

I feel you @nbibin001; I’m also disappointed with my 3rd party board. Especially as we cannot buy a separate original Nvidia board which means buying a new Orin + Carrier Board.

Anyway, although I’m a bit annoyed I have to make clear that I totally appreciate the support here by @WayneWWW and @DaveYYY !

14

Could you flash your board again and share us the serial console log?

I would like to know if it is same error log as previous one.

15

Hi @WayneWWW,
Do you mean with JetPack 5?

I will try to do that using a VM or Docker and let you know here.

16

No, I mean jetpack6.

17

Ok, I’m not sure why there would be a difference because I flashed the Orin in exactly the same manner as before, but I just did it like you asked. Below are the logs from flashing the Orin10 minutes ago:

Like with the first logs, I can see a lot of errors in the console log, but I have no idea if those are the cause of the problem.
I hope you can notice something :)

18

Just a reminder, I actually don’t care about the flash process. It looks successful anyway.
What I want to check is the log after your flash.

Please do not just cut the log down. I want to see that boot log after that reboot.

19

That is the problem → minicom does not log anything during boot after flashing. Nothing happens.

20

Then what is the log after you remove the jumper and reboot the device manually?

21

Also without jumper nothing shows up in the log. I’ve tried more than 20 times with the jumper off and on and try removing the jumper during flashing etc. Nothing is showing in the logs during boot.