mx53loco: Fix PMIC name
PATCH 1/1 mx53loco: Fix PMIC name
commit c73368150 (pmic: Extend PMIC framework to support multiple instances of PMIC devices) has incorrectly passed the PMIC name under the FSL PMIC case.
Fix that by passing "FSL_PMIC" as the parameter of pmic_get.
--- board/freescale/mx53loco/mx53loco.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
board/freescale/mx53loco/mx53loco.c +1 -1
@@ -374,7 +374,7 @@ static int power_init(void)if (retval)return retval; - p =pmic_get ("DIALOG_PMIC" ); + p =pmic_get ("FSL_PMIC" );if (!p)return -ENODEV ;
Signature · 1 line
1.7.9.5
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 16 lines · Fabio Estevam
commit
c73368150(pmic: Extend PMIC framework to support multiple instances of PMIC devices) has incorrectly passed the PMIC name under the FSL PMIC case.Fix that by passing "
FSL_PMIC" as the parameter ofpmic_get.Signed-off-by Fabio Estevam <[email protected]>--- board/freescale/mx53loco/mx53loco.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)board/freescale/mx53loco/mx53loco.c +0
-0
board/freescale/mx53loco/mx53loco.c static int power_init(void) · line 380
Quoted 8 lines
board/freescale/mx53loco/mx53loco.c +1
-1@@ -374,7 +374,7 @@ static int power_init(void)if (retval)return retval; - p =pmic_get ("DIALOG_PMIC" ); + p =pmic_get ("FSL_PMIC" );if (!p)return -ENODEV ;
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH 1/1 mx53loco: Fix PMIC name
In reply to Fabio EstevamQuoted 24 lines · Fabio Estevam
commit
c73368150(pmic: Extend PMIC framework to support multiple instances of PMIC devices) has incorrectly passed the PMIC name under the FSL PMIC case.Fix that by passing "
FSL_PMIC" as the parameter ofpmic_get.Signed-off-by Fabio Estevam <[email protected]>--- board/freescale/mx53loco/mx53loco.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)board/freescale/mx53loco/mx53loco.c +1
-2@@ -374,7 +374,7 @@ static int power_init(void)if (retval)return retval; - p =pmic_get ("DIALOG_PMIC" ); + p =pmic_get ("FSL_PMIC" );if (!p)return -ENODEV ; --
Quoted 1 line
1.7.9.5
Hi Fabio,
It looks like we need one more fixup after commit c73368150 on the first run/older (non R, Dialog, bug wired extra Capacitor) version of this board.. Do you happen to have any in your lab?
U-Boot 2013.01-rc2-dirty (Dec 20 2012 - 15:55:01)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB pmic_alloc: No available memory for allocation! pmic_init: POWER allocation error! CPU: Freescale i.MX53 family rev2.0 at 800 MHz Reset cause: POR MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
(and it just keeps on resetting)
It looks to be failing after calloc...
http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/power/power_core.c#l100
100 p = calloc(sizeof(*p), 1);
101 if (!p) {
102 printf("%s: No available memory for
allocation!\n", __func__);
103 return NULL;
104 }
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Hi Robert,
Quoted 5 lines · Robert Nelson
Hi Fabio,
It looks like we need one more fixup after commit
c73368150on the first run/older (non R, Dialog, bug wired extra Capacitor) version of this board.. Do you happen to have any in your lab?
Thanks for reporting this issue. I will try to get access to mx53qsb dialog next week to investigate this further.
Regards,
Fabio Estevam
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
In reply to Robert NelsonRobert,
Quoted 23 lines · Robert Nelson
Hi Fabio,
It looks like we need one more fixup after commit
c73368150on the first run/older (non R, Dialog, bug wired extra Capacitor) version of this board.. Do you happen to have any in your lab?U-Boot 2013.01-rc2-dirty (Dec 20 2012 - 15:55:01)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB pmic_alloc: No available memory for allocation! pmic_init: POWER allocation error! CPU: Freescale i.MX53 family rev2.0 at 800 MHz Reset cause: POR MMC: FSL_SDHC: 0, FSL_SDHC: 1*** Warning - bad CRC, using default environment
(and it just keeps on resetting)
It looks to be failing after calloc...
http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/power/power_core.c#l100
Quoted 6 lines
100 p =
calloc(sizeof(*p), 1);
101 if (!p) {
102 printf("%s: No available memory for
allocation!\n",__func__);
103 return NULL;
104 }
I can reproduce this issue using top of head U-boot tree.
It seems indeed to be caused by:
Author: ?ukasz Majewski <[email protected]> Date: Tue Nov 13 03:21:55 2012 +0000 commit c7336815078ff3745e3130aeff35991e3e98e61e Author: ?ukasz Majewski <[email protected]> Date: Tue Nov 13 03:21:55 2012 +0000
pmic: Extend PMIC framework to support multiple instances of PMIC devices
The PMIC framework has been extended to support multiple instances of the variety of devices responsible for power management.
This change allows supporting of e.g. fuel gauge, charger, MUIC (Micro USB Interface Circuit).
Power related includes have been moved to ./include/power directory. This is a first of a series of patches - in the future "pmic" will be replaced with "power".
Two important issues:
1. The PMIC needs to be initialized just after malloc is configured
2. It uses list to hold information about available PMIC devices
I am Ccing Lukasz/Stefano in case they have any suggestion.
With the new PMIC framework: is it safe to call the PMIC API from board_init function?
Regards,
Fabio Estevam
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 2 lines · Fabio Estevam
With the new PMIC framework: is it safe to call the PMIC API from
board_initfunction?
Calling it from board_late_init fixes the issue for me.
Will send the patch soon.
Regards,
Fabio Estevam
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Robert,
Quoted 8 lines · Fabio Estevam
Quoted 2 lines · Fabio Estevam
With the new PMIC framework: is it safe to call the PMIC API from
board_initfunction?Calling it from
board_late_initfixes the issue for me.Will send the patch soon.
Can you try the patch below?
board/freescale/mx53loco/mx53loco.c | 10 ++++++++--
include/configs/mx53loco.h | 1 + 2 files changed, 9 insertions(+), 2 deletions(-)
(quoted diff) +0 -0
b/board/freescale/mx53loco/mx53loco.c
index 2c8cb7a..63a4f8b 100644
board/freescale/mx53loco/mx53loco.c +8 -2
@@ -462,12 +462,18 @@ int board_init(void)mxc_set_sata_internal_clock ();setup_iomux_i2c (); + +lcd_enable (); + +return 0 ; +} + +int board_late_init (void ) +{if (!power_init ())clock_1GHz ();print_cpuinfo (); -lcd_enable (); -return 0 ; }
include/configs/mx53loco.h +1 -0
@@ -39,6 +39,7 @@#define CONFIG_SYS_MALLOC_LEN (10 * 1024 * 1024)#define CONFIG_BOARD_EARLY_INIT_F +#define CONFIG_BOARD_LATE_INIT #define CONFIG_MXC_GPIO #define CONFIG_REVISION_TAG
Signature · 47 lines
1.7.9.5
It boots now, but I get resets now:
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 13:13:28)
Board: MX53 LOCO
I2C: ready
DRAM: 1 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
In: serial
Out: serial
Err: serial
CPU: Freescale i.MX53 family rev2.1 at 1000 MHz
Reset cause: WDOG
Net: FEC
Warning: FEC using MAC address from net device
Hit any key to stop autoboot: 0
data abort
MAYBE you should read doc/README.arm-unaligned-accesses
pc : [<aff72220>] lr : [<aff721fc>]
sp : af565e20 ip : af566918 fp : 00000000
r10: 00000003 r9 : affabb5b r8 : af565f58
r7 : 00000000 r6 : 36747fff r5 : af5668e8 r4 : 36747fff
r3 : af5668ec r2 : af5668eb r1 : 00000000 r0 : af5668e8
Flags: NzcV IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 13:13:28)
Board: MX53 LOCO
I2C: ready
DRAM: 1 GiB
but it looks like a separate issue?
Regards,
Fabio EstevamPATCH 1/1 mx53loco: Fix PMIC name
Hi Fabio,
Quoted 5 lines · Fabio Estevam
Robert,
Quoted 2 lines · Fabio Estevam
On Wed, Dec 26, 2012 at 1:02 PM, Fabio Estevam <[email protected]> wrote:
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
With the new PMIC framework: is it safe to call the PMIC API from
board_initfunction?Calling it from
board_late_initfixes the issue for me.Will send the patch soon.
Can you try the patch below?
Thanks for taking a look at this..
Quoted 36 lines
board/freescale/mx53loco/mx53loco.c| 10 ++++++++--include/configs/mx53loco.h | 1 + 2 files changed, 9 insertions(+), 2 deletions(-)board/freescale/mx53loco/mx53loco.c +8
-2@@ -462,12 +462,18 @@ int board_init(void)mxc_set_sata_internal_clock ();setup_iomux_i2c (); + +lcd_enable (); + +return 0 ; +} + +int board_late_init (void ) +{if (!power_init ())clock_1GHz ();print_cpuinfo (); -lcd_enable (); -return 0 ; }include/configs/mx53loco.h +0
-0
include/configs/mx53loco.h line 42
Quoted 4 lines
include/configs/mx53loco.h +1
-0@@ -39,6 +39,7 @@#define CONFIG_SYS_MALLOC_LEN (10 * 1024 * 1024)#define CONFIG_BOARD_EARLY_INIT_F +#define CONFIG_BOARD_LATE_INIT
Ah, i was missing this when heading down the "board_late_init" road on friday..
Quoted 11 lines
include/configs/mx53loco.h +0
-1#define CONFIG_MXC_GPIO #define CONFIG_REVISION_TAG --1.7.9.5
It boots now, but I get resets now:
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 13:13:28)
Quoted 11 lines
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.1 at 1000 MHz Reset cause: WDOG Net: FEC Warning: FEC using MAC address from net device
Interesting, I'm still only getting this far on the old Dialog board..
U-Boot 2013.01-rc2-00173-gd781d95-dirty (Dec 26 2012 - 09:42:43)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB
I'm going to start printf'ing:
http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/power/power_dialog.c
as we aren't getting the memory error, so it should be atleast past
that...
Quoted 6 lines
Hit any key to stop autoboot: 0
data abortMAYBE you should read doc/README.arm-unaligned-accesses
pc : [<aff72220>] lr : [<aff721fc>]
Quoted 8 lines
sp :
af565e20ip :af566918fp : 00000000
r10: 00000003 r9 :affabb5br8 :af565f58
r7 : 00000000 r6 :36747fffr5 :af5668e8r4 :36747fff
r3 :af5668ecr2 :af5668ebr1 : 00000000 r0 :af5668e8
Flags: NzcV IRQs off FIQs off ModeSVC_32
Resetting CPU ...resetting ...
I've reverted this just to double check (no change for me...):
http://git.denx.de/?p=u-boot.git;a=commit;h=28e5ac2d974547bde0c72aa0c1d66fd22c6ef3ad
Quoted 8 lines
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 13:13:28)
Board: MX53 LOCO I2C: ready DRAM: 1 GiBbut it looks like a separate issue?
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 7 lines · Robert Nelson
Interesting, I'm still only getting this far on the old Dialog board..
U-Boot 2013.01-rc2-00173-gd781d95-dirty (Dec 26 2012 - 09:42:43)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB
I tested with 2 mx53loco boards here: one with FSL PMIC and one with Dialog.
I recall we had 2 versions of boards with Dialog PMIC, but at least with the one I have here it boots fine now after applying the patch I just sent.
If you have any news, just let us know.
Thanks,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 10 lines · Fabio Estevam
Quoted 7 lines · Robert Nelson
Interesting, I'm still only getting this far on the old Dialog board..
U-Boot 2013.01-rc2-00173-gd781d95-dirty (Dec 26 2012 - 09:42:43)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB
Quoted 5 lines
I tested with 2 mx53loco boards here: one with FSL PMIC and one with Dialog.
I recall we had 2 versions of boards with Dialog PMIC, but at least with the one I have here it boots fine now after applying the patch I just sent.
Okay, good to hear it works with the Dialog PMIC you have, as that should cover a majority of the Dialog based boards customers actually have. As the one I have here was one of the very first ones and i know something changed later in production...
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 4 lines · Robert Nelson
Okay, good to hear it works with the Dialog PMIC you have, as that should cover a majority of the Dialog based boards customers actually have. As the one I have here was one of the very first ones and i know something changed later in production...
Yes, but not happy to see a regression with your board and also the resets that started to happen now.
Which toolchain did you use? I am using gcc 4.6.3. If you have a chance to try the same toolchain to make sure we got the same results, that would be nice.
Regards,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 9 lines · Fabio Estevam
Quoted 4 lines · Robert Nelson
Okay, good to hear it works with the Dialog PMIC you have, as that should cover a majority of the Dialog based boards customers actually have. As the one I have here was one of the very first ones and i know something changed later in production...
Yes, but not happy to see a regression with your board and also the resets that started to happen now.
I'll keep debugging it here, did reverting this commit, help with the resets?
http://git.denx.de/?p=u-boot.git;a=commit;h=28e5ac2d974547bde0c72aa0c1d66fd22c6ef3ad
Quoted 3 lines
Which toolchain did you use? I am using gcc 4.6.3. If you have a chance to try the same toolchain to make sure we got the same results, that would be nice.
That build was with Linaro's 4.7.1 2012.04 release, from:
https://launchpad.net/linaro-toolchain-binaries/
./arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (crosstool-NG linaro-1.13.1-2012.04-20120426 - Linaro GCC 2012.04) 4.7.1 20120402 (prerelease)
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 2 lines · Robert Nelson
I'll keep debugging it here, did reverting this commit, help with the resets?
http://git.denx.de/?p=u-boot.git;a=commit;h=28e5ac2d974547bde0c72aa0c1d66fd22c6ef3ad
Tried reverting it and still see the data-aborts.
I am also testing on my mx53loco board with the mc34708 pmic and I see that it hangs on boot about 10% of the attempts:
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 15:15:27)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1
This did not happen prior to commit c73368150 (pmic: Extend PMIC framework to support multiple instances
of PMIC devices).
Regards,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 11 lines · Fabio Estevam
Quoted 2 lines · Robert Nelson
I'll keep debugging it here, did reverting this commit, help with the resets?
http://git.denx.de/?p=u-boot.git;a=commit;h=28e5ac2d974547bde0c72aa0c1d66fd22c6ef3adTried reverting it and still see the data-aborts.
I am also testing on my mx53loco board with the mc34708 pmic and I see that it hangs on boot about 10% of the attempts:
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 15:15:27)
Quoted 8 lines
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1This did not happen prior to commit
c73368150(pmic: Extend PMIC framework to support multiple instances
of PMIC devices).
Okay, now we are on the same page, upgraded to:
"arm-linux-gnueabihf-gcc (crosstool-NG
linaro-1.13.1-4.7-2012.12-20121214 - Linaro GCC 2012.12) 4.7.3 20121205 (prerelease)"..
With your Dialog patch, it is properly setting 1Ghz, and just keeps rebooting.. :)
U-Boot 2013.01-rc2-00173-ga0d04f3 (Dec 26 2012 - 11:47:34)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.0 at 1000 MHz Reset cause: WDOG Net: FEC Warning: FEC using MAC address from net device
Hit any key to stop autoboot: 0
data abort
MAYBE you should read doc/README.arm-unaligned-accesses
pc : [<aff72250>] lr : [<aff72228>]
sp : af565d68 ip : fffffff4 fp : 00000000
r10: 00000003 r9 : affab8d9 r8 : af565f58
r7 : 00000000 r6 : e5bc345d r5 : af6df330 r4 : e5bc345d
r3 : af6df334 r2 : af6df333 r1 : 00000000 r0 : af6df330
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
U-Boot 2013.01-rc2-00173-ga0d04f3 (Dec 26 2012 - 11:47:34)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.0 at 1000 MHz
Reset cause: WDOG
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 49 lines · Robert Nelson
Quoted 11 lines · Fabio Estevam
Quoted 2 lines · Robert Nelson
I'll keep debugging it here, did reverting this commit, help with the resets?
http://git.denx.de/?p=u-boot.git;a=commit;h=28e5ac2d974547bde0c72aa0c1d66fd22c6ef3adTried reverting it and still see the data-aborts.
I am also testing on my mx53loco board with the mc34708 pmic and I see that it hangs on boot about 10% of the attempts:
U-Boot 2013.01-rc2-00172-gf8cfcf1-dirty (Dec 26 2012 - 15:15:27)Quoted 8 lines
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1This did not happen prior to commit
c73368150(pmic: Extend PMIC framework to support multiple instances
of PMIC devices).Okay, now we are on the same page, upgraded to:
"arm-linux-gnueabihf-gcc (crosstool-NG
linaro-1.13.1-4.7-2012.12-20121214 - Linaro GCC 2012.12) 4.7.3 20121205 (prerelease)"..With your Dialog patch, it is properly setting 1Ghz, and just keeps rebooting.. :)
U-Boot 2013.01-rc2-00173-ga0d04f3 (Dec 26 2012 - 11:47:34)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.0 at 1000 MHz Reset cause: WDOG Net: FEC Warning: FEC using MAC address from net deviceHit any key to stop autoboot: 0
data abort
MAYBE you should read doc/README.arm-unaligned-accessespc : [<aff72250>] lr : [<aff72228>]
Quoted 8 lines
sp :
af565d68ip :fffffff4fp : 00000000
r10: 00000003 r9 :affab8d9r8 :af565f58
r7 : 00000000 r6 :e5bc345dr5 :af6df330r4 :e5bc345d
r3 :af6df334r2 :af6df333r1 : 00000000 r0 :af6df330
Flags: nzCv IRQs off FIQs off ModeSVC_32Resetting CPU ...
resetting ...
Okay success on another bisect run to find what was causing the Data Abort with linaro's gcc toolchain..
gcc version 4.7.3 20121205 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2012.12-20121214 - Linaro GCC 2012.12)
Reverting, Troy's last 4 imximage changes:
ab857f2613be39274d0870768720067ff9d859c0 (imximage: make set_imx_hdr_v1/v2 easier to read) ad0826dcd81ba6cf4cc93a4ca8337e1bc676c238 (imximage: change parameters to set_imx_hdr)243319825fa6e79885d57b6b78e72f3fe10ef69c (imximage: delay setting of image size) 348ca8efb79652d2b259fbd0ed6d317a77a8cbb9 (imximage: fix size of image to load.) (this was the first bad bisect, the previous 3 are needed for a clean revert)
Along with Fabio's "mx53loco: Call PMIC related functions from board_late_init()"
The Dialog based mx53loco is no operating correctly with linaro's toolchain...
U-Boot 2013.01-rc2-00176-gbc67175-dirty (Jan 02 2013 - 12:14:51)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.0 at 1000 MHz Reset cause: POR Net: FEC Warning: FEC using MAC address from net device
Hit any key to stop autoboot: 0
mmc0 is current device
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Booting from net ...
BOOTP broadcast 1
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 37 lines · Robert Nelson
Okay success on another bisect run to find what was causing the Data Abort with linaro's gcc toolchain..
gcc version 4.7.3 20121205 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2012.12-20121214 - Linaro GCC 2012.12)Reverting, Troy's last 4 imximage changes:
ab857f2613be39274d0870768720067ff9d859c0(imximage: make set_imx_hdr_v1/v2 easier to read)ad0826dcd81ba6cf4cc93a4ca8337e1bc676c238(imximage: change parameters toset_imx_hdr)243319825fa6e79885d57b6b78e72f3fe10ef69c(imximage: delay setting of image size)348ca8efb79652d2b259fbd0ed6d317a77a8cbb9(imximage: fix size of image to load.) (this was the first bad bisect, the previous 3 are needed for a clean revert)Along with Fabio's "mx53loco: Call PMIC related functions from
board_late_init()"The Dialog based mx53loco is no operating correctly with linaro's toolchain...
U-Boot 2013.01-rc2-00176-gbc67175-dirty (Jan 02 2013 - 12:14:51)
Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1*** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial CPU: Freescale i.MX53 family rev2.0 at 1000 MHz Reset cause: POR Net: FEC Warning: FEC using MAC address from net device
Quoted 6 lines
Hit any key to stop autoboot: 0
mmc0 is current device
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Booting from net ...
BOOTP broadcast 1
Thanks for bisecting, Robert.
Troy/Stefano,
Any suggestions about this? It would be really nice if we could keep mx53loco functional when using gcc 4.6.2.
Regards,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 3 lines · Fabio Estevam
Thanks for bisecting, Robert. Troy/Stefano, Any suggestions about this? It would be really nice if we could keep mx53loco functional when using gcc 4.6.2. Regards, Fabio Estevam
Could you see if this patch makes any difference? It still needs cleaned up some before mainline
[PATCH V4 01/11] imximage: mx53 needs transfer length a multiple of 512
tools/imximage.c +9 -1
@@ -494,6 +494,8 @@ static void imximage_print_header(const void *ptr) } } +#define ALIGN (a, b) (((a) + (b) - 1) & ~((b) - 1)) +static void imximage_set_header (void *ptr,struct stat *sbuf,int ifd,struct mkimage_params *params) {
@@ -515,7 +517,13 @@ static void imximage_set_header(void *ptr, struct stat *sbuf, int ifd,/* Set the imx header */ (*set_imx_hdr)(imxhdr, dcd_len, params->ep, imxhdr->flash_offset); - *header_size_ptr = sbuf->st_size + imxhdr->flash_offset; +/* +* ROM bug alert +* mx53 only loads 512 byte multiples. +* The remaining fraction of a block bytes would +* not be loaded. +*/ + *header_size_ptr =ALIGN (sbuf->st_size + imxhdr->flash_offset,512 ); }int imximage_check_params (struct mkimage_params *params)
-- 1.7.9.5
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 27 lines · Troy Kisky
Quoted 4 lines · Fabio Estevam
Thanks for bisecting, Robert. Troy/Stefano, Any suggestions about this? It would be really nice if we could keep mx53loco functional when using gcc 4.6.2. Regards, Fabio Estevam
Could you see if this patch makes any difference? It still needs cleaned up some before mainline
[PATCH V4 01/11] imximage: mx53 needs transfer length a multiple of 512tools/imximage.c +1
-1@@ -494,6 +494,8 @@ static void imximage_print_header(const void *ptr) } } +#define ALIGN(a, b) (((a) + (b) - 1) & ~((b) - 1)) +static void imximage_set_header (void *ptr,struct stat *sbuf,int ifd,struct mkimage_params *params) {@@ -515,7 +517,13 @@ static void imximage_set_header(void *ptr, struct stat *sbuf, int ifd,/* Set the imx header */ (*set_imx_hdr)(imxhdr, dcd_len, params->ep, imxhdr->flash_offset); - *header_size_ptr = sbuf->st_size + imxhdr->flash_offset;
tools/imximage.c static void imximage_set_header(void *ptr, struct stat · line 521
Quoted 10 lines
tools/imximage.c +7
-1+/* +* ROM bug alert +* mx53 only loads 512 byte multiples. +* The remaining fraction of a block bytes would +* not be loaded. +*/ + *header_size_ptr =ALIGN (sbuf->st_size + imxhdr->flash_offset,512 ); }int imximage_check_params (struct mkimage_params *params) -- 1.7.9.5
Sweet! Thanks Troy,
That fixes it on my Dialog based mx53loco with linaro's 4.7.3 gcc toolchain...
Regards,
Signature · 2 lines
Robert Nelson http://www.rcn-ee.com/
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 3 lines · Robert Nelson
Sweet! Thanks Troy,
That fixes it on my Dialog based mx53loco with linaro's 4.7.3 gcc toolchain...
Excellent, Troy!
Fixes the issue for me with gcc 4.6.2 as well.
It would be really nice to have this one applied for 2013.01.
Thanks,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 11 lines · Fabio Estevam
Quoted 3 lines · Robert Nelson
Sweet! Thanks Troy,
That fixes it on my Dialog based mx53loco with linaro's 4.7.3 gcc toolchain...
Excellent, Troy!
Fixes the issue for me with gcc 4.6.2 as well.
It would be really nice to have this one applied for 2013.01.
Hi all,
the patch was only blocked for Wolfgang's comment regarding the introduced ALIGN() macro. I think the other doubts regarding issues on other Socs (i.e., MX6) can be considered closed as well. IMHO it is enough to rename the macro to ROUND_UP (as Troy have already proposed), and then I will apply to i.MX tree.
Regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Hi Stefano,
Quoted 7 lines · Stefano Babic
Hi all,
the patch was only blocked for Wolfgang's comment regarding the introduced
ALIGN()macro. I think the other doubts regarding issues on other Socs (i.e., MX6) can be considered closed as well. IMHO it is enough to rename the macro toROUND_UP(as Troy have already proposed), and then I will apply to i.MX tree.
I tried using DIV_ROUND_UP definition from common.h and the board does not boot.
I rename it to ROUND, which matches the definition in common.h.
Just sent the patch.
Regards,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Dear Fabio Estevam,
Quoted 11 lines
Hi Stefano,
Quoted 7 lines · Stefano Babic
Hi all,
the patch was only blocked for Wolfgang's comment regarding the introduced
ALIGN()macro. I think the other doubts regarding issues on other Socs (i.e., MX6) can be considered closed as well. IMHO it is enough to rename the macro toROUND_UP(as Troy have already proposed), and then I will apply to i.MX tree.
Quoted 4 lines
I tried using
DIV_ROUND_UPdefinition fromcommon.hand the board does not boot.I rename it to ROUND, which matches the definition in
common.h.
Ugh, why can't the stuff from common.h be used ?
Quoted 5 lines
Just sent the patch.
Regards,
Fabio Estevam
Best regards,
Marek Vasut
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 1 line · Marek Vasut
Ugh, why can't the stuff from
common.hbe used ?
Yes, I tried it initially, but it throws a lot of errors that I am not sure that they can be easily fixed:
....
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -idirafter /home/fabio/denx/u-boot-imx/include -idirafter /home/fabio/denx/u-boot-imx/include2 -idirafter /home/fabio/denx/u-boot-imx/include -I /home/fabio/denx/u-boot-imx/lib/libfdt -I /home/fabio/denx/u-boot-imx/tools -DCONFIG_SYS_TEXT_BASE=0x77800000
-DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -o imximage.o imximage.c -c
make[1]: Leaving directory /home/fabio/denx/u-boot-imx/arch/arm/cpu/armv7' make[2]: Entering directory /home/fabio/denx/u-boot-imx/tools/kernel-doc' make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/fabio/denx/u-boot-imx/tools/kernel-doc' In file included from /home/fabio/denx/u-boot-imx/include/common.h:39:0,
from imximage.c:34:
/home/fabio/denx/u-boot-imx/include/linux/bitops.h: In function ?generic_set_bit?:/home/fabio/denx/u-boot-imx/include/linux/bitops.h:141:23: error:
?BITS_PER_LONG? undeclared (first use in this function) /home/fabio/denx/u-boot-imx/include/linux/bitops.h:141:23: note: each undeclared identifier is reported only once for each function it appears in /home/fabio/denx/u-boot-imx/include/linux/bitops.h: In function ?generic_clear_bit?:/home/fabio/denx/u-boot-imx/include/linux/bitops.h:149:23: error:
?BITS_PER_LONG? undeclared (first use in this function)
In file included from /home/fabio/denx/u-boot-imx/include/common.h:174:0,
from imximage.c:34:
/home/fabio/denx/u-boot-imx/include/asm/global_data.h: At top level:/home/fabio/denx/u-boot-imx/include/asm/global_data.h:69:2: error:
unknown type name ?phys_size_t?
In file included from imximage.c:34:0:/home/fabio/denx/u-boot-imx/include/common.h:270:1: error: unknown type name ?phys_size_t? /home/fabio/denx/u-boot-imx/include/common.h:311:1: error: unknown type name ?u8? /home/fabio/denx/u-boot-imx/include/common.h:328:14: error: unknown type name ?cmd_tbl_t? /home/fabio/denx/u-boot-imx/include/common.h:331:19: error: unknown type name ?cmd_tbl_t? /home/fabio/denx/u-boot-imx/include/common.h:334:17: error: unknown type name ?cmd_tbl_t? /home/fabio/denx/u-boot-imx/include/common.h:344:5: error: conflicting types for ?setenv?/usr/include/stdlib.h:585:12: note: previous declaration of ?setenv? was here /home/fabio/denx/u-boot-imx/include/common.h:562:1: error: unknown type name ?u32?
In file included from imximage.c:34:0:/home/fabio/denx/u-boot-imx/include/common.h:787:5: error: conflicting types for ?_IO_getc?/usr/include/libio.h:462:12: note: previous declaration of ?_IO_getc? was here /home/fabio/denx/u-boot-imx/include/common.h:791:23: error: macro "putc" requires 2 arguments, but only 1 given /home/fabio/denx/u-boot-imx/include/common.h:791:6: error: ?putc? redeclared as different kind of symbol /home/fabio/denx/u-boot-imx/include/common.h:792:6: error: conflicting types for ?puts? /home/fabio/denx/u-boot-imx/include/common.h:810:5: error: conflicting types for ?fprintf? /home/fabio/denx/u-boot-imx/include/common.h:812:6: error: conflicting types for ?fputs? /home/fabio/denx/u-boot-imx/include/common.h:813:6: error: conflicting types for ?fputc? /home/fabio/denx/u-boot-imx/include/common.h:815:5: error: conflicting types for ?fgetc?/usr/include/stdio.h:537:12: note: previous declaration of ?fgetc? was here In file included from /home/fabio/denx/u-boot-imx/include/common.h:825:0,
from imximage.c:34:
/home/fabio/denx/u-boot-imx/include/net.h:42:1: error: unknown type name ?u32? /home/fabio/denx/u-boot-imx/include/net.h:632:1: error: unknown type name ?u8? /home/fabio/denx/u-boot-imx/include/net.h:644:1: error: unknown type name ?u8? /home/fabio/denx/u-boot-imx/include/net.h:655:1: error: unknown type name ?u8? /home/fabio/denx/u-boot-imx/include/net.h:670:1: error: unknown type name ?u8? make[1]: *** [imximage.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/home/fabio/denx/u-boot-imx/tools'
make: *** [tools] Error 2
Regards,
Fabio Estevam
PATCH 1/1 mx53loco: Fix PMIC name
Dear Fabio Estevam,
Quoted 5 lines · Marek Vasut
Quoted 1 line
Ugh, why can't the stuff from
common.hbe used ?Yes, I tried it initially, but it throws a lot of errors that I am not sure that they can be easily fixed:
Only with #include <common.h> ?
Quoted 3 lines
Regards,
Fabio Estevam
Best regards,
Marek Vasut
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 2 lines · Marek Vasut
Dear Fabio Estevam,
Hi,
Quoted 7 lines
Quoted 5 lines · Marek Vasut
Quoted 1 line
Ugh, why can't the stuff from
common.hbe used ?Yes, I tried it initially, but it throws a lot of errors that I am not sure that they can be easily fixed:
Only with #include <
common.h> ?
I will remark a previous comment - even if including common.h seems a good idea to avoid duplications, it makes tools like mkimage to depend on the selected board, because <board>_config must run. Even if this is not a problem for us u-boot developers, it becomes an issue when these tools are included in distros (like u-boot-tools in Ubuntu) and cannot be packaged.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH 1/1 mx53loco: Fix PMIC name
Quoted 17 lines · Stefano Babic
Quoted 2 lines · Marek Vasut
Dear Fabio Estevam,
Hi,
Quoted 5 lines
Quoted 4 lines · Marek Vasut
Quoted 1 line
Ugh, why can't the stuff from
common.hbe used ?Yes, I tried it initially, but it throws a lot of errors that I am not sure that they can be easily fixed:
Only with #include <
common.h> ?I will remark a previous comment - even if including
common.hseems a good idea to avoid duplications, it makes tools like mkimage to depend on the selected board, because <board>_config must run. Even if this is not a problem for us u-boot developers, it becomes an issue when these tools are included in distros (like u-boot-tools in Ubuntu) and cannot be packaged.
Quoted 3 lines
Best regards,
Stefano Babic
It would be good to include this in commit log if not already committed.
Thanks
Troy
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
Quoted 1 line · Troy Kisky
It would be good to include this in commit log if not already committed.
Ok, just sent a v2 with such comment.
Regards,
Fabio Estevam
Fabio Estevam
reviewerPATCH 1/1 mx53loco: Fix PMIC name
In reply to Marek VasutQuoted 9 lines · Marek Vasut
Dear Fabio Estevam,
Quoted 5 lines · Marek Vasut
Quoted 1 line
Ugh, why can't the stuff from
common.hbe used ?Yes, I tried it initially, but it throws a lot of errors that I am not sure that they can be easily fixed:
Only with #include <
common.h> ?
Yes, correct.
PATCH 1/1 mx53loco: Fix PMIC name
In reply to Fabio EstevamQuoted 12 lines · Fabio Estevam
Hi Stefano,
Quoted 7 lines · Stefano Babic
Hi all,
the patch was only blocked for Wolfgang's comment regarding the introduced
ALIGN()macro. I think the other doubts regarding issues on other Socs (i.e., MX6) can be considered closed as well. IMHO it is enough to rename the macro toROUND_UP(as Troy have already proposed), and then I will apply to i.MX tree.
Quoted 3 lines
I tried using
DIV_ROUND_UPdefinition fromcommon.hand the board does not boot.I rename it to ROUND, which matches the definition in
common.h.
I agree with this solution - I do not like that common.h is included, because _config must run and tools should be independent from the selected board.
Quoted 2 lines
Just sent the patch.
Then I apply it !
Thanks,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================