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

[Otavio Salvador]

On Wed, Feb 13, 2013 at 3:26 PM, Sumedha Widyadharma
<Sumedha.Widyadharma at basyskom.com> wrote:
>
> On February 13, 2013 at 5:58 PM Otavio Salvador <otavio at ossystems.com.br> wrote:
>
>> On Wed, Feb 13, 2013 at 2:35 PM, Sumedha Widyadharma <
>> Sumedha.Widyadharma at basyskom.com> wrote:
>>
>> >
>> >
>> > On February 13, 2013 at 4:16 PM Otavio Salvador <otavio at ossystems.com.br>
>> > wrote:
>> >
>> > > On Wed, Feb 13, 2013 at 12:22 PM, Sumedha Widyadharma <
>> > > Sumedha.Widyadharma at basyskom.com> wrote:
>> > >
>> > > > 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.
>> > >
>> > >
>> > > This won't work. I will send a patch updating the u-boot-imx with proper
>> > > fix.
>> > >
>> > >
>> > > > I'll report back once the image is done.
>> > > >
>> > >
>> > > I think it won't boot.
>> >
>> > ...and it didn't.
>> >
>> > To sum up the results so far:
>> >
>> > Adding UBOOT_SUFFIX/UBOOT_PADDING/PREFERRED_PROVIDER as per the u-boot-imx
>> > recipe leads to a booting sdcard image
>> > with working I2C.
>> >
>> > Additionally i found out that u-boot-imx does not know if/then/else :)
>> >
>> > I've booted both images and here are the i2cdump outputs:
>> > https://gist.github.com/anonymous/4945858
>>
>>
>> I don't have sabreauto here to test this.  Any clue?
>
> Unfortunately not. I don't know u-boot. Does it set up the clocks for the I2C
> bus?

Fabio, can you take a look?

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br