Hi Bruce, I don't think it can be the "Pin Change Interrupt" sources. The firmware works on Ver1 boards. I don't change a thing when I hook up the boards to the Dragon. The same code is used for both versions. Ver1 works while Ver2 hangs at PORTB.0 = 1. Thanks, Richard Cooke --- In AVR-Chat@yahoogroups.com, Bruce Parham <obparham@...> wrote: > > Richard Cooke wrote: > > > Hi Folks, > > > > I've run into a problem that has me pulling out my hair. I'm using > > the AVR Dragon and the latest version of AVR Studio to debug my > > boards. I have two versions let's all them Ver1 and Ver2. The only > > difference being the RF matching network. Ver1 works fine. If I use > > the exact same firmware that works in Ver1 in Ver2 it will hang at a > > spot that makes no sense. > > > > After working for quite a while, I discovered the offending code as > > "PORTB.0 = 1;". All I am doing is setting the PORTB.0 pin high but as > > I single step through the code it will hang right here. So, the code > > snippet looks like: > > > > PORTD.7 = 1; <-- this works > > PORTB.0 = 1; <-- hangs here > > > > If I reverse the two lines to this: > > > > PORTB.0 = 1; <-- now this works > > PORTD.7 = 1; <-- debugger hangs here > > > > > > This strange behavior doesn't occur with the Ver1 board, only with > > Ver2. I've checked (multiple times) to make sure that there are no > > shorts. I've checked the bare boards and everything looks good. > > > > Does anybody have any ideas what I should try next? > > > > Thanks, > > > > Richard Cooke > > Lake Forest, CA USA > > > > Hi Richard, > > Both of those pins are listed as "Pin Change Interrupt" sources. Have they > somehow become unmasked? > > Bruce >
Message
Re: Debugging a ATmega48V - what's going on?
2007-11-12 by Richard Cooke
Attachments
- No local attachments were found for this message.