DevKit cannot start after successful DRIVEOS flashing, returning MCU_FOH error code

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
2.1.0
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Issue Description
Finally I successfully flashed DRIVE OS 6.0.6 to DevKit via SDK Manager. However, the DevKit still cannot start. The log is attached, seems MCU_FOH error.
Please support.

img_v3_02jt_aa82d4c7-9b4f-4e09-a4ff-ef5bbad999bg
img_v3_02jt_aa82d4c7-9b4f-4e09-a4ff-ef5bbad999bg1440Ă—1080 184 KB

Error String
< Please provide just the error messages here >
MCU_FOH: SOC error pin is asserted
MCU_FOH: SOC error pin is de-asserted
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: ErrReport: ErrorCode-0x28da ReporterId-0xe04c Error_Attribute-0x0 Times
tamp-0x653bc2b
MCU_FOH: ErrReport: ErrorCode-0x28d1 ReporterId-0xe04c Error_Attribute-0x0 Times
tamp-0x653bf1b
MCU_FOH: ErrReport: ErrorCode-0x30000008 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x653c21b
MCU_FOH: ErrReport: ErrorCode-0x9 ReporterId-0x800d Error_Attribute-0x0 Timestam
p-0x653c68b
MCU_FOH: ErrReport: ErrorCode-0x2c000008 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x6644293
MCU_FOH: ErrReport: ErrorCode-0x34000008 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x6644a7b
MCU_FOH: ErrReport: ErrorCode-0x38000008 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x664521b
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x67ab15b
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x67ab94b
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failur
e_Attribute-0x22
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failur
e_Attribute-0xee
INFO: Marvell Phy: Phy init completed…
INFO: MCU_PltfPwrMgr: PHYs Init
INFO: MCU_PltfPwrMgr: StbM Init
INFO: MCU_PLTFPWRMGR: Power-up sequence is complete !
INFO: MCU_PLTFPWRMGR: DL Ready drive to HIGH !
Power on the system
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 agai
nst rated maxrpm
INFO: CmnIf: Get update FW version - complete
INFO: CmnIf: Get Prod FW version - complete
INFO: CmnIf: Get update FW version - complete
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
INFO : IST_TESTAPP: IST Result Ready to fetch
MCU_FOH: ErrReport: ErrorCode-0x18550080 ReporterId-0x8001 Error_Attribute-0x0 T
imestamp-0x420425db
MCU_FOH: ErrReport: ErrorCode-0x18550080 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x4615eddd

Logs
Provide logs in text box instead of image

Please paste the complete application log here. If there are multiple logs, please use multiple text box
Log_6.0.6_afterFlashing_1stRestart.txt (7.7 KB)

2

Dear @hengfeng.wang ,
This looks like aurix console. What do you notice on tegra console (/dev/ttyACM0)?

1 Like
3

wow! with ACM0, it asked me to input username and password, and it shows like below.
It seems ok?

But the DP display still did not work.

and some error popup up.

Screenshot from 2025-02-27 16-05-07
Screenshot from 2025-02-27 16-05-073072Ă—1920 398 KB

5

Dear @hengfeng.wang,
The messages on tegra console can be ignored. Could you check changing display monitor? Did you accept EULA( Finalize DRIVE AGX Orin System Setup | NVIDIA Docs) in first boot after you receive board? Did you get display earlier before flashing DRIVE OS 6.0.6? Also, any reason for using older release DRIVE OS 6.0.6?