gptpon command not listed in aurix console

Hi,

I am following the steps on DRIVE PDK 5.0.10.3 release to sync up time between aurix and Xavier A on DRIVE AGX DEV KIT. I found gptpon is an invalid command from aurix console. also help command only lists the following commands. please advise. thanks

aurixreset : Power cycle board including Aurix
cemode [read|write] [n] : Read or write CE Mode in inforom
cimrom get sku : Get the information from CIM I2C ROM
date [0x12345678] : Set date = 0x12345678 on Aurix in seconds(Unix style)
help : Shows all available commands supported
i2cread x y z n : Reads ‘n’ bytes from device ‘y’ at offset ‘z’ of I2C-controller ‘x’ (all hex-byte-values)
i2cscan [0|1] : Scan all connected I2C devices at I2C module 0 or 1
i2cwrite x y z n b0 b1 … : Writes ‘n’ bytes to device ‘y’ at offset ‘z’ , values Byte-b0, Byte-b1 … of I2C-controller ‘x’ ()
inforom [dump] : Dump the Inforom M24C02 content in hex format
poweron : Turn main power on and release Tegra resets
poweroff : Set the outputs to system power off state
readNvRam : Read NvRam content
setdio [0|1] [on|off] : Set DIO pin on Aurix ‘0 = AURIX_LED1 | 1 = AURIX_LED2’ to on/off
tegrarecovery [x1|x2|cvm] [on|off] : Set Tegra X1/X2/CVM in recovery mode
tegrareset [x1|x2|cvm] [h] : Reset Tegra X1/X2/CVM. Default is ‘X1’. If ‘h’ option is supplied, then hold the specified Tegra in .
cansetbr [a|b|c|d|e|f] [125|250|500|1000] [1000|2000] : Switch baudrate of requested CAN channel to supported baudrate
status : Display the Aurix internal status
versio

Dear jerryc_sf,

Could you please update Drive AGX PDK to the latest version(DRIVE Software 8.0)?
Aurix FW will be updated new version and then you can find command like below. Thanks.

shell> version
Info: Executing cmd: version, argc: 0, args:
SW Version: DRIVE-V5.0.13-E3550-EB-Aurix-ForHyperion-3.01.05
Compilation date: Nov 12 2018, 12:50:16
Command Executed
shell> help
Info: Executing cmd: help, argc: 0, args:
DEBUG: command_help()
aurixreset : Power cycle board including Aurix
cemode [read|write] [n] : Read or write CE Mode in inforom
cimrom get sku : Get the information from CIM I2C ROM
date [0x12345678] : Set date = 0x12345678 on Aurix in se)
help : Shows all available commands supportd
i2cread x y z n : Reads ‘n’ bytes from device ‘y’ at o)
i2cscan [0|1] : Scan all connected I2C devices at I21
i2cwrite x y z n b0 b1 … : Writes ‘n’ bytes to device ‘y’ at of)
inforom [dump] : Dump the Inforom M24C02 content in ht
poweron : Turn main power on and release Tegras
poweroff : Set the outputs to system power off e
readNvRam : Read NvRam content
setdio [0|1] [on|off] : Set DIO pin on Aurix '0 = AURIX_LED1f
tegrarecovery [x1|x2|cvm] [on|off] : Set Tegra X1/X2/CVM in recovery mode
tegrareset [x1|x2|cvm] [h] : Reset Tegra X1/X2/CVM. Default is 'X.
cansetbr [a|b|c|d|e|f] [125|250|500|1000] [1000|2000] : Switch baudrate of requested CAN chae
gptpon : Switch gPTP on (for AURIX)
gptpoff : Switch gPTP off (for AURIX, this is )
status : Display the Aurix internal status
bootstrap [x1|x2] [qspi|emmc|ufs] : Configure strap settings for boot mem
version : Shows the SW version
Command Executed

Thanks for your reply. I installed sdkmanager_0.9.9-2351_amd64.deb and I tried the update by falshing Xavier A&B in parallel or A only, unfortunately both failed to work.

a) error message from NV_FLASH_XAVIER_PDKFLASH_A_COMP.log:

/home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh: line 291: [: too many arguments
error-tool-tegrarcm-chipinfo – Failed to get UID of chip
bootburn flashing failed! error code = 50
Info: [ Component Install Finished with Error ]
Error: NV_FLASH_XAVIER_PDKFLASH_A_COMP command ./pdk_flash.sh -b e3550b03-t194a-es finished with error

b) error message from NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP.log

