No minicom access to tegra A after flashing from sdk manager

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.8.1.10392
other

Host Machine Version
native Ubuntu 18.04
other

i have flashed my nvidia drive agx device and i am able to access Tegra B via minicom (sudo minicom -D /dev/ttyUSB6)

however i am unable to access Tegra A (sudo minicom -D /dev/ttyUSB2)
the terminal appears to be frozen.
logs from sdk manager attached
SDKM_logs_DRIVE_OS_5.2.6_SDK_Linux_for_DRIVE_AGX_Xavier_2022-08-29_07-48-48.zip (177.9 KB)

thanks for the help

3

Dear @yoav10,
As per logs, flashing seems to successful. Could you check accessing Tegra A from Tegra B (via ssh nvidia@10.42.0.28) and confirm if it is accessible?

4

i am unable to access via ssh as well

nvidia@tegra-ubuntu:~$ ssh nvidia@10.42.0.28
ssh: connect to host 10.42.0.28 port 22: No route to host
5

Hi @SivaRamaKrishnaNV,

This issue follows Aurix - no access, failed to find flashing SDK - #8 by SivaRamaKrishnaNV

We got Drive product, and flashed it to our Aurix. But we still can’t access Tegra A (no ping).

Can you please help?

6

Dear @adi4,
I could see you have tried flashing Tegra A alone as well. I don’t see any errors in flashing logs. Could you check poweroff x1 and poweron x1?

7

Thank you @SivaRamaKrishnaNV
We tried it, it didn’t help. Still no access

8

Dear @adi4,
Could you check version command output on aurix. Please update aurix FW if not matches to DRIVE OS 5.2.6 release.
I am assuming you can access Tegra B via ssh from other network machine and vice versa. Please confirm that.

9

We are unable to get internet access on Tegra B:

nvidia@tegra-ubuntu:~$ systemctl status NetworkManager
   NetworkManager.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

We can unmask the process but I think it will uninstall it and that we have a problem.

This is the Aurix version:
SW Version: DRIVE-V5.1.6-E3550-EB-Aurix-With3LSS-ForHyperion-StepA-3.05.04
How do we update the FW? by flashing it again?

10

Dear @adi4,
Could you check https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/Flashing%20Basics/flashing_aurix.html# ?

11

Dear @SivaRamaKrishnaNV
we tried to flash the aurix using windows host but we are getting an error from memtool:
“Can’t establish connection to target”
cfg file and error log attached
i verified that i am able to access the Com port
mcu switch is set to PRG

__connection_failed_report__Controller0_Core0_2022_08_31.txt (9.8 KB)
TriBoard_TC39x.cfg (1.4 KB)

please advise

12

can anyone help
thanks

13

Dear @SivaRamaKrishnaNV,
Can you please help?

Is it possible to have an online support session with you? via Zoom or Google meet or such?

14

Hi @adi4 what did you mean flashed it to “our” Aurix? What actually did you do?

15

Dear @VickNV
i am working with @adi4 and can answer your question,
we used sdk manager to flash our nvidia drive device , i flashed Tegra A and Tegra B.
however there is no minicom connection to Tegra A, i have minicom connection to Aurix and Tegra B
also there is no ping between Tegra A and Tegra B

16

Please follow Flashing AURIX on Xavier and see if you can update the firmware via Tegra B.

17

@VickNV tried to follow the guide but i get the following :

Press CTRL-A Z for help on special keys

-auto_updateubuntu:~$ sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh
[sudo] password for nvidia:
starting Aurix FW checking…
Checking arguments…
Aurix Updater feature is valid for DRIVE AGX board, on Tegra-A only
nvidia@tegra-ubuntu:~$

content of /lib/firmware

