AVR-Chat

>
> I have only a generic response to make here.  To paraphrase Sherlock
> Holmes a bit:
> 
> "If your facts make no sense, examine your assumptions, one or more of
> them is incorrect."
> 
> So, check your assumptions, even the most trivial could cause you this
> kind of headache.
> 
> DLC
> --
> Dennis Clark
> 
> > 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
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

>
> On Mon, Nov 12, 2007 at 08:02:13PM -0000, Richard Cooke wrote:
> > Dennis,
> > 
> > I've been trying to come up with assumptions to test.  The thing that
> > really is frustrating is the firmware works on one board but not the
> > new ones so I think that the firmware can be eliminated as the source
> > of the error.
> 
> New boards using new chips? Do you have any new old stock from the prior
> batch of boards? Sometimes chips change. Search the errata notices at
> Atmel.com.
> 
> -- 
> David Kelly N4HHE, dkelly@...
> ========================================================================
> Whom computers would destroy, they must first drive mad.
>

> 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
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>