Hi,
For checking purpose, your board configurations written in autoconf.mk in
uboot under (include/). I hope the CONFIG_I2C address macro will not
written in .config file.
If you are using yocto, you include the custom patch in uboot 2015
recipies for making the change as permanent one.
Thanks & Regards
Pitchaiah M
On Thu, 13 Dec, 2018, 15:55 Wiholm, Willie ActeSE <willie.wih...@acte.se
wrote:
> Hello,
>
>
>
> Thank you for your reply,
>
>
>
> I changed the include/configs/mx6sabre_common.h
>
> #define CONFIG_POWER_PFUZE_I2C_ADDR 0x0a
>
>
>
> Then I ran make mx6dlsabresd_defconfig
>
> And got a .config file
>
> But it did not include my changes.
>
> What do I need to build in order to apply changed made in the
> include/config/mybard.h files to u-boot?
>
>
>
> Thanks again,
>
>
>
> Best Regards,
>
> Willie
>
>
>
> *Från:* prakash m <prakash56...@gmail.com>
> *Skickat:* den 13 december 2018 08:02
> *Till:* Wiholm, Willie ActeSE <willie.wih...@acte.se>
> *Kopia:* meta-freescale@yoctoproject.org
> *Ämne:* Re: [meta-freescale] Understanding U-boot
>
>
>
> 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.wih...@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
> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffreescale.com%2Fimx%2Ffsl-arm-yocto-bsp&data=02%7C01%7CWillie.wiholm%40acte.se%7Cfc68d8bbf81e4c32885908d660c8e08b%7C309e17c286e24bd1ac236459b0d1065a%7C1%7C1%7C636802813224233594&sdata=GnZf0OhkW0atVmQNZ6XVnJzyBQpJmpQHOMe42tahDug%3D&reserved=0>
> -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
> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fu-boot-imx_2015.04.bb&data=02%7C01%7CWillie.wiholm%40acte.se%7Cfc68d8bbf81e4c32885908d660c8e08b%7C309e17c286e24bd1ac236459b0d1065a%7C1%7C0%7C636802813224243607&sdata=24p%2BfgKJhySYZOEzF0sy6DRgSuncaMWbyRP678jcH7c%3D&reserved=0>
> 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
> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fu-boot_2016.03.bb&data=02%7C01%7CWillie.wiholm%40acte.se%7Cfc68d8bbf81e4c32885908d660c8e08b%7C309e17c286e24bd1ac236459b0d1065a%7C1%7C0%7C636802813224243607&sdata=FDXRFMdalkb2Xw4CmrGiCfHm5nK4GVCIyQ%2FPvTyawCk%3D&reserved=0>
> .
>
>
>
> 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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fmeta-freescale&data=02%7C01%7CWillie.wiholm%40acte.se%7Cfc68d8bbf81e4c32885908d660c8e08b%7C309e17c286e24bd1ac236459b0d1065a%7C1%7C1%7C636802813224253607&sdata=ZEMux%2FeNw76kMO0ZVWPLsaXWoEuYI065EIzby8vcy6c%3D&reserved=0>
>
>
--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
