Official Guidance on Safe Shutdown for Drive AGX Orin Dev Kit?

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

I apologize for the basic question.

In conclusion, for the Drive AGX Orin Developer Kit, is it acceptable to perform shutdown using the Power Off option from the GUI system tray in the top right corner?

Within my company, there is a common understanding that even for the Developer Kit (not just production boards), the proper shutdown procedure requires connecting via Micro USB and issuing the poweroff command through NVShell using TeraTerm.

However, this requires preparing another PC and opening TeraTerm every time I need to shut down, which is quite cumbersome.

I work in the automotive industry as part of a data collection team, and our department owns and uses multiple Drive AGX Orin Developer Kits.
We are also planning to provide these kits to our clients, but they are asking if there is any way to avoid having to prepare a separate PC solely for shutdown purposes.

Personally, I believe that shutting down via the GUI Power Off option should be fine, but I cannot find any explicit documentation from NVIDIA confirming that the GUI shutdown is acceptable for the Drive AGX Orin Developer Kit.

Could anyone point me to an official page that clearly states whether GUI shutdown is safe for the Drive AGX Orin Developer Kit?

Thank you for your support.

Dear @masaya.mitsushio.bf ,
FYI, you can use common_if_testapp -h to know list commands that can run from tegra console . However, the recommended shutdown method is use MCU console and issue poweroff.

I executed common_if_testapp -h and reviewed the available commands. While there are several options related to rebooting, I did not find any commands specifically for shutting down the system.

I understand that the recommended method is to use the poweroff command via NVShell. However, I’m curious to know if there have been any reports of issues arising from shutting down the Drive AGX Orin Developer Kit using the GUI’s “Power Off” option within the Drive OS environment.

Here is the output from common_if_testapp -h:

DU_MCC_Init done. Handle is 0xffff9c77e208
You are executing the TEST application for Common Interface APIs between Tegra and MCU
Your options are -

-mcureset               : Reset MCU. Reset the complete DRIVE AGX board
        -tDelay_mcuwait <T>     : TimeDelay in seconds that MCU should wait before MCU Reset
        -set_tegra_rec  <1|0>   : 1 => set Tegra A into recovery mode on next reboot

-tegrareset <x1|x2>     : Reset Tegra
        -h  <1|0>       : hold Tegra in reset state
        -tDelay_mcuwait <T>     : TimeDelay in seconds that MCU should wait before Tegra Reset

-set_default_bootchain <x1|x2> <A|B|C|D>   : Set the default boot chain for Drive Update

-get_default_bootchain <x1|x2> : Get the default boot chain for Tegra

-set_next_bootchain   <x1|x2>  <A|B|C|D>   : Set the boot chain temporarily for next reboot

-get_active_bootchain <x1|x2> : Get the active boot chain for Tegra

-test_get_default_bootchain <arg1: TegraId> <arg2: Outparam, 0-NULL or 1-Valid pointer> : Test behavior of DU_MCC_GetDefault_BootChain API with any argument.
-test_set_default_bootchain <arg1: TegraId> <arg2: BootChainId> : Test behavior of DU_MCC_SetDefault_BootChain API with any arguments.
-test_get_active_bootchain <arg1: TegraId> <arg2: Outparam, 0-NULL or 1-Valid pointer> : Test behavior of DU_MCC_GetActive_BootChain API with any argument.
-test_set_next_bootchain <arg1: TegraId> <arg2: BootChainId> : Test behavior of DU_MCC_SetNext_BootChain API with any arguments.
-test_tegra_reboot <arg1: TegraId> <arg2: HoldOption> <arg3: delay> : Test behavior of DU_MCC_TegraReboot API with any arguments.
-test_system_reset <arg1: delay> : Test behavior of DU_MCC_SystemReset API with any arguments.

-flash_mcu_fw <new_Hexfile>  -f (for force flash) : Flash the new Production FW on MCU
              Provide the full path of the Production FW hexfile to be flashed

-flash_mcu_ufw <new_UFW_Hexfile>  -f (for force flash) : Flash the new Update-FW on MCU
               Provide the full path of the UpdateFW hexfile to be flashed

-get_fw_version         : Read currently running MCU FW version

-get_update_fw_version  : Read UPDATE-FW version flashed on MCU

-get_mcu_hexfile_version <mcu_Hexfile> : Read the version of the hexfile from its content
                         Provide the full path of the hexfile

-get_inforom_dump           : Read data from infoROM dump

-set_bootstrap <x1|x2> <ufs|qspi|emmc>  : Change Tegra boot strap medium

-safety_services <enable|disable|getStatus>  : Enable or disable Safety Services on MCU.
                         getStatus : prints the current status of Safety Services

-nw_cfg <base|base_safety|hyperion_dev|hyperion_8_1_dev|hyperion_8_1_safety|getStatus>  : choose or get NW Configuration on MCU.
               getStatus : prints the current status of NW Configuration on MCU.

-reboot_mcu_afw  -tDelay_mcuwait <T> -set_tegra_rec  <1|0> : Reboot MCU in Production FW mode
-reboot_mcu_ufw  -tDelay_mcuwait <T> -set_tegra_rec  <1|0> : Reboot MCU in Update-FW mode

-set_mission_mode <on|off> : Set or Reset the Mission mode status for MCU

-enter_sc7 : Enter SC7 mode

-get_uss_monitor : Get USS Monitor data