DriveAGX unit doesn't power up, MCU_PLTFPWRMGR Error

Please provide the following info (tick the boxes after creating this topic):
Software Version
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-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.2.10884
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

The unit doesn’t power up at initial bringup. In the debug console the following error is shown:

MCU_FOH: E2E Initialized
MCU_FOH: Initialization done
INFO: MCU_PLTFPWRMGR Power-on Triggered …
MCU_FOH: SOC error pin is asserted
ERROR: MCU_PLTFPWRMGR: Enable Pre-regulator Request failed … Move to error state!
INFO: MCU_SWC_FanControl: max_rpm fan1 : 0
INFO: MCU_SWC_FanControl: max_rpm of fan1 has more than 50 percent deviation against rated max rpm
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: max_rpm of fan2 has more than 50 percent deviation against rated max rpm

Dear @stefan65,
The unit doesn’t power up at initial bringup

Does that mean, you just unboxed the board and noticed the issue when booting first time?

Did you check flashing the board with latest release?

yes, that’s correct, this is right after unboxing. Also when I lift the unit, there is a bit of rattling sound from inside, like something is loose.
No, didn’t flash a newer SW version, but this error shows up right at the beginning of the start up sequence, and so not sure if the SW I’ll be flashing is impacting this low level code. I can certainly try.

Dear @stefan65,
Please check flashing new DRIVE OS or DRIVE OS 6.0.4 to see if it fixes the issue. If that does not fix, could you share complete boot log of Tegra A(sudo minicom -D /dev/ttyACM0)

@stefan65 in the meantime, please also provide the serial number of the system for our investigation.

Also, please go through the steps in DRIVE AGX Orin Developer Kit Hardware Quick Start Guide and make sure accept the EULA.

image

1 Like

Dear @VickNV, please find the serial number below.
1425022019060

here is a screen dump from minicom prior to flashing the new SDK version:
Welcome to minicom 2.8

OPTIONS: I18n
Port /dev/ttyACM1, 16:31:52

Press CTRL-A Z for help on special keys

*************** NvShell Initialization Start******************
DRIVE-V6.0.4-P3710-AFW-Aurix-StepB-5.05.0
*************** NvShell Initialization Start******************
DRIVE-V6.0.4-P3710-AFW-Aurix-StepB-5.05.03
Compilation date: Jul 16 2022, 01:07:14
Enter ‘help’ to see the available commands.

*************** NvShell Initialized *************************
Press ‘Enter’ for NvShell prompt


MCU_FOH: E2E Initialized
MCU_FOH: Initialization done
INFO: MCU_PLTFPWRMGR: Power-on Triggered…
MCU_FOH: SOC error pin is asserted
ERROR: MCU_PLTFPWRMGR: Enable Pre-regulator Request failed …Move to error state !
INFO: MCU_SWC_FanControl: max_rpm fan1 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan1 has more than 50 percent deviation against rated maxrpm
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

@SivaRamaKrishnaNV here is the log from the flashing attempt after following step by step instructions from here. Isn’t the issue here that the initial startup fails due to the low level error (fan failure), so the actual flushing never starts.

