All of lore.kernel.org
 help / color / mirror / Atom feed
From: J. L. Sloan <jsloan@diag.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for AT91RM9200-EK?
Date: Tue, 29 Jul 2008 16:23:00 -0600	[thread overview]
Message-ID: <00c101c8f1c9$ad9f5500$08ddff00$@com> (raw)

Just to make sure I'm not spinning my wheels, has anyone gotten Buildroot
(22987 is what I'm using right now) working for the Atmel AT91RM9200-EK
board (Atmel AT91 ARM9)?

 

I've got the 2.6.25.10 kernel booting okay, but as soon as it goes to run
/init (really, busybox) wackiness ensues. It traps in clear_user trying to
zero out part of the loaded ELF. GDB+BDI suggests that the address passed
from padzero to clear_user is bogus, but I'm not sure I'm trusting what it's
telling me (some of the other stuff on the stack trace looks questionable).

 

readelf-h suggests AFAIK that everything is built as OABI. (I may restart
from the beginning with EABI, but I'm not sure how U-Boot on the EK was
built, and I'm not sure if that really matters. But U-Boot does "call" the
kernel to start it.)

 

Thanks for any insight.

 

--

John Sloan <http://www.diag.com/navigation/metadata/jsloan.html>
Consulting Technologist

jsloan at diag.com          Digital Aggregates Corporation
<http://www.diag.com/> 

+1 303 489 5178 (Mobile) Arvada
<http://www.google.com/maps?f=q&hl=en&geocode=&q=Arvada+Colorado&ie=UTF8&z=1
1&iwloc=addr&om=1>  Colorado 80001-0587 USA

+1 303 940 9064 (Office) www.diag.com <http://www.diag.com/> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080729/fc346d0d/attachment.htm 

             reply	other threads:[~2008-07-29 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 22:23 J. L. Sloan [this message]
2008-07-29 23:28 ` [Buildroot] Buildroot for AT91RM9200-EK? J. L. Sloan
2008-07-30 14:07   ` J. L. Sloan
2008-07-30 20:19   ` J. L. Sloan
2008-07-30 22:39     ` J. L. Sloan

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='00c101c8f1c9$ad9f5500$08ddff00$@com' \
    --to=jsloan@diag.com \
    --cc=buildroot@busybox.net \
    /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.