All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: barebox@lists.infradead.org
Subject: confusion about relocation (ARM)
Date: Fri, 1 Jan 2010 20:48:22 +0100	[thread overview]
Message-ID: <20100101194822.GR5093@darwin> (raw)

hi,

i'm trying to run barebox on an EP93xx (ARM) board, but don't get
beyond the invocation of some initcalls from start_barebox(). at the
moment i have no JTAG for debugging and rely on LEDs for hints whats
going on. my suspicion is that the stack or SDRAM isn't set up
correctly.

a comment in start_barebox() says 'We are running from RAM now', so i
deduced SDRAM must work. but after having a look at start-arm.S i'm a
little bit confused. as far as i understand the barebox code is copied
to RAM in copy_loop(). what i don't see is where the program counter
is set to the address in RAM?

any insights?

-- 
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

    Me lo contaron y lo olvidé, lo vi y lo entendí, lo hice y lo aprendí
                              (Confucio)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

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

             reply	other threads:[~2010-01-01 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01 19:48 Matthias Kaehlcke [this message]
2010-01-01 20:36 ` confusion about relocation (ARM) Eric Bénard
2010-01-01 21:48   ` Matthias Kaehlcke
2010-01-04 12:07     ` Sascha Hauer
2010-01-04 19:21       ` Matthias Kaehlcke
2010-01-04 20:13         ` Robert Schwebel
2010-01-04 21:10           ` Matthias Kaehlcke

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=20100101194822.GR5093@darwin \
    --to=matthias@kaehlcke.net \
    --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.