Xavier A not responding and not able to flash

Hi all,

My Xavier A won’t boot up this morning, I didn’t do anything specifically to it and the Xavier B is working properly.

I try to take a UART read out and here’s the result I got

[0001.540] E> WP1.5 ACK pending

[0001.543] E> Error: 0

[0001.545] E> Task 79 failed (err: 0x32320006)

[0001.549] E> Top caller module: CPUINIT, error module: CPUINIT, reason: 0x06, aux_info: 0x00
[0001.557] I> MB1(1.6.0.0-t194-41334769-b6f2af00) BIT boot:
00000000000111111111101111111111111111111110111111111011110

[0001.586] I> Reset to recovery mode

I also try to flash the system to recover, it also failed and the part of log output is here

[2020-08-26 13:42:36,642 root DEBUG console_logger.py 17 3178] b’Flashing-boot started\r\n’
[2020-08-26 13:42:36,653 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/mb1/mb1_t194_prod.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/mb1_recovery.bin’\r\n"
[2020-08-26 13:42:36,654 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/mb1/mb1_t194_prod.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/mb1.bin’\r\n"
[2020-08-26 13:42:36,658 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/mts/mce_c10_prod_cr.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/mce_c10_cr.bin’\r\n"
[2020-08-26 13:42:36,659 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/mts/mce_c10_prod_grp.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/mce_c10_grp.bin’\r\n"
[2020-08-26 13:42:36,662 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/mts/mts_c10_prod_cr.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/mts_c10_cr.bin’\r\n"
[2020-08-26 13:42:36,663 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x//qb_cpu.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/qb_cpu.bin’\r\n"
[2020-08-26 13:42:36,663 root DEBUG console_logger.py 17 3178] b’Appending Qb DTB to Qb binary\r\n’
[2020-08-26 13:42:36,665 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//firmwares/bin/t19x/nvtboot.bin’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/nvtboot.bin’\r\n"
[2020-08-26 13:42:37,125 root DEBUG console_logger.py 17 3178] b’Generating BR_BCT File\r\n’
[2020-08-26 13:42:37,467 root DEBUG console_logger.py 17 3178] b’Generating MB1_BCT File\r\n’
[2020-08-26 13:42:37,469 root DEBUG console_logger.py 17 3178] b’Generating MEM BCT files\r\n’
[2020-08-26 13:42:37,998 root DEBUG console_logger.py 17 3178] b’Generating Flash Images, this may take a few minutes\r\n’
[2020-08-26 13:42:38,180 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//platform-config/bpmp_dt/t19x/tegra194-a02-bpmp-e3550-0001-b01-A.dtb’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/bpmp.dtb’\r\n"
[2020-08-26 13:42:38,340 root DEBUG console_logger.py 17 3178] b"’/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/…/…/…/…//platform-config/bpmp_dt/t19x/tegra194-a02-bpmp-e3550-0001-b01-A.dtb’ -> ‘/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_MMEcvmA1Yq/flash-images/bpmp.dtb’\r\n"
[2020-08-26 13:45:07,579 root DEBUG console_logger.py 17 3178] b’Flashing-Images started\r\n’
[2020-08-26 13:45:07,601 root DEBUG console_logger.py 17 3178] b’Waiting for USB device. This may take up to 100 seconds…\r\n’
[2020-08-26 13:45:08,733 root DEBUG console_logger.py 17 3178] b’Android Debug Bridge version 1.0.36\r\nRevision -android\r\nPlatform version 7.0\r\nsupports 262144 Bytes MAX_PAYLOAD\r\nThis build is for NVIDIA embedded bootburn\r\nBuild time : May 16 2017 01:26:13\r\n’
[2020-08-26 13:45:11,739 root DEBUG console_logger.py 17 3178] b’* daemon not running. starting it now on port 5037 \r\n daemon started successfully *\r\n’
[2020-08-26 13:46:51,754 root DEBUG console_logger.py 17 3178] b’Could not find a device online\r\n’
[2020-08-26 13:46:51,756 root DEBUG console_logger.py 17 3178] b’\r\n ------------ Stack Trace ------------\r\nstack frame 0 - 297 AbnormalTermination /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh\r\n’
[2020-08-26 13:46:51,757 root DEBUG console_logger.py 17 3178] b’stack frame 1 - 46 CheckUSBServiceInit /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_adb.sh\r\n’
[2020-08-26 13:46:51,759 root DEBUG console_logger.py 17 3178] b’stack frame 2 - 2697 FlashImages /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh\r\n’
[2020-08-26 13:46:51,760 root DEBUG console_logger.py 17 3178] b’stack frame 3 - 368 source /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_active.sh\r\n’
[2020-08-26 13:46:51,762 root DEBUG console_logger.py 17 3178] b’stack frame 4 - 995 main /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/drive-t186ref-foundation//tools/host/flashtools/bootburn_t19x/bootburn.sh\r\n’
[2020-08-26 13:46:51,763 root DEBUG console_logger.py 17 3178] b’-------------------------------------\r\n\r\n’
[2020-08-26 13:46:51,764 root DEBUG console_logger.py 17 3178] b’Tool OutPut:\r\n’
[2020-08-26 13:46:51,765 root DEBUG console_logger.py 17 3178] b’Bus 001 Device 011: ID 0955:7019 NVidia Corp. \r\nBus 001 Device 013: ID 0955:7019 NVidia Corp. \r\n’
[2020-08-26 13:46:51,765 root DEBUG console_logger.py 17 3178] b’Tool OutPut to stderr:\r\n’
[2020-08-26 13:46:51,766 root DEBUG console_logger.py 17 3178] b’Bus 001 Device 011: ID 0955:7019 NVidia Corp. \r\nBus 001 Device 013: ID 0955:7019 NVidia Corp. \r\n’
[2020-08-26 13:46:51,767 root DEBUG console_logger.py 17 3178] b’error-adb-timeout\r\n’
[2020-08-26 13:46:53,224 root DEBUG console_logger.py 17 3178] b’Process CMD (3920) still running. Trying to kill after 5 seconds\r\n’
[2020-08-26 13:46:58,834 root DEBUG console_logger.py 17 3178] b’\r\n’
[2020-08-26 13:46:58,936 root ERROR pdk_flasher.py 168 3178] Flashing process exited with error 5
[2020-08-26 13:46:58,936 root CRITICAL runner.py 37 3178] Error in flashing!
[2020-08-26 13:46:58,937 root DEBUG runner.py 38 3178] Exception info:
Traceback (most recent call last):
File “./pdkinstaller”, line 777, in
pdk_flasher.flash()
File “/home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/pdkinstaller/module/pdk_flasher.py”, line 171, in flash
raise FlashingError
module.errors.FlashingError: Error in flashing!
[2020-08-26 13:46:58,940 root CRITICAL runner.py 43 3178] pdkinstaller cannot continue! Check the log file for details: /home/audi-user/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_DDPX/DriveSDK/pdkinstaller/pdkinstaller.log
[2020-08-26 13:46:58,940 root DEBUG runner.py 60 3178] Cleaning up…
[2020-08-26 13:46:58,940 root DEBUG utilities.py 124 3178] Deleting temporary directories…
[2020-08-26 13:46:58,941 root DEBUG utilities.py 126 3178] Deleting /tmp/pdkinstall-tmp-wfk980xh-bind
[2020-08-26 13:46:58,941 root DEBUG runner.py 62 3178] Closing the log file.

Does anyone knows what’s going on and how to recover from that?

Dear @hao.wang,
Could you check flashing latest DRIVE SW release?

Hi,

It failed, also, in SDK Manager, the board has been identified as a Jetson board instead of Drive board, it warns me that I selected for the Drive board but it’s detected as a Jetson. Is it more likely to be a hardware issue?

Dear @hao.wang,
the board has been identified as a Jetson board instead of Drive board

This is surprising. Could you just connect only Drive platform and check again. Could you attach pictures if possible

Dear @hao.wang,
Could you provide any update?

Hi,

Amazingly it self healed on second day, we didn’t do anything after the attempt of flashing was failed but it just boot up and works fine on the next morning.
I’m sorry I didn’t save a image that it’s being detected as a Jetson in SDK manager, however out partner who’s working on another board told us that they have booting issues as well, sometime they have to do multiple power cycles in order to boot, and it’s always only boot up Xavier B but not A.
BTW just for clarification, the boards we have are Drive AGX boards so I might accidentally put the post under wrong subject.

Dear @hao.wang,
ok. So the issue is fixed now? If you see new issue file a new topic.