I want to install the latest DriveWorks on P2379 with SDKManager 188.8.131.5210
and so I have downloaded all packages and after flashing the Tegra A and B successfully (at least it seems so)
I can see all target packages status “OS image ready”
What has to be done, so that SDK manager installs them on the target?
I want to install the latest DriveWorks on P2379 with SDKManager 184.108.40.20610
You need to select Target and flash via sdkmanger. Please check https://docs.nvidia.com/sdk-manager/install-with-sdkm-drive/index.html for installation steps
Sorry, I might have been a little bit too ambigious,
All 4 SDKManager installation steps seem to be successful, and in step 3 I have selected the target “Flash Tegra A and B”. See the screenshot
But no OS image has been updated on the target.
Here is the log extract and there is an error 1001 in step 3
20:56:42.231 - info: Event: NV_DRIVEWORKS_TARGET_COMP@PX2_AUTOCHAUFFEUR - drive-t186ref-linux-220.127.116.11-12606092-aarch64-driveworks-v1.2.400-a7f5475-478955.run - finished downloading
20:56:42.231 - info: Event: NV_DRIVE_WORKS_TARGET_GROUP@PX2_AUTOCHAUFFEUR - finished downloading
20:56:42.239 - info: All required files were downloaded
20:56:49.048 - debug: running command < true >
20:56:49.052 - info: cmd finished success SDKM_END_CODE_SUCCESS_0e495776-2262-4c3e-8cc4-1296a303c86f
20:56:49.052 - info: command finished successfully
20:56:49.055 - debug: running command < stat /dev/ttyUSB1 >
20:56:49.057 - info: File: ‘/dev/ttyUSB1’
20:56:49.057 - info: Size: 0 Blocks: 0 IO Block: 4096 character special file
20:56:49.058 - info: Device: 6h/6d Inode: 538 Links: 1 Device type: bc,1
20:56:49.058 - info: Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 20/ dialout)
20:56:49.058 - info: Access: 2020-11-17 18:27:57.135348380 +0100
20:56:49.058 - info: Modify: 2020-11-17 18:27:57.135348380 +0100
20:56:49.058 - info: Change: 2020-11-17 17:43:37.135348380 +0100
20:56:49.062 - info: Birth: -
20:56:49.062 - info: cmd finished success SDKM_END_CODE_SUCCESS_041b2519-a54b-4e58-8847-b8f4c954de36
20:56:49.062 - info: command finished successfully
20:56:49.064 - debug: running command < true >
20:56:49.067 - info: cmd finished success SDKM_END_CODE_SUCCESS_fa1f1a3d-0fe4-4d90-9318-723ac3ba768e
20:56:49.068 - info: command finished successfully
20:56:49.074 - debug: running command < lsof /dev/ttyUSB1 2>/dev/null >
20:56:49.250 - debug: cmd finished failure SDKM_END_CODE_FAILURE_5844be3d-14f9-4f42-a997-c9b8720f69d3_1
20:56:49.250 - error: command error code: 1
20:56:49.250 - info: Event: - error code is: 1001
20:56:49.250 - warn: Failed to get component from group data map for
20:56:49.250 - debug: command terminated with error
20:56:49.254 - info: Dialog was closed: pre-flash dialog. Duration: 00:00:07
20:56:49.254 - info: #### dialog event: Dialog was closed: pre-flash
20:56:49.254 - info: #### dialog timing: Dialog timing: pre-flash 00:00:07
20:56:49.254 - info: Event: NV_FLASH_TEGRA_A_COMP@PX2_AUTOCHAUFFEUR - skip started
20:56:49.255 - info: Event: NV_FLASH_TEGRA_A_COMP@PX2_AUTOCHAUFFEUR - skip ended
20:56:49.256 - info: Event: NV_FLASH_TEGRA_B_COMP@PX2_AUTOCHAUFFEUR - skip started
20:56:49.256 - info: Event: NV_FLASH_TEGRA_B_COMP@PX2_AUTOCHAUFFEUR - skip ended
20:56:49.279 - info: memInfo [total: 35.27GB, free: 407.22MB, available: 30.66GB]
20:56:49.279 - info: Event: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR - install started
20:56:49.280 - info: estimated install timeout for NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP: 3600s
20:56:49.298 - debug: running command < true >
20:56:49.305 - info: cmd finished success SDKM_END_CODE_SUCCESS_6b1b8353-bd5a-4c94-b78f-90b4aed1eb45
20:56:49.305 - info: command finished successfully
20:56:49.308 - debug: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR: using adapter to install NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR to /home/cuda/nvidia/nvidia_sdk/DRIVE_OS_18.104.22.168_SDK_with_DriveWorks_Linux_OS_PX2_AUTOCHAUFFEUR
20:56:49.316 - info: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR: Return success directly for empty component
20:56:49.321 - info: cmd finished success SDKM_END_CODE_SUCCESS_daf94ae2-e3e4-4a2c-96d6-cc877f53cb2e
20:56:49.321 - info: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR: command finished successfully
20:56:49.327 - info: Event: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR - install ended
20:56:49.328 - info: Summary: NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP@PX2_AUTOCHAUFFEUR: Install completed successfully.
20:56:49.329 - info: Stopping all currently running download services
20:56:49.330 - info: The overall duration (Download + Install) is 00:00:07
20:56:49.331 - info: All done!
20:56:49.398 - info: *** Dialogs Timing Summary ***
pre-flash: duration: 00:00:07
*** End of Dialogs Timing Summary ***
20:56:49.401 - info:
*** Download Summary ***
- Bundle: DRIVE OS 22.214.171.124 SDK with DriveWorks Linux for DRIVE PX 2 AutoChauffeur - Download server: - 0B downloaded of 20.11GB - Download started on: Tue Nov 17 2020 20:56:42 GMT+0100 (Central European Standard Time). - Download ended on: Tue Nov 17 2020 20:56:49 GMT+0100 (Central European Standard Time). - Download duration: 00:00:07. - Average total download speed: 0B/s = total downloaded bytes / download duration. - Average total bandwidth: 0B/s, average accumulation of all file chunk's speed, downloaded concurrently. - Average file chunk's download speed: 0B/s, average of all downloaded file chunk's speed. - Max 6 concurrent files using 6 threads. Total 25 files: - 0 downloaded, 0 cached, 0 failed, 25 skipped
could you please share the complete logs?( ~/.nvsdkm/logs and ~/.nvsdkm/sdkm.log files)
Here we go.
sdkm-2020-11-17-20-06-57.log.gz (11.7 KB)
Is it possible, that SDK Manager prefers NVOnline Accounts - and not Nvidia Developer accounts?
If I log into SDKMAnager with my NVOnline account, SDKM tells me, that there are no packages available for me.
If I log into SDKM with my Nvidia Developer account, SDKM shows full access to Drive PX2 Packages, but the sdkm.log comes up with
10:53:10.318 - info: validating release: DRIVE OS 126.96.36.199 PDK 10:53:10.318 - error: Not NVOnline user 10:53:10.319 - warn: No access to release DRIVE OS 188.8.131.52 PDK. Message invalid level3 json path 10:53:10.319 - info: Event: Login Progress: Loading and processing available products...
and that’s why I can not install the PDK on the target machine??
NVOnline accounts are different from Developer account. The releases for these accounts also different based on the engagement with NVIDIA. Could you please share the requested ~/.nvsdkm.logs folder as well?
Here is the complete exported log.
SDKM_logs_DRIVE_OS_184.108.40.206_SDK_with_DriveWorks_Linux_for_DRIVE_PX_2_AutoChauffeur_2020-11-18_14-30-59.zip (63.0 KB)
any updates on the issue?
I could see in the log the flashing part is skipped due to some error. I am checking with engineering team and waiting for an update.
May I know which DRIVE version the board already has before you flash? Is it just an upgrade or re-flashing latest release?
We could identify the root cause and working on solution. We will update you soon
Great. I am eager to upgrade.
please go to SDK Manager v1.3 install location, back up the binary back up the binary /opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter , and replace it by the attached one adapter.txt ( Please remove .txt extension)
I have done the file exchange, removed the .nvsdkm directory and retried to install on the AutoCruise, but flashing the SW ended with a “permission denied” error accessing /dev/ttyUSB1, see the attached screenshot and log.
SDKM_logs_DRIVE_OS_220.127.116.11_SDK_with_DriveWorks_Linux_for_DRIVE_PX_2_AutoCruise_2020-11-30_16-52-37.zip (209.1 KB)
Can you please tell me, what to do next?
Is the target connected to host? please share lssub output.
Could you check accessing aurix (via dev/ttyUSB1 serial port) using minicom and confirm?
I can connect via minicom to aurix shell
I can ping the p3479 at eth0 within the 10.42.0.x net
I cannot ping Tegra A (10.42.0.28) and
I cannot ping Aurix (10.42.0.146)
aurix shell> status reveals
Info: Executing cmd: status, argc: 0, args:
Alive : 19:01:14
CPU load Core 0: 8%
CPU load max Core 0: 9%
CPU load Core 1: 0%
CPU load max Core 1: 0%
CPU load Core 2: 0%
CPU load max Core 2: 0%
IP-address (Tegra): 10.42.0.28
IP-address (AURIX): 10.42.0.146
MAC-address (Tegra): 0x0000000000000000
MAC-address (AURIX): 0x0000000000000000
Bus 002 Device 005: ID 04f2:1113 Chicony Electronics Co., Ltd
Bus 002 Device 004: ID 1bcf:08a0 Sunplus Innovation Technology Inc.
Bus 002 Device 006: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 002 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Do I need some preparation on the p3407 side for flashing? Documentation on this is rather slim.
Have you closed all the serial connections from host before flashing target?
Yes, all minicom connections have been closed with .
Ctrl a x
I could see in the earlier logs that you were trying to flash autochauffeur.
Now in the latest logs, I could see autocruise.
Is it another board you trying to flash? If so, what is the status of autochauffer?
Could you check running below command on host terminal when board is connected to host. If there is permission issue, please close other terminal/minicom window that is opening the aurix port then retry.
stty -F /dev/ttyUSB1 115200 echo tegrarecovery on > /dev/ttyUSB1 echo tegrareset > /dev/ttyUSB1