Hi all,
I got my orin nano devkit today. Flashed a sd card and fired it up.
I get the green boot flash screen followed by the scrolling text. All good to this point.
Then the display goes black and, sometimes, i get a very quick flash of what might be a small graphical window. It’s too fast to see properly.
My monitor shows the displayport feed is disconnected with the occassional momentary connection.
I’ve tried displayport version 1.1 and 1.2, reflashing a different card. Rebooting many times. I can hit escape and get into the boot config without an issue but then the boot continues into darkness like before. I have no idea what is up here and would welcome any help.
I tried nvidia support and they suggested i ask here before returning it.
Thanks in advance for any advice.
Have you tried to put the board into recovery mode and let sdkmanager to flash it from another x86 host PC?
Or you totally don’t know what I am telling here?
Hi,
I don’t have an x86 Linux machine to hand. Do you have any idea what the nature of the problem is? I’m at a loss. I suspected the sd card but I’ve tried two and they survived validation in balena . The only thing I can think of is that at the end of the boot the video output is changed to a different resolution and the hardware is struggling with it. I’m using a Samsung 27” monitor that is about 4 years old and has always been perfect so I think it’s unlikely that the problem is there. That said I have ordered a display port to hdmi cable for today to replace the display port to display port cable I am using just in case.
Hi,
Just to clarify. It is common to have a x86 Linux to reflash your board. This is actually the first thing you should learn when you get a Jetson. Such method has been there for 10 years since the first day the Jetson device was published.
If your power LED on the board is stably powered on, then you may need to dump the log by using below method. And we can check what is happened on the board
Sdcard image didn’t really reflash the board here. It is just like a rootfs is on this card. But if the bootloader software on the board is corrupted, then only using x86 host could recover it. So if replacing sdcard won’t work, then it could be this case.
Even if you dump the log, if this is indeed software corruption in bootloader, then you still need x86 host to flash your board.
Thanks for your reply.
Before I dive into this can you help me understand something. Do you think that my brand new orin has a hardware fault that I can get around by setting up a Linux box and following the instructions in the link you sent?
Do you know if this is a common problem?
On my side, after waiting since Jan for my Orin nano to arrive I am super keen to make a start with it but not at the cost of having to make do with brand new but faulty hardware. I’d like to be able to follow the ‘getting started’ instructions and achieve the results expected. I don’t mind minor glitches that I can easily deal with but not major hardware problems that could leave me limping along going forward.
Any thoughts on how I should proceed?
Just to clarify again.
None of the information you provided here ever really told me that this is hardware problem. I won’t know if this is a hardware problem by just such information you provided.
Based on my past experience, most likely your board just got a software issue and could be recovered by reflashing by sdkmanager from host PC.
In short, I feel it is just a common software issue.
Most of new Jetson beginners always fear about their board has hardware broken because they only rely on the monitor to check whether the board is alive or not.
If you want a more precise analysis, dump the log as I mentioned in previous post.
Hi,
Thanks for this.
Update. I just received my display port to hdmi cable and plugged it in. Works fine, just dandy.
My guess was, and remains, that my monitor, which is only 4 years old (Samsung) doesn’t speak displayport 1.4 and can’t synch to a dp1.1 or dp1.2 video source. Using an dp to hdmi cable solved the problem and I get to the post boot system configuration window.
I think that there is a resolution change in the video and my DP1.2 monitor lost synch with this change. So it wasn’t really a hardware or software failure in the end. I hope this helps others.
1 Like