Closed AxelZschutschke closed 3 years ago
Any help highly appreciated. I am happy to test and/or supply additional info!
Side-note 1: /dev does not have any "video" listings Side-note 2: using your kernel driver but the device-tree file tegra210-p3448-0000-p3449-0000-b00.dtb from the arducam-guys seemingly works... unfortunately I did not find any sources from them
Checked out dts diffs after de-compiling: only found a couple of renames and the following diffs: you use status : "okay" -> setting "disabled" seems to fix the issue (or shadows) it - but I am able to capture images
zip contains the result of your patch and a "fixed" version, which does the trick for me decompiled_dts.tar.gz
Did some more tests with the workaround image today, cams are working but driver is refusing cam id #1. Seems it does not allow for "compatible":"nvidia,imx477" -> I changed this to "riderun/imx477" as with the id #0 cam and now it works...
Same issue here. i2c fails to register.
peter@ariel:~$ dmesg | grep "imx\|ic2\|video"
[ 0.000000] Kernel command line: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 tegra_fbmem=0x800000@0x92cb0000 is_hdmi_initialised=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet
[ 0.619555] Linux video capture interface: v2.00
[ 1.210729] i2c i2c-7: Failed to register i2c client imx477 at 0x1a (-16)
[ 1.218354] i2c i2c-7: of_i2c: Failure registering /cam_i2cmux/i2c@0/rbpcv3_imx477_a@1a
[ 1.226402] i2c i2c-7: Failed to create I2C device for /cam_i2cmux/i2c@0/rbpcv3_imx477_a@1a
[ 1.226678] i2c i2c-8: Failed to register i2c client imx477 at 0x1a (-16)
[ 1.233502] i2c i2c-8: of_i2c: Failure registering /cam_i2cmux/i2c@1/rbpcv3_imx477_e@1a
[ 1.233506] i2c i2c-8: Failed to create I2C device for /cam_i2cmux/i2c@1/rbpcv3_imx477_e@1a
[ 1.233926] imx477 6-001a: tegracam sensor driver:imx477_v2.0.6
[ 1.257287] imx477 6-001a: imx477_board_setup: error during i2c read probe (-121)
[ 1.257313] imx477 6-001a: board setup failed
[ 1.257374] imx477: probe of 6-001a failed with error -121
Cheers,
Peter.
Hi @AxelZschutschke, we just pushed some changes to the repo, including the change in the compatible that you found, nice catch! Please cive it a try and let me know if the current patch works properly for you without modifications. In Jetson Nano only 1 camera should load. You can see /dev/video0 device after loading the kernel and DTB
Hi @rrcarlosrodriguez, thank you for the support and the good work alltogether! I will try the version during the day. But one question straight away: why only one camera?
Hi @AxelZschutschke , interesting, after reading your question I was wondering why people is talking about 2 cameras support in the Jetson Nano. And then I realized we are working with the very first model, A02, which has 1 camera port only. There is a new EV Kit model, B01 which has 2 camera ports, which is probably the one you have. You can see the differences here
Please test the new version of the patches and let me know if it works with the 2 cameras in the Jetson Nano.
Just tried the latest changes and it still fails to register the i2c client for me.. It's basically the same error msg as before. I'm also running the B01 board with two camera outputs, my camera is in the cam0 port.
Even if I'm using Xavier NX (not Nano), it still fails just like @ClonedPuppy .. exactly same issue.. :( How did you make it in NX, @AxelZschutschke ?
Hi @zinuok. Did you perform any hardware change? We didn't see problems with i2c buses and your problem happens like if our hardware was different.
-JC
Just to be clear, to get the camera in the i2c bus you need to make this change:
Did you do the change already?
@DavidSoto, not sure if you're asking me or @zinuok, but if me, then yep, mod has been done. I''m on a Nano however, B01 board (two cam ports).
To @juankruz and @DavidSoto : my hardware is
should we remove the resistor in Xavier NX?
After removing the R8 resistor from IMX477, it works very well with Xavier NX. Thank you for @juankruz and @DavidSoto , also @ClonedPuppy for inviting me to this issue Thanks :)
Glad to hear that it worked!
Hi,
We just pushed a new change in the DTB, to enable 2 cameras on the Jetson Nano revision B01.This new version of the patches fixes this issue. Closing it now. Feel free to let us know how it works for you
driver issue with Jetson Nano
approach
Test kernel patch with 2x IMX477 Raspberry HQ cams on Jetson Nano and Jetson Xavier -> Xavier works fine -> Nano does not detect cams
issue observed
While working fine with Jetson Xavier, when switching to Nano, the same hardware-arrangement except for the Jetson module, gives me error message:
environment
Jetson Nano B01 on dev-kit board B01 with JetPack 4.4
kernel has been custom build following procedure description ridgerun
device tree file seems active, /proc/device-tree shows imx477 nodes (all 3 of them in host1x and cami2cmux)