Wandboard WB-IMX6U-BW CAM-OV5645 camera


Terry Barnaby
 

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


Otavio Salvador
 

Hello Terry,

I am adding John on Cc so he can support you.

Em ter., 16 de fev. de 2021 às 05:39, Terry Barnaby
<terry@beam.ltd.uk> escreveu:


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




--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750


Fabio Estevam
 

Hi Terry,

On Tue, Feb 16, 2021 at 5:39 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

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
Which U-Boot version is this?

Can you try U-Boot 2021.01?


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
I don't recall getting these I2C failures.

Which kernel version is this?

I tested camera capture recently on Wandboard with a mainline kernel
and it worked well.

Regards,

Fabio Estevam


Terry Barnaby
 

Hi Fabio,

Many thanks for your reply. Notes below:

Terry
On 16/02/2021 20:55, Fabio Estevam wrote:
Hi Terry,

On Tue, Feb 16, 2021 at 5:39 AM Terry Barnaby <terry@...> wrote:
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
Which U-Boot version is this?

Can you try U-Boot 2021.01?

It was "U-Boot 2020.04+fslc+g88c58453be (Oct 13 2020 - 21:59:38 +0000)". This is what was built using the instructions at: http://freescale.github.io but using what I thought would be the latest GIT using "repo init -u https://github.com/Freescale/fsl-community-bsp-platform" not the rocko branch.

I have just downloaded the latest u-boot from its upstream GIT and built "U-Boot 2021.04-rc2 (Feb 16 2021 - 12:47:43 +0000)" and that has detected the revD1 board and has info on the PMIC. Thanks for the heads up. Although 2020.04 appeared to have code to check for the PMIC it looks like it only supported the quad processor variant not the dual lite.

As an aside, when building a Linux BSP for this or other iMX6/8 boards is http://freescale.github.io the best starting point (being new to the iMX6/8 platforms) ?




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
I don't recall getting these I2C failures.

Which kernel version is this?

I tested camera capture recently on Wandboard with a mainline kernel
and it worked well.

Thanks for the info. I am coming to the conclusion that either I have a duff CAM-OV6545 board (it was new) or the CAM-OV6545 hardware has changed in some way. Certainly I cannot get the particular CAM-OV6545 board working on an iMX6 or iMX8 platform and it doesn't show up with an i2cdetect probe before or after the ov6545.ko module is loaded (I think the ov6545.ko module may power up the board with a GPIO line, but I have found no documentation on the CAM-OV6545module apart from the Wandboard user-manual pinout for the connector but the user manual for the WB-IMX6U-BW only has schematics for the revA1 board not the revD1). I have ordered another CAM-OV6545 board.



Regards,

Fabio Estevam





Fabio Estevam
 

Hi Terry,

On Wed, Feb 17, 2021 at 2:32 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

Hi Fabio,

Many thanks for your reply. Notes below:

Terry
On 16/02/2021 20:55, Fabio Estevam wrote:

Hi Terry,

On Tue, Feb 16, 2021 at 5:39 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

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

Which U-Boot version is this?

Can you try U-Boot 2021.01?

It was "U-Boot 2020.04+fslc+g88c58453be (Oct 13 2020 - 21:59:38 +0000)". This is what was built using the instructions at: http://freescale.github.io but using what I thought would be the latest GIT using "repo init -u https://github.com/Freescale/fsl-community-bsp-platform" not the rocko branch.

I have just downloaded the latest u-boot from its upstream GIT and built "U-Boot 2021.04-rc2 (Feb 16 2021 - 12:47:43 +0000)" and that has detected the revD1 board and has info on the PMIC. Thanks for the heads up. Although 2020.04 appeared to have code to check for the PMIC it looks like it only supported the quad processor variant not the dual lite.
I don't have access to a imx6dl-wandboard revd1, but I thought that
someone else has tested it for me when I fixed revd1 detection in this
commit:
https://gitlab.denx.de/u-boot/u-boot/-/commit/4c13a4db60b4d570ea8cc496d02e5ea31adf27f0

If there is still issues, please let me know.



As an aside, when building a Linux BSP for this or other iMX6/8 boards is http://freescale.github.io the best starting point (being new to the iMX6/8 platforms) ?
For i.MX6 I would go with upstream kernel. For i.MX8M, you may want to
use the 5.4 branch maintained by Otavio and folks.



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.) ?
I think the best route would be to ask in the U-Boot or Linux arm
kernel mailing lists.

