We use the orin module and our customized board to bring up orin using SDK MANAGER, and the following error occurs.
1.emcc flash:
sdk manager log:
ERROR: might be timeout in USB write
orin Serial port log:
2.nvme flash:
sdk manager log:
ERROR: might be timeout in USB read
orin Serial port log:
There are no errors similar to emcc
There is also a development board we customized that does not have an HDMI interface reserved, so how can we complete the bring up without knowing the IP address? Thank you.
Do you know where the problem is and how to solve it? If so, please let us know.
You should try to share full text log but not these screenshot.
Sdkmanager does not support custom board either. Learn to use command line tool from BSP.
Thanks a lot,
Is there any specific command to flash orin that you can share?
Thank U，I will have a try.
After executing the flash command, an error occurred. The error on the host side is as follows:
flash.log (11.8 KB)
The error on the host side is as follows:
orin.log (25.8 KB)
May I double check you are talking about Orin 32GB module but not Orin 64GB or Orin Nano/NX?
Also, is same command able to flash same module if it is on NV devkit?
We are talking about the orin module, is there a big difference between 32GB and 64GB, I feel the main problem is that the orin serial port log cannot open the device block
Hi,
Since you are using custom board, your hardware design may be the problem here too.
That is why I need to ask did you ever try it on devkit because that is the only baseline that I can guarantee working.
We plan to try it on the developer kit tomorrow and synchronize the information with you.
I plan to use this orin module to connect to theboard of the developer kit. Is this possible?
I haven’t did that,i will have a try for this.
The programming was brought up successful after connecting to the development board. Do you have the circuit diagram of the development board?
Over the download center:
After flashing the machine on the development board, I put the machine on the custom board. It cannot be started, and the bootloader is stuck. The above is the normal orin serial port printing on the development version, and the bottom is the orin serial port printing on the custom board.
As I already told yesterday.
OK,Thanks a lot.After changing this, I need to recompile BootLoader and upgrade it. I haven’t seen instructions for compiling and upgrading BootLoader separately. Is there any corresponding guidance?
I am not sure why you think this needs to compile bootloader… this does not need. That is why document didn’t mention anything further.
Just configure the file and reflash the board and it would take effect.
