The Nvidia board is also getting very hot now.
Also, no need use such comment here. Such comment is not precise and not helping.
For example, A 70C could be hot one for human but totally not fatal to Jetson. Your hand won’t tell the real temperature there, so no need to care about that.
Im using USB UART connection as it is done in this tutorial https://jetsonhacks.com/2019/04/19/jetson-nano-serial-console/ you asked me to follow.
when I disconnect the USB i see the error “Cannot Open /dev/ttyUSB0!”
Hi,
That one does not matter. That is totally not a log from Jetson at all.
You could take a look at other topics and see how the log would be like…
I am merely talking about take a look at how the logs look like. Not asking you to refer to whole topic.
Please take a picture of how you really connect those cables there. I don’t think you are doing it right.
or try to use picocom instead of minicom.
For example,
sudo picocom -b 115200 /dev/ttyUSB0
What is the meaning of color of your wire here?
USB UART SIDE:
Yellow : TXD
Green : RXD
Orange : GND
JETSON SIDE:
Green : TXD
Yellow : RXD
Orange : GND
Have you ever tried to swap the TX/RX here or try other UART cable?
Hi
@WayneWWW I have tested with switching the RX and TX wires. Still no response.
I have used another USB UART as well. same response.
Try other cables and host PC.
As I already mentioned, if your host side flash log already went into “Waiting for target to boot-up…” then it 100% would have logs to UART.
And just to clarify. You have to open the console and wait there before you power on the board.
You cannot power on the board like 30 mins and then connect the UART cable and tell me you cannot see any log.
Thats how I did. I opened the console then power up and I still cant see any logs.
As I mentioned previously, I have tested it with multiple hosts and cables, and the issue persists. I’m confident the problem lies with the Jetson board itself. If that’s not the case, your technical team should be able to get it up and running quickly.
I’m struggling to understand the value of the warranty if I have to spend three weeks troubleshooting this issue, only to be told that I’m not handling it correctly. Please advise on the next steps to resolve this promptly.
Hi,
Then please RMA the device. This is your freedom to do so.
Just to clarify. There is no sufficient evidence here to show that your board really has issue.
If this board is really broken, then you won’t even get into this log.
15:38:34.649 - Info: Waiting for device to expose ssh …Waiting for device to expose ssh …Run command: flash on fc00:1:1:0::2
15:38:45.947 - Info: SSH ready
This log is from your previous sdkmanager flash log. As you could see, your host PC even can ssh to Jetson board in this situation. So the board itself is still working.
As I mentioned previously, I have tested it with multiple hosts and cables, and the issue persists.
Your flash issue and cannot dump UART log issue are separate items.
I don’t know what cables you are talking about here. I am merely talking about the UART cable you are using to dump log. Not usb cable. Your usb cables are fine and your host PC could even ssh to Jetson during your flash.
If you ever tried other host PC and flash went failure too, share me the log you got there. At least the host side log could at least provide clues.
Please do not just tell me “It got failed”. There was another guy totally not powered on the board and told me his board failed to boot before. Such “got failed” really not helped here.
Hi all,
Not sure if i have a related problem. 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.
Please file your own topic and we could discuss there.
