AVR-Chat

At 08:14 AM 17/06/2007, you wrote:
>M128, it shouldn't be ANYWHERE near there though..

Is your code LESS than 64K? Or are you passing the 64K boundary?
I have never gone past that so don't really know what lies beyond
that.

>In the disasm, the call reads as rcall PC+0268

Have you tried CALL just in case? Maybe some wraparound? I know I'm
clutching at straws...forgetting to pop something off the stack and
the pc gets messed up? Thinking aloud sometimes helps even if the questions
are silly and obvious..


Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 15/06/2007 11:31 AM

On 6/16/07, John Samperi <samperi@ampertronics.com.au> wrote:
> At 08:14 AM 17/06/2007, you wrote:
> >M128, it shouldn't be ANYWHERE near there though..
>
> Is your code LESS than 64K? Or are you passing the 64K boundary?
> I have never gone past that so don't really know what lies beyond
> that.

WAY less. 3064 words

>
> >In the disasm, the call reads as rcall PC+0268
>
> Have you tried CALL just in case?

Yup, same thing.

>Maybe some wraparound? I know I'm
> clutching at straws...forgetting to pop something off the stack and
> the pc gets messed up? Thinking aloud sometimes helps even if the questions
> are silly and obvious..

At this point (starting the failing call), the SP is at 10FF, which is correct.
It's on the call in, where everything fails, I don't even get to the return.