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
Hello, is there a way we could issue a restart to the NvMedia engines (ISP, NVENC, NVDEC, VIC) without doing a full system reboot? We are able to issue a reboot to the system with the command below, is there something similar for each of the engines?
system reboot command: sudo su -c 'echo 1 > /sys/class/tegra_hv_pm_ctl/tegra_hv_pm_ctl/device/trigger_sys_reboot'
Hey @SivaRamaKrishnaNV, we noticed that it is possible to get the NvMedia engine into an error state, which we have done before accidentally with the encoder, but is not always repeatable (we got into this error state with bad encoder configuration parameters). Restarting the system resolves the error state, so it would be great if there is a way to restart the engine instead of the entire system.
Can you provide few more details about the use case
What was the error code status like ( NVIDIA DRIVE OS Linux SDK API Reference: Basic NvMedia Types and Structures | NVIDIA Docs) NVMEDIA_STATUS_BAD_PARAMETER/NVMEDIA_STATUS_ERROR/NVMEDIA_STATUS_UNDEFINED_STATE/NVMEDIA_STATUS_INVALID_STATE ? Which APIs has returned the error?
None of NvMediaIEP APIs not working once you enter that state and hence requires to reset the engine to proceed?
Yeah, we are building up a module and would like to integrate recovery options. One recovery method is to reset the engine directly and reinitialize the engine.
Yeah that’s right, there is no error code for this, you are able to call the API but the module just hangs right after. We needed a power cycle for the engine to reset properly. Specifically I have got into this stage only with the encoder engine thus far. I believe this happens when the NvMediaEncodePicParamsH265 is not default initialized, and somehow the encoder still works to encode for a few frames before getting into the error state.
However, while building up other NvMedia modules, we hope to integrate the engine reset (SIPL, encoder, decoder, VIC) as a possible recovery mechanism.