Xavier A on NVIDIA Drive Xavier not able to flash / not able to boot

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Hello,

after flashing Linux to the Drive Xavier platform with the sdk manager, I’m only able to access the Xavier B part of the platform.
This also is the case for manual flashing. All I/O of Xavier A is not supplied with power.
I can’t boot into Linux on Xavier A and hence can’t run the bug-report-script. Sdk manager is also unable to reach Xavier A as well.
How can I resolve this issue?
sdkm.log (4.24 MB)
NV_FLASH_XAVIER_PDKFLASH_B_COMP.log (132 KB)
NV_FLASH_XAVIER_PDKFLASH_A_COMP.log (179 KB)

2

Dear lucas.mahler,

Could you please upload the full logs available at below locations for your topic?
~/.nvsdkm/sdkm.log
~/.nvsdkm/logs

3

Hi lucas.mahler,

Have you managed to get device flashed and boot up successfully?
Any result can be shared?

4

Since I am only able to flash Xavier B of the Platform, I searched for said files but couldn’t find them on the target system.

So I am able to flash the device, but only Xavier B is then physically accessible. All ports of Xavier A are not even powered on.

I hope this was somewhat helpful.

5

Dear lucas.mahler,

The files are in your hostPC not target system.
Could you please re-search the files on your hostPC? Thanks.

6

I attached the files to the original post.
Are there any specific files from the .nvsdkm/logs directory which I need to post?

7

Dear lucas.mahler,

Oh sorry.
We will check the log files. Thanks.

8

Dear lucas.mahler,

According to sdkm.log, there is no DriveAGX information, I just found JetPack_4.2.2 in the log so this is for Jetson platform.
Could you please upload you DriveAGX SDK manager log?
And also please help to upload Aurix console log with sudo minicom -D /dev/ttyUSB2 -C aurix.log Thanks.

9

Hi SteveNV,

I tried to connect via minicom but I couldnt establish a connection successfully.
Currently, I am trying to flash Xavier A+B again in order to provide you with an up to date log file.

However, attached you will find and old log. A colleague of mine already issued a forum post about the exact same problem on the exact same machine.
https://devtalk.nvidia.com/default/topic/1048300/general/usb-device-missing-when-in-recovery-mode/post/5353842/#5353842

EDIT:

Flashing failed again, the logs are attached to this Post.
I suspect, that there is a hardware problem with a SoC on this board.
Can we somehow determine if this is actually the case?
sdkm_f.log (1.11 MB)
SDKM_logs_DRIVE_Software_8.0_Linux_for_DRIVE_AGX_Developer_Kit_2019-11-04_13-03-22.zip (1.92 MB)

10

Dear lucas.mahler,

According to the sdkm_f.log, there is Drive Software 8.0 not 9.0.
Did you try to flash Drive Software 9.0?
If not, could you please try to flash Drive Software 9.0?

And did you set it up to use the minicom tool?
[url]DRIVE OS Linux

11

I tried installing DriveSoftware 9.0 just now, logs attached, but again, it was not successfull.

And I did indeed setup the minicom tool, but I can’t seem to get a connection.
I suspect that there is a hardware problem.

EDIT:

I also tried flashing Xavier A and B separately but this yielded the same result.
SDKM_logs_DRIVE_Software_9.0_Linux_for_DRIVE_AGX_Developer_Kit_2019-11-08_10-42-39.zip (1.18 MB)

12

Dear lucas.mahler,

Found following error in log when flashing with DRIVE SW 9.0:
2019-11-08 11:02:59.948 - info: Invalid Board Name e3550b03-t194 !!!

Could you let us know what type of board you have?

