From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcmVhcyBCaWXDn21hbm4=?= Date: Tue, 11 Oct 2011 15:52:41 +0200 Subject: [U-Boot] u-boot not working on Atmel ATNGW100 (AVR32) In-Reply-To: <4E944699.3020801@stackframe.org> References: <4E943F3B.8060404@stackframe.org> <4E944334.9060704@gmail.com> <4E944477.1040801@gmail.com> <4E944699.3020801@stackframe.org> Message-ID: <4E944A29.8090204@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Sven, Am Di 11 Okt 2011 15:37:29 CEST schrieb Sven Schnelle: > 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: >> >> >>>> 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). We use a self-build toolchain from some older buildroot which has * avr32-linux-gcc (GCC) 4.2.2-atmel.1.1.3.buildroot.1-20100804 * GNU ld (GNU Binutils) 2.18.atmel.1.0.1.buildroot.1 gcc got another patch to have the build date in version string. > 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 So you do not have a *-linux-* toolchain? > not sure if this is related to the problem i'm seeing. Maybe ... I guess since I could build working binaries with my toolchain something toolchain related is going wrong. Maybe have a look for http://distribute.atmel.no/tools/opensource/avr32-gcc/ (the script should build a uclibc toolchain) to get another toolchain. I had a short look for these patches some days ago cause we are hunting another maybe toolchain related problem. AFAIK there are some different linker settings. The avr32-linux toolchain does set the processor to ap7000 (is it -m?) but the avr32-elf (which uses newlib) does not set ap7000 as default. Maybe this could be the solution for your problem. best regards Andreas Bie?mann