RE: [avr-gcc-list] WinAvr 20081205 and Xmega AVR

2009-02-06 Thread larry barello
-list@nongnu.org; Anatoly Sokolov Subject: RE: [avr-gcc-list] WinAvr 20081205 and Xmega AVR > -Original Message- > From: > avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org > [mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu. > org] On Behalf Of

RE: [avr-gcc-list] WinAvr 20081205 and Xmega AVR

2009-02-06 Thread Weddington, Eric
g > Subject: [avr-gcc-list] WinAvr 20081205 and Xmega AVR > > So what should really happen is: > > > > return ( AS2 > (out,__SP_L__,%B1) CR_TAB > > + AS2 > (out,__SP_H_

RE: [avr-gcc-list] WinAvr 20081205 and Xmega AVR

2009-02-05 Thread larry barello
I just got email from Atmel verifying that the two instruction sequence for updating SP is correct. -Original Message- From: Anatoly Sokolov [mailto:ae...@post.ru] Sent: Wednesday, February 04, 2009 11:27 AM To: larry barello; avr-gcc-list@nongnu.org Subject: Re: [avr-gcc-list] WinAvr

Re: [avr-gcc-list] WinAvr 20081205 and Xmega AVR

2009-02-04 Thread Anatoly Sokolov
Hi. In fact, the XMEGA A manual, page9, section 3.8 states that NOTHING is needed other than writing the SPL first (writing SPL disables interrupts for four cycles). Wow Thanks for catch it! I wanted to see it in the new core and upset when not found. In ATxmega A MANUAL revision A th

[avr-gcc-list] WinAvr 20081205 and Xmega AVR

2009-02-04 Thread larry barello
The Xmega support involves a convoluted mechanism to update the SP after a var-arg procedure call. return (AS2 (mov,__tmp_reg__,r24) CR_TAB + AS2 (ldi,r24,0xD8) CR_TAB +