NVidia Jetson Jetpack 6 support?
-
@otca
Please runcat /etc/extlinux/extlinux.conf, and paste here. -
@veye_xumm
TIMEOUT 50
DEFAULT JetsonIOMENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-configLABEL recovery
MENU LABEL Ubuntu (Recovery Mode - Runlevel 1)
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config singleLABEL Multi-User-With-Networking
MENU LABEL Ubuntu (Multi-User-With-Networking - Runlevel 3)
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config 3LABEL Multi-User-With-GUI
MENU LABEL Ubuntu (Multi-User-With-GUI - Runlevel 5)
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config 5LABEL JetsonIO
MENU LABEL Custom Header Config: <CSI Camera IMX219 Dual>
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config
OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veye_mvcam-dual.dtbo -
@veye_xumm
I have decompiled the dtb file usingdtc -I dtb -O dts -o decompiled.dts tegra234-p3767-camera-p3768-veye_mvcam-dual.dtboI see that these parameters are not set correctly for IMX264, correct me if I'm wrong.
i2c@0 { reg = <0x00>; #address-cells = <0x01>; #size-cells = <0x00>; rbpcv3_mvcam_a@3b { compatible = "nvidia,veye_mvcam"; reg = <0x3b>; devnode = "video0"; physical_w = "5.6"; physical_h = "3.1"; sensor_model = "mvcam"; use_sensor_mode_id = "false"; status = "okay"; reset-gpios = <0x5a 0x3e 0x00>; phandle = <0x482>; mode0 { mclk_khz = "24000"; num_lanes = "2"; tegra_sinterface = "serial_b"; phy_mode = "DPHY"; discontinuous_clk = "yes"; dpcm_enable = "false"; cil_settletime = "0"; lane_polarity = "6"; active_w = "3088"; active_h = "2064"; mode_type = "raw"; csi_pixel_bit_depth = "8"; pixel_phase = "y8"; readout_orientation = "0"; line_length = "3088"; inherent_gain = "1"; mclk_multiplier = "2"; pix_clk_hz = "375000000"; gain_factor = "16"; framerate_factor = "1000000"; exposure_factor = "1000000"; min_gain_val = "16"; max_gain_val = "170"; step_gain_val = "1"; default_gain = "16"; min_hdr_ratio = "1"; max_hdr_ratio = "1"; min_framerate = "2000000"; max_framerate = "20000000"; step_framerate = "1"; default_framerate = "20000000"; min_exp_time = "13"; max_exp_time = "333333"; step_exp_time = "1"; default_exp_time = "2495"; embedded_metadata_height = "0"; };The corresponding parameters for IMX264 is as follow:
Property IMX264 physical_w 8.390 physical_h 7.066 active_w 2432 active_h 2048 pixel_t RG 8,10,12 max_gain_val 48 step_gain_val 0.100 max_framerate (2L08) 35.5 max_framerate (2L10) 35.5 max_framerate (2L12) 35.5 what do u think about do the needed changes and recompile the dts to dtbo?
Thanks for ur help
-
@otca i have done the top changes and still i have the same errors:
dmesg | grep -i 'fail'
[ 5.139606] hid-generic: probe of 0003:1C4F:0202.0004 failed with error -22
[ 9.364966] videodev: module verification failed: signature and/or required key missing - tainting kernel
[ 11.505696] dce: dce_admin_setup_clients_ipc:561 Get queue info failed for [2]
[ 12.284602] veye_mvcam: mvcam_read: Reading register 0x04 failed
[ 12.284613] mvcam 9-003b: failed to read chip id
[ 12.284617] mvcam 9-003b: mvcam_identify_module failed.
[ 12.795113] veye_mvcam: mvcam_read: Reading register 0x04 failed
[ 12.795129] mvcam 10-003b: failed to read chip id
[ 12.795133] mvcam 10-003b: mvcam_identify_module failed.
[ 17.325445] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:dmesg | grep -i 'i2c'
[ 0.236421] i2c_dev: i2c /dev entries driver
[ 3.375822] tegra-i2c 3160000.i2c: Adding to iommu group 1
[ 3.380887] tegra-i2c 3180000.i2c: Adding to iommu group 1
[ 3.384775] tegra-i2c 31b0000.i2c: Adding to iommu group 1
[ 3.388075] tegra-i2c c240000.i2c: Adding to iommu group 1
[ 3.391424] i2c 1-0025: Fixing up cyclic dependency with 3520000.padctl
[ 3.392065] tegra-i2c c250000.i2c: Adding to iommu group 1
[ 3.396084] i2c i2c-2: Added multiplexed i2c bus 9
[ 3.396781] i2c i2c-2: Added multiplexed i2c bus 10
[ 3.396786] i2c-mux-gpio bus@0:cam_i2cmux: 2 port mux on 3180000.i2c adapterdmesg | grep -i 'veye'
[ 11.782990] mvcam 9-003b: veye mv series camera driver version: 01.01.04
[ 12.284602] veye_mvcam: mvcam_read: Reading register 0x04 failed
[ 12.286011] mvcam 10-003b: veye mv series camera driver version: 01.01.04
[ 12.795113] veye_mvcam: mvcam_read: Reading register 0x04 failed -
@otca
I would say that this phenomenon now has nothing to do with the details of the dts. The problem now is that i2c doesn't work.
This is often something to do with the hardware connection cables, and whether the camera is working properly.
Do you have a multimeter? An oscilloscope? Can you measure the power supply to the camera module, and whether the i2c communication is working? -
@otca
Have you ever disassembled the camera module?Is the direction of the internal FFC flex cable correct? -
@veye_xumm said in NVidia Jetson Jetpack 6 support?:
Have you ever disassembled the camera module?Is the direction of the internal FFC flex cable correct?
I have not disassembled camera but if you think i should disassemble and check connections, I'll give it a try.
if its possible please give me reference needed for this part.
and for the other question, I did check the power supply and it was 5.14 V. -
-
@otca
There's nothing wrong with that in my opinion. You have 4 cameras, have you tried any others?
Or try plugging the camera into another mipi port ? -
@veye_xumm i did try the other cameras and i got the same results
-
Based on the current situation, it seems unlikely that the camera module is damaged because the probability of both cameras failing at the same time is very low. Do you have any other Jetson boards, or even a Raspberry Pi? If you do, you could try connecting the camera to them to determine if the camera is functioning properly.
In addition, could you measure the voltage level of the following pin?
-
@veye_xumm said in NVidia Jetson Jetpack 6 support?:
Based on the current situation, it seems unlikely that the camera module is damaged because the probability of both cameras failing at the same time is very low. Do you have any other Jetson boards, or even a Raspberry Pi? If you do, you could try connecting the camera to them to determine if the camera is functioning properly.
Thanks for the suggestion! I do have other Jetson and Raspberry Pi boards available, so I’ll try connecting the camera to one of those to see if it’s working properly. By the way, I checked the J1-Pin11 voltage, and it reads 3.33V. If there are any other measurements or tests you think I should run, just let me know.
-
Do u know this issue?
-
Idk but i think this is helpful to know
My jetson 24pin csi connector:
-
@otca It looks like the driver is reporting an error. Suggest you don't use the jetson-io mechanism and try strictly following the steps on our wiki.
-
@veye_xumm well I done the whole process of jetson upgrade for MV-MIPI-IMX264M on another jetson orin nano jetpack 6 (5.15.136-tegra) and still the i2cdetect -y -r 9 and i2cdetect -y -r 10 returns the following:
i2cdetect -y -r 9 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --i2cdetect -y -r 10 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --ls /sys/firmware/devicetree/base/bus@0/cam_i2cmux/i2c@0/ '#address-cells' phandle rbpcv3_mvcam_a@3b '#size-cells' name rbpcv2_imx219_a@10 reg statusls /sys/bus/i2c/drivers/ at24 fusb301 nxp-pca9450 sec_pmic axp20x-i2c ina3221 pca953x simple-mfd-i2c bd9571mwv max732x pca954x smbus_alert bq27xxx-battery max77620 pf8x00 tpm_i2c_infineon cros-ec-i2c max8973 pfuze100-regulator ucsi_ccg cs2000-cp mp8859 rk808 usb3503 dummy mvcam rohm-bd718x7 vc5 fan53555-regulator nvvrs_pseq rtc-ds3232extLinux Config
LABEL imx264 MENU LABEL Ubuntu (MV-MIPI-IMX264) LINUX /boot/Image FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv.dtb INITRD /boot/initrd APPEND ${cbootargs} root=PARTUUID=3354a552-d558-40fb-857c-8e1886cb2a67 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config OVERLAYS /boot/dtb/tegra234-p3767-camera-p3768-veye_mvcam-dual.dtboUpgarde Jetson Jetpack 6
My guess is that the drivers (.ko) are installed correctly but the device tree still need some works to do, because i don't detect the camera on my i2c.
These are the steps I have done till now:sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/downstream/i2c/* /lib/modules/$(uname -r)/updates/drivers/media/i2c/ -f sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/downstream/terga-camera/tegra-camera.ko /lib/modules/$(uname -r)/updates/drivers/media/platform/tegra/camera -f sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/upstream/*.ko /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ -f sudo depmodcontent of each folder is as follow:
ls /lib/modules/$(uname -r)/updates/drivers/media/i2c/ ar1335_common.ko lt6911uxc.ko nv_ar0234.ko nv_imx274.ko nv_ov5693.ko veye_mvcam.ko cs_imx307.ko max9295.ko nv_hawk_owl.ko nv_imx318.ko pca9570.ko veye_vbyone.ko cs_sc132.ko max9296.ko nv_imx185.ko nv_imx390.ko veyecam.ko virtual_i2c_mux.ko ds90ub954.ko max96712.ko nv_imx219.ko nv_imx477.ko veye_imx335.ko ls /lib/modules/$(uname -r)/updates/drivers/media/platform/tegra/camera tegra-camera.ko ls /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ v4l2-async.ko v4l2-dv-timings.ko v4l2-fwnode.ko v4l2-h264.ko v4l2-mem2mem.ko videodev.koI am clueless what it is wrong here.
Thanks -
@otca
In fact, when the following pin is high, i2cdetect should be able to show 0x3b that the device is online. This has nothing to do with either ko or dtb.
So I'm wondering why this is the case with your board.
Also, with your current configuration, can you use sudo dmesg and send me all the outputs to look at?
-
@Otca
I wonder if it would be convenient for you to send me your jetson board along with a set of camera boards and we'll test them? -
@veye_xumm
thanks for your guidance.
The dmesg log is appended.
MV-MIPI-IMX264.txtunfortunately I'm too far away from you.I'm so sorry that it's not an option for me to send board and camera.
-
@otca
All of this still suggests that i2c is not working.
When I look at your other postings, they seem to say that the camera itself is fine and not broken, right?
