let me gather the device for checking,
in the meanwhile, is it possible for moving to latest Jetpack release version for confirmation?
Hi, @JerryChang
We have used JetPack 5.1 L4T- 35.2.1 BSP
This release supports Jetson Orin NX 16GB production module, Jetson AGX Orin 32GB production module and Jetson AGX Orin Developer Kit. It also supports Jetson AGX Xavier series and Jetson Xavier NX series modules, as well as Jetson AGX Xavier Developer Kit and Jetson Xavier NX Developer Kit.
Should we try Jetson Linux 35.3.1 BSP ?
hello san1998,
please check you’re using correct GPIO pins.
for example, you may see-also reference driver, it’s CAM1_PWDN, TEGRA234_MAIN_GPIO(AC, 0) as reset-gpios for CSI-C.
or… you may try removing those overlay files to avoid it overwrite your settings.
Hi, @JerryChang
These are the current settings for GPIO:
#define CAM0_RST_L TEGRA234_MAIN_GPIO(H, 3)
#define CAM0_PWDN TEGRA234_MAIN_GPIO(H, 6)
#define CAM1_RST_L TEGRA234_MAIN_GPIO(AC, 1)
#define CAM1_PWDN TEGRA234_MAIN_GPIO(AC, 0)
#define CAMERA_I2C_MUX_BUS(x) (0x1E + x)
/ {
gpio@2200000 {
camera-control-output-low {
gpio-hog;
output-low;
gpios = <CAM0_RST_L 0 CAM0_PWDN 0
CAM1_RST_L 1 CAM1_PWDN 1>;
label = "cam0-rst", "cam0-pwdn"
"cam1-rst", "cam1-pwdn";
};
};
i2c@3180000 {
ov5693_c@36 {
clocks = <&bpmp_clks TEGRA234_CLK_EXTPERIPH1>,
<&bpmp_clks TEGRA234_CLK_PLLP_OUT0>;
clock-names = "extperiph1", "pllp_grtba";
mclk = "extperiph1";
clock-frequency = <24000000>;
reset-gpios = <&tegra_main_gpio 1 GPIO_ACTIVE_HIGH>;
pwdn-gpios = <&tegra_main_gpio 0 GPIO_ACTIVE_HIGH>;
vana-supply = <&p3509_avdd_cam_2v8>;
vif-supply = <&p3509_vdd_1v8_sys>;
};
};
};
And on the Xavier NX carrier board our camera module is connected to J9 Camera Conn. #2 which is CSI-2 according to p579520-Jetson_Xavier_NX_DevKit_Carrier_Board_Specification_v1.0.pdf
The camera module is connected on CAM0 , which is CSI -2 according to the Xavier NX carrier board diagram.
hello san1998,
let’s try back-up and removing all those device tree overlay files for testing.
i.e. $ ls /boot/*camera*.dtbo
hi @JerryChang,
I removed tegra194-p2822-camera-e3326-overlay.dtbo and checked, there seems to be no change. I am still getting a green screen.
Also, I would like to confirm if OV5693 camera is supported by Orin NX.
Thank you.
that’s not supported due to different camera connector. however, ov5693 camera is supported with AGX Orin.
Would a custom hardware with the right camera connector work for Orin NX to support OV5693?
And may I know why would a different camera connector cause a problem?
Thanks.
The OV5693 camera that works with the Xavier NX Dev-board, has the compatible camera connector for it.
This camera also works with the Xavier NX SoC on Xavier NX Dev-board. However, when I use the OrinNX SoC on the same board, the camera does not stream any CSI data.
I am puzzled by this, since the connector should be functional for both SoCs.
Thanks.
hello san1998,
we’ve test on Orin NX ( P3768+P3767), it’s verified CSI-C works normally with latest Jetpack release version, Jetpack-5.1.2
Hi,
For now we do not have a Orin carrier board (p3767), hence using Xavier carried board (p3509). We have flashed the hardware using the p3768+p3509 configuration file with the version JP5.1.1 (release-35.3.1)
The OV5693 camera that works with the Xavier NX Dev-board, has the compatible camera connector for it.
This camera also works with the Xavier NX SoC on Xavier NX Dev-board. However, when I use the OrinNX SoC on the same board, the camera does not stream any CSI data.
FYI, there’re some booting issues with JP-5.1.2 on P3509+P3768.
We are able to boot the device from external USB drive and able to access the board. We are just trying to understand what must be causing the issue with Orin soc on Xavier carrier board for the video not to stream…
Thanks.
hello san1998,
may I also know how you flash the target? can you confirm the flash process is complete?
here’s an example,
Orin NX + Xavier NX carrier (p3509+p3767)
$ sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal
@JerryChang Hi,
Yes the flash process was complete and we used the same script for flashing.
sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device sda1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal
hello san1998,
you may disassembler the dtb file into text file, please share that for examination.
for example, $ dtc -I dtb -O dts -o output.txt tegra234-xxx.dtb
BTW, you may check /boot/extlinux/extlinux.conf for FDT entry to confirm the device tree blob you’re using.
@JerryChang Hi,
I have attached the text format of final the final dtb.
Yes, also checked that in extlinux.conf the FDT entry is same as the device tree blob we use.
Thanks.
output.txt (409.2 KB)
I’ve reviewed device tree settings, please refer to Topic 260583 to apply camera firmware with debug flag enabled to gather more details.
@JerryChang , hi
On Orin NX (p3768 + p3767) with latest JP-5.1.2 I face the exact same issue with same errors…
I am using OV5693 camera sensor connected to CSI-2.
and set the lane polarity to 0
And the connector is verified, according to the schematic below:
Thanks.