/home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh: line 291: [: too many arguments
error-tool-tegrarcm-chipinfo – Failed to get UID of chip

Generating Flashing-RCM Images
Sending bct and prerequisite binaries
Sending Blob for RCM blob to target
Applet version 01.00.0000
Sending blob
[. ] 002%
[… ] 005%
[… ] 008%
[… ] 011%
[… ] 014%
[… ] 016%
[… ] 019%
[… ] 022%
[… ] 025%
[… ] 028%
[… ] 031%
[… ] 033%
[… ] 036%
[… ] 039%
[… ] 042%
[… ] 045%
[… ] 047%
[… ] 050%
[… ] 053%
[… ] 056%
[… ] 059%
[… ] 062%
[… ] 064%
[… ] 067%
[… ] 070%
[… ] 073%
[… ] 076%
[… ] 078%
[… ] 081%
[… ] 084%
bootburn flashing failed! error code = 50
Info: [ Component Install Finished with Error ]
Error: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP command ./pdk_flash.sh -b e3550b03-t194-es finished with error

Dear jerryc_sf,

Did you put the board into Recovery mode for flashing?
Please the following step to flash the platform with a new image.

To flash the platform with a new image

  1. Connect the USB A cable to the platform:
    If no other USB/Serial adapters are connected to the host, the ttyUSB port are as follows:
    • AURIX UART: /dev/ttyUSB3
    • Tegra A UART: /dev/ttyUSB2
    • Tegra B UART: /dev/ttyUSB6
    If other USB serial adapters are already in use, the host takes relative numbering.
  2. Use the AURIX serial console to put the board into Recovery mode for flashing.
    tegrarecovery on
    tegrareset
    Where is x1 or x2.
  3. On the host system, verify that Tegra is in recovery mode using the following lsusb command to display the NVIDIA device.
    lsusb | grep -i nvidia
    Bus 001 Device 006: ID 0955:7721 Nvidia Corp
  4. Flash your board using one of the following commands:
    Xavier A (x1):
    ./bootburn.sh -b e3550xxx-t194a -B qspi
    Xavier B (x2):
    ./bootburn.sh -b e3550xxx-t194b -B qspi

Thank you SteveNV. I run the sdkmanager to flash but it failed and stopped. I could try your above steps manually, but I am afraid it won’t help update aurix firmware to the new version, right? how could I get the whole system upgraded to DRIVE Software 8.0?

By the way, I found there are two folders contain bootburn.sh, which one should I use if I try your steps?

./nvidia_sdk/DRIVE/Linux/5.0.10.3/SW/DrivePDK/drive-t186ref-foundation/tools/host/flashtools/bootburn/bootburn.sh
./nvidia_sdk/DRIVE/Linux/5.0.10.3/SW/DrivePDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn.sh

Dear jerryc_sf,

Regarding “I run the sdkmanager to flash but it failed and stopped.”, could you please provide the log?

I am not sure how to attach the log file. I am pasting a few lines before and after keyword “Failed” message in sdkm.log.

2019-01-30 16:02:28.174 - info: [ Package Install Finished Successfully ]
2019-01-30 16:02:28.175 - info: [ 57.64 MB released. Disk Avail: 160.61 GB ]
2019-01-30 16:02:28.175 - info: [ NV_DRIVE_HYPERION_TARGET_COMP Install took 0s ]
2019-01-30 16:02:28.175 - info: cmd finished success SDKM_END_CODE_SUCCESS_18e0ea89-a7af-498c-9698-286aa322f8b7
2019-01-30 16:02:28.175 - info: command finished successfully
2019-01-30 16:02:28.202 - info: install 'Hyperion-7.1' success
2019-01-30 16:02:40.011 - info: skip install Flash Xavier A+B in parallel
2019-01-30 16:02:40.012 - info: install 'Flash Xavier A+B in parallel' Skipped
2019-01-30 16:02:40.098 - info: Start to install 'Flash Xavier A'
2019-01-30 16:02:40.099 - info: estimated install timeout for NV_FLASH_XAVIER_PDKFLASH_A_COMP: 3600s
2019-01-30 16:02:40.202 - info: [ Disk Avail:160.61 GB ]
2019-01-30 16:02:40.202 - info: Using GenericInstaller to Install NV_FLASH_XAVIER_PDKFLASH_A_COMP
2019-01-30 16:02:40.203 - info: enter working directory: /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK
2019-01-30 16:02:40.203 - info: [ Component PreInstall Started ]
2019-01-30 16:02:40.203 - info: current working directory is /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK
2019-01-30 16:02:40.203 - info: exec_command: [ -e /dev/ttyUSB3 ] || echo Failed to flash device: detected no board connected to your host with USB cable. >&2
2019-01-30 16:02:40.203 - info: exec_command: sudo rm -f /var/lock/LCK..ttyUSB3 /var/lock/LCK..bootburn_seq /var/lock/LCK..bootburn
2019-01-30 16:02:40.214 - info: [ Component PreInstall Finished Successfully ]
2019-01-30 16:02:40.214 - info: [ Component Install Started ]
2019-01-30 16:02:40.215 - info: current working directory is /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK
2019-01-30 16:02:40.215 - info: exec_command: sudo adduser `whoami | tr -d '
2019-01-30 16:02:40.215 - info: '`  dialout
2019-01-30 16:02:40.253 - info: The user `jc' is already a member of `dialout'.
2019-01-30 16:02:40.254 - info: exec_command: sudo chmod a+rw /dev/ttyUSB*
2019-01-30 16:02:40.261 - info: exec_command: ./pdk_flash.sh -b e3550b03-t194a-es
2019-01-30 16:02:40.264 - info:
2019-01-30 16:02:40.264 - info: e3550b03-t194a-es will be flashed
2019-01-30 16:02:40.264 - info:
2019-01-30 16:02:40.265 - info: linux will be flashed
2019-01-30 16:02:40.266 - info: Make sure only one target  is connected to USB
2019-01-30 16:02:40.267 - info: and Aurix port is not open in minicom or another terminal
2019-01-30 16:02:40.267 - info:
2019-01-30 16:02:40.268 - info: +++++++++++++++++++++++++++++++++++++++++++++++++
2019-01-30 16:02:40.268 - info: make -f Makefile.bind BOARD=e3550b03-t194a PCT=linux >>>>>>
2019-01-30 16:02:40.268 - info: target SOC is t194
2019-01-30 16:02:41.768 - info: Target rootfs will be flashed into emmc
2019-01-30 16:02:41.936 - info: ./bootburn.sh -b e3550b03-t194a -B qspi -x /dev/ttyUSB3
2019-01-30 16:02:41.950 - info: Execute Xavier Script
2019-01-30 16:02:41.983 - info: Successfully acquired lock over /var/lock/LCK..bootburn
2019-01-30 16:02:41.983 - info: Successfully acquired lock over /var/lock/LCK..ttyUSB3
2019-01-30 16:02:41.996 - info: Read skuinfo from InfoRom...
2019-01-30 16:02:45.698 - info: Disabling SIGINT <Ctrl+C> temporarily
2019-01-30 16:02:48.412 - info: Setting Tegra-A on hold... Done
2019-01-30 16:02:51.119 - info: Setting Tegra-B on hold... Done
2019-01-30 16:02:56.607 - info: Setting Tegra-A in recovery... Done
2019-01-30 16:03:02.095 - info: Setting Tegra-B in recovery... Done
2019-01-30 16:03:02.184 - info: Enabling SIGINT <Ctrl+C>
2019-01-30 16:03:07.484 - info:
2019-01-30 16:03:07.484 - info:  ------------ Stack Trace ------------
2019-01-30 16:03:07.485 - info: stack frame 0 - 287 AbnormalTermination /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
2019-01-30 16:03:07.485 - info: stack frame 1 - 1084 GetTargetECID /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
2019-01-30 16:03:07.485 - info: stack frame 2 - 340 source /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_active.sh
2019-01-30 16:03:07.485 - info: stack frame 3 - 1014 main /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn/../bootburn_t19x//bootburn.sh
2019-01-30 16:03:07.486 - info: -------------------------------------
2019-01-30 16:03:07.486 - info:
2019-01-30 16:03:07.486 - info: /home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh: line 291: [: too many arguments
2019-01-30 16:03:07.487 - info: error-tool-tegrarcm-chipinfo -- Failed to get UID of chip
2019-01-30 16:03:12.617 - info: bootburn flashing failed! error code = 50
2019-01-30 16:03:12.617 - info: exit status 50
2019-01-30 16:03:12.618 - info: [ Component Install Finished with Error ]
2019-01-30 16:03:12.618 - error: NV_FLASH_XAVIER_PDKFLASH_A_COMP command ./pdk_flash.sh -b e3550b03-t194a-es finished with error
2019-01-30 16:03:12.618 - info:
2019-01-30 16:03:12.618 - info: [ 32.49 MB used. Disk Avail: 160.58 GB ]
2019-01-30 16:03:12.618 - info: [ NV_FLASH_XAVIER_PDKFLASH_A_COMP Install took 33s ]
2019-01-30 16:03:12.619 - info: command ./pdk_flash.sh -b e3550b03-t194a-es finished with error
2019-01-30 16:03:12.619 - info: cmd finished failure SDKM_END_CODE_FAILURE_35351985-d18d-4df2-b8d6-8aa19241bed7
2019-01-30 16:03:12.619 - error: command terminated with error
2019-01-30 16:03:12.620 - error: install 'Flash Xavier A' failure, command < cd '/home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW' ; /opt/nvidia/sdkmanager/resources/app.asar.unpacked/output/installUtils/adapter -a='install' -b='NV_DRIVE_LINUX_BUNDLE' -c='eyJpZCI6Ik5WX0ZMQVNIX1hBVklFUl9QREtGTEFTSF9BX0NPTVAiLCJuYW1lIjoiRmxhc2ggWGF2aWVyIEEiLCJkZXNjcmlwdGlvbiI6IkZsYXNoIFhhdmllciBBIHdpdGggVjUuMEwgU0RLIGNvbXBvbmVudHMuIiwiaXNWaXNpYmxlIjp0cnVlLCJsaWNlbnNlSWQiOiJOVl9EUklWRV9TTEFfREVDMjAxOCIsImlzRGV0ZWN0YWJsZUluc3RhbGwiOmZhbHNlLCJpc0luc3RhbGxQYXRoQ3VzdG9taXphYmxlIjp0cnVlLCJ0aW1lb3V0U2Vjb25kcyI6MzYwMCwidmVyc2lvbiI6IjUuMC4xMy4yIiwib3BlcmF0aW5nU3lzdGVtcyI6WyJ1YnVudHUxNDA0IiwidWJ1bnR1MTYwNCJdLCJpbnN0YWxsU2l6ZU1CIjoyMDUzLCJpbnN0YWxsUGF0aERlZmF1bHQiOiJ+L252c19wYWNrYWdlcyIsImRvd25sb2FkRmlsZXMiOltdLCJpbnN0YWxsUGFyYW1ldGVycyI6eyJpbnN0YWxsRGlyIjoiRHJpdmVTREsiLCJwcmVpbnN0YWxsQ29tbWFuZHMiOlt7InVzZXJDb21tYW5kIjoiWyAtZSAvZGV2L3R0eVVTQjMgXSB8fCBlY2hvIEZhaWxlZCB0byBmbGFzaCBkZXZpY2U6IGRldGVjdGVkIG5vIGJvYXJkIGNvbm5lY3RlZCB0byB5b3VyIGhvc3Qgd2l0aCBVU0IgY2FibGUuID4mMiJ9LHsidXNlckNvbW1hbmQiOiJzdWRvIHJtIC1mIC92YXIvbG9jay9MQ0suLnR0eVVTQjMgL3Zhci9sb2NrL0xDSy4uYm9vdGJ1cm5fc2VxIC92YXIvbG9jay9MQ0suLmJvb3RidXJuIn1dLCJpbnN0YWxsQ29tbWFuZHMiOlt7InVzZXJDb21tYW5kIjoic3VkbyBhZGR1c2VyIGB3aG9hbWkgfCB0ciAtZCAnXG4nYCAgZGlhbG91dCJ9LHsidXNlckNvbW1hbmQiOiJzdWRvIGNobW9kIGErcncgL2Rldi90dHlVU0IqIn0seyJ1c2VyQ29tbWFuZCI6Ii4vcGRrX2ZsYXNoLnNoIC1iIGUzNTUwYjAzLXQxOTRhLWVzIn1dfSwidGFyZ2V0SWRzIjpbIkREUFgiXSwiZGVwZW5kZW5jaWVzIjpbeyJpZCI6Ik5WX0dOVV9UT09MQ0hBSU5TX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEzLjIifSx7ImlkIjoiTlZfRFJJVkVfRk9VTkRBVElPTl9QQUNLQUdFU19TREtfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiI1LjAuMTMuMiJ9LHsiaWQiOiJOVl9EUklWRV9GT1VOREFUSU9OX09TU19DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMy4yIn0seyJpZCI6Ik5WX0UzNTUwX1NQRUNJRklDX1BBQ0tBR0VfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiI1LjAuMTMuMiJ9LHsiaWQiOiJOVl9PU1NfQU5EX05WX1BBQ0tBR0VTX1NES19DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMy4yIn0seyJpZCI6Ik5WX0RQWF9QQUNLQUdFU19DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMy4yIn0seyJpZCI6Ik5WX0FVUklYX1VQREFURVJfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiI1LjAuMTMuMiJ9LHsiaWQiOiJOVl9DVURBX1RBUkdFVF9MSU5VWF9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjEwLjAifSx7ImlkIjoiTlZfVEVOU09SUlRfVEFSR0VUX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNC4wIEdBIn0seyJpZCI6Ik5WX0RSSVZFX0lYX1RBUkdFVF9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjIuMSJ9LHsiaWQiOiJOVl9EUklWRV9BUl9UQVJHRVRfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiIxLjAifSx7ImlkIjoiTlZfRFJJVkVfSFlQRVJJT05fVEFSR0VUX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEzLjIifV0sImV4dGVybmFsX2RlcGVuZGVuY2llcyI6W10sInBhcmVudElEIjoiTlZfRFJJVkVfRkxBU0hfVEFSR0VUX0dST1VQIiwiYWN0aW9uIjoxLCJkb3dubG9hZEVycm9ycyI6W10sImV4ZWMiOiIvaG9tZS9qZXJyeS5jYW8vRG93bmxvYWRzL252aWRpYS9zZGttX2Rvd25sb2FkcyIsImluc3RhbGxQYXRoIjoiL2hvbWUvamVycnkuY2FvL252aWRpYS9udmlkaWFfc2RrL0RSSVZFL0xpbnV4LzUuMC4xMy4yL1NXIiwidGltZW91dENCIjpudWxsfQ==' -i='NV_FLASH_XAVIER_PDKFLASH_A_COMP' -v='5.0.13.2' -l='/home/jc/nvidia/nvidia_sdk/DRIVE/Linux/5.0.13.2/SW' -L='/home/jc/.nvsdkm/logs/DRIVE/Linux/5.0.13.2/SW' -p='22283' -u='/opt/nvidia/sdkmanager/resources/app.asar.unpacked/output/installUtils/NV_DRIVE_LINUX_BUNDLE/common/_installer/InstallUtil' -t='DDPX' -x='SDK' -e='/home/jc/Downloads/nvidia/sdkm_downloads' > terminated with error
2019-01-30 16:03:12.631 - info: skip install Flash Xavier B
2019-01-30 16:03:12.631 - info: install 'Flash Xavier B' Skipped
2019-01-30 16:03:13.741 - info: The overall duration (Download + Install) is 00:04:42
2019-01-30 16:03:13.742 - info:
Install summary of 26 components:

Install started on: 15:56:36 GMT-0800 (PST).

Install ended on: Wed Jan 30 2019 16:03:13 GMT-0800 (PST).

Install duration:  00:06:37 .

Install idle time: 00:02:10 .

Real install duration (duration - idle time): 00:04:27 .

Install 23 components.

    - Already Install 10 components.

Install failed 1 files.

Install skipped 2 files.

Install details:

- NV_CUDA_HOST_COMP: Already Installed.
- NV_TENSORRT_HOST_COMP: Already Installed.
- NV_DRIVE_AV_HOST_COMP: Already Installed.
- NV_DRIVE_AV_HOST_CROSS_COMPILE_LINUX_COMP: Already Installed.
- NV_DRIVE_AV_HOST_SAMPLES_COMP: Already Installed.
- NV_DRIVE_AR_HOST_COMP: Already Installed.
- NV_TEGRA_GRAPHICS_DEBUGGER_COMP: Already Installed.
- NV_NVIDIA_NSIGHT_SYSTEMS_COMP: Already Installed.
- NV_PERFWORKS_COMP: Already Installed.
- NV_DEVTOOLS_DOCS_LINUX_COMP: Already Installed.
- NV_GNU_TOOLCHAINS_COMP: Installed - 00:00:08 -start: 15:58:32 GMT-0800 (PST) - end: 15:58:41 GMT-0800 (PST).
- NV_DRIVE_FOUNDATION_PACKAGES_SDK_COMP: Installed - 00:00:08 -start: 15:58:41 GMT-0800 (PST) - end: 15:58:49 GMT-0800 (PST).
- NV_DRIVE_FOUNDATION_OSS_COMP: Installed - 00:00:04 -start: 15:58:49 GMT-0800 (PST) - end: 15:58:54 GMT-0800 (PST).
- NV_E3550_SPECIFIC_PACKAGE_COMP: Installed - 0.191s -start: 15:58:54 GMT-0800 (PST) - end: 15:58:54 GMT-0800 (PST).
- NV_OSS_AND_NV_PACKAGES_SDK_COMP: Installed - 00:02:36 -start: 15:58:54 GMT-0800 (PST) - end: 16:01:31 GMT-0800 (PST).
- NV_DPX_PACKAGES_COMP: Installed - 0.445s -start: 16:01:31 GMT-0800 (PST) - end: 16:01:31 GMT-0800 (PST).
- NV_AURIX_UPDATER_COMP: Installed - 0.190s -start: 16:01:31 GMT-0800 (PST) - end: 16:01:32 GMT-0800 (PST).
- NV_DRIVE_HYPERION_TARGET_COMP: Installed - 0.714s -start: 16:02:27 GMT-0800 (PST) - end: 16:02:28 GMT-0800 (PST).
- NV_CUDA_TARGET_LINUX_COMP: Installed - 00:00:05 -start: 16:01:32 GMT-0800 (PST) - end: 16:01:37 GMT-0800 (PST).
- NV_TENSORRT_TARGET_COMP: Installed - 00:00:03 -start: 16:01:37 GMT-0800 (PST) - end: 16:01:40 GMT-0800 (PST).
- NV_DRIVE_AV_TARGET_COMP: Installed - 00:00:41 -start: 16:01:41 GMT-0800 (PST) - end: 16:02:22 GMT-0800 (PST).
- NV_DRIVE_IX_TARGET_COMP: Installed - 00:00:03 -start: 16:02:22 GMT-0800 (PST) - end: 16:02:25 GMT-0800 (PST).
- NV_DRIVE_AR_TARGET_COMP: Installed - 00:00:01 -start: 16:02:26 GMT-0800 (PST) - end: 16:02:27 GMT-0800 (PST).
- NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP: Skipped.
- NV_FLASH_XAVIER_PDKFLASH_A_COMP: Failed - start: 16:02:40 GMT-0800 (PST) - end: 16:03:12 GMT-0800 (PST).
- NV_FLASH_XAVIER_PDKFLASH_B_COMP: Skipped.

2019-01-30 16:03:13.742 - error: flash failed
2019-01-30 16:03:13.750 - info:

********************** Completed install for bundle DRIVE Software 8.0 Linux for DRIVE AGX Developer Kit time: 30/01/19 16:03:13 is succeeded: false **********************
2019-01-30 16:03:37.500 - info: exporting logs from /home/jc/.nvsdkm/logs/DRIVE/Linux/5.0.13.2/SW

Dear jerryc_sf,

Could you please let me know the board part number?

and please upload full log. ~/.nvsdkm/sdkm.log

I had seen a similar error message when sdkmanager (or one of it’s child processes) wasn’t able to access USB device node. Does sdkmanager have access to /dev/bus/usb/*?

SteveNV, sdkm.log attached.

Thanks, punitagrawal. sdkmanager asked root permission during the installation, I guess it should have access to /dev/bus/usb
sdkm.log (2.19 MB)

Hi Jerry,

have a look here https://devtalk.nvidia.com/default/topic/1046975/drive-agx/sdkmanager-0-9-9-flash-agx-failed/2/?offset=21#5313645 and provide us all the information I have requested from Davy and Atsutaka as well.

Thanks.

Fabian

Hi Fabian,

I am using Ubuntu 16.04 with kernel version 4.4.0-142-generic. We have not decided to upgrade the system firmware yet. the reason is that I found out that the CUDA version will be upgraded to 10.0 from 9.2. Our engineers are extensively using 9.2 on the pc. so we need to evaluate it before upgrading to 10.0.

I do want to upgrade the firmware of Aurix to the new version ( to get the gptpon command). If I flash the aurix firmware only through windows, does it have any side effect later on when I run your updated version of sdkmanager?

Thanks
Jerry

Dear jerryc_sf,
I don’t think there will be a big side effect however if the PDK and Aurix FW do not match, there may be a problem.

Okay, we have decided to upgrade to the latest firmware. plan to use the following commands to upgrade Xavier_A and B respectively, based on the other post.

./bootburn.sh -b e3550b03-t194a -B qspi -x /dev/ttyUSB3
./bootburn.sh -b e3550b03-t194b -B qspi -x /dev/ttyUSB3

please let me know what script to use to flash firmware for Aurix and what firmware version to use? Should I flash Aurix firmware before or after flashing Xavier firmware?

Thanks
Jerry

Dear jerryc_sf,

Thank you for your update.

I think Aurix FW will be updated automatically when run the above command.

However if Aurix FW is not updated, you have to update it manually.
For flashing Aurix, please refer to Flashing AURIX part in NVIDIA Drive SoftWare 8.0 doc.
DRIVE OS -> Flahsing Basics -> Flashing AURIX.

Please check Aurix FW version with below command via HostPC.

$sudo minicom -D /dev/ttyUSB3

In Aurix termial.

shell> version
Info: Executing cmd: version, argc: 0, args:
SW Version: DRIVE-V5.0.13-E3550-EB-Aurix-ForHyperion-3.01.05
Compilation date: Nov 12 2018, 12:50:16
Command Executed
shell>

I managed to upgrade the firmware for aurix and Xavier A&B using the methods based the other posts. The tricky part was that I had to upgrade Xavier B first using sdkmanager, and then I can either upgrade A&B in parallel or just A only.

Now I got gptpon command from aurix console. I am trying to sync time on Xavier A&B to aurix. but the third command below failed to execute

timedatectl set-ntp 0
./phc2sys -s /dev/ptp0 -w -S 1.0 -O 0 &
./ptp4l -f ./gPTP_slave.cfg -p /dev/ptp0 -i eth0.200 -m -l 7

The error message is as below:

selected /dev/ptp0 as PTP clock
ioctl SIOCGIFHWADDR failed: No such device.
failed to generate a clock identity.

please advise.

Dear jerryc_sf,

Could you please help to check the following link and command? Thanks.

https://devtalk.nvidia.com/default/topic/1046714/drive-agx/linux-ptp-instructions-in-drive-sw-manual-fail/

First, go to https://www.epochconverter.com

and convert any arbitrary human readable date/time

to epoch time format - this will be a decimal

value so be sure to convert it to hex

On Aurix shell

Check current epoch time

date

Set epoch time

date 0x[epoch in hex format]

Confirm the time you set above

date

Enable gPTP

gptpon

On Tegra shell

Read system time

date

Take down br0.200

ifconfig br0.200 down

Create a new VLAN to communicate with Aurix

ip link add link eth0 name eth0.200 type vlan id 200

Set ip addr of eth0.200 (x.x.x.28 if Tegra A, x.x.x.29 if Tegra B)

ifconfig eth0.200 10.42.0.28
ifconfig eth0.200 up

Follow the normal procedure

cd ~/drive-t186ref-linux/samples/nvavb/daemons
timedatectl set-ntp 0
./phc2sys -s /dev/ptp0 -w -S 1.0 -O 0 &
./ptp4l -f ./gPTP_slave.cfg -p /dev/ptp0 -i eth0.200 -m -l 7

Verify system time is synced (might need a separate terminal)

date

Jerry,

Just to check the status, could you resolve the issue?

Fabian

Hi Fabian,

I did not. After flashing the new firmware, I found

  1. a nv_ptp_master.service is already started on xavier A, and nv_ptp_slave.service on xavier B, both on eth0. I am a little bit confused now. do I need to kill the processes started by nv_ptp_master.service and nv_ptp_slave.service first before running your scripts? also, your scripts use eth0.200 (of course, br0.200 down first). could you detail the difference?

  2. regardless if the rtc module is connected or not, after a cold reboot, aurix data reverts back to July 4, 1970.

Thanks
Jerry

Jerry,

br0.200 is the Ethernet bridge we are using.

Regarding 2) please open a bug request via the partners portal.

Fabian