Regards,

Fabio Estevam


Terry Barnaby
 

On 19/02/2021 01:19, Fabio Estevam wrote:

Which U-Boot version is this?

Can you try U-Boot 2021.01?

It was "U-Boot 2020.04+fslc+g88c58453be (Oct 13 2020 - 21:59:38 +0000)". This is what was built using the instructions at: http://freescale.github.io but using what I thought would be the latest GIT using "repo init -u https://github.com/Freescale/fsl-community-bsp-platform" not the rocko branch.

I have just downloaded the latest u-boot from its upstream GIT and built "U-Boot 2021.04-rc2 (Feb 16 2021 - 12:47:43 +0000)" and that has detected the revD1 board and has info on the PMIC. Thanks for the heads up. Although 2020.04 appeared to have code to check for the PMIC it looks like it only supported the quad processor variant not the dual lite.
I don't have access to a imx6dl-wandboard revd1, but I thought that
someone else has tested it for me when I fixed revd1 detection in this
commit:
https://gitlab.denx.de/u-boot/u-boot/-/commit/4c13a4db60b4d570ea8cc496d02e5ea31adf27f0

If there is still issues, please let me know.
The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work fine on the Wandboard revD1, as I tested above, thanks for including this commit. It's the Yocto meta-freescale build I was having problems with.

Maybe I am doing something wrong. I checked the http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that git commit would have added ?

I assumed that the http://freescale.github.io Yocto master would be using the latest upsteam git u-boot if I didn't specify a particular branch, I guess I am wrong on that.

Terry


Fabio Estevam
 

Hi Terry,

On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
fine on the Wandboard revD1, as I tested above, thanks for including
this commit. It's the Yocto meta-freescale build I was having problems with.
Ok, I am adding Otavio on Cc.

I have the impression that the Yocto meta-freescale is using an older U-Boot.

Maybe I am doing something wrong. I checked the
http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not
contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
git commit would have added ?
It is the commit that I pointed out that introduces
arch/arm/dts/imx6dl-wandboard-revd1.dts.

Such commit entered U-Boot 2020.07.

I assumed that the http://freescale.github.io Yocto master would be
using the latest upsteam git u-boot if I didn't specify a particular
branch, I guess I am wrong on that.
Hopefully, Otavio can help clarifying. It could be that the U-Boot
version needs to be bumped.

Regards,

Fabio Estevam


Andrey Zhizhikin
 

Hello Terry and Fabio,

On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:

Hi Terry,

On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
fine on the Wandboard revD1, as I tested above, thanks for including
this commit. It's the Yocto meta-freescale build I was having problems with.
Ok, I am adding Otavio on Cc.

I have the impression that the Yocto meta-freescale is using an older U-Boot.

Maybe I am doing something wrong. I checked the
http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not
contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
git commit would have added ?
It is the commit that I pointed out that introduces
arch/arm/dts/imx6dl-wandboard-revd1.dts.

Such commit entered U-Boot 2020.07.

I assumed that the http://freescale.github.io Yocto master would be
using the latest upsteam git u-boot if I didn't specify a particular
branch, I guess I am wrong on that.
Hopefully, Otavio can help clarifying. It could be that the U-Boot
version needs to be bumped.
Indeed, the u-boot-fslc that is a part of Community BSP has a version
2020.04 for [dunfell] branch. [master] branch has already been
advanced to 2020.10 so it should have that DTS in that you're looking
for.

I do not know if it is safe to upgrade the U-Boot on the LTS version,
I'd leave it to Otavio to decide.

Terry,
Can you try to initialize your BSP build from [master] branch and test
to see if (a) you have a support for the OV5645; and (b) whether that
would be an option for you to utilize [master] instead of [dunfell]?


Regards,

Fabio Estevam



--
Regards,
Andrey.


Terry Barnaby
 

Hi Andrey,

On 19/02/2021 12:59, Andrey Zhizhikin wrote:
Hello Terry and Fabio,

On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
Hi Terry,

On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
fine on the Wandboard revD1, as I tested above, thanks for including
this commit. It's the Yocto meta-freescale build I was having problems with.
Ok, I am adding Otavio on Cc.

I have the impression that the Yocto meta-freescale is using an older U-Boot.

Maybe I am doing something wrong. I checked the
http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not
contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
git commit would have added ?
It is the commit that I pointed out that introduces
arch/arm/dts/imx6dl-wandboard-revd1.dts.

