All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jürgen <J.Kilb@phytec.de>
To: barebox@lists.infradead.org
Subject: Re: Antwort: Re: v2013.02.0 phyCORE-OMAP4 MLO to big
Date: Tue, 05 Mar 2013 14:30:22 +0100	[thread overview]
Message-ID: <5135F36E.2090401@phytec.de> (raw)
In-Reply-To: <OFC6CD83ED.4FD2D09A-ONC1257B25.0047F4F9-C1257B25.00480A80@phytec.de>

On 11.02.2013 Sascha Hauer wrote:
> On Fri, Feb 08, 2013 at 04:22:09PM +0100, Jan Weitzel wrote:
>> Hi,
>> with the release v2013.02.0 the MLO gets so bit, that it eats the boot
>> information in the SRAM.
>>
>> nm --size-sort
>>
>> ...
>> 00000630 D nand_flash_ids
>> 000008c0 t mci_probe
>> 00000c00 b gpio_desc
>> 00001400 b files
>>
>> If I remove  GPIOLIB from MLO it work again. Maybe setting MAX_FILES
>> down or find a dynamic way for the big arrays is a better solution.
>> Any Ideas?
> Could you link the MLO to SDRAM instead?
Hi Sascha, we have tried as you suggested and it doesn't work without 
changes...

We found two things:

1.) There is early code which is not relocatable.

We solved this by adding -fPIC to the CPPFLAGS.
But I think, this is also solved with your patch 
http://lists.infradead.org/pipermail/barebox/2013-March/013366.html

2.) The TEXTBASE is passed to the signGP tool, which is wrong if
       TEXT_BASE is different from the executing address before relocating.
       In our case TEXT_BASE would be 0x86000000 but the MLO is executed 

in internal SRAM at 0x40300000.

So I would suggest to create a config option like OMAP_IFT_BASE which 
can be passed to the signGP tool and is set to 0x40300000 per default..

What do you think?

Jürgen


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

  parent reply	other threads:[~2013-03-05 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 15:22 v2013.02.0 phyCORE-OMAP4 MLO to big Jan Weitzel
2013-02-11 10:04 ` Sascha Hauer
     [not found]   ` <OFC6CD83ED.4FD2D09A-ONC1257B25.0047F4F9-C1257B25.00480A80@phytec.de>
2013-03-05 13:30     ` Jürgen [this message]
2013-03-07  8:18       ` Antwort: " Sascha Hauer
2013-03-07 11:19         ` Jean-Christophe PLAGNIOL-VILLARD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5135F36E.2090401@phytec.de \
    --to=j.kilb@phytec.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.