Drive AGX flash error

[2024-05-24 17:24:54,950 root DEBUG console_logger.py 17 47245] b'[bootburnTegra-A]: [checkMd5(425)] : \x1b[01;32m target md5 =  /dev/block/3270000.spi not found, looking by controller instance... matches host side md5 = 32ff3dcac6c57ad54d54a76f383f7e19\x1b[0m\r\n[bootburnTegra-A]: [SendFileUsingADB(608)] : Image written correctly, md5 sum matches\r\ncommand line used was:\r\n[\'/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation//tools/flashtools/bootburn/bootburn.py\', \'-b\', \'p3710-10-a01\', \'-B\', \'qspi\', \'-x\', \'/dev/ttyACM1\', \'--init_persistent_partitions\', \'-D\']\r\n\r\n\r\n\x1b[01;31mFlashing Failed Propagated Error\x1b[0m\r\n\r\n[bootburnTegra-A]: [FlashImages(3131)] : **** FlashImages::Exception in flashing ****\r\n[bootburnTegra-A]: [FlashImages(3133)] : exception dictionary - {}\r\n[bootburnTegra-A]: [FlashImages(3142)] : flashExcept return code - 116\r\n[bootburnTegra-A]: [FlashImages(3152)] : **** s_BrickOnTCFFlashingFail is disabled in the configuration ****\r\ncommand line used was:\r\n[\'/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation//tools/flashtools/bootburn/bootburn.py\', \'-b\', \'p3710-10-a01\', \'-B\', \'qspi\', \'-x\', \'/dev/ttyACM1\', \'--init_persistent_partitions\', \'-D\']\r\n\r\n\r\n\x1b[01;31mFlashing failed and target was not bricked as per configuration\x1b[0m\r\n\r\n\r\n\r\n\x1b[01;31mException 116 raised in bootburn_active \x1b[0m\r\nTraceback (most recent call last):\r\n  File "/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 156, in bootburn_active\r\n    bootburnOrin.Boot_Create_Flash_Coldboot()\r\n  File "/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py", line 756, in Boot_Create_Flash_Coldboot\r\n    self.FlashImages(self.targetConfig.p_OutDirPath)\r\n  File "/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive'
[2024-05-24 17:24:54,967 root DEBUG console_logger.py 17 47245] b'-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3153, in FlashImages\r\n    AbnormalTermination("Flashing failed and target was not bricked as per configuration", flashExceptRetCode)\r\n  File "/home/vector/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 249, in AbnormalTermination\r\n    raise OSError(errorCode)\r\nOSError: 116\r\n'
[2024-05-24 17:24:55,028 root DEBUG console_logger.py 17 47245] b'\r\n'
[2024-05-24 17:24:55,129 root ERROR pdk_flasher.py 277 47245] Flashing process exited with error 116
[2024-05-24 17:24:55,130 root INFO runner.py 37 47245] Error in flashing!
[2024-05-24 17:24:55,130 root DEBUG runner.py 39 47245] Error on line 968
[2024-05-24 17:24:55,130 root DEBUG runner.py 40 47245] Exception info: Exception Type <class 'module.errors.FlashingError'>, Traceback <traceback object at 0x7f594ab60a88>
[2024-05-29 09:52:28,469 root DEBUG console_logger.py 17 21] b"command line used was:\r\n['/drive/drive-foundation//tools/flashtools/bootburn/bootburn.py', '-b', 'p3710-10-a01', '-B', 'qspi', '-x', '/dev/ttyACM1']\r\n\r\n\r\n\x1b[01;31mFlashing Failed Propagated Error\x1b[0m\r\n\r\n"
[2024-05-29 09:52:28,471 root DEBUG console_logger.py 17 21] b'[bootburnTegra-A]: [FlashImages(3440)] : **** FlashImages::Exception in flashing ****\r\n'
[2024-05-29 09:52:28,472 root DEBUG console_logger.py 17 21] b'[bootburnTegra-A]: [FlashImages(3442)] : exception dictionary - {}\r\n'
[2024-05-29 09:52:28,473 root DEBUG console_logger.py 17 21] b'[bootburnTegra-A]: [FlashImages(3451)] : flashExcept return code - 117\r\n'
[2024-05-29 09:52:28,474 root DEBUG console_logger.py 17 21] b"[bootburnTegra-A]: [FlashImages(3461)] : **** s_BrickOnTCFFlashingFail is disabled in the configuration ****\r\ncommand line used was:\r\n['/drive/drive-foundation//tools/flashtools/bootburn/bootburn.py', '-b', 'p3710-10-a01', '-B', 'qspi', '-x', '/dev/ttyACM1']\r\n\r\n\r\n\x1b[01;31mFlashing failed and target was not bricked as per configuration\x1b[0m\r\n\r\n\r\n\r\n\x1b[01;31mException 117 raised in bootburn_active \x1b[0m\r\n"
[2024-05-29 09:52:28,475 root DEBUG console_logger.py 17 21] b'Traceback (most recent call last):\r\n  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 156, in bootburn_active\r\n    bootburnOrin.Boot_Create_Flash_Coldboot()\r\n  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py", line 760, in Boot_Create_Flash_Coldboot\r\n    self.FlashImages(self.targetConfig.p_OutDirPath)\r\n  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3462, in FlashImages\r\n    AbnormalTermination("Flashing failed and target was not bricked as per configuration", flashExceptRetCode)\r\n  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 251, in AbnormalTermination\r\n    raise OSError(errorCode)\r\nOSError: 117\r\n'
[2024-05-29 09:52:30,548 root DEBUG console_logger.py 17 21] b'\r\n'
[2024-05-29 09:52:30,649 root ERROR pdk_flasher.py 280 21] Flashing process exited with error 117
[2024-05-29 09:52:30,649 root INFO runner.py 37 21] Error in flashing!
[2024-05-29 09:52:30,650 root DEBUG runner.py 39 21] Error on line 990
[2024-05-29 09:52:30,650 root DEBUG runner.py 40 21] Exception info: Exception Type <class 'module.errors.FlashingError'>, Traceback <traceback object at 0x7fba1b5d3600>

Such error messages haven’t been seen except in Flashing process exited with error 116 due to a component change.

Could you please get the current version by running the following command in the Aurix console?
NvShell>version

Power cycling both the host and target system is always worth a try.

Additionally, could you check with your colleague to get the previous status of this system? Also, what is the serial number of the system?