[Bug 1192047] New: Camera module does not work with ov5647 device on RPi3B+
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047 Bug ID: 1192047 Summary: Camera module does not work with ov5647 device on RPi3B+ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: guillaume.gardet@arm.com QA Contact: qa-bugs@suse.de CC: afaerber@suse.com, dmueller@suse.com, mbrugger@suse.com Found By: --- Blocker: --- Created attachment 853365 --> http://bugzilla.opensuse.org/attachment.cgi?id=853365&action=edit dmesg log I tried to use an IR camera module, based on OV5647 device, but I fail to get it working. On top of Tumbleweed, I installed raspberrypi-firmware-extra and created /boot/efi/extraconfig.txt with: # Camera IR ov5647 start_x=1 gpu_mem=128 dtoverlay=ov5647 # I2C dtparam=i2c_arm=on On reboot, ov5647 and bcm2835_v4l2 kernel drivers are loaded, but no error is displayed in dmesg and there is no /dev/video* devices. 'i2cdetect -l' retuns: i2c-0 i2c i2c-11-mux (chan_id 0) I2C adapter i2c-1 i2c bcm2835 (i2c@7e804000) I2C adapter i2c-2 i2c bcm2835 (i2c@7e805000) I2C adapter i2c-10 i2c i2c-11-mux (chan_id 1) I2C adapter i2c-11 i2c bcm2835 (i2c@7e205000) I2C adapter and 'i2cdetect -y 10' confirms that i2c address 36 is used by a driver, likely ov5647: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Any idea what I am missing? -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c1
--- Comment #1 from Guillaume GARDET
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c2
Micha�� Szczepaniak
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c3
--- Comment #3 from Micha�� Szczepaniak
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c4
--- Comment #4 from Guillaume GARDET
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c5
--- Comment #5 from Guillaume GARDET
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c6
--- Comment #6 from Guillaume GARDET
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c7
--- Comment #7 from Micha�� Szczepaniak
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047
http://bugzilla.opensuse.org/show_bug.cgi?id=1192047#c8
Matthias Brugger
Upstream refused to implement it: https://github.com/raspberrypi/firmware/issues/1641
So, we likely need to update config.txt file manually at each update of raspberrypi-firmware-config
Or maybe someone has a better idea? Such as creating raspberrypi-firmware-config-camera flavor?
How can we make sure that does not break? We would have two packages that will change config.txt For example we update run zypper up raspberrypi-firmware-config-camera and later zypper up raspberrypi-firmware-config Then I understand the config.txt would not reflect the changes from raspberrypi-firmware-config-camera, right? -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com