[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] Bizarre string problem, part 3
From: |
Joerg Wunsch |
Subject: |
Re: [avr-gcc-list] Bizarre string problem, part 3 |
Date: |
Thu, 9 Sep 2004 17:06:25 +0200 (MET DST) |
André - BOL <address@hidden> wrote:
> avr-gcc -g -mmcu=atmega32 -Wall -o t.o t.c
> avr-objcopy -j .text -O ihex t.o t.hex
First, you don't link your stuff at all, you're trying to feed a
relocatable object file into your MCU. That doesn't work.
Second, your objcopy line misses the -j .data option, which is
repsonsible for copying over the initialization data for your
initialized variables -- exactly the problem you're seeing.
If you don't fully understand all implications, why are you rolling
your own set of commands, instead of resorting to a known-to-be-good
Makefile to produce your loadable hex file?
--
J"org Wunsch Unix support engineer
Wir stellen aus! Auf der SYSTEMS 2004 vom 18.-22. Oktober in München
Halle B 3, Stand 320-206 (Partner-Stand von Sun Microsystems)
Halle B 2, Stand 605 "Die Musterfirma"
- [avr-gcc-list] Bizarre string problem, part 3, André - BOL, 2004/09/08
- Re: [avr-gcc-list] Bizarre string problem, part 3, Eric Fu, 2004/09/08
- Re: [avr-gcc-list] Bizarre string problem, part 3, Ian Caddy, 2004/09/08
- Re: [avr-gcc-list] Bizarre string problem, part 3, Richard Urwin, 2004/09/09
- Re: [avr-gcc-list] Bizarre string problem, part 3, Ian Caddy, 2004/09/09
- Re: [avr-gcc-list] Bizarre string problem, part 3,
Joerg Wunsch <=