[meta-freescale] Understanding U-boot

prakash m prakash56755 at gmail.com
Wed Dec 12 23:01:46 PST 2018


Hi,

If the latest uboot uses dts model, then you can find the  i2c address of
pmic pfuze100 in arch/arm/dts/your-dtb-file under i2c node

Which looks like

&I2C
{
Pfuze: {
reg = <I2c-pfuze-address>
};
};

The above one is sample which is not similar in your case.

or if the latest uboot not uses the dts model, then you can find the I2c
pfuze address in include/configs/mx6sabresd.h ,

#define CONFIG_POWER_PFUZE_I2C_ADDR 0X08


After finiding your pfuze  I2c address, you can change the I2c pfuze in
uboot 2015 under the file include/configs/mx6sabresd.h

The replace the new address with old address in the below macro,

#define CONFIG_POWER_PFUZE_I2C_ADDR 0X08

Thanks & Regards
Pitchaiah M



On Thu, 13 Dec, 2018, 09:04 Wiholm, Willie ActeSE <Willie.wiholm at acte.se
wrote:

> Hello guys,
>
>
>
> I’m very new with Yocto so if these questions are too trivial don’t
> hesitate to remove them 😊.
>
>
>
> Background:
>
> I have a imx6dlsabresd board and I have downloaded the repository
> freescale.com/imx/fsl-arm-yocto-bsp -b imx-4.1-krogoth.
>
> After setting everything up I built the “fsl-image-qt5” and when I tried
> to boot it I got the following error:
>
>
>
> U-Boot 2016.03-imx_v2016.03_4.1.15_2.0.0_ga+g0ec2a01 (Nov 30 2018 -
> 20:56:51 +0100)
>
>
>
> CPU:   Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
>
> CPU:   Extended Commercial temperature grade (-20C to 105C) at 42C
>
> Reset cause: POR
>
> Board: MX6-SabreSD
>
> I2C:   ready
>
> DRAM:  1 GiB
>
> Can't find PMIC:PFUZE100
>
> initcall sequence 4ff968f0 failed at call 178040a4 (err=-19)
>
> ### ERROR ### Please RESET the board ###
>
>
>
> After reading different forums I believe the reason is that they changed
> the PMIC address in the I2C in a newer version(This is just my guess). My
> idea of solving this was to try with an older version of u-boot, and this
> is where things got confusing.
>
>
>
> My thought was that the files in meta-fsl-arm/recipes-kernel and
> recipes-bsp were used for that image.
>
> But when I looked in the u-boot folder I saw that the u-boot provided by
> fsl contained u-boot-imx_2015.04.bb and that the U-boot used by my image
> was the U-boot located in poky/meta/recipes-bsp/u-boot/u-boot_2016.03.bb.
>
>
>
> I think understanding this is the key to my problem, so my questions are:
>
> 1. Why is the U-boot provided by poky used in the fsl images?
>
> 2. Is It possible to completely change U-boot for a image? For example to
> downgrade 2016.03 to 2015.04 and how would one do that.
>
> 3. Any general information regarding the works if this would be greatly
> appreciated.
>
>
>
> Best Regards,
>
> Willie
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20181213/7d91e250/attachment.html>


More information about the meta-freescale mailing list