[Buildroot] Buildroot for AT91RM9200-EK?
J. L. Sloan
jsloan at diag.com
Tue Jul 29 23:28:58 UTC 2008
Just rebuilt everything from scratch (starting from svn co) for EABI (and
verified with readelf -h against both vmlinux and busybox for "Version4
EABI") with exactly the same result. The kernel is build with EABI and with
OABI compat. Padzero/clear_user goes south trying to load /init.
#0 0xc00f920c in __clear_user ()
#1 0xc00aa9ec in padzero (elf_bss=665549) at include/asm/uaccess.h:420
#2 0xc00ab8a8 in load_elf_binary (bprm=0xc1c25b00, regs=0xc1c19f00)
#3 0xc0082700 in search_binary_handler (bprm=0xc1c25b00, regs=0xc1c19f00)
#4 0xc00837e4 in do_execve (filename=dwarf2_read_address: Corrupted DWARF
) at fs/exec.c:1339
#5 0xc0025928 in kernel_execve (filename=0xc022fea0 "/init",
envp=0xc039a168) at arch/arm/kernel/sys_arm.c:288
#6 0xc0022278 in run_init_process (
init_filename=0xa27cd <Address 0xa27cd out of bounds>) at
#7 0xc00222e4 in init_post () at init/main.c:784
#8 0xc0008900 in kernel_init (unused=<value optimized out>) at
#9 0xc0034928 in sys_waitid (which=<value optimized out>, upid=2099,
infop=0x0, options=0, ru=0x0) at kernel/exit.c:1613 Backtrace stopped:
previous frame inner to this frame (corrupt stack?)
Again, thanks for any pointers (so to speak).
<http://www.diag.com/navigation/metadata/jsloan.html> John Sloan
<mailto:jsloan at diag.com> jsloan at diag.com <http://www.diag.com/>
Digital Aggregates Corporation
+1 303 489 5178 (Mobile)
1&iwloc=addr&om=1> Arvada Colorado 80001-0587 USA
+1 303 940 9064 (Office) <http://www.diag.com/> www.diag.com
From: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org] On
Behalf Of J. L. Sloan
Sent: Tuesday, July 29, 2008 4:23 PM
To: buildroot at uclibc.org
Subject: [Buildroot] Buildroot for AT91RM9200-EK?
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 18.104.22.168 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>
jsloan at diag.com Digital Aggregates Corporation
+1 303 489 5178 (Mobile) Arvada
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...
More information about the buildroot