Failed to execute sample_driveupdate

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.6.1.8175
1.6.0.8170
other

Host Machine Version
native Ubuntu 18.04
other

Judging from the following execution results, writing serve local_path="/home/nvidia/update" to /gos-a/content/cmd failed.

$ ./sample_driveupdate -d /home/nvidia/update/dumaster-metadata.json
[INFO]Client will connect to server
[INFO]Create a socket 127.0.0.1:0
[INFO]Connection to /gos-a not ready
Retrying connect to router. retries = 10
[INFO]Connection to /gos-a not ready
Retrying connect to router. retries = 9
[INFO]Peer is closed. Try to connect with magic word.
[INFO]Socket 0: 127.0.0.1:34270 <-> 127.0.0.1:5009, FD: 5 is connected.
[INFO]Handle 0x7f8f975a88, client request a connection
[INFO]Handle 0x7f8f975a88, client request a connection
[INFO]Remote node /gos-a is connected
[INFO]CONMGR-IVC: handle Id 0x110001 P2P connection established
serveCmd=serve local_path="/home/nvidia/update"
[ERR][dulink_remote_ops.c:1414]Remote operation returned failure
Error export files to DULINK space
Failed to serve File

Dear @mayinghua,
May I know the used platform and drive release version?

Drive OS is 5.2.0.
Platform is p3479a04-t194.

Dear @mayinghua,
Could you confirm if you have flashed Devzone release on p3479?

What is Devzone release ?
On the p3479a04-t194 platform, only the virtualization configuration of QNX OS is available. I added the virtualization configuration of the Linux OS to drive-t186ref-foundation.

I have tested the sample_driveupdate on e3550_t194a platform.
The same error occurred.
DRIVE OS Linux 5.2.0

Dear @mayinghua,
Devzone means, you logged in sdkmanager using developer.nvidia.com credentials and get the Drive release. It looks like you have not used Devzone release. Could you please confirm that?

I got the Drive release from sdkmanager.

I use dushell to export local files to /gos-a/dushell/files.

Execute the following command:
echo “deploy metadata=/gos-a/dushell/files/dumaster-metadata.json content_root=/gos-a/dushell/files” > /master/cmd

The tii plugin execution failed:
[INFO]Scheduler state: INSTALLING
[INFO]State written to listener 0 from element /tii: IDLE
[INFO]cmd: deploy
[INFO]State written to listener 0 from element /tii: INSTALLING
[INFO]The version of metadata: /gos-a/dushell/files/TII_TegraA.json is 1.0
[ERR][dutii_mdparser.c:884]Not support metadata v1 commands
[WARN]Fail to dutiiDeployMetadata: /gos-a/dushell/files/TII_TegraA.json
[INFO]State written to listener 0 from element /tii: ERROR
[WARN]Action ID 0 resulted in error state
[INFO]cmd: clear_error

The contents of the TII_TegraA.json file are as follows:

{
    "metaVersion" : "1.0",
    "procedure": [
        {
            "cmd":"install_brbct_mb1",
            "a_mb1_path":"2_mb1_zerosign.bin",
            "b_mb1_path":"3_mb1_zerosign.bin",
            "a_brbct_path":"A_bct_BR_zerosign.bct",
            "b_brbct_path":"B_bct_BR_zerosign.bct"
        },
        {
            "cmd":"install_img",
            "partition_name":"mem-bct",
            "img_fname":"B_bct_MEM_zerosign.bct"
        },
        {
            "cmd":"install_group_img",
            "img_group": [
                {
                    "partition_name":"bpmp-fw",
                    "img_fname":"B_11_bpmp_zerosign.bin"
                },
                {
                    "partition_name":"cpu-bootloader",
                    "img_fname":"B_9_qb_cpu_zerosign.bin"
                },
                {
                    "partition_name":"bpmp-fw-dtb",
                    "img_fname":"B_12_bpmp_zerosign.dtb"
                }
            ]
        },
        {
            "cmd":"install_ gpt",
            "guest_id":"1",
            
            "gpt_path":"B_1_1_PT.bin"
        },
        {
            "cmd":"install_pt_brbct",
            "pt_path":"4_PT.bin",
            "a_brbct_path":"A_bct_BR_zerosign.bct",
            "b_brbct_path":"B_bct_BR_zerosign.bct"
        },
        {
            "cmd":"switch_bootchain",
            "a_brbct_path":"A_bct_BR_zerosign.bct",
            "b_brbct_path":"B_bct_BR_zerosign.bct"
        },
	     {
		   "cmd":"reboot"
	     }
    ]
}

From the above results, tii does not support the v1 command. Can you provide a metadata example of the v2 version?

Dear @mayinghua,
Could you please check private message.

Dear @mayinghua,
Let me check internally and get back to you.