We use an application to sample frames from GMSL cameras and encode them. While running the application, we get the “System Throttled due to Over-current” notification and the below print in the dmesg.
As per the data from jtop the overall power usage is around 15-16W only and it is much lower than the 20W power mode that we are using.
Also, strangely the occurrence of the issue reduces while running in 20W, 4-core mode. But the CPU usage is extremely high in this mode, and it is not suitable for our use case.
We tried setting custom power mode profile in 20W,6-core mode by reducing the nvenc frequency to 499MHz and all CPU frequency to 1.3GHz. Even in this configuration we are facing the issue.
It’s not direct gstreamer commands. We are using custom application based on OpenCV which grabs frames from 4x GMSL cameras and post process frame (i.e., scaling and stitching).
Our assumption is OC warning should be triggered when overall Xavier NX power consumption is greater than or equal to 5000mA (crit_current_limit_0). As you can see jtop result, the power consumption of NX is only around 15W (i.e., power mode set to 20W) and current limit is not crossed.
Questions:
Why OC warnings triggered when NVENC block alone stressed to max operating frequency?
Is there any known limitation with respect to NVENC max frequency operation?
Is that fine to disable OC warnings and ignore this warning with above CPU & GPU consumption level?
Kindly let us know your recommendation. It’s critical factor to decide Xavier NX SOM performance for our use case.
The “5000 mA” limitation is also there on 32.7.x. And you may not able to observe by jtop because the over current warning would come up if a sudden over current situation happened. Which means jtop is not able to observe it as the sampling period is not fast enough.