Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

Re: [AVR-Chat] why unintialized stack errors?

Re: [AVR-Chat] why unintialized stack errors?

2007-01-02 by John Samperi

At 09:32 AM 3/01/2007, you wrote:
>the .eseg directive should result in
>this table data being pulled into EEprom

Correct! Except that the reset rjmp points to it and Start will
evaluate to 0x0000 being the first byte in EEPROM therefore rjmp
will jump to 0x0000 or to itself at infinitum (oh I spoke Latin :) )

>;
> > RESET:
> >   rjmp START
>
> > ; Program starts here after Reset
> > ;
> > START:
> >
> >
> >    .eseg


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
********************************************************

Re: [AVR-Chat] why unintialized stack errors?

2007-01-02 by David VanHorn

>
>
> Correct! Except that the reset rjmp points to it and Start will
> evaluate to 0x0000 being the first byte in EEPROM therefore rjmp
> will jump to 0x0000 or to itself at infinitum (oh I spoke Latin :) )


As written in the first message, I disagree.
I use this form in my own programs, with the reset vector jumping past the
vector table, and ISRs, and other stuff, to "Init", which falls through to
"main".

"Start" is in front of the .eseg directive, and should evaluate to the same
address as "Begin"
A look at the .lst file will tell, but that's what should be happening.


[Non-text portions of this message have been removed]

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.