public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot not working on Atmel ATNGW100 (AVR32)
Date: Tue, 11 Oct 2011 15:37:29 +0200	[thread overview]
Message-ID: <4E944699.3020801@stackframe.org> (raw)
In-Reply-To: <4E944477.1040801@gmail.com>

On 10/11/2011 03:28 PM, Andreas Bie?mann wrote:
> Dear Sven,
>
> Am Di 11 Okt 2011 15:23:00 CEST schrieb Andreas Bie?mann:
>> Dear Sven,
>>
>> Am 11.10.2011 15:06, schrieb Sven Schnelle:
> <snip>
>
>>> Does anyone also still have this problem? Or does anyone have a
>>> pointer for me before i start digging into that problem?
>> I do not have any pointers right now but really interested in your
>> investigations.
> One thing, we had much truble with our toolchain. Which toolchain do you
> use? Could you provide me (off list) a u-boot.bin for atstk1002 or
> grasshopper?

I'm using the atmel avr32 toolchain 3.2.3, which contains avr32-gcc 
4.4.3 and binutils 2.20.1.
I can't try the older atmel toolchain due to missing dependencies for my 
OS (Debian).

i've just recognized that ld complains during built:

avr32-ld:built in linker script:15: warning: memory region `FLASH' not 
declared
avr32-ld:built in linker script:69: warning: memory region `CPUSRAM' not 
declared

not sure if this is related to the problem i'm seeing.

Thanks
Sven

  reply	other threads:[~2011-10-11 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 13:06 [U-Boot] u-boot not working on Atmel ATNGW100 (AVR32) Sven Schnelle
2011-10-11 13:12 ` Sven Schnelle
2011-10-11 13:23 ` Andreas Bießmann
2011-10-11 13:28   ` Andreas Bießmann
2011-10-11 13:37     ` Sven Schnelle [this message]
2011-10-11 13:52       ` Andreas Bießmann
2011-10-11 16:15         ` Sven Schnelle
2011-10-12  8:05           ` Andreas Bießmann
2011-10-11 14:05     ` Andreas Bießmann

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=4E944699.3020801@stackframe.org \
    --to=svens@stackframe.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox