Directdu script not working

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
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.3.10904
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

Hi!

I am working with the following scripts:

  • dupkg: found on the docker dir: /drive/drive-foundation/tools/driveupdate/dupkg
  • directdu: found on the docker dir: /drive/drive-foundation/tools/driveupdate/directdu

Currently I am using the dupkg to create a package:

HOST_SRC=/drive/drive-foundation/tools/driveupdate/delta_tools/test_dir
SRC_NAME=ridgerun-ota-test.py
TARGET_DIR=/rgonzalez/test
OUTPUT_DIR=/drive/ricardo

dupkg gen --template dupkg_sample_template --in SAMPLE_SRC=$HOST_SRC SAMPLE_NAME=$SRC_NAME DESTINATION_SRC=$TARGET_DIR --out $OUTPUT_DIR

# Output
DRIVE Update Packaging Tool
Version 1.4.6

Generating packages...  Done

When trying to send it to my target device with directdu script I get the following output:

python3 direct_driveupdate.py -p /drive/ricardo/ -t 10.251.101.68 --results-file /drive/drive-foundation/tools/driveupdate/log.json --log-file /drive/drive-foundation/tools/driveupdate/log.txt --target-controlled -v
2024-07-23 19:11:22,376 - [INFO]Connecting to target board
2024-07-23 19:11:22,377 - [DEBUG]Wait 1 second before next retry
2024-07-23 19:11:22,377 - [DEBUG][INFO]Client will connect to server
2024-07-23 19:11:22,377 - [DEBUG][INFO]Create a connection on 0.0.0.0:0
2024-07-23 19:11:22,377 - [DEBUG][INFO]Connection to /gos-a not ready in dulinkRemoteOpReadAttrSize
2024-07-23 19:11:23,378 - [DEBUG]Wait 1 second before next retry
2024-07-23 19:11:23,379 - [DEBUG][INFO]Establishing 10.251.101.39:52450 <-> 10.251.101.68:4455, FD 9.
2024-07-23 19:11:23,380 - [DEBUG][INFO]Connection to /gos-a not ready in dulinkRemoteOpReadAttrSize
2024-07-23 19:11:23,482 - [DEBUG][INFO]Peer is closed. Try to connect with magic word.
2024-07-23 19:11:23,584 - [DEBUG][INFO]Establishing 10.251.101.39:52456 <-> 10.251.101.68:4455, FD 9.
2024-07-23 19:11:23,585 - [DEBUG][INFO]Socket 0: 0.0.0.0:52456 <-> 10.251.101.68:4455, FD: 9 is connected.
2024-07-23 19:11:23,586 - [DEBUG][INFO]Handle 0x7fc255af5270, client request a connection
2024-07-23 19:11:23,586 - [DEBUG][INFO]Handle 0x7fc255af5270, client request a connection
2024-07-23 19:11:23,587 - [DEBUG][INFO]Remote node /gos-a is connected
2024-07-23 19:11:24,381 - [INFO]Target board connected
2024-07-23 19:11:24,386 - [INFO]Trigger update: deploy metadata=/gos-a/ddu/du_master.json content_root=/gos-a/ddu
2024-07-23 19:11:24,389 - [INFO]Update has been successfully triggered
Progress: [****************************************] 100 %2024-07-23 19:11:24,392 - [INFO]Update state STATE_DORMANT, Update complete!
2024-07-23 19:11:24,891 - [INFO]Update completed!
Successfully deployed package /drive/ricardo/
Please see /drive/drive-foundation/tools/driveupdate/log.txt for logs of the run
Please see /drive/drive-foundation/tools/driveupdate/log.json for detailed stats
2024-07-23 19:11:24,893 - [DEBUG]

When checking on my target device for the package I cant find it on /rgonzalez/test/ dir.

Do you know what is happening here? Where is the package going?

3

Dear @ricardo.gonzalez1,
The direct_driveupdate.py is used to update the DriveOS on target board with the host update package path provided -p option, it’s not used to copy package from host to target environment.

The log shows DriveUpdate running successfully, it’s an expected behavior.

4

Hi, @SivaRamaKrishnaNV,

Thanks for the explanation!

I tested it again after copying the package onto the target board via ssh. I ran the api inside the target board and got an error:

nvidia@tegra-ubuntu:~/rgonzalez/ota/directdu$ python3 direct_driveupdate.py -p ~/rgonzalez/test-pkg-ricardo/ --results-file log.json --log-file log.txt -v
2024-07-30 17:58:17,620 - [INFO]Connecting to target board
2024-07-30 17:58:17,621 - [DEBUG]Wait 1 second before next retry
2024-07-30 17:58:18,622 - [DEBUG]Wait 1 second before next retry
2024-07-30 17:58:19,623 - [INFO]Target board connected
2024-07-30 17:58:19,625 - [INFO]Trigger update: deploy metadata=/gos-a/ddu/du_master.json content_root=/gos-a/ddu
2024-07-30 17:58:19,627 - [INFO]Update has been successfully triggered
Progress: [|                                       ] 0 %2024-07-30 18:02:30,142 - [ERROR]Update Failed! STATE_UPDATE_FAILED
2024-07-30 18:02:30,403 - [DEBUG]  

Error running Direct Drive Update.
Failed to deploy DU package.
2024-07-30 18:02:30,403 - [ERROR]Error running Direct Drive Update.
Failed to deploy DU package.

What can be happening? I also added the –target-controlled flag and got the same error.

5

Hi @SivaRamaKrishnaNV can you help us with this?

7

Driveupdate is not supported on DRIVE OS SDK

10

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