RE: [avr-gcc-list] jump_to_null question

[Eric Weddington]

The OP pointed out the same thing as Eric P. and Bernard both point out. He
told me in a private response (that I think he forgot to CC the list).

Eric Weddington

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Eric Pasquier
> Sent: Thursday, May 24, 2007 9:10 AM
> Cc: address@hidden
> Subject: Re: [avr-gcc-list] jump_to_null question
> 
> "I don't see how you can avoid jumping to 0x0 when a 
> bootloader ends its 
> work"
> 
> Check MCUCSR ?
> 
> Eric Pasquier
> 
> ----- Original Message ----- 
> From: "Bernard Fouché" <address@hidden>
> To: "Eric Weddington" <address@hidden>
> Cc: <address@hidden>
> Sent: Thursday, May 24, 2007 4:40 PM
> Subject: Re: [avr-gcc-list] jump_to_null question
> 
> 
> > Eric Weddington wrote:
> >>  2. The best way to reset the AVR, is not by jumping to 
> the reset vector.
> >> When you do that, some of the registers may be left in a 
> state that is 
> >> not
> >> the default. The best way to reset is to enable the 
> watchdog timer on the
> >> shortest time-out, go into an infinite loop, and let the 
> watchdog reset 
> >> the
> >> AVR. Depending on which AVR you are using, you will have 
> to turn off the
> >> watchdog timer after reset, with code in the .init3 
> section, for example.
> >>
> >>
> > In this case his bootloader will start again. I don't see 
> how you can 
> > avoid jumping to 0x0 when a bootloader ends its work.
> >
> > Bernard