2019-11-08 10:59:27.904 - info: exec_command: cd pdkinstaller && ./bin/python3 -E ./pdkinstaller --installtype bindflash --boardtype ES --pdkinstalledpath /home/ubuntu/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK --configjson ./manifests/install_pdk_config/av_ddp_pegasus_hyp71_linux_tegraAB_install_config.json --consoleout enable
...
2019-11-08 11:01:53.804 - info: Running flash command: sudo -E /home/ubuntu/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/drive-t186ref-foundation//tools/host/flashtools/bootburn_t19x/bootburn.sh -b e3550b03-t194 -B qspi -x /dev/ttyUSB3
2019-11-08 11:02:59.940 - error: Flashing process exited with error 255
2019-11-08 11:02:59.941 - info: [host] [sudo] password for ubuntu: 
2019-11-08 11:02:59.941 - info: Successfully acquired lock over /var/lock/LCK..bootburn
2019-11-08 11:02:59.942 - info: Successfully acquired lock over /var/lock/LCK..ttyUSB3
2019-11-08 11:02:59.942 - info: Read skuinfo from InfoRom...
2019-11-08 11:02:59.943 - info: Process CMD (15899) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.943 - info: Disabling SIGINT <Ctrl+C> temporarily
2019-11-08 11:02:59.944 - info: Setting Tegra-A on hold... Process CMD (15962) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.944 - info: Done
2019-11-08 11:02:59.944 - info: Setting Tegra-B on hold... Process CMD (15993) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.945 - info: Done
2019-11-08 11:02:59.945 - info: Setting Tegra-A in recovery... Process CMD (16027) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.946 - info: Process CMD (16058) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.946 - info: Done
2019-11-08 11:02:59.947 - info: Setting Tegra-B in recovery... Process CMD (16092) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.947 - info: Process CMD (16123) still running. Trying to kill after 5 seconds
2019-11-08 11:02:59.948 - info: Done
2019-11-08 11:02:59.948 - info: Enabling SIGINT <Ctrl+C>
2019-11-08 11:02:59.948 - info: <b>Invalid Board Name e3550b03-t194 !!!</b>
2019-11-08 11:02:59.949 - info: Provide board name as sim-t194, basefpga-t194, maxfpga-t194, gpufpga-t194, e3550b01-t194a, e3550b01-t194b, e3550b01-t194ia, e3550b03-t194a, e3550b03-t194b, e3550b03-t194ia, p3479-t194, p3479a01-t194, p3479a01-t194s, xavier-slt-auto, xavier-slt, p2972-t194, p2888-t194, boden-t194.
13

Dear lucas.mahler,
Adding to Steve’s comments, Also share your Host kernel version as I see cat: /dev/ttyUSB3: Resource temporarily unavailable in NV_FLASH_XAVIER_PDKFLASH_A_COMP.log. Also, please check our flashing technical bulletin for knows issues and work arounds https://developer.download.nvidia.com/driveworks/secure/docs/DRIVE_9.0_Release_Docs/NVIDIA_DRIVE_AGX_Developer_Kit_Flashing_Technical_Bulletin_9.0.pdf?ZR4Dccv_eOQWZEU0-bwqUYQNjQHGsNoEk02WnbdnPmDmwHJ2GS8m_gKUD-KRc0ZHO4csnfh-siT33-Sdmn9iiuz-RUzW36cNGAQ7zwqEn8dlG0vgKkXDy_YjBAOo5lxpwD2d5aq4u_4xjpo2IcqCUVT20o-F5XZfFf8YUr_eCrVB6s10Na-npvQnT_06Bbpm0TkrCd836IaadBNqmgAJ0aATYud4e4ksInjQZpsNgA

14

Dear lucas.mahler,

I would like to get the following data to confirm the aurix is performing the operations correctly to set the devices in recovery mode.

“tegrareset x1 h”
“lsusb”                -- capture lsusb output 
“tegrareset x2 h”
“lsusb”                -- capture lsusb output 
“tegrarecovery  x1 on”
“lsusb”                -- capture lsusb output
“tegrarecovery x2 on”
“lsusb”                -- capture lsusb output

Also execute bootburn with -D option to get us detailed logs.
bootburn tool is in /home/USER/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn

15

Dear lucas.mahler,
Did you check the provided suggestions? Could you share any updates?

16

We are currently working on it. We keep you posted with updates asap.

17

I have executed all of the suggested commands, the logs are attached to this post. The command used for the bootburn tool is:

sudo nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn/bootburn.sh -D -b e3550b03-t194 -B qspi -x /dev/ttyUSB3 >> bootburnlog.txt
lsusb_reset_x1.log (780 Bytes)

bootburn.log (2.2 KB)

18

Dear lucas.mahler,
Thank you for your update.
We will look into the log files and update. Thanks.

19

Dear lucas.mahler,

Sorry, I missed the reset in the sequence.
Could you please get the following data to confirm the aurix is performing the operations correctly to set the devices in recovery mode? Thanks.

“tegrareset x1 h”
“lsusb”                                                
“tegrareset x2 h”
“lsusb”                                                
“tegrarecovery  x1 on”
“lsusb”                  --   capture lsusb output
“tegrarecovery x2 on”
“lsusb”                  --    capture lsusb output
“ tegrareset x1”
“lsusb”                  --    capture lsusb output
“ tegrareset x2”
“lsusb”                  --    capture lsusb output
20

Dear lucas.mahler,

Would you please help to update the current status of this is not an issue now?
Any result can be shared?

Thanks