Attached is some simple code and makefile that will reproduce the issue for
XMEGA and MEGA AVRs
http://old.nabble.com/file/p29424434/Main.c Main.c
http://old.nabble.com/file/p29424434/Makefile Makefile
Joerg Wunsch wrote:
>
> As DarkDragon wrote:
>
>> I initially submitted this bug under
As DarkDragon wrote:
> Now that I'm checking all my applications, I see that my XMEGA
> applications all have this problem with both the AVR toolchain AND
> WinAVR2010.
Btw., in that case, filing your bug report to the Atmel folks was OK.
The Xmega patch did not get its way into the upstream GCC
Yes even with HTTPS, our proxy flags the site as "Downloadable Content" and
blocks it.
Now that I'm checking all my applications, I see that my XMEGA applications
all have this problem with both the AVR toolchain AND WinAVR2010.
With this problem existing since at least January, can I really be
As DarkDragon wrote:
> I initially submitted this bug under GCC bugzilla, but upon further
> investigation, it looks like this comes from AVR-LibC as I can take
> the LibC from the toolchain, insert it in WinAVR2010 and get the
> same stack prologue code.
Please submit some code (and compilation
With the beta AVR toolchain 3.0.0.207, the prologue for functions using a
frame
has changed and is now causing stack corruption when an interrupt fires.
Take
for example a function which needs 5 bytes of frame. This is how the frame
is
setup in the function prologue:
Under WinAVR2010:
a30: df 93