All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasili Galka <vvv444@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Recommended AVR32 toolchain
Date: Thu, 21 Aug 2014 13:53:38 +0300	[thread overview]
Message-ID: <CA+gZxsMQTjvXm11MpxLyBNz+0oRZyu1-p9vOVKs2TTjXUwGQHA@mail.gmail.com> (raw)
In-Reply-To: <53F5072F.1040208@googlemail.com>

Hi Andreas,

The toolchain from kernel.org indeed works fine.

Thank you very much for your help!

Best regards,
Vasili

On Wed, Aug 20, 2014 at 11:38 PM, Andreas Bie?mann
<andreas.devel@googlemail.com> wrote:
> Hi Vasili,
>
> On 20.08.14 18:10, Vasili Galka wrote:
>> Hi Andreas,
>>
>> I'm trying to verify the correct build of all AVR32 boards. What is
>> the recommended toolchain to use?
>
> it depends, at least you should use a avr32-linux toolchain. The
> avr32-elf one builds u-boot fine but has some runtime flaws. For compile
> testing this would be Ok.
>
>> I tried the one that comes with Ubuntu:
>>
>> sudo apt-get install gcc-avr binutils-avr gdb-avr avr-libc avrdude
>
> Ouch, that is wrong. You got the avr 8-bit variant. There is no mainline
> avr32 gcc support!
> The patches come from atmel [1] and are for an outdated gcc version
> unfortunately.
> You cold use the pre-compiled avr32 toolchain provided by kernel.org
> [2]. I personally have never run this toolchain but others said it works.
>
> Best regards
>
> Andreas Bie?mann
>
> [1] http://distribute.atmel.no/tools/opensource/
> [2] https://www.kernel.org/pub/tools/crosstool/

      reply	other threads:[~2014-08-21 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 16:10 [U-Boot] Recommended AVR32 toolchain Vasili Galka
2014-08-20 20:38 ` Andreas Bießmann
2014-08-21 10:53   ` Vasili Galka [this message]

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=CA+gZxsMQTjvXm11MpxLyBNz+0oRZyu1-p9vOVKs2TTjXUwGQHA@mail.gmail.com \
    --to=vvv444@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.