Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Kim Phillips
On Thu, 22 Jan 2009 15:05:24 -0800
Ron Madrid ron_mad...@sbcglobal.net wrote:

 +ENTRY(_start)
 +ASSERT(_end = 0xfff01000, NAND bootstrap too big);

Ron, the above gets asserted when building for large page nand with a
gcc 4.1.2 based toolchain:

[...@beaut u-boot (next)]$ ./MAKEALL SIMPC8313_SP
...Small Page NAND...Configuring for SIMPC8313 board...
   textdata bss dec hex filename
 250704   20964   28472  300140   4946c ./u-boot
[...@beaut u-boot (next)]$ ./MAKEALL SIMPC8313_LP
...Large Page NAND...Configuring for SIMPC8313 board...
ld: NAND bootstrap too big
ld: NAND bootstrap too big
make[1]: *** [/home/kim/git/u-boot/nand_spl/u-boot-spl] Error 1
make: *** [nand_spl] Error 2
make: *** Waiting for unfinished jobs
size: './u-boot': No such file

Kim
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Ron Madrid
--- On Fri, 1/23/09, Kim Phillips kim.phill...@freescale.com wrote:

 From: Kim Phillips kim.phill...@freescale.com
 Subject: Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313
 To: Ron Madrid ron_mad...@sbcglobal.net
 Cc: u-boot@lists.denx.de
 Date: Friday, January 23, 2009, 12:36 PM
 On Thu, 22 Jan 2009 15:05:24 -0800
 Ron Madrid ron_mad...@sbcglobal.net wrote:
 
  +ENTRY(_start)
  +ASSERT(_end = 0xfff01000, NAND bootstrap
 too big);
 
 Ron, the above gets asserted when building for large page
 nand with a
 gcc 4.1.2 based toolchain:

Please forgive my ignorance, but how can I go about fixing this?  How do I
determine my toolchain and how can I use the same one you are referring to? 
Are there any documents that can point me in the right direction?

Also, this seems strange that they should have different sizes when being
built as they have always been identical sizes for my builds.  But I'll
determine the reason for this soon.

Ron
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Kim Phillips
On Fri, 23 Jan 2009 13:29:03 -0800 (PST)
Ron Madrid ron_mad...@sbcglobal.net wrote:

 --- On Fri, 1/23/09, Kim Phillips kim.phill...@freescale.com wrote:
 
  From: Kim Phillips kim.phill...@freescale.com
  Subject: Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313
  To: Ron Madrid ron_mad...@sbcglobal.net
  Cc: u-boot@lists.denx.de
  Date: Friday, January 23, 2009, 12:36 PM
  On Thu, 22 Jan 2009 15:05:24 -0800
  Ron Madrid ron_mad...@sbcglobal.net wrote:
  
   +ENTRY(_start)
   +ASSERT(_end = 0xfff01000, NAND bootstrap
  too big);
  
  Ron, the above gets asserted when building for large page
  nand with a
  gcc 4.1.2 based toolchain:
 
 Please forgive my ignorance, but how can I go about fixing this?  How do I
 determine my toolchain and how can I use the same one you are referring to? 
 Are there any documents that can point me in the right direction?

I'm just using what Fedora brought to me on my G5 box (native
compiler).  I still use it because it's close to what the ELDK version
is (or used to be - I can't immediately tell which version the ELDK is
using right now).  Where/when did you get your toolchain?

 Also, this seems strange that they should have different sizes when being
 built as they have always been identical sizes for my builds.  But I'll
 determine the reason for this soon.

this is true; if it helps, I tried playing with the LP's PAD_TO value
to no avail...

Kim
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Ron Madrid

--- On Fri, 1/23/09, Kim Phillips kim.phill...@freescale.com wrote:
   
+ENTRY(_start)
+ASSERT(_end = 0xfff01000, NAND
 bootstrap
   too big);
   
   Ron, the above gets asserted when building for
 large page
   nand with a
   gcc 4.1.2 based toolchain:
  
  Please forgive my ignorance, but how can I go about
 fixing this?  How do I
  determine my toolchain and how can I use the same one
 you are referring to? 
  Are there any documents that can point me in the right
 direction?
 
 I'm just using what Fedora brought to me on my G5 box
 (native
 compiler).  I still use it because it's close to what
 the ELDK version
 is (or used to be - I can't immediately tell which
 version the ELDK is
 using right now).  Where/when did you get your toolchain?

I am using the one that came with FC4.  I'm guessing that I should go ahead
an update my gcc.  I'm in the middle of doing that.  I'll get back to you
if I discover anything and then of course I'll resubmit.

 
  Also, this seems strange that they should have
 different sizes when being
  built as they have always been identical sizes for my
 builds.  But I'll
  determine the reason for this soon.
 
 this is true; if it helps, I tried playing with the
 LP's PAD_TO value
 to no avail...

Thanks for the info.

