From: Michel Benoit <murpme@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] building ARM toolchain with nofpu
Date: Mon, 5 Feb 2007 10:26:55 +0100 [thread overview]
Message-ID: <c88e466f0702050126p997c485g97a29bc99d5d7348@mail.gmail.com> (raw)
In-Reply-To: <007e01c74652$d9c41f40$01c4af0a@atmel.com>
Hej Ulf
I don't think that the NWFPE stuff is linked into the u-boot code
automatically. The build instructions in the u-boot tree are very
explicit about using -msoft-float.
When I build u-boot with a buildroot toolchain based on gcc 3.4.3 with
no fpu support the bootloader works as it should.
When I build u-boot with fpu support in the toolchain and I remove the
-msfot-float option according to your suggestion, the bootloader
crashes almost immediately. It may be related to NAND access but
could also be due to the printouts (printf can use float ops).
On 2/1/07, Ulf Samuelsson <ulf@atmel.com> wrote:
> Michel Benoit wrote:
> > Thanks that worked!
> >
> > On 2/1/07, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote:
> >> Hello all!
> >> Michel, Carl.
> >>
> >> On Thursday 01 February 2007 010, Michel Benoit wrote:
> >>> I'm trying to build a toolchain with soft floating point enabled for
> >>> ARM arm26t target platform. I'm doing this in order to build u-boot
> >>> for my target.
> >> [--SNIP--]
>
> You can build u-boot with a NWFPE compiler
> if you just remove the "-msoft-float" from cpu/arm926ejs/config.mk and
> from cpu/arm926ejs/at91sam926x/config.mk
> That is what I do in my buildroot (That part yet to be submitted).
>
>
> Best Regards,
> Ulf Samuelsson
> ulf at atmel.com
> GSM: +46 (706) 22 44 57
> Tel: +46 (8) 441 54 22
> Fax: +46 (8) 441 54 29
> Mail: Box 2033 174 02 Sundbyberg
> Visit: Kavalleriv?gen 24
> 174 58 Sundbyberg'
> Sweden
>
>
next prev parent reply other threads:[~2007-02-05 9:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 0:09 [Buildroot] building ARM toolchain with nofpu Michel Benoit
2007-02-01 19:15 ` Yann E. MORIN
2007-02-01 20:51 ` Michel Benoit
2007-02-01 22:46 ` Ulf Samuelsson
2007-02-05 9:26 ` Michel Benoit [this message]
2007-02-07 20:09 ` James Newell
2007-02-07 20:24 ` Yann E. MORIN
2007-02-07 20:36 ` Yann E. MORIN
2007-02-08 7:50 ` carl zhu
2007-02-08 14:26 ` James Newell
2007-02-09 1:41 ` James Newell
2007-02-09 13:10 ` Bernhard Fischer
2007-03-01 10:01 ` carl zhu
2007-02-08 17:25 ` Bernhard Fischer
2007-02-08 17:33 ` Yann E. MORIN
2007-02-08 17:40 ` Bernhard Fischer
2007-02-09 14:10 James Newell
2007-02-09 14:29 ` Bernhard Fischer
2007-02-09 17:57 ` Yann E. MORIN
2007-02-09 18:21 ` Bernhard Fischer
2007-02-09 18:48 ` Yann E. MORIN
2007-02-09 14:51 James Newell
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=c88e466f0702050126p997c485g97a29bc99d5d7348@mail.gmail.com \
--to=murpme@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 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.