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.Message
strange -problems?
2006-12-30 by Thomas Keller