Ron
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Ron Madrid
--- On Fri, 1/23/09, Ron Madrid ron_mad...@sbcglobal.net wrote:

 From: Ron Madrid ron_mad...@sbcglobal.net
 Subject: Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313
 To: Kim Phillips kim.phill...@freescale.com
 Cc: u-boot@lists.denx.de
 Date: Friday, January 23, 2009, 2:29 PM
 --- On Fri, 1/23/09, Kim Phillips
 kim.phill...@freescale.com wrote:

 +ENTRY(_start)
 +ASSERT(_end = 0xfff01000,
 NAND
  bootstrap
too big);

Ron, the above gets asserted when building
 for
  large page
nand with a
gcc 4.1.2 based toolchain:
   
   Please forgive my ignorance, but how can I go
 about
  fixing this?  How do I
   determine my toolchain and how can I use the same
 one
  you are referring to? 
   Are there any documents that can point me in the
 right
  direction?
  
  I'm just using what Fedora brought to me on my G5
 box
  (native
  compiler).  I still use it because it's close to
 what
  the ELDK version
  is (or used to be - I can't immediately tell which
  version the ELDK is
  using right now).  Where/when did you get your
 toolchain?
 
 I am using the one that came with FC4.  I'm guessing
 that I should go ahead
 an update my gcc.  I'm in the middle of doing that. 
 I'll get back to you
 if I discover anything and then of course I'll
 resubmit.

I upgraded my gcc and did not see any difference in the builds.  I'm not sure 
where to go from here.

Ron
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Kim Phillips
On Fri, 23 Jan 2009 15:36:40 -0800 (PST)
Ron Madrid ron_mad...@sbcglobal.net wrote:

 --- On Fri, 1/23/09, Ron Madrid ron_mad...@sbcglobal.net wrote:
 
  From: Ron Madrid ron_mad...@sbcglobal.net
  Subject: Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313
  To: Kim Phillips kim.phill...@freescale.com
  Cc: u-boot@lists.denx.de
  Date: Friday, January 23, 2009, 2:29 PM
  --- On Fri, 1/23/09, Kim Phillips
  kim.phill...@freescale.com wrote:
 
  +ENTRY(_start)
  +ASSERT(_end = 0xfff01000,
  NAND
   bootstrap
 too big);
 
 Ron, the above gets asserted when building
  for
   large page
 nand with a
 gcc 4.1.2 based toolchain:

Please forgive my ignorance, but how can I go
  about
   fixing this?  How do I
determine my toolchain and how can I use the same
  one
   you are referring to? 
Are there any documents that can point me in the
  right
   direction?
   
   I'm just using what Fedora brought to me on my G5
  box
   (native
   compiler).  I still use it because it's close to
  what
   the ELDK version
   is (or used to be - I can't immediately tell which
   version the ELDK is
   using right now).  Where/when did you get your
  toolchain?
  
  I am using the one that came with FC4.  I'm guessing
  that I should go ahead
  an update my gcc.  I'm in the middle of doing that. 
  I'll get back to you
  if I discover anything and then of course I'll
  resubmit.
 
 I upgraded my gcc and did not see any difference in the builds.  I'm not sure 
 where to go from here.

me neither.  I know it works with gcc 4.2, just not gcc 4.1, and I
don't know what version the ELDK currently uses.  I'll just take it
since it's so early in the cycle, and WD seems to be overtaking me in
83xx patches anyway ;). I expect the issue to be fixed before the next
release though.

Kim
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Wolfgang Denk
Dear Kim Phillips,

In message 20090123175552.3f60db0b.kim.phill...@freescale.com you wrote:

 me neither.  I know it works with gcc 4.2, just not gcc 4.1, and I
 don't know what version the ELDK currently uses.  I'll just take it
 since it's so early in the cycle, and WD seems to be overtaking me in
 83xx patches anyway ;). I expect the issue to be fixed before the next
 release though.

ELDK uses:

ELDK 4.0:   gcc version 4.0.0
ELDK 4.1:   gcc version 4.0.0
ELDK 4.2:   gcc version 4.2.2

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
I can't understand it. I can't even understand  the  people  who  can
understand it.- Queen Juliana of the Netherlands.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v5] mpc83xx: New board support for SIMPC8313

2009-01-23 Thread Kim Phillips
On Sat, 24 Jan 2009 02:14:16 +0100
Wolfgang Denk w...@denx.de wrote:

 In message 20090123175552.3f60db0b.kim.phill...@freescale.com you wrote:
 
  me neither.  I know it works with gcc 4.2, just not gcc 4.1, and I
  don't know what version the ELDK currently uses.  I'll just take it
  since it's so early in the cycle, and WD seems to be overtaking me in
  83xx patches anyway ;). I expect the issue to be fixed before the next
  release though.
 
 ELDK uses:
 
 ELDK 4.0: gcc version 4.0.0
 ELDK 4.1: gcc version 4.0.0
 ELDK 4.2: gcc version 4.2.2

great, then all should be ok.

Thank you Wolfgang,

Kim
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot