Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <fivemiletom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Arm / buildroot / kernel issue: init crashes?
Date: Mon, 18 Jun 2007 17:22:12 -0700	[thread overview]
Message-ID: <467721B4.3090906@gmail.com> (raw)
In-Reply-To: <6311fe0b0706161136q30c4ca11qbd6ac0e50baf66d8@mail.gmail.com>

Rex Ashbaugh wrote:
> Go right to the problem,
> make a text dump of your init program and see what the undefined 
> instruction is (at pc=00008c60).

Good idea: instruction is 0xe12fff38, blx, which my ARM920T ARMv4T does 
not support.
Have tried both "generic_arm" and "ARM920T" as mentioned, but I guess 
will go over all buildroot and nested options again.

Thanks.

> 
> 
> -Rex
> 
> 
> 
> On 6/16/07, * Rex Ashbaugh* <rexonator@gmail.com 
> <mailto:rexonator@gmail.com>> wrote:
> 
>     Go right to the problem,
>     make a text dump of your init program and see what the undefined
>     instruction is (at pc=00008c60).
> 
> 
>     -Rex
> 
> 
> 
> 
>     On 6/15/07, * Tom* <fivemiletom@gmail.com
>     <mailto:fivemiletom@gmail.com>> wrote:
> 
>         Hello,
> 
>         I have built an ARM toolchain via buildroot. I am building my kernel
>         2.6.21.1 <http://2.6.21.1> successfully with this toolchain, it
>         boots up OK.
> 
>         I am compiling a very simple init program (hello world & endless
>         loop)
>         'arm-linux-uclibcgnueabi-gcc -static init.c -o init'. It crashes
>         "init
>         (1): undefined instruction: pc=00008c60"
> 
>         Both buildroot and kernel are using EABI. I presume that the headers
>         2.6.21.1 <http://2.6.21.1> (my kernel) and 2.6.20.4
>         <http://2.6.20.4> (buildroot) are close enough in
>         respect to system calls.
>         I tried toolchain and kernel both with and without SOFT_FLOAT(after
>         reading a thread "Problem with EABI"), but same crash either
>         way. Tried
>         both generic_arm and ARM920T.
> 
>         I suspect my options for buildroot / uclibc, but don't know what
>         exactly
>         to look for, anyone any ideas?
> 
>         Thanks
>         Tom
>         _______________________________________________
>         buildroot mailing list
>         buildroot at uclibc.org <mailto:buildroot@uclibc.org>
>         http://busybox.net/mailman/listinfo/buildroot
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2007-06-19  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  8:10 [Buildroot] Arm / buildroot / kernel issue: init crashes? Tom
     [not found] ` <6311fe0b0706161040h626e4d85x227e490373938537@mail.gmail.com>
2007-06-16 18:36   ` Rex Ashbaugh
2007-06-19  0:22     ` Tom [this message]
2007-06-19 23:26       ` Tom
2007-06-20  0:03         ` Rex Ashbaugh
     [not found]         ` <6311fe0b0706191700g54364c24s3440e62e45eec187@mail.gmail.com>
2007-06-20  7:42           ` Tom
2007-06-20  7:49           ` Tom
2007-06-27  0:12             ` Tom

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=467721B4.3090906@gmail.com \
    --to=fivemiletom@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox