AVR-Chat

Dave and John,

I'm developing an automatic ass kicking machine right now, to be used 
when I do something that's really dumb.  The first copy is mine.  Shall 
I sign you up for one?

The biggest problem to date has been finding a size 11EEE combat boot 
like my Drill Instructor in Bootcamp had.


REB



David VanHorn wrote:

>>What is PHYSICALLY there? Have you loaded the code into the simulator
>>or used other debugging tools to have a look at that location?
>>    
>>
>
>Yup, in the sim, $FFFF is what's at that location, but the RCALL isn't
>calling that location.
>
>  
>
>>Included the wrong interrupt vectors (SOMEONE did this a while ago)?
>>No memory at 0x00f020? Which chip are you using?
>>    
>>
>
>M128, it shouldn't be ANYWHERE near there though..
>In the disasm, the call reads as rcall PC+0268
>PC at this moment is 00001B5, so that should call   0041D
>Reading the .lst file, the routine I want is conveinently located at 0041D
>so I single step, and...
>
>I'm at 0000F020 with an opcode of $FFFF
>
>
>
>  
>
>>You do know that it will be something silly and you will kick
>>yourself when you find it :-)
>>    
>>
>
>Yeah.. I'm taking yoga now, so I'm getting better at that.
>
>  
>
>>A few days ago I spend about half an hour trying to figure out
>>why my Dragon was acting funny, I could not read porta no matter
>>what I did....well it turned out that I had changed debugging
>>mode from Dragon to simulator and what I was looking was not
>>the physical port at all.... :-[
>>    
>>
>
>Yup, that happens.
>And it's probably something like that, since this is a new install,
>and "cold start" of a project.
>  
>