could you confirm that orin nx devkit 16 gb module can not be used with nx devkit board or otherwise?
Hi,
It can work with Xavier NX devkit board. Older L4T release does not support the module so please use Jetpack 4.6.2/4.6.3 or Jetpack 5 release. Please use Jetpack 5.1 release.
@DaneLLL
Thank you for your reply
Could you also extend on the heatsink, please? How can it be addressed if we just got the nx devkit board then get the orin module? What are the options for the heatsink for the production orin nx module?
Hi,
My apology I thought you were asking about Xavier NX 16 GB module, and there was mistake in previous command. Have corrected it.
For the query about heatsink, so you have got Orin NX module and there is no heatsink or fan with it?
Hi @DaneLLL
To clarify : having NX devkit, having ordered NX orin 16 Gb module.
What are the options to use the Orin NX module with the NX devkit?
How does it address the heatsink issue won’t it emerge?
Hi,
The config file for Orin NX module + Xavier NX devkit is in Jetpack 5.1:
nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/p3509-a02+p3767-0000.conf
Once you get the Orin NX module, you can try to flash the device through initrd command.
@DaneLLL
Hi ,
Thank you for following up.
Could you extend what exactly initrd command to use for orin nx 16gb module on nx devkit carrier board , please?
I guess the arguments need to exactly match the setup otherwise it won’t work
so as basis we can use this beginning
sudo ./tools/kernel_flash/l4t_initrd_flash.sh
but what is the complete sequence?
@DaneLLL
we got the module
could you supply the flashing command to flash with initrd, please? so that lashing will be on nx devkit with nx orin 16 gb module, please?
Is the command below exactly correct?
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0nlpl -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_gspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal
Thanks
AV
Hi,
Your command is precise. Please insert NVMe SSD to carrier board and give it a try.
For using initrd, please check the README:
/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt
@DaneLLL
Comment?
/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra$ 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_gspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 internal
/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_gspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 internal
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign -c p3509-a02+p3767-0000 internal
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 2.1
# User release: 0.0
###############################################################################
Board ID() version() sku() revision()
Chip SKU() ramcode() fuselevel(fuselevel_production) board_FAB()
emc_opt_disable_fuse:(0)
Error: missing cfgfile (/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/p3509-a02+p3767-0000).
-------------------
However:
/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra$ ls p3509-a02+p3767-0000
p3509-a02+p3767-0000-as-p3767-0001.conf p3509-a02+p3767-0000-as-p3767-0004.conf p3509-a02+p3767-0000-maxn.conf
Replied in another thread.
@WayneWWW I am not sure you addressed the cause of the error.
after fresh sdkmanager install the resulting folder has:
mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra$ ls | grep p3509-a02+p3767-0000
p3509-a02+p3767-0000-as-p3767-0001.conf
p3509-a02+p3767-0000-as-p3767-0003.conf
p3509-a02+p3767-0000-as-p3767-0004.conf
p3509-a02+p3767-0000.conf
p3509-a02+p3767-0000-maxn.conf
but the execution returns the same error:
/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra$ 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_gspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 internal
/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_gspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 internal
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign -c p3509-a02+p3767-0000 internal
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 2.1
# User release: 0.0
###############################################################################
Board ID() version() sku() revision()
Chip SKU() ramcode() fuselevel(fuselevel_production) board_FAB()
emc_opt_disable_fuse:(0)
Error: missing cfgfile (/mnt/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/p3509-a02+p3767-0000).
why doesn’t the installer see the conf file? due to internal processing error?
it only worked after renaming the file p3509-a02+p3767-0000.conf to p3509-a02+p3767-0000
Did you actually remove the “.conf” file extension? It makes me think there is an error inside of the file which refers to the .conf file (perhaps that file is missing the .conf extension).
1 Like
there is another issue in the loop
as the module has been supploed without heatsink [ orin nx production module] it will overheat if just put it into nx devkit, right?
Are there any cooling solutions around for that module specifically?
Hi,
Please check if you have other Xavier NX developer kit. You can move the fan to Orin NX module and try.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.