root@6.0.6.0-0004-build-linux-sdk:/drive# python flash.py /dev/ttyACM1 p3710
2023-05-05 00:40:31 INFO : Flashing already set for dual bootchain
2023-05-05 00:40:31 INFO : Flash clean already disabled for persistent partitions
2023-05-05 00:40:31 INFO : Initiating pre-flash check
2023-05-05 00:40:31 INFO : Checking Serial Port Connection
2023-05-05 00:40:31 INFO : Serial Port found /dev/ttyACM1
2023-05-05 00:40:31 INFO : Running basic open/close tests on Serial Port Connection
2023-05-05 00:40:31 INFO : Serial Port is open
2023-05-05 00:40:31 INFO : Flushing input and output buffer, discard all content
2023-05-05 00:40:31 INFO : Serial Port is closed
2023-05-05 00:40:31 INFO : Checking available targets
2023-05-05 00:40:31 INFO : Checking Orin board connection
2023-05-05 00:40:31 INFO : Orin board with Device ID – 0955:7045 found.
2023-05-05 00:40:31 INFO : Orin board device path is /dev/bus/usb/003/006
2023-05-05 00:40:31 INFO : Pre-flash check complete
2023-05-05 00:40:31 INFO : Flashing DRIVE OS Docker
2023-05-05 00:40:31 INFO : driveinstaller v2.0
2023-05-05 00:40:31 INFO :
2023-05-05 00:40:31 INFO : SDK/PDK Installer and Flasher
2023-05-05 00:40:31 INFO : Run ./driveinstaller --help for usage information.
2023-05-05 00:40:31 INFO :
2023-05-05 00:40:31 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-05-05 00:40:31 INFO : Manifest version 2.0
2023-05-05 00:40:31 INFO :
2023-05-05 00:40:34 INFO : Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
2023-05-05 00:40:34 INFO : Failed to bind partitions!
2023-05-05 00:40:34 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-05-05 00:40:34 INFO :
2023-05-05 00:40:34 INFO :
2023-05-05 00:40:34 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_79amc5ltzj34qwib0y8pnhg6f1kdsevo.txt and /drive/driveinstaller/driveinstaller.log
2023-05-05 00:40:34 ERROR : Traceback (most recent call last):
File “flash.py”, line 153, in
flash_config(args.board, args.aurixport, args.tegra, args.pct_variant, args.recovery_timeout)
File “flash.py”, line 143, in flash_config
raise Exception(f’Error {proc.returncode} occurred’)
Exception: Error 140 occurred

Dear @stefan65,
Could you also please share driveinstaller.log as well.
Just want to confirm, Is Tegra A booting and accessible via minicom?

yes of course, here it is:
2023-05-05 02:36:36 INFO : Flashing already set for dual bootchain
2023-05-05 02:36:36 INFO : Flash clean already disabled for persistent partitions
2023-05-05 02:36:36 DEBUG : flash_config:
{
“path”: “/tools/flashtools/bootburn/”,
“scripts_home”: “./scripts/”,
“identify_aurix”: “identifyAurix.sh”,
“args”: [
“-B qspi”,
“-x DEBUG”
]
}
2023-05-05 02:36:36 INFO : Flashing DRIVE OS Docker
2023-05-05 02:36:36 DEBUG : [‘./driveinstaller’, ‘–configjson’, ‘./manifests/install_pdk_config/av_orin_p3710_driveos_linux_tegraA_install_pdk_config.json’, ‘–installtype’, ‘bindflash’, ‘–pdkinstalledpath’, ‘/drive’, ‘–boardtype’, ‘ES’, ‘–consoleout’, ‘enable’, ‘–port’, ‘/dev/ttyACM1’]
2023-05-05 02:36:36 INFO : driveinstaller v2.0
2023-05-05 02:36:36 INFO :
2023-05-05 02:36:36 INFO : SDK/PDK Installer and Flasher
2023-05-05 02:36:36 INFO : Run ./driveinstaller --help for usage information.
2023-05-05 02:36:36 INFO :
2023-05-05 02:36:36 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-05-05 02:36:36 INFO : Manifest version 2.0
2023-05-05 02:36:36 INFO :
2023-05-05 02:36:40 INFO : Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
2023-05-05 02:36:40 INFO : Failed to bind partitions!
2023-05-05 02:36:40 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-05-05 02:36:40 INFO :
2023-05-05 02:36:40 INFO :
2023-05-05 02:36:40 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_9m5vufycex18jqpdwiokn4ah6t072sbr.txt and /drive/driveinstaller/driveinstaller.log
2023-05-05 02:36:40 ERROR : Traceback (most recent call last):
File “flash.py”, line 153, in
flash_config(args.board, args.aurixport, args.tegra, args.pct_variant, args.recovery_timeout)
File “flash.py”, line 143, in flash_config
raise Exception(f’Error {proc.returncode} occurred’)
Exception: Error 140 occurred

/drive_flashing/log_9m5vufycex18jqpdwiokn4ah6t072sbr.txt (END)

@stefan65 any updates regarding the EULA?

@VickNV it never gets to that point, the MCU errors out right at startup. See the minicom screen dump for NvShell at the beginning of this post.

Let us know if you received the replacement devkit. Thanks.

@VickNV the replacement unit arrived today. It started up without issues.

I’ve managed to create my account and log in for the first time. Also updated DRIVE OS. The unit is ready for development.

Thanks for your help!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.