Driver development 0v5693

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
1

I want to force the Xavier AGX developer kit to use the OV5943 driver instead of the camera plugin manager. so I followed the below link to force use the standard driver and device tree for the OV sensor.

using this link Welcome — Jetson Linux<br/>Developer Guide 34.1 documentation,
under Device Registration->using main platform device tree,

After doing all the process still, I could not able to enumerate OV5943 as a video device so that I can read the data from the camera.

The process followed,
I have edited this device-tree file as follows, removed the camera plugin manager, and added the Omni sensor device tree file.

the edited device-tree file is “kernel/hardware/nvidia/platform/t19x/galen/kernel-dts/tegra194-p2888-0001-p2822-0000.dts”.
default is
" #include “common/tegra194-p2888-0001-p2822-0000-common.dtsi”
#include “common/tegra194-p2822-camera-modules.dtsi”
#include “t19x-common-modules/tegra194-camera-plugin-manager.dtsi”"

the plugin manager is removed from the file and added the respected device tree,
“#include “common/tegra194-p2822-0000-camera-e3326-a00.dtsi””

then changed the camera modules file like this,
“i2c@3180000 {
e3326_cam0: ov5693_c@36 {
status = “okay”;
};”

then recompiled my kernel and flash with into the Xavier with LFS also. but sometimes my login screen not coming, but on serial port login work but no video device enumeration in the dev folder of my LFS.

3

What’s the LFS, Could you attached your dtb here. And what’s the version?
Also what the message about the ov5693 when failed to gen the video node? dmesg | grep -i ‘ov5693|nvcsi|vi4’

4

LFS - Linux File System.
version - 4.9.140-Tegras

I have added the screenshots of the result

Terminalcapture
Terminalcapture1920×1080 778 KB

this is the device tree zip complete which i used
nvidia.zip (1.2 MB)

5

Enable the debug print of the sensor driver to check what’s happen.

6

enabled debug print this is what its showing

Screenshot from 2020-11-09 21-34-54
Screenshot from 2020-11-09 21-34-541920×1080 683 KB

7

What’s the below

dmesg | grep -i 'ov5693\|nvcsi\|vi'
v4l2-ctl --list-devices
8

the grep response -
grep_out.txt (11.8 KB)

the v4l2-ctl response is

Screenshot from 2020-11-10 10-31-40
Screenshot from 2020-11-10 10-31-401920×1080 229 KB

9

Addd status = “okay”; to the nvcsi and vi scope to try.

10

can you please tell which file we need to add

11

Should be below file.
…/hardware/nvidia/platform/t19x/common/kernel-dts/t19x-common-modules/tegra194-camera-e3326-a00.dtsi

12

after adding the status to vi and nvcsi the video0 device got enumerated but just want to know can i view the sensor output using any player directly.

the dmesg we got is this,
grep_out.txt (12.9 KB)

13

You can run the v4l2-ctl to check if the sensor is working well then run nvgstcapture-1.0 to get the preview.

14

thank you, tried using ‘gst-launch-1.0 nvarguscamerasrc ! nvvidconv ! xvimagesink’. the camera output came.

can you help me how to control these registers write a read of these using a c or cpp code.

15

What register do you want to access?

16

i had omni sensor where they gave register to write in basic settings for longer and shorter cable, similarly to write like BLC, gains of rgb channels like those.

17

Have reference to programing guide to developer sensor driver to do it.