Re: [avr-gcc-list] JTAG ICE Problem (Off Topic)

[Ian Caddy]

Hi,

We are still doing our first AtMega128 project, but this has happened to 
me on different micros before.

Have you guys enabled the watchdog timer in the processors.  On some 
processors this causes a watchdog reset if you don't keep executing the 
code, and once a reset occurs, the device does not think it is under BDM 
any more.

I can not say for sure that this is happening, but we have no problems 
debugging on the M128 part using GDB, but I have made sure the watchdog 
is disabled, at least while we are debugging.

I hope this helps.

Ian Caddy


Brett Abbott wrote:

> Hi
>
> We also have the same symptoms/issue using AtMega128 and Studio 4.06 so 
> I suspect your board is probably ok.  Unfortunately I have no answer to 
> this other than dont wait too long between steps.....
>
> Regards
> Brett
>
> Date: Mon, 18 Aug 2003 15:07:03 -0400
> From: James Dabbs <address@hidden>
> To: avr <address@hidden>
> Subject: [avr-gcc-list] JTAG ICE Problem (Off Topic)
> Message-ID: <address@hidden>
> Content-Type: text/plain
> MIME-Version: 1.0
> Precedence: list
> Message: 2
>
> This has turned out not to be a GDB problem, but I had a note ready to go..
>
> I am having trouble with our JTAG ICE.  We are using it with our board,
> based on a 16MHz ATMega169.  Basically, the ICE "looses touch" with the 
> AVR.
> When I break, if I look at registers or examine breakpoints, the 
> application
> code just continues running and all of the variables and registers shown in
> the debugger appear as 0xFF.  The software runs *properly* in this state,
> just without any connection to the debugger, which has to be restarted to
> regain control.  This happens with an assembler project under AVRStudio
> 4.07.  If I move quickly, I can step through code, but as soon as I pause
> for more than a couple of seconds, the application code starts running and
> leaves the ICE behind.  The ICE connection has been verified, the 
> voltage is
> within 2% of 5V, and the oscillator is 16.0000MHz.  I believe this is 
> either
> an electrical problem with our board (although it is an infuriatingly 
> simple
> PCB) or possibly a problem with 16MHz parts.  Has any one had similar
> troubles?
>
>
>
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list