From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] at91rm9200 linking problem (?)
Date: Tue, 21 Jun 2011 16:35:47 +0200 [thread overview]
Message-ID: <4E00AC43.2060307@gmail.com> (raw)
In-Reply-To: <9AE98995-924C-4A11-9221-9754429E7FEE@gmail.com>
Dear Marcin G?rski,
Am 21.06.2011 15:19, schrieb Marcin G?rski:
>>> CONFIG_SYS_INIT_RAM_SIZE and
>>> CONFIG_SYS_INIT_SP_ADDR. Can this cause this problem?
>>
>> SYS_INIT_SP_ADDR is required, if you see 'DRAM: ...' output it is likely
>> to be a correct value for you. I guess your gd_t parameters for SDRAM
>> size are not correct which leads to a wrong relocation address and
>> therefore relocate_code() fails.
>
>
> Yes, I've fixed gd_t parameter but the result hasn't changed.
Ok ... can you debug the board_init_f/relocate_code/board_init_r functions?
Where is your relocate_code() destination address (it is calculated in
board_init_f())?
Is relocate_code() reached?
Does the fixup loop's run? (don't forget to reload symbol file as
described in doc/README.arm-relocation)
Is board_init_r() reached?
...
> All behaviour described so far relates to at91rm9200dk board.
at91rm9200dk uses the deprecated arm920t/at91rm9200 stuff and is known
to be broken currently! The arm920t/at91rm9200 code will be deleted in
near future! (and so at91rm9200dk board, if you have one handy please
try to get it working with arm920t/at91 files). If your board uses
arm920t/at91rm9200 configuration please convert it to arm920t/at91 ASAP!
> You mentioned trying at91rm9200ek board, so I switched to it,
> but I have problems with with compilation when data flash memory is used
> (I need it to store environment settings).
Sorry, I can not help here cause I didn't get dataflash working with
at91rm9200ek yet.
> So I tried not to store environment settings
> by defining CONFIG_ENV_IS_IN_NOWHERE and comment out all data flash configs, but I end up
> with multiple undefined references (to flash, spi and dataflash).
> How did you make your board to run only in RAM omitting flash configuration?
Well I own an at91rm9200ek and use the at91rm9200ek_ram_config to build
(is mainline). The NOR flash booting is currently broken but getting
this working is my next target.
Dataflash for at91 targets in principle is currently somewhat
broken/unreliable/defective API (there was a discussion these days,
search the list).
regards
Andreas Bie?mann
prev parent reply other threads:[~2011-06-21 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 8:36 [U-Boot] at91rm9200 linking problem (?) Marcin Górski
2011-06-20 9:04 ` Andreas Bießmann
[not found] ` <BANLkTi==e5RwZKGRTS=bdiHZ61VT37JYOg@mail.gmail.com>
2011-06-20 9:59 ` Andreas Bießmann
2011-06-21 13:19 ` Marcin Górski
2011-06-21 14:35 ` Andreas Bießmann [this message]
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=4E00AC43.2060307@gmail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox