How can use Jetson Xavier NX Carrier board with Orin NX module flash image

Hello,we buy a orin nx 16G module,want use on Jetson Xavier NX Carrier board,how can i flash image.

Hello @kevin.yu1

The p3509-a02+p3767-0000.conf file has been prepared for Orin modules with Xavier NX Dev. kit.

The sample flashing command look like this:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

~/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra


  •                                 *
    
  • Step 3: Start the flashing process *
  •                                 *
    

Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Timeout
Cleaning up…

The system worked on JetPack-5.1. However, we are facing the same issue on JetPack-5.1.1.

We are waiting the following post to someone will reply

who have the good idea flash image?

Actually the moderators know better.

I found @Jerry-W’s reply. He was be able to flash with SDK Manager

Just want to clarify. If this is custom board but not NV devkit, then every situation here is case by case. One successful case does not 100% mean you can copy it.

Dump the serial console log from the UART and it will tell you what gets timeout.

This is basically same as this topic I am talking about.

We read the documentation of Nvidia(Jetson Xavier NX Series Interface Comparison and Migration), we don’t use the functions of these different pins, but we can’t flash the system with the old nx carrier board and orin nx core board?Thanks

Hi,

前面已經說過了, 麻煩直接dump serial console log from uart. 我可以看你的uart lo判斷為何燒不過.
如果不提供的話, 我無從得知為何沒辦法燒 每個人不能燒的原因都不相同

Already mentioned in previous comment, please share the serial console log from uart. I can use the uart log to tell why you cannot flash.

If you don’t share such log, then it is not possible to know why it cannot flash.

hi,
we are facing the same issue
cmd log.txt (276.3 KB)
debug log.txt (72.1 KB)

Hi @a5ndri0s ,

Are you a co-worker or colleague of @kevin.yu1 ?

If not, please file new topic and add me there.

我使用这个命令烧录:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

uart debug信息见附件,帮忙看看是什么问题。谢谢。
debug.log (80.9 KB)

你是真的用這個command下去跑還是只是貼上來這裡的時候打錯?

flash_t234_gspi.xml

沒有gspi這種東西 只有qspi…

不好意思,贴错了,是flash_t234_qspi.xml

我重新更新了烧录跑完的log(debug.log)及烧录界面在上方

Hi,

不確定你之前有沒有用過orin AGX custom board的經驗. CVB eeprom讀取必須要設定成關閉

預設是開啟的狀況, 所以才有以下error

E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
E> eeprom: Failed to read I2C slave device
C> Task 0x0 failed (err: 0x1f1e050d)
E> Top caller module: I2C_DEV, error module: I2C, reason: 0x0d, aux_info: 0x05
I> Busy Spin

https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html?highlight=cvb#eeprom-modifications

谢谢,我们让软件看看

Someone asked this question in another thread, but it wasn’t actually answered before the Nvidia admin closed the thread.

I have several Xavier NX dev boards. There is no Orin NX Dev kit I’ve seen. I want to buy the Nvidia Orin NX product and use it in my Nvidia Xavier NX Dev board. If I plug it in without any custom firmware, will it damage my Dev board or Orin? Please don’t link to that compatibility doc link. The answer isn’t plainly in there and this is a simple, binary question and answer. I don’t care if all features work. I only want to know if Nvidia has designed this new SOM card (which has the same form factor as the previous generation) in such a way that if I swap the old SOM (Xavier NX) with the new one (Orin NX) it will cause damage to either product. This is a straight forward question by many customers. Please just provide the answer and not a link to a document for your customer to (hopefully) interpret correctly. I have already spotted several typos in that documentation anyway. Thank you.

A wrong software/firmware will not cause a immediate hardware problem.
But some functions which are not compatible may not work there. Again, this is not hardware problem. Just because what Orin supports are not same as Xavier.

Please don’t think this is just a yes or no answer here. We don’t know about your board design so we cannot say “yes, it will be totally fine on your board”.
But we can guarantee Xavier NX devkit carrier board can work with Orin NX module. If your board design is totally same as XNX devkit, then it may work fine.

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