Drive OS not flashed successfully from 6.0.8 to 6.0.10

[allenzhu]

DRIVE OS Version: 6.0.8.1

Issue Description: I used the latest drive-os image to migrate the 6.0.8 OS from my local drive orin device to 6.0.10, but encountered an error. the log info:

the log file:

log_kwfctx8lu136gneq0zp7smbir5v2o9a4.txt (1.4 KB)

driveinstaller.log (28.2 KB)

It seems like recovery mode failed to enter. However, since this is my first time flashing on Drive Orin, I’m currently not sure what to do.

lsusb on docker:

lsusb on external:

I executed the following command:

NvShell>tegrarecovery x1 on
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on
Command Executed
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification…(20 seconds max)
MCU_FOH: SPI : E2E_P05Check Status : 7 : 170
ERROR: MCU_ERRHANDLER: McuFoh : ReporterID - 0x810E ErrorCode - 0x3
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A
INFO: BtChn_Cfg: Bootchain Pin 0xc set to 0
INFO: BtChn_Cfg: Bootchain Pin 0x150 set to 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
MCU_FOH: Spi Transmit Started
MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started…
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm
ERROR: MCU_SWC_FanControl: count_NoEthFrame expired
ERROR: MCU_SWC_FanControl: count_NoEthFrame_TA value reached to: 101
ERROR: MCU_SWC_FanControl: moving to error state

looking forward to a reply

[allenzhu]

the latest info:

but the drive orin don’t start:

[SivaRamaKrishnaNV]

@allenzhu

but the drive orin don’t start:

The log shared is from aurix console(i.e /dev/ttyACM1). Please use minicom -D /dev/ttyACM0 to connect to tegra console.
May I know what you did to flash the target successfully. Make sure the target is normal mode when you access tegra console. You can confirm it using lsusb on host machine(Only one NVIDIA device should be visible)

Please use text messages instead of images in posts

[allenzhu]

I followed the official tutorial for flash. I connected the micro usb and the LEFT USB type-c from drive orin to host pc, and then executed the command in the image: ./flash.py /dev/ttyACM1 p3710

the log is as follows:

driveinstaller.log (1.4 MB)

[allenzhu]

But, After the flash was completed, I used minicom -D /dev/ttyACM1 and then repowered the device. Is there any problem with this step? As you said, should I use minicom -D /dev/ttyACM0?

[SivaRamaKrishnaNV]

Dear @allenzhu ,
Yes. You need to connect to tegra console(sudo minicom -D /dev/ttyACM0) and configure the board. Please see Finalize DRIVE AGX Orin System Setup | NVIDIA Docs

[allenzhu]

Thank you all for your support. I think I’ve succeeded