All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] FOSDEM
Date: Thu, 22 Jan 2009 07:11:02 +0100	[thread overview]
Message-ID: <20090122071102.693fa01f@hcegtvedt> (raw)
In-Reply-To: <1232566648.11888.56.camel@elrond.atmel.com>

On Wed, 21 Jan 2009 20:37:28 +0100
Ulf Samuelsson <ulf.samuelsson@atmel.com> wrote:

<snipp>

> Maybe a few AVR32 Network Gateways as well. Checking if Atmel will
> sponsor...
> 

Check with the marketing people, it should be okay IMHO.

> They are a little difficult to use if you do not have
> a JTAG-ICE Mk II, which you worst case may need to reprogram U-Boot.
> If you are fine with the on-board U-boot that is of course not a
> problem.
> 

NGW100 ships with a preprogrammed U-Boot, so you do not need a JTAGICE
mkII, I seldom use my JTAG tool.

If you are unable to upgrade U-Boot by using the different tools[1] then
you can either use a binary U-Boot[2] or a binary FlashUpgrade[1][3].
For U-Boots v1.3.x and later you can self program the bootloader.

<snipp>

1: http://avr32linux.org/twiki/bin/view/Main/FlashUpgrade
2: http://www.atmel.no/buildroot/buildroot-bin.html
3: http://www.atmel.no/buildroot/buildroot-u-boot.html

-- 
Best regards,
Hans-Christian Egtvedt

      parent reply	other threads:[~2009-01-22  6:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 19:37 [Buildroot] FOSDEM Ulf Samuelsson
2009-01-21 20:09 ` Peter Korsgaard
2009-01-22  8:12   ` Thomas Lundquist
2009-01-29 19:13     ` Markus Heidelberg
2009-01-29 19:15       ` Peter Korsgaard
2009-01-30  8:43       ` Thomas Lundquist
2009-02-08  2:17         ` Thomas Lundquist
2009-02-09 22:29           ` Markus Heidelberg
2009-01-22  6:11 ` Hans-Christian Egtvedt [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=20090122071102.693fa01f@hcegtvedt \
    --to=hans-christian.egtvedt@atmel.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.