[meta-freescale] I2C issues with u-boot from fsl-community-bsp

Sumedha Widyadharma Sumedha.Widyadharma at basyskom.com
Wed Feb 13 06:22:37 PST 2013


On February 13, 2013 at 1:53 PM Otavio Salvador <otavio at ossystems.com.br> wrote:

> On Wed, Feb 13, 2013 at 10:18 AM, Sumedha Widyadharma
> <Sumedha.Widyadharma at basyskom.com> wrote:
> > I have an issue with I2C not working when using a fsl-community-bsp (danny
> > branch) built u-boot on imx6qsabreauto.
> >
> > I'm pretty sure it has to do with u-boot because using the kernel and rootfs
> > built by fsl-community-bsp with the u-boot from the 1.1.0 BSP I2C works.
> >
> > For now I'm just doing that, using u-boot from the BSP and our
> > kernel/rootfs,
> > but I'd really like to be able to use the sdcard images.
> >
> > Is this a known problem?
> > Any u-boot flavours/configurations I could try?
>
> You can use the u-boot-imx together with the Yocto; but in any case
> can you provide a test we can do so we fix it in U-Boot mainline?
 
I'm building a new image with u-boot-imx right now.
The u-boot-imx recipe had an error which I worked around with a
do_compile_append rename from u-boot.bin to u-boot.imx, probably not the right
fix.
 
What can I do to help fix this? Our most basic test is to run "i2cdetect 2".
With the BSP u-boot we see the devices, with the yocto u-boot we see only UU
where drivers have claimed addresses, but no actual devices.
 
I'll report back once the image is done.
 
Regards,
Sumedha Widyadharma




More information about the meta-freescale mailing list