u-boot 2017.03 PMIC read error

[manjunathjoshi]

Hello all,

As seen in below logs, I am not able to boot u-boot 2017,  but the PMIC with same ID and configuration works in u-boot 2016.

Is there any difference in the way we port for u-boot 2017.08. Did anyone try this newer version of u-boot. It looks completely new since it has dts like kernel has.

U-Boot 2017.03-svn16 (Nov 17 2017 - 10:40:30 +0530)

CPU:   Freescale i.MX6DP rev1.0 996 MHz (running at 792 MHz)
CPU:   Automotive temperature grade (-40C to 125C) at 37C
Reset cause: POR
Model: Freescale i.MX6 Quad SABRE Smart Device Board
Board: Sabresd
DRAM:  1 GiB
ERROR: read error from device: 4ef37860 register: 0x0!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
ERROR: read error from device: 4ef37860 register: 0x3!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
PMIC: PFUZE100! DEV_ID=0xfffffffb REV_ID=0xfffffffb
ERROR: read error from device: 4ef37860 register: 0x21!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
ERROR: write error to device: 4ef37860 register: 0x21!
at drivers/power/pmic/pfuze100.c:36/pfuze100_write()
ERROR: read error from device: 4ef37860 register: 0x24!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
ERROR: write error to device: 4ef37860 register: 0x24!
at drivers/power/pmic/pfuze100.c:36/pfuze100_write()
ERROR: read error from device: 4ef37860 register: 0x2f!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
ERROR: write error to device: 4ef37860 register: 0x2f!
at drivers/power/pmic/pfuze100.c:36/pfuze100_write()
ERROR: read error from device: 4ef37860 register: 0x32!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
ERROR: write error to device: 4ef37860 register: 0x32!
at drivers/power/pmic/pfuze100.c:36/pfuze100_write()
ERROR: read error from device: 4ef37860 register: 0x0!
at drivers/power/pmic/pfuze100.c:46/pfuze100_read()
Not supported, id=11
initcall sequence 4ffa78ac failed at call 17804b20 (err=-22)
### ERROR ### Please RESET the board ###

[prasannakulkarni]

Hi all,

We have solved this issue....  in our custom board... I2c2 default pin muxing was changed to some other pins so it was not able to communicate with pmic pfuze100 and printing above errors... After correcting that it worked for us....

[manjunathjoshi]

Thanks for the info.

[prasannakulkarni]

Hi Manjunath,

        Your u-boot issue got solved? if so can you just share it, we are also facing the same issue...

[weidong_sun]

Hello Manjunath,

      Our linux BSP ver 4.9 (latest one) supports u-boot 2017, So please use or refer to it!

Have a nice day!

TIC Weidong Sun