Xavier a doesn't work for Nvidia AGX Pegasus

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

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.6 and DriveWorks 4.0
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.7.1.8928
other

Host Machine Version
native Ubuntu 18.04
other

Hi expert,
Xavier-a doesn’t work for AGX Pegasus, only xavier-b can work, include HMDI, USB, network etc…
Use device-query, only find one device for xavier-b.
Please support to guide us to use xavier-a.

thanks

2

Hi, @user103454

Please help to elaborate on how you checked with “device-query”. Is it a command? How did you run it?

3

Dear @user103454,
Please clarify below things

  1. Which DRIVE release is flashed on Xavier A and Xavier B? Since when you notice this issue like after flashing or running any application?
  2. Could you check connecting Tegra A using sudo minicom -D /dev/ttyUSB2. If it does not work check running tegrarecovey x1 off, tegrareset x1,poweroff, poweron commands on aurix console` and see if you can get access to Xavier A console via minicom.
  3. Do you see any issues in boot log via minicom when you restart the machine, if so, please share the aurix console, tegra console booting logs.
4

Nvidia CUDA tool, use for to check cuda device.
Locate at: cuda/samples/1_Utilities/deviceQuery/

5

Hi expert,

  1. DRIVE Software 9.0.
  2. we can’t input any character in aurix console. aurix log when restart the system as attachment.
    console.log (267.1 KB)
6

Dear @user103454,
Just to clarify, when you run deviceQuery on Tegra A, it shows only GPU devices associated with Tegra A and not Tegra B.
Could you share the output log of lsusb on host after connecting host(any usb port) and target(debug port) via usb-usb cable?
Also, please double check connecting Tegra A, Tegra B, Aurix consoles and confirm which are working for you. Press ENTER on each console if you don’t see any output
For Tegra A: sudo minicom -D /dev/ttyUSB2
For Tegra B: sudo minicom -D /dev/ttyUSB6
For Aurix : sudo minicom -D /dev/ttyUSB3

7

Tegra-B, Aurix are work.
Tegra-A doesn’t work, the log as previous log: console.log.
lADPJv8gRrF1zerNAjjNAvQ_756_568.jpg_620x10000q90g

8

Dear @user103454,
If you have access to Aurix console, could you run the above mentioned commands in earlier post and check

9

Run the following command: tegrarecovey x1 off , tegrareset x1 , poweroff , poweron, tegra-a also donesn’t work, the log is the same as above.

10

Dear @user103454,
As I understand, Tegra A has DRIVE SW 9.0 currently and you are able to access it.
May I know since when it is not working? was the board used in car or office premises?

Could you check flashing DRIVE SW 10.0 on Tegra A and see if it fixes the issue. If you hit any flashing issue, could you attach the logs here?

11
  1. Tegra-A can’t access, Tegra-B is ok.
  2. Office.
  3. We will try it.
12

Hi expert,
we have downloaded DRIVE SW 10.0 offline, how to flash to the target device without network?

thanks,
fu

13

Could you try if https://docs.nvidia.com/sdk-manager/0.9beta14/offline-install/index.html#offline-install helps with your case?

14

How to connect target device with host machine? use use debug port?

15

After flash DRIVE SW 10.0, the entire system doesn’t work. the detail log as follow:
SDKM_logs_2021-12-31_18-02-49.zip (2.5 MB)

17

Dear @user103454,
I could see flashing is successful in the log(NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP.log)

Flashing successful for given configuration!
Info: [ Component Install Finished Successfully ]
Info: [host] [ 731.29 MB used. Disk Avail: 288.66 GB ]
Info: [ NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP Install took 1h53m34s ]

After flash DRIVE SW 10.0, the entire system doesn’t work

what does that mean? Yo don’t see display GUI? Could you check accessing Tegra A/B and Aurix via minicom and confirm if it works? Please connect host and target via usb debug cable before using minicom.

18

the entire AGX system doesn’t work after upgraded. tegra-a, mcu, tegra-b log as attachments.
tegra-b.txt (917 Bytes)
mcu.txt (10.5 KB)
tegra-a.txt (1.4 KB)

19

Dear @user103454,
when you flash with sdkmanager, did you see flashing successful message on sdkmanager GUI window? Is the target connected to internet and double check the system requirements(https://docs.nvidia.com/drive/drive_os_5.1.6.1L/drive-qsg/get-started-drive-software/index.html#system-requirements).
Could you confirm if you are getting access to Aurix console to run commands in the end?

20

Yes, we got successful message on sdkmanager GUI window.
No network connected for target device.
We can enter Aurix console, BUT can’t input any character.

Do we take following actions when upgrade SW 10.0 ?
" When upgrading an existing DRIVE AGX Developer Kit to DRIVE Software10.0, it is required to manually update the DRIVE AGX Developer Kit PCIe Switch and eSATA Firmware."

21

Upgrade from SW 9.0 from 10.0, can you give us a detail steps for flashing?