Dave
checking for avr-strip... no
checking for strip... strip
checking for avr-gcc... no
...
checking for avr-as... no
checking for as... as
checking for avr-ranlib... no
checking for ranlib... ranlib
checking for avr-ar... no
checking for ar... ar
configure: error: Wrong C compiler
Advait,
lets try to answer your question:
void try1(void){ char a[20];- Request for 20
bytes on the stackunsigned
char i;
for(i=0;i20;i++) a[i] =
com1_msgbuf[i];}the assembly for this function is this: (from the
.lss file)
void
try1(void){ 5a40: cf
93
push
Hi,
in the middle of a running project I received from make the very
expressive error message:
.dep/blcd.o.d:1: *** multiple target patterns. Stop.
I'm using WinAVR + Cygwin together. My Unix tools are from Cygwin
while the avr-gcc comes from WinAVR. That works fine except for avr-gdb
which I'm
Simon,
the easiest way to find out how gcc would call a function, is to write a
small C-programm calling the function and let it compile only to
assembler by a make testprog.s, while testprog.c is the source. There
you will find all details without additonal reading. You should set the
Hi,
while the size of my programm shrunk after adding some cases I looked to the
list file. I saw that a switch was converted from a structured if-then-else to
a table jump (compiled with -Os). That's okay. A detailed analyses points to a
gcc problem: I use a volatile variable. If a samll
Hi,
-Original Message-
From: Eric Weddington [mailto:[EMAIL PROTECTED]
Sent: Monday, March 26, 2007 2:46 PM
To: Schwichtenberg, Knut; avr-gcc-list@nongnu.org
Subject: RE: [avr-gcc-list] Inconsisten behaviour of switch statement
The compiler has heuristics that decide when
Hi,
-Original Message-
From: Joerg Wunsch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 9:51 AM
To: avr-gcc-list@nongnu.org
Cc: Schwichtenberg, Knut
Subject: Re: [avr-gcc-list] Inconsisten behaviour of switch statement
Yes, but this is technically OK. The volatile
Hi,
I know I could set the length of a segment in the linker script. Is
there a chance to set it in the makefile? While the linker scripts for
the avr5 are able to handle the M128-memory my M32 run out of memory
without any comment - especially if I add an additional bootloader.
Cheers
Knut
Larry,
I have not tried, but at 31.03.06 Uwe Fechner came around here with the
same problem. He solved the problem and on his last email he showed his
makefile which puts the CRC behind the last used byte of code.
# Create final output files (.hex, .eep) from ELF output file.
%.hex: %.elf
Gre7g,
-Original Message-
From:
[EMAIL PROTECTED]
g
[mailto:[EMAIL PROTECTED]
ongnu.org] On Behalf Of Gre7g Luterman
Sent: Tuesday, May 08, 2007 8:29 PM
To: AVR-GCC-list@nongnu.org
Subject: [avr-gcc-list] Linker error with gcc WinAVR
Why on Earth does it think .update2_app
Hi,
is there a cpp-macro / definition to distiguish between the different
gcc platform implementations? I read the cpp-man describing __xxx__
macros like __GNUC__ and did not find any. But there may be one not
officially documented. At least I want to know within my source code if
the file is
:[EMAIL PROTECTED]
Sent: Tuesday, July 31, 2007 12:04 PM
To: avr-gcc-list@nongnu.org
Cc: Schwichtenberg, Knut
Subject: Re: [avr-gcc-list] GCC platform specific identification?
$ cpp -dM /dev/null
With windows replace /dev/null with NUL. You might also have
to append the
same command line
Hi David,
if you use older AVRs and do not wonder about some serious looking
messages at compile time then you could use VMLAB - which seems to be
out of service. It provides the ability to add some predefined
peripherals like LCD, keyboard, analogue inputs and also you can
simulated 2 devices at
Klaus,
is simulavrxx properly running under Cygwin? I thought it was a 'nix
only application?
Knut
-Original Message-
From:
[EMAIL PROTECTED]
g
[mailto:[EMAIL PROTECTED]
ongnu.org] On Behalf Of Klaus Rudolph
Sent: Thursday, August 09, 2007 8:24 AM
To: David Carr;
Yannick,
and here is another solution: Forget the bootloader section. Use the
text section instead. Now if the object files are created rename the the
section in the makefile.
Makefile snipet example:
%.o : %.c
@echo
@echo $(MSG_COMPILING) $
$(CC) -c $(CFLAGS) $ -o $@
cp $@ $*_text.o
On Friday, December 07, 2007 5:24 PM, David Kelly wrote:
The compiler won't read PINB using the above.
In general on AVR when one reads PORTB one reads the output latchs, in
other words the last value written. On other CPU's this same
action may
read the input buffers. AVR provids PIN
Ruud,
it looks that you use a structure to define your high and low byte. Why
don't you define a union covering high and low byte structure and a 16
bit value? Gcc knows how to handle that and there is no need for
shifting. I use this very often and if your CPU support 16 bit loads gcc
uses them.
Dave,
you are using the avr-gcc to pass the parameter to the linker. Did you
try to use the linker directly with
avr-ld --script=avr5.x --defsym=__libdatareserve=0x4 -o user user.o
bootlibentries.o
I'm not sure if the command line is okay :-(.
Knut
-Original Message-
From:
[EMAIL
I'm aware of several AVR simulator running on different OS.
VMLAB, AVRStudio, avrora, simulavr* and there was one mentioned here specially
developped for the gcc regression tests. Could anyone forward the URL for this
simulator please.
Thanks,
Knut
Thanks for the fast reply
Knut
-Original Message-
From: Wouter van Gulik [mailto:avrm...@xs4all.nl]
Sent: Thursday, April 02, 2009 8:49 AM
To: Schwichtenberg, Knut
Cc: avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list] AVR simulators
Schwichtenberg, Knut schreef:
I'm aware
The increase in size was also subject for other gcc versions. Often the
following gcc comand-line swichtes were proposed:
-fno-inline-small-function
-fno-split-wide-types
-fno-move-loop-invariants
-
Additionally Larry Barello provided the following
21 matches
Mail list logo