Image based OTA for jetson-orin-nano-devkit and costum board

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
,
1

Hello

I am currently testing the image based ota for my jetson-orin-nano-devkit.
Using the l4t_generate_ota_package.sh I found out that the jetson-orin-nano-devkit is currently not supported.
Is there a way to tweak the scripts such that I can test the image based ota for my jetson-orin-nano-devkit?

Furthermore, I generated a costum board configuration (with adjusted Device Tree ect) that I was able to use with the flashing script. Is there a way such that I can use my costum board name for the l4t_generate_ota_package.sh, e.g. providing the name of my board instead of jetson-orin-nano-devkit, similar as I do it when using the flash script?

Any advise and help is highly appriciated
Kind regards

3

Hi knezevic,

For the Orin-NX/Nano, since the r35.3 is the first public release, so we will support image-based OTA from r35.3 to r35.3+ in the next JP5.1.2 (r35.4).

Do you mean that you create another board configuration for the devkit? Or the custom board?
Image-based OTA should also work for the custom board if you don’t modify the partition layout or the custom data in BCT.

4

Do you mean that you create another board configuration for the devkit? Or the custom board?
Image-based OTA should also work for the custom board if you don’t modify the partition layout or the custom data in BCT.

I mean for the custom board.

What I mean is that when I do the flashing, i use the following command:
sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 **MY_BOARD_NAME** internal

Now I could not find instructions to make generating the ota packages with the command:
sudo ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh **MY_BOARD_NAME** R35-3
work.

Am I missing something? Dont the files present in the mentioned .conf file get updated with image based OTA?

5

What do you mean here?
You could refer to the following instruction to use this script, but it seems not supported for Orin NX/Nano yet.
Software Packages and the Update Mechanism — Steps Performed on the Host Machine

6

What do you mean here?

What I mean is that I followed the following guide to adjust the pinmux/device tree to my own hardware:
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-325/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/adaptation_and_bringup_tx2.html

This resulted in a costum configuration file where now my pinmux/device tree is taken.
When I flash my board, I can use the name of my costum hardware configuration file as described in the previous post.
Now my question is what i need to do so i can use my own configuration file name when executing the l4t_generate_ota_package.sh script.

7

The guide you are referring is for TX2. Are you using Orin Nano or TX2?

For Orin Nano, please refer to the following instruction for pinmux configuration.
Jetson Module Adaptation and Bring-Up - Jetson Orin NX and Nano Series

8

Thanks for the Link.
I am using the Orin Nano. But that is not the point.
My question still remains.
My question is what i need to do so i can use my own configuration file name when executing the l4t_generate_ota_package.sh script.

9

Yes, you could use your custom board configuration for image-based OTA.
For Orin Nano, I would suggest verifying it with upcoming JP5.1.2 for image-based OTA.

10

Thanks for the reply. Is there any date when the next JP is released this month?

11

It should be released in the early Aug.
Thanks!

13

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