Possiblythe WiKi is not quite up to
date.
Please correct me, butit wasmy impression that
the general opinion was thatthe 4-byte alignment method will be less
efficient and more difficult to implement.
1.) IMO the fastest way willbe to insert jump stubs
to the function entry point in the
Haase Bjoern (PT-BEU/EMT) * wrote:
1.) IMO the fastest way will be to insert jump stubs to the function
entry point in the lower 128k as part of the prologues
Will this work when one wants to write a bootloader ?
Bernard
___
AVR-GCC-list
At which address does the bootloader code end up?
-Ursprüngliche Nachricht-
Von: Bernard Fouché [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 4. Oktober 2005 10:32
An: Haase Bjoern (PT-BEU/EMT) *
Cc: Martijn van Balen; avr-gcc-list@nongnu.org
Betreff: Re: AW: [avr-gcc-list] Using current
After reading your message I conclude that you will probably not be having any
problem unless that you are planing to use pointers to functions in your
bootloader code. The jump stubs will be used *only* in case that you are using
a function pointer because this way, we could stick to 2-byte
Haase Bjoern (PT-BEU/EMT) * wrote:
At which address does the bootloader code end up?
Always at the end of the flash... from 4 to 32 pages of 256 bytes
reserved from the end.
Now one may need more than 8K bytes of program size for a complex
bootloader and so extend its size downward from
Haase Bjoern (PT-BEU/EMT) * wrote:
After reading your message I conclude that you will probably not be having any
problem unless that you are planing to use pointers to functions in your
bootloader code. The jump stubs will be used *only* in case that you are using
a function pointer because
IMO: NO. Not within the next half year.
Bjoern.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Lars Noschinski
Gesendet: Dienstag, 4. Oktober 2005 14:29
An: avr-gcc-list@nongnu.org
Betreff: [avr-gcc-list] Interrupt overhead again
Hello!
Haase Bjoern (PT-BEU/EMT) * schrieb:
Possibly the WiKi is not quite up to date.
Well, someone restored an old version, I restored the must recent
version, it should be uptodate now.
Please correct me, but it was my impression that the general opinion
was that the 4-byte alignment method
It is not returning MOB_RX_COMPLETED, because the RXEN doesn't set.
I have a sender at90can, wich I am almost sure that works
(osciloscope), and the sender and the receiver are at the same
frequency, same baudrate and same everything...
I think that the problem is that I'm not using the can
Timothy Smith [EMAIL PROTECTED] wrote:
my apologes for not giving this to start with
%avr-gcc -g -mmcu=atmega32 -Os -c BarGimp.c
%avr-gcc -g -o BarGimp.out BarGimp.o
Make this:
avr-gcc -mmcu=atmega32 -o BarGimp.out BarGimp.o
and it will work. The linker needs to know as well which CPU
Hi every body, Im experimenting some problems writing to a flash page in my
ATMEGA8, does some one know any good source to solve this or any tutorial on
how to write and read from the flas memory.
I include the compiler output when I try to use the bootloader functions
thanks
JAJM
#include
http://better-scm.berlios.de/comparison/comparison.html
--
A J Erasmus
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
On Wednesday 05 October 2005 10:37, wbounce wrote:
avr-gcc (GCC) 3.4.1
I must be using an old version
avr-gcc (GCC) 3.4.1
I can not find #include sys/types.h
This is the command line I am using
Oops, braino, I forgot to build it with avr-gcc :)
Try inttypes.h instead of sys/types.h.
--
13 matches
Mail list logo
