All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] at91rm9200 linking problem (?)
Date: Mon, 20 Jun 2011 11:59:13 +0200	[thread overview]
Message-ID: <4DFF19F1.1080300@gmail.com> (raw)
In-Reply-To: <BANLkTi==e5RwZKGRTS=bdiHZ61VT37JYOg@mail.gmail.com>

Dear Marcin G?rski,

please no TOFU, use inline quoting (and send also to the list).

Am 20.06.2011 11:39, schrieb Marcin G?rski:
> Hello,
> 
> I already use CONFIG_SKIP_LOWLEVEL_INIT to prevent U-Boot from reinitilizing
> hardware. My board has 128MB RAM, so 0x22000000 address is not a problem.

Ok so far.

> Have you got any ideas why U-Boot cannot correctly detect RAM size (it shows
> "DRAM:  1 MiB") and crashes after that?

How do you setup your gd_t? Have you written a correct 'int dram_init()'
in your board code (see board/atmel/at91rm9200ek/at91rm9200ek.c for
example)?

> To compile it I also had to add 3 macros to the configuration file:
> CONFIG_SYS_INIT_RAM_ADDR,

Why this? I guess you mean CONFIG_SYS_SDRAM_BASE here.

> 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.

regards

Andreas Bie?mann

  parent reply	other threads:[~2011-06-20  9:59 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 [this message]
2011-06-21 13:19       ` Marcin Górski
2011-06-21 14:35         ` Andreas Bießmann

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=4DFF19F1.1080300@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 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.