NvOdmDevice BadValue #2

Hi, this is a follow up of NvOdmDevice BadValue.

I tried it outside of the container and it seems to work there. Inside, I randomly gets the following output from the Argus::CameraProvider::create() function:

OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0
NvPclHwGetModuleList: WARNING: Could not map module to ISP config string
NvPclHwGetModuleList: No module data found
(NvOdmDevice) Error BadValue:  (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/HotplugMonitor.cpp, function initializeHotplug(), line 201)

After that, the function gets stuck. Any idea what could be wrong?

Ok, maybe it is a permission thing. It does not work if the application is run as normal user inside the container but running it again as root (sudo), it seems to work. Here is the output from the Argus::CameraProvider::create call in that case:

OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0
NvPclHwGetModuleList: WARNING: Could not map module to ISP config string
NvPclHwGetModuleList: No module data found
OFParserGetVirtualDevice: NVIDIA Camera virtual enumerator not found in proc device-tree
---- imager: No override file found. ----
LSC: LSC surface is not based on full res!

Any idea whats wrong with running as normal user? The user inside the container is in the video group, is that enough?

Need below for argus in docker.
/tmp/argus_socket:/tmp/argus_socket

Hi ShaneCCC,

I built with -DDISABLE_MULTIPROCESS=ON, so argus_socket should not be necessary. I think it also wouldn’t work as root then.

Yes, if build by DDISABLE_MULTIPROCESS=ON don’t need argus_socket.
Don’t have much idea for your case. Maybe some libs access permission problem.

What is the meaning of this error message?

(NvOdmDevice) Error BadValue:  (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/HotplugMonitor.cpp, function initializeHotplug(), line 201)

Because this is only printed when it gets stuck. Maybe can you check what could lead to this error message to narrow down the issue?

This message doesn’t cause the problem.

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