Need some materials and resources to verify ota related functions on the system

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.2.10884
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

  1. For OTA debugging, we need to obtain system partition table information (device node or mount point corresponding to each OTA partition) and its corresponding version image file or file system file.
  2. For OTA debugging, the upgraded partition needs to be able to read and write, please help open the read and write interface of this part of the partition to us;
  3. For OTA update, NVIDIA needs to provide us with partition slot management capabilities, including obtaining the current slot, switching slot after upgrade, and restarting interfaces for us to call;
  4. For OTA debugging, NVIDIA needs to provide us with different version packages of partitions to be upgraded for debugging and verification;

Dear @jiangwenjie,
I will check internally and update you on queries. Thank you

Dear @jiangwenjie,
OTA is not supported in DevZone release.

Hi,can you provide the resource packs and methods mentioned above?
We’ll build OTA capabilities on the development kits.

HI, We learned the following two things:

  1. “DU client” related API maybe get partition table and partiton images. And invoking “DU client” related API also can get partition R/W permission.
  2. “dupkg” already contain the relevant action in du_master.json file, we can verify and debug slot capability by “common_if_testapp” tool.

so, can you provide DU client(related sample) and dupkg tools, and accompanying guidance and instructions.

thanks!

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