AVR-Chat

I stepped through the code....it is doing something really strange.  
When it gets to the last instruction (out   TCNT0, r31 which is at 
address 0x16) it jumps to 0x17 (which is one byte past the last 
instruction in the code, per the mapper) issues an "unsupported 
instruction:  muls", then jumps to 0x18 and issues "unsupported 
instruction:  mulsu" then jumps to 0x01f7 and issue an "invalid opcode: 
0xffff" error, then just kleeps repeaing that...the trace using F11 
doesn't show anything happening at all.


    Flamboozled.

Perhaps you should put in this at the end:

Done:
	Rjmp	Done

To prevent the CPU from running on like it want's to.

-----Original Message-----
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of Thomas Keller
Sent: Saturday, December 30, 2006 3:41 PM
To: avr-chat@yahoogroups.com
Subject: [AVR-Chat] strange -problems?

I stepped through the code....it is doing something really strange.  
When it gets to the last instruction (out   TCNT0, r31 which is at 
address 0x16) it jumps to 0x17 (which is one byte past the last 
instruction in the code, per the mapper) issues an "unsupported 
instruction:  muls", then jumps to 0x18 and issues "unsupported 
instruction:  mulsu" then jumps to 0x01f7 and issue an "invalid opcode: 
0xffff" error, then just kleeps repeaing that...the trace using F11 
doesn't show anything happening at all.


    Flamboozled.


 
Yahoo! Groups Links

At 05:41 PM 12/30/2006 -0600, Thomas Keller wrote:
>I stepped through the code....it is doing something really strange.
>When it gets to the last instruction (out   TCNT0, r31 which is at
>address 0x16) it jumps to 0x17 (which is one byte past the last
>instruction in the code, per the mapper)

Well what is there to prevent it from doing that?

Robert

http://www.aeolusdevelopment.com/

 From the Divided by a Common Language File (Edited to protect the guilty)
ME - "I'd like to get Price and delivery for connector Part # XXXXX"
Dist./Rep - "$X.XX Lead time 37 days"
ME - "Anything we can do about lead time?  37 days seems a bit high."
Dist./Rep - "that is the lead time given because our stock is live.... we 
currently have stock."