How to debug the unbootable issue on NX platform

Dears,
We have designed the carrier board by ourselves. The core board is the NVIDIA NX board.
But the system can not be bootalbe now. The Power supply, Clock, reset can be considered is fine and we followed the chekclist.
We have read the NX guide book. But it seems that our design has no problem according the NX guide book.
Anybody can give some advise for us. Many thanks.

Hi,

Probably need to share the serial console log to see where it gets stuck in boot.

https://elinux.org/Jetson/General_debug

Dears,

There is no log output from NX board. Is there a method to check or debug the system when it does not any output.

Thank you.

Hi,

Have you ever flashed your board with sdkmanager? If it is just a NX module out of box, it may have nothing on it.

Dears,

We have flash the SD card with OS by using SDKmanager. But the system can not be boot.

Thank you.

Hi,

Are you able to see the log from UART during flash? Normally, it should have log during flash.
Please check the functionality of UART first.

Dears,

The UART can work and there is no any output form the UART. Thank you.

What does that mean the UART can work but no output from UART? Then how did you know the UART can work?

If you claimed your board can be flashed, then it should give out the UART log during flash process. Otherwise, means the UART is not working.

Dears,

Please refer to the attached.

It can identify the 4232. But there is no any interaction between NX. All data is 0x00 from NX.

0fd58e301e4a33e15d6453f15977252.png

But your board can be flashed successfully, right?

Dears,

Can the NX module connect with the Nano carrier board? Please confirm this. Thank you.

Yes, it can.

Got it.

Many thanks.

The whole picture of debug is like below

  1. NX+ your carrier board . Please confirm if current status is “you could flash the board successfully but no output from UART”.

  2. NX (flashed on your carrier board) + Nano devkit. Please dump the UART log on devkit and see if it could have log. It should have. This is very common usecase on our side too.

If (2) can work, probably means the UART on your board cannot work for some reason.

Got it. I will try it. Thanks for support.