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?
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?
may I know what’s your steps to update device tree?
please also check /boot/extlinux/extlinux.conf, if there’s FDT entry, it’ll prior to load device tree via file system.
thanks
since there’s FDT entry, it’ll prior to load device tree via file system.
why don’t you scp the compiled device tree, tegra234-p3701-0000-p3737-0000.dtb to the target, and revise the extlinux.conf file to point FDT as your new dtb file.
could you please also modify the device tree file, for example, /kernel-dts/cvb/tegra234-p3737-camera-modules.dtsi
please exclude all other include files and leave only imx185 enabled for confirmation, thanks
My target is let Orin generate /dev/video0 through remove i2c
Updated my status:
I’m back to use e3333 (I’m unfamiler to use imx185) and modify some files which followed as Xavier’s:
a.) tegra234-p3701-0000-p3737-0000.dts
Add 1 line #include "cvb/tegra234-p3737-0000-camera-e3333-a00.dtsi"
b.) tegra234-p3737-camera-modules.dtsi
Only included e3333.
And only one camera which same as e3326 set status is okay
i2c@3180000 {
e3326_cam0: ov5693_c@36 {
status = "disabled";
};
...
tca9548@77 {
status = "disabled";
i2c@0 {
e3333_cam0: ov5693_a@36 {
status = "disabled";
};
};
i2c@1 {
e3333_cam1: ov5693_b@36 {
status = "disabled";
};
};
i2c@2 {
e3333_cam2: ov5693_c@36 {
status = "okay";
};
};
since there’re GPIO driver fixes, and l4t-r34 is a developer preview release, it may deprecated when production release is available.
please wait JetPack 5.0.2, and please verify camera porting on this first JetPack 5 production release.
thanks
I have a similar problem to you…
I use ov5693 to test jetpack 5.0.1 on Xavier and it doesn’t work
In addition, Orin cannot directly connect to ov5693. Did you make the transfer cable yourself?
please note that JetPack 5.0.2 is now available, please access JetPack SDK 5.0.2 | NVIDIA Developer and moving to production release.
JetPack 5.0.1 is developer preview release, and it’ll deprecated soon.