nvidia@tegra-ubuntu:~$ ll /lib/firmware/
total 29208
drwxr-xr-x 16 root root 4096 Apr 22 2021 ./
drwxr-xr-x 14 root root 4096 Apr 22 2021 …/
-rw-r–r-- 1 root root 212392 Apr 22 2021 164.13_1.0.AA_ATMEL_mXT2954T2_NVIDIA_P2737.fw
-rw-r–r-- 1 root root 8424 Apr 22 2021 ATMEL_2954T2_NVIDIA_P1332_CFG.raw
-rw-r–r-- 1 root root 8424 Apr 22 2021 ATMEL_mXT2954T2_NVIDIA_P2737_CFG.raw
-rw-r–r-- 1 root root 8424 Apr 22 2021 ATMEL_mXT2954T2_NVIDIA_P2737_CFG_land.raw
-rw-r–r-- 1 root root 3224136 Apr 22 2021 DRIVE-V5.2.6-E3550-AFW-Aurix-With3LSS-StepA-4.04.01.hex
-rw-r–r-- 1 root root 3248732 Apr 22 2021 DRIVE-V5.2.6-E3550-AFW-Aurix-With3LSS-StepB-4.04.01.hex
-rw-r–r-- 1 root root 3166438 Apr 22 2021 DRIVE-V5.2.6-P3479-AFW-Aurix-With3LSS-StepA-4.04.01.hex
-rw-r–r-- 1 root root 3208522 Apr 22 2021 DRIVE-V5.2.6-P3479-AFW-Aurix-With3LSS-StepB-4.04.01.hex
-rw-r–r-- 1 root root 1063481 Apr 22 2021 DRIVE-V5.2.x-E3550-NV-Aurix-IFW-StepA-1.29.16.hex
-rw-r–r-- 1 root root 1240914 Apr 22 2021 DRIVE-V5.2.x-E3550-NV-Aurix-IFW-StepB-1.36.16.hex
-rw-r–r-- 1 root root 1063035 Apr 22 2021 DRIVE-V5.2.x-E3550-NV-Aurix-UPDATE-StepA-1.29.16.hex
-rw-r–r-- 1 root root 1240417 Apr 22 2021 DRIVE-V5.2.x-E3550-NV-Aurix-UPDATE-StepB-1.36.16.hex
-rw-r–r-- 1 root root 1063035 Apr 22 2021 DRIVE-V5.2.x-P3479-NV-Aurix-UPDATE-StepA-1.29.16.hex
-rw-r–r-- 1 root root 1240417 Apr 22 2021 DRIVE-V5.2.x-P3479-NV-Aurix-UPDATE-StepB-1.36.16.hex
-rwxr-xr-x 1 root root 2113368 Apr 22 2021 adsp.elf*
drwxr-xr-x 5 root root 4096 Apr 22 2021 aquantia/
-rwxr-xr-x 1 root root 71827 Apr 22 2021 bluetooth-bcm4359-b1-fw.hcd*
drwxr-xr-x 2 root root 4096 Apr 22 2021 brcm/
drwxr-xr-x 2 root root 4096 Apr 22 2021 gp10b/
drwxr-xr-x 3 root root 4096 Apr 22 2021 gp10x/
drwxr-xr-x 3 root root 4096 Apr 22 2021 gv10x/
drwxr-xr-x 2 root root 4096 Apr 22 2021 gv11b/
drwxr-xr-x 3 root root 4096 Apr 22 2021 marvell_ethernet/
drwxr-xr-x 3 root root 4096 Apr 22 2021 marvell_sata/
-rw-r–r-- 1 root root 55296 Apr 22 2021 nvhost_nvdla010.fw
-rw-r–r-- 1 root root 139008 Apr 22 2021 nvhost_nvenc070.fw
-rwxr-xr-x 1 root root 22784 Apr 22 2021 nvhost_vic042.fw*
drwxr-xr-x 2 root root 4096 Apr 22 2021 nvlink/
drwxr-xr-x 5 root root 4096 Apr 22 2021 pcie-switch/
-rwxr-xr-x 1 root root 7150880 Apr 22 2021 pg418_selfupgrade*
drwxr-xr-x 2 root root 4096 Apr 22 2021 tegra18x/
-rw-r–r-- 1 root root 124416 Apr 22 2021 tegra18x_xusb_firmware
drwxr-xr-x 2 root root 4096 Apr 22 2021 tegra19x/
-rw-r–r-- 1 root root 124928 Apr 22 2021 tegra19x_xusb_firmware
drwxr-xr-x 3 root root 4096 Apr 22 2021 tu10x/
drwxr-xr-x 3 root root 4096 Apr 22 2021 vbios/
nvidia@tegra-ubuntu:~$

not sure what am i missing
is it possible to do an online debug session?

19

We will check with our team why the aurix firmware wasn’t updated and get back to you. Thanks.

20

Were you able to access Tegra A via UART before flashing DRIVE OS 5.2.6? What’s your previous experience with the system?

21

didn’t try to access it via uart
i don’t have much experience with the system

22

Dear @VickNV
small update, i have flashed Tegra A and Tegra B again using sdk manager and now i can access Tegra B via ssh and minicom
however Tegra A is still not accessible, no minicom access