mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0
@ 2020-02-07 10:17 Koelle, Holger
  2020-02-07 10:33 ` Ahmad Fatoum
  0 siblings, 1 reply; 4+ messages in thread
From: Koelle, Holger @ 2020-02-07 10:17 UTC (permalink / raw)
  To: barebox

Hey there,

this week i updated some imx27 based phycard from Barebox 2019.01 to 2020.01. After the update at Boot nothing happens.. no output on serial.
Devicetree and Configuration (barebox.config in ptxdist) looks fine...got anyone suggestions for me?


Regards,

H.Koelle


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0
  2020-02-07 10:17 imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0 Koelle, Holger
@ 2020-02-07 10:33 ` Ahmad Fatoum
  2020-02-11 15:33   ` AW: " Koelle, Holger
  0 siblings, 1 reply; 4+ messages in thread
From: Ahmad Fatoum @ 2020-02-07 10:33 UTC (permalink / raw)
  To: Koelle, Holger, barebox

Hello,

On 2/7/20 11:17 AM, Koelle, Holger wrote:
> Hey there,
> 
> this week i updated some imx27 based phycard from Barebox 2019.01 to 2020.01. After the update at Boot nothing happens.. no output on serial.
> Devicetree and Configuration (barebox.config in ptxdist) looks fine...got anyone suggestions for me?

Try finding the offending commit with git-bisect:

git bisect good v2019.01.0
git bisect bad v2020.01.0
# build, flash, run barebox
git bisect good # if it works
git bisect bad # if it doesn't work

There have been 1004 revisions between the two tags, which means, a binary
search will find the offending commit in 10 iterations.

When you've found the commit and need to take a more thorough look (printf-debugging),
you can add low level UART debug support to your board.

Keep us updated!

Cheers
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 4+ messages in thread

* AW: imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0
  2020-02-07 10:33 ` Ahmad Fatoum
@ 2020-02-11 15:33   ` Koelle, Holger
  2020-02-12  8:08     ` Sascha Hauer
  0 siblings, 1 reply; 4+ messages in thread
From: Koelle, Holger @ 2020-02-11 15:33 UTC (permalink / raw)
  To: barebox; +Cc: Ahmad Fatoum

Hey,

today i followed yout recommends with git bisect.

I've found the offending commit. 
It is Commit :  [b0348d677bb47bdbd368983603b3e9604528d4ed] ARM: Compile with -fPIE

If I remove the Compilerflag (line 145) :

CPPFLAGS += -fPIE 

from arch/arm/Makefile , then every Barebox Version (include v2020.01.0) compile and run fine on phycard imx27.

Whats the impact if I remove this flag? Does imx27 not support this option?


Regards

Holger

 

-----Ursprüngliche Nachricht-----
Von: Ahmad Fatoum <a.fatoum@pengutronix.de> 
Gesendet: Freitag, 7. Februar 2020 11:33
An: Koelle, Holger <Holger.Koelle@allegion.com>; barebox@lists.infradead.org
Betreff: Re: imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0

Hello,

On 2/7/20 11:17 AM, Koelle, Holger wrote:
> Hey there,
> 
> this week i updated some imx27 based phycard from Barebox 2019.01 to 2020.01. After the update at Boot nothing happens.. no output on serial.
> Devicetree and Configuration (barebox.config in ptxdist) looks fine...got anyone suggestions for me?

Try finding the offending commit with git-bisect:

git bisect good v2019.01.0
git bisect bad v2020.01.0
# build, flash, run barebox
git bisect good # if it works
git bisect bad # if it doesn't work

There have been 1004 revisions between the two tags, which means, a binary search will find the offending commit in 10 iterations.

When you've found the commit and need to take a more thorough look (printf-debugging), you can add low level UART debug support to your board.

Keep us updated!

Cheers
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0
  2020-02-11 15:33   ` AW: " Koelle, Holger
@ 2020-02-12  8:08     ` Sascha Hauer
  0 siblings, 0 replies; 4+ messages in thread
From: Sascha Hauer @ 2020-02-12  8:08 UTC (permalink / raw)
  To: Koelle, Holger; +Cc: barebox, Ahmad Fatoum

Hi Holger,

On Tue, Feb 11, 2020 at 03:33:12PM +0000, Koelle, Holger wrote:
> Hey,
> 
> today i followed yout recommends with git bisect.
> 
> I've found the offending commit. 
> It is Commit :  [b0348d677bb47bdbd368983603b3e9604528d4ed] ARM: Compile with -fPIE
> 
> If I remove the Compilerflag (line 145) :
> 
> CPPFLAGS += -fPIE 
> 
> from arch/arm/Makefile , then every Barebox Version (include v2020.01.0) compile and run fine on phycard imx27.
> 
> Whats the impact if I remove this flag? Does imx27 not support this option?

The problem here is that the i.MX27 only loads 2k of memory from NAND
initially from which we have to bootstrap ourselves. This code is
cumbersome to write in assembly, so it is written in C. This requires
us to run code from a location it is not linked at. the -fPIE flag
influences the way how this code is compiled and apparently it doesn't
cope well with this flag.

The relevant code is in arch/arm/mach-imx/external-nand-boot.c.

I can see if I can find some time to debug it. Which toolchain are you
using?

Regards,
 Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-02-12  8:08 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-07 10:17 imx27 phycard update problems from barebox 2019.01.0 to 2020.01.0 Koelle, Holger
2020-02-07 10:33 ` Ahmad Fatoum
2020-02-11 15:33   ` AW: " Koelle, Holger
2020-02-12  8:08     ` Sascha Hauer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox