After QSPI flash no monitor output anymore

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
1

Hello,

I have a Jetson Orin Nano DevKit,
P3767-0005
with a single SSD, no SD available.

The ext4 partition is on /dev/nvmeOn1p1

Ubuntu 20.04.6 LTS
GNU/Linux 5.10.104-tegra aarch64

I flashed the QSPI

sudo ./flash.sh -c ./bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvmeOn1p1

The script runs through and the JON reboots.

I can putty into the JON, but the monitor is either black or white (depending when I switch to the monitor).

No NVIDIA logo nor boot options

I tried some other options, but with no luck.

Does anybody have an idea how to get monitor output back?

Thank you
Olaf

3

Please put the serial console log here:

4

@DaveYYY , the cable is ordered. It will take some days.

5

Jetson Orin Nano Devkit B01.txt (149.0 KB)

Sorry about the delay.

I have a Jetson Orin Nano Devkit B01.
From the outside the bootup looks correct.

The probIem started with no output on the monitor.
Since trying to flash the JON I cannot putty in anymore.
But running the restore with RAMDisk, which also fails, at the end SSH is established, which is working.
The files on the hidden partition are still there.

The log looks OK for me until
13.412187] imx219 9-0010: imx219_board_setup: error during i2c read probe

6

What if you re-flash everything including bootloader and rootfs?

7

I could get my hands on a second JON (Reference system) for some cross-testing. Results:

JonR + SddR = OK

Jon1 + Sdd1 = Boot without screen output, very short fan stop (like in the middle), fan continues, until fan stops, from here no fan, no putty

JonR + Sdd1 = Boot with Splash-Screen until fan stops, from here no fan, no putty

Jon1 + SddR = Boot without screen output until fan stops, from here no fan, no putty

Flashing always ends in error messages like “Partition not found”.

I tried to create a disc image with “DiskGenius” from SddR and this also ended with “Partition not found”.

8

What are you talking about with SddR and Sdd1?

9

SddR = Harddrive of the reference system

Sdd1 = Harddrive of the faulty system

10

Can you put the complete flashing log here?
If it’s really about I2C transmission error, it won’t get fixed no matter what disks you use.

11

Correct: The cross-check has proven that
a) the disk-drive is not correct
b) even with a correct drive, from another JON, it is not booting beyond the fan-stop.

So what does b) mean? Is there a fix for it?

12

Running through several programmes and hardware I managed to clone the disk-drive of the reference system.
The clone is working correctly.

Then I tried to delete the partitions of the disk-drive of the faulty JON in order to put also a clone on it.
Turns out that it is reports loads of faulty sectors.

I assume that here is the root-cause of all the problems.
I will now try to re-flash the QSPI and upgrade the Jet-Pack…

1 Like
13

I installed a cloned drive into the faulty JON.
Then I ran the “bootFromExternalStorage” script from JetsonHacks.
The JON is working again!!! :-)

The only thing missing is the boot splash screen. No logo, no text.
I have visual after the fan restarts.

14

So is this still an issue now?

15

JON 20240726 - 12-40.txt (89.7 KB)

It is indeed. At boot the screen is black.
The log shows the correct entries and when you clock enter at the correct point the boot process stops.

16

I ordered a Jetson Orin Nano DevKit

It says DevKit on the box.

JTOP says it is a DevKit

but when you look closely it says p -0003 which is NOT a DevKit.

So trying to flash a non-existing DevKit probably explains most problems.

After one botched up flash attempt, which left the JON nearly dead, a flash by SDK-Manager (using 0003 as target) worked for the first time.

I am now on 35.5.0, Firmware 5.0-35550185, GNU/Linux 5.10.192-tegra, L4T 35.5.0, JetPack 5.1.3

And the Splash Screen for the bios is also back again.

So this episode is settled finally.

Question now is, how to get to JP6. SDK-Manager errors out on writing the Linux image, no matter if I select p -0003 or -0005, But this is another story.
You can close this case.

18

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