Orin can not access /dev/video0

hello syan,

may I know how you obtain the kernel sources, are you using source_sync.sh?
please try download R34.1.1 public_sources.tbz2, and use the GCC-9.3 toolchain to build the kernel sources .
here’re steps for your reference,
$ export TEGRA_KERNEL_OUT=/home/user/Orin/r34.1.1_build
$ export CROSS_COMPILE_AARCH64=/home/user/toolchain_gcc_9.3/bin/aarch64-buildroot-linux-gnu-
$ cd Linux_for_Tegra/source/public
$ ./nvbuild.sh -o $TEGRA_KERNEL_OUT

Hi Jerry,
I’m using toolchain to build kernel.
And I found my GCC version is 11.3.
I can succeesully build kernel dtb after downloading GCC-9.3

Build kernel command as same as Xavier except GCC path.

Now I want to reflash orin by this command

./flash.sh  -k kernel-dtb jetson-agx-orin-devkit mmcblk0p1

But occur error

Error:  Return Value 13
Command tegradevflash_v2 --earse kernel-dtb
Failed to flash/read t186ref.

hello syan,

the partition name has changed as you can see via Orin’s flash messages,
for example,

[ 650.2811 ] Writing partition A_kernel-dtb with kernel_tegra234-p3701-0000-p3737-0000_with_odm.dtb [ 307630 bytes ]
[ 650.2836 ] [................................................] 100%
[ 651.6726 ] Writing partition B_kernel-dtb with kernel_tegra234-p3701-0000-p3737-0000_with_odm.dtb [ 307630 bytes ]
[ 651.6747 ] [................................................] 100%

hence, please update the commands as… -r -k A_kernel-dtb to update orin’s kernel-dtb partition.
thanks

Hi Jerry,
I update command as

sudo ./flash.sh -r -k A_kernel-dtb jetson-agx-orin-devkit mmcblk0p1

It says file does not exist…

hello syan,

it’s the -r options to skips building system.img; reuse the existing one. please check whether you have system.img created on your local host. you may remove -r options for the first time running this.

Hi Jerry,

It can work and successifully flash orin by

sudo ./flash.sh -k A_kernel-dtb jetson-agx-orin-devkit mmcblk0p1

But I still can not access /dev/video0 by ov5693

I followed 4.1.5 to change default camera:

Step 1.) update this file

hardware/nvidia/platform/t23x/concord-dts/ tegra234-p3701-0000-p3737-
0000.dts

Step 2.) add ov5693

#include "cvb/tegra234-p3737-0000-camera-e3333-a00.dtsi"

Step 3.) complie kernel and flashed orin

When host device shows successifully, I type ls -la /dev/vid* on orin

It strill can not work…

hello syan,

is the device register correctly? could you please gather the complete logs via serial console for reference,
thanks

Hi Jerry,

Do you mean my step 3.) compile kernel logs?

compilerLog.txt (498.2 KB)

hello syan,

no, I meant the bootloader logs and kernel init messages while system boot-up.
please setup serial console and gather the logs for reference, thanks

Hi Jerry,

I use demsg to get some log…
I’m not sure this log is what you want…?
dmesg.txt (82.5 KB)

hello syan,

[    7.598816] tegra194-vi5 13e40000.host1x:vi0@15c00000: initialized
[    7.599582] (NULL device *): fops function table already registered

it looks NULL devices.
may I know what’s the camera board you’re using, could you please take a snapshot and share the camera board naming.

Hi Jerry,

I think it is ov5693

1 Like

hello syan,

yes, it’s the ov5693 sensor module, but this is the camera board named e3326. this is not supported currently.

Hi Jerry,
I have checked the different of e3326 on Xavier and e3333 on Orin.
And I found e3326 just have 1 node and e3333 have 6 node.

i2c@0{
.....
};

i2c@1{
.....
};

....

If I delete other 5 node, does e3326 can work?
Because I just have e3326 this camera board…

Or you have the other way let orin support it?

hello syan,

they’re different, there’s i2cmux with e3333 to expand the i2c-bus for six camera nodes; but e3326 don’t.
we don’t enable e3326 since it cannot connect to Orin platform directly, however, you’ve a flex cable to extend the camera connection.

Hi Jerry,
So In Orin e3326 is defual disable.
But we still can modfy some files in manually to enable it?
if yes, how should we do next?

hello syan,

there also some issues for enabling e3333 on Orin series with JP-5.0 DP.
I’ll suggest you waits for next JetPack public release, (which should release around Q3/2022), this release will include the fixes to enable ov5693.
after that, you may try revise the device tree and bringup e3326 camera board.

Hi Jerry,
I want to double check my flow is correct to change orin’s default camera(imx274 daul → ov5693 e3333)

As Orin can not access /dev/video0 - #12 by syan I said.

1.) Does it succesiful change, or I miss some step you can point that.
2.) If orin changed , how we can validated it?
3.) If I change my camera to imx185 does orin can support it or it still has camera borad limit?

hello syan,

note, this JetPack 5.0.1 is a development preview release.
your previous comment looks correct steps, please have a try to see-also Release Notes (r34.1) for session [4.1.5 Important Note] to enable IMX185.
thanks

Hi Jerry,
Ok. We’re looking forward to next JetPack version!!

And I trying to change default camera to imx185 which according to session 4.1.5
Then I reference this post Xavier - using raw CSI without i2c to remove i2c .

It should generate/dev/video0 automatically, does it?

Here’s my dmesg log.
dmesg.txt (82.5 KB)