Such commit entered U-Boot 2020.07.

I assumed that the http://freescale.github.io Yocto master would be
using the latest upsteam git u-boot if I didn't specify a particular
branch, I guess I am wrong on that.
Hopefully, Otavio can help clarifying. It could be that the U-Boot
version needs to be bumped.
Indeed, the u-boot-fslc that is a part of Community BSP has a version
2020.04 for [dunfell] branch. [master] branch has already been
advanced to 2020.10 so it should have that DTS in that you're looking
for.

I do not know if it is safe to upgrade the U-Boot on the LTS version,
I'd leave it to Otavio to decide.

Terry,
Can you try to initialize your BSP build from [master] branch and test
to see if (a) you have a support for the OV5645; and (b) whether that
would be an option for you to utilize [master] instead of [dunfell]?
Thanks for the reply.

I'm a bit new to meta-freescale and the use of the "repo" utility. I did a:

"repo init -u https://github.com/Freescale/fsl-community-bsp-platform" ie without "-b <branch>" which I assumed would pull the master ?

Should I do something else to get the master branch of all the necessary GIT repositories ?



Regards,

Fabio Estevam


Andrey Zhizhikin
 

Hello Terry,

On Fri, Feb 19, 2021 at 2:28 PM Terry Barnaby <terry@beam.ltd.uk> wrote:

Hi Andrey,

On 19/02/2021 12:59, Andrey Zhizhikin wrote:
Hello Terry and Fabio,

On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
Hi Terry,

On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
fine on the Wandboard revD1, as I tested above, thanks for including
this commit. It's the Yocto meta-freescale build I was having problems with.
Ok, I am adding Otavio on Cc.

I have the impression that the Yocto meta-freescale is using an older U-Boot.

Maybe I am doing something wrong. I checked the
http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not
contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
git commit would have added ?
It is the commit that I pointed out that introduces
arch/arm/dts/imx6dl-wandboard-revd1.dts.

Such commit entered U-Boot 2020.07.

I assumed that the http://freescale.github.io Yocto master would be
using the latest upsteam git u-boot if I didn't specify a particular
branch, I guess I am wrong on that.
Hopefully, Otavio can help clarifying. It could be that the U-Boot
version needs to be bumped.
Indeed, the u-boot-fslc that is a part of Community BSP has a version
2020.04 for [dunfell] branch. [master] branch has already been
advanced to 2020.10 so it should have that DTS in that you're looking
for.

I do not know if it is safe to upgrade the U-Boot on the LTS version,
I'd leave it to Otavio to decide.

Terry,
Can you try to initialize your BSP build from [master] branch and test
to see if (a) you have a support for the OV5645; and (b) whether that
would be an option for you to utilize [master] instead of [dunfell]?
Thanks for the reply.

I'm a bit new to meta-freescale and the use of the "repo" utility. I did a:

"repo init -u https://github.com/Freescale/fsl-community-bsp-platform"
ie without "-b <branch>" which I assumed would pull the master ?
Actually, it had pulled a "default" branch, which appears to be [dunfell]. :)

I've done the same, and here is the output of repo info command:
----
repo info
Manifest branch: dunfell
Manifest merge branch: refs/heads/dunfell
Manifest groups: all,-notdefault
----------------------------
Project: Documentation
Mount path: /development/tmp/sources/Documentation
Current revision: 4558857539fd5395e9657500f84017e2722ba433
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: fsl-community-bsp-base
Mount path: /development/tmp/sources/base
Current revision: 9d7b7caeba7ebd6c315bf99950e4501662ddeb80
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale
Mount path: /development/tmp/sources/meta-freescale
Current revision: 11170950b155168ec414bbde48e3a4427fcac4bd
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale-3rdparty
Mount path: /development/tmp/sources/meta-freescale-3rdparty
Current revision: 058316a502cdba7fad02df8c857c72e218b7bc45
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale-distro
Mount path: /development/tmp/sources/meta-freescale-distro
Current revision: 5d882cdf079b3bde0bd9869ce3ca3db411acbf3b
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-openembedded
Mount path: /development/tmp/sources/meta-openembedded
Current revision: de37512b25c1f8c6bb6ab2b3782ac0fe01443483
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: poky
Mount path: /development/tmp/sources/poky
Current revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
Manifest revision: dunfell
Local Branches: 0
----------------------------
----

As you can see, manifest default branch is set to [dunfell], so you
should explicitly use [-b master].


