From: "Terry Barnaby" <terry@beam.ltd.uk>
To: meta-freescale@lists.yoctoproject.org
Subject: Wandboard WB-IMX6U-BW CAM-OV5645 camera
Date: Tue, 16 Feb 2021 08:39:14 +0000 [thread overview]
Message-ID: <f9774d69-5a87-7f42-c8e2-af291dc43326@beam.ltd.uk> (raw)
Hi,
I am trying to get the CAM-OV5645 MIPI-CSI camera interface working on a
WB-IMX6U-BW board for a development experiment. However, I'm not having
much luck with many different Linux "distribution" installs and info on
the Wandboard WB-IMX6U-BW and CAM-OV5645 camera seems very hard to get
hold of. The camera also does not appear to work on a PICO-PI-IMX8-PRO
board. I get kernel messages like those listed at the bottom of this
email. I guess the camera module may be faulty, (it is new), or there
may have been hardware changes. The kernel is not seeing the OV5645 on
the I2C-2 bus although the ov5645 kernel driver module is loaded. This
is just a check to see if anyone can shed any light on this ?
Also the WB-IMX6U-BW board is a revD1 board. However I note that the
current freescale.github.io Yocto build appears to consider it a revB1
board and both uboot and the kernel tries to use the
imx6dl-wandboard-revb1.dtb rather than the imx6dl-wandboard-revd1.dtb.
As a quick hack I have copied imx6dl-wandboard-revd1.dtb over
imx6dl-wandboard-revb1.dtb in /boot for the kernel but not touched
uboot. The Linux boots fine with this (The Ethernet was not working with
imx6dl-wandboard-revb1.dtb). Not sure what is wrong here ?
Also anyone know of any sources of information as the wandboard.org site
does not seem to be active/maintained (no forums, not contacts etc.) ?
Terry
Yocto http://freescale.github.io build:
[ 5.667968] coda 2040000.vpu: Firmware code revision: 46076
[ 5.673786] coda 2040000.vpu: Initialized CODA960.
[ 5.678626] coda 2040000.vpu: Firmware version: 3.1.1
[ 5.714096] coda 2040000.vpu: encoder registered as video4
[ 5.714250] imx-sdma 20ec000.sdma: loaded firmware 3.5
[ 5.728100] coda 2040000.vpu: decoder registered as video5
[ 5.970899] ov5645 1-003c: ov5645_write_reg: write reg error -6:
reg=3a19, val=f8
[ 5.978823] ov5645 1-003c: could not set init registers
[ 6.036752] ov5645 1-003c: could not power up OV5645
[ 7.721385] EXT4-fs (mmcblk2p1): re-mounted. Opts: (null)
[ 9.220292] urandom_read: 2 callbacks suppressed
[ 9.220303] random: dd: uninitialized urandom read (512 bytes read)
[ 9.615513] Atheros 8035 ethernet 2188000.ethernet-1:01: attached PHY
driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet-1:01,
irq=POLL)
[ 9.752082] random: dbus-uuidgen: uninitialized urandom read (12
bytes read)
[ 9.759225] random: dbus-uuidgen: uninitialized urandom read (8 bytes
read)
[ 13.633273] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.670960] Bluetooth: BNEP socket layer initialized
[ 13.834885] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow
control rx/tx
[ 13.910157] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
On a PICO-PI-IMX8-PRO I get:
[ 17.549380] caam 30900000.caam: ERA source: CCBVID.
[ 17.553567] ov5645_mipi 1-003c: ae_target missing in dev tree, using
default 52
[ 17.556845] caam 30900000.caam: device ID = 0x0a16040100000000 (Era 9)
[ 17.561668] ov5645_mipi 1-003c: 1-003c supply DOVDD not found, using
dummy regulator
[ 17.568336] caam 30900000.caam: job rings = 3, qi = 0, dpaa2 = no
[ 17.578033] ov5645_mipi 1-003c: 1-003c supply DVDD not found, using
dummy regulator
[ 17.588458] caam-snvs 30370000.caam-snvs: can't get snvs clock
[ 17.591927] ov5645_mipi 1-003c: 1-003c supply AVDD not found, using
dummy regulator
[ 17.597591] caam-snvs 30370000.caam-snvs: violation handlers armed -
non-secure state
[ 21.540628] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor
subdevice: ov5645_mipi 1-003c
[ 21.551463] camera ov5645_mipi is found
[ 21.555815] ov5645_mipi 2-003c: ae_target missing in dev tree, using
default 52
[ 21.563329] ov5645_mipi 2-003c: 2-003c supply DOVDD not found, using
dummy regulator
[ 21.571320] ov5645_mipi 2-003c: 2-003c supply DVDD not found, using
dummy regulator
[ 21.579210] ov5645_mipi 2-003c: 2-003c supply AVDD not found, using
dummy regulator
[ 21.657381] ov5645_read_reg:write reg error:reg=300a
[ 21.662404] camera ov5645_mipi is not found
next reply other threads:[~2021-02-16 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 8:39 Terry Barnaby [this message]
2021-02-16 20:46 ` [meta-freescale] Wandboard WB-IMX6U-BW CAM-OV5645 camera Otavio Salvador
2021-02-16 20:55 ` Fabio Estevam
2021-02-17 5:31 ` Terry Barnaby
2021-02-19 1:19 ` Fabio Estevam
2021-02-19 7:24 ` Terry Barnaby
2021-02-19 11:09 ` Fabio Estevam
2021-02-19 12:59 ` Andrey Zhizhikin
2021-02-19 13:28 ` Terry Barnaby
2021-02-19 13:34 ` Andrey Zhizhikin
2021-02-19 13:45 ` Terry Barnaby
2021-02-19 15:22 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9774d69-5a87-7f42-c8e2-af291dc43326@beam.ltd.uk \
--to=terry@beam.ltd.uk \
--cc=meta-freescale@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).