Hello,
i’m trying to upgrade or flash process from 35.5.0 to 36.3 with ROOTFS A/B. When flashing the APP_b partition, the flash seems to be stuck and fails when writing the App partition b.
I am flashing a custom BSP with l4t_initrd_flash.sh (23.0 KB).
Also, the size of the UDA partition does not seem to be auto resized.
Thanks for the support.
Hi jan-rs,
Are you using the devkit or custom board for Orin NX?
Do you use the exact same partition layout file to generate OTA package?
Please share the full log when you generate OTA package and also the log when you run reboot to trigger OTA update.
Hi KevinFFF,
I am using a custom board.
I am not using the OTA package, i am only trying to flash the latest 36.3 release.
Okay, I thought you hit the issue during OTA process.
To flash the custom carrier board, have you requested the custom BSP package from your vendor for Jetpack 6?
Please also share the full flash log for further check.
Sorry to jump in the middle of this thread, but I have a question: If the BSP provided by my vendor contains JetPack 5, is there any possibility of upgrading it to JetPack 6, or does the vendor have to do it?
The vendor has to do it. We don’t know what is their hardware detail.
The software we can provided is only for NV devkit.
Thanks for your answer. I understand you will not deliver sw for their custom boards… My question was just trying to find out if there’s a way to update to jetpack 6 from a jetpack 5 BSP without the vendor intervention… I’ve seen people on the forum saying they’ve upgraded the same custom board I have (the vendor is yahboom) to JetPack 6, while the vendor published BSPs are based on JP5
Your board might have chance to get broken interface after doing so. Most likely the usb port won’t work if you tried to upgrade the BSP without the help from vendor.
Hi @KevinFFF ,
You can find the full flash log here.
The kernel and bsp are available on GitHub. I am currently building the kernel before flashing.
Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.8oOH8n4VNb. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2"
Cleaning up...
Do you mount the NFS for your rootfs on your host?
Please share the command you used to flash the board.
I’m using the l4t_initrd_flash command for flashing:
sudo ROOTFS_AB=1 \
BOARDID=3767 \
BOARDSKU=0000 \
FAB=300 \
BOARDREV=M.1 \
EXT_NUM_SECTORS=976562499 \
./tools/kernel_flash/l4t_initrd_flash.sh \
-S 25GiB \
--external-device nvme0n1p1 \
-c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_ab.xml \
-p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs \
--no-flash \
--network usb0 \
jetson-orin-nano-devkit internal
and
sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0
If you have the option of USB flashing port enabled coming out the unit, where you can force the unit to recovery mode using the “sudo reboot -force --forced-recovery” your self
And you can set up a host PC, download the BSP for jetpack 6.0 and do the flashing yourself, if you understand the steps to flash clearly from Nvidia developer user guide website
I think I kind of understand the steps, but I don’t want to end up with a briked board… Would love to have a guide from Yahoom, or at least someone who has the same board and is able to share the process followed.
You don’t need to add ROOTFS_AB=1 in this command since this parameter is used for board config to select the correct partition layout and you’ve generated the package in previous command.
Since you are using the custom carrier board, we would suggest you request the custom BSP package from your vendor first.
Is the board designed by you?
Or you are just using the BSP package and Kernel source released by your vendor?
It seems " orin_nx_JP6_0_bsp.tar.xz" the one you need.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.