What is the definition and usage of dulink and ducc interfaces such as dulinkRead and DUCC_Request_RunLevel
Hello @wanghu and welcome to the NVIDIA developer forums.
Would you mind sharing on which platform you are developing? Because then I can redirect you to the correct sub-forums on this server where they will be able to assist you.
In general dulink and ducc are part of the Drive Update ecosystem that allows OTAs for our Drive Hardware offerings.
Thanks!
Hello @MarkusHoHo , the platform infomation as follows:
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
Software Version
DRIVE OS 6.0.6
Thanks!
I moved this to the correct category now.
Dear @wanghu,
FYI, drive update is not supported for SDK customers(i.e Devzone release)
Dear @SivaRamaKrishnaNV ,thanks for your reply.
I don’t understand what you said about “drive update is not supported for SDK customers”.
Based on what I read in the documentation “NVIDIA DRIVEUPDATE OVERVIEW.pdf”, as follows:
OVERVIEW - DRIVE Update architecture
DU plug-in
A component to perform tasks in support of update operations. DU plug-ins are managed by DU Master.
DU Master
A DU plug-in which manages all the other DU plug-ins. A single DU Master can manage multiple Tegra and runs in Update VM on Tegra A. The user can start an update by issuing the command to start deploying a package for update via DU Master interface.
DU TII
DRIVE Update Tegra Image Installer. A DU plug-in running in Update VM to perform storage update of the Xavier Soc that it is running on. It always updates partitions that belong to the Inactive Chain.
Content Server
A DU plug-in to export update payload and file-based content to be read by other plug-ins. Content Server runs in Guest OS on Xavier A. The user can expose the package files to DU Master and DU TII via Content Server interface.
DU Link
The communication protocol among all DU plug-ins, which enables the distributed interconnection among DU plug-ins with file-system-like topology.
DU Link Router
The router to connect DU Link network for interconnection among customer OTA application and DU plug-ins.
DUCC
DRIVE Update Command and Control interface for the user to get DU status, to control and interact with customer OTA application in the user’s OTA solution.
BHC
Boot Health Check. BHC DU plug-in is a validator type plug-in to provide the user with the interface to perform boot health check on the newly updated packages after update.
DU Boot Manager
A DU plug-in that handles bootchain selection and board-level reset on GPIO based bootchain selection board.
DUCC API:
Drive Update Command and Control interface is used for the user to control and interact with customer OTA application in the user’s OTA solution.It is provided to the user as a shared library libnvducc.so in Guest OS.C APls are declared in ducc.h header file.
DU Link API:
DU Link interface provides C function APls for the user to access the exposed DU Link file node interfaces like that of DU Master and Content Server. It is provided by libnvdulink.so shared library. C APIs are declared in dulink.h header file.
In my ubuntu system, I have found libnvdulink.so and libnvducc.so.
According to the documents-direct_driveupdate.py, I have a general understanding of the use of dulink api(i.e dulinkRead), but I have not found the use of ducc api.
Looking forward to your reply.
Thanks!
Dear @wanghu,
Just to clarify, ducc.h and dulink.h are part of PDK release. The devZone release(SDK release) don’t have them.