Should I do something else to get the master branch of all the necessary
GIT repositories ?



Regards,

Fabio Estevam
--
Regards,
Andrey.


Terry Barnaby
 

On 19/02/2021 13:34, Andrey Zhizhikin wrote:
Hello Terry,

On Fri, Feb 19, 2021 at 2:28 PM Terry Barnaby <terry@beam.ltd.uk> wrote:
Hi Andrey,

On 19/02/2021 12:59, Andrey Zhizhikin wrote:
Hello Terry and Fabio,

On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
Hi Terry,

On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:

The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
fine on the Wandboard revD1, as I tested above, thanks for including
this commit. It's the Yocto meta-freescale build I was having problems with.
Ok, I am adding Otavio on Cc.

I have the impression that the Yocto meta-freescale is using an older U-Boot.

Maybe I am doing something wrong. I checked the
http://freescale.github.io code out using:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform

(also tried "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")

When I "bitbake u-boot" with this the u-boot build source tree does not
contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
git commit would have added ?
It is the commit that I pointed out that introduces
arch/arm/dts/imx6dl-wandboard-revd1.dts.

Such commit entered U-Boot 2020.07.

I assumed that the http://freescale.github.io Yocto master would be
using the latest upsteam git u-boot if I didn't specify a particular
branch, I guess I am wrong on that.
Hopefully, Otavio can help clarifying. It could be that the U-Boot
version needs to be bumped.
Indeed, the u-boot-fslc that is a part of Community BSP has a version
2020.04 for [dunfell] branch. [master] branch has already been
advanced to 2020.10 so it should have that DTS in that you're looking
for.

I do not know if it is safe to upgrade the U-Boot on the LTS version,
I'd leave it to Otavio to decide.

Terry,
Can you try to initialize your BSP build from [master] branch and test
to see if (a) you have a support for the OV5645; and (b) whether that
would be an option for you to utilize [master] instead of [dunfell]?
Thanks for the reply.

I'm a bit new to meta-freescale and the use of the "repo" utility. I did a:

"repo init -u https://github.com/Freescale/fsl-community-bsp-platform"
ie without "-b <branch>" which I assumed would pull the master ?
Actually, it had pulled a "default" branch, which appears to be [dunfell]. :)

I've done the same, and here is the output of repo info command:
----
repo info
Manifest branch: dunfell
Manifest merge branch: refs/heads/dunfell
Manifest groups: all,-notdefault
----------------------------
Project: Documentation
Mount path: /development/tmp/sources/Documentation
Current revision: 4558857539fd5395e9657500f84017e2722ba433
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: fsl-community-bsp-base
Mount path: /development/tmp/sources/base
Current revision: 9d7b7caeba7ebd6c315bf99950e4501662ddeb80
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale
Mount path: /development/tmp/sources/meta-freescale
Current revision: 11170950b155168ec414bbde48e3a4427fcac4bd
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale-3rdparty
Mount path: /development/tmp/sources/meta-freescale-3rdparty
Current revision: 058316a502cdba7fad02df8c857c72e218b7bc45
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-freescale-distro
Mount path: /development/tmp/sources/meta-freescale-distro
Current revision: 5d882cdf079b3bde0bd9869ce3ca3db411acbf3b
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: meta-openembedded
Mount path: /development/tmp/sources/meta-openembedded
Current revision: de37512b25c1f8c6bb6ab2b3782ac0fe01443483
Manifest revision: dunfell
Local Branches: 0
----------------------------
Project: poky
Mount path: /development/tmp/sources/poky
Current revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
Manifest revision: dunfell
Local Branches: 0
----------------------------
----

As you can see, manifest default branch is set to [dunfell], so you
should explicitly use [-b master].
Hi Andrey,

Ah, many thanks that will help !

I will try to build from that, might also sort out my issue with "gstreamer1.0-plugins-imx".

Terry


Otavio Salvador
 

Em sex., 19 de fev. de 2021 às 09:59, Andrey Zhizhikin
<andrey.z@gmail.com> escreveu:
On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
I do not know if it is safe to upgrade the U-Boot on the LTS version,
I'd leave it to Otavio to decide.
Upgrade U-Boot on dunfell is risky but I believe it is worth it. The
2020.10 has been in use in master for long time and people did not
report issues so we can do the upgrade.

Once we do it on Dunfell, we could upgrade it to 2021.01 release on master.

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750