"No v4l2_dev found"

Software
,
1

Does anyone have any hints on debbugging this kind of errors?

[   96.065064] zedx 10-0010: Detected ZED-X sensor
[   96.065070] zedx 10-0010: zedx_probe: Serial Number : 309XXXXXX
[   96.065073] No v4l2_dev found and associated in tegracam_v4l2subdev_register(..).
[   96.065074] This most certainly means that you have an error in your dts,
[   96.065076] often related to tegra-camera-platform node, nvcsi or vi node addresses.
[   96.065077] It can also be due to status = "disabled" properties when using overlays.
[   96.065275] zedx 10-0010: zedx_probe: Video device id not found

media-ctl shows nothing, no channels defined:

Media controller API version 5.15.136

Media device information
------------------------
driver          tegra-camrtc-ca
model           NVIDIA Tegra Video Input Device
serial
bus info
hw revision     0x3
driver version  5.15.136

Device topology

(there’s nothing else, that’s the end of media-ctl output)

The relevant chunks are defined in the device tree, camera → nvcsi → capture-vi.
However, it’s a dynamically loaded overlay, which complicates things a lot.

Are these v4l2 devices created during a camera probe, or do they need to be pre-initialized for the camera driver somehow? Also, is there a way to force re-configuration, or re-initialize this subsystem somehow without rebooting the system?

2

Hi @asuykov
Can you please describe what’s your goal?
Do you need a custom device tree for a custom carrier board?

3

The goal is to get the cameras working in BalenaOS. It’s not exactly L4T, and it has its own quirks and limitations which I’m trying to find a way around. In particular, it cannot load device tree overlays the usual way, at least not yet.

The system is running on a Syslogic device which you have a device tree for already. I’m getting the same exact message using that tree as well, so that’s not the problem most likely.

What I’m looking for is, perhaps there are developers who have encountered similar issues before and who would be willing to share some insights. Maybe there’s a known cause for this, or there’s something I could check that might help, or just general tips on debugging camera driver initialization issues.

4

@asuykov please write an email to support@stereolabs.com with all the details