M68000_Users_Manual.pdf indicates that the PC of the instruction after
the illegal one will be stored on the stack. The simulator stores the PC of
the illegal instruction.

I know that there is a similar thread from 2005 indicating that Bus Error
and Address traps do the same thing (link below) and it won't be fixed.
I just wanted to document the behavior to save others some debugging
time. It didn't take me too long

http://www.easy68k.com/EASy68Kforum/vie ... hlight=bus

aaron boxer
Millogic

This one now seems a little more important than I first thought. Since the
68000 has no breakpoint instruction, debuggers may use illegal instruction
traps as a mechanism for implementing breakpoints.

In this case, knowing what PC the 68000 silicon pushes on the stack is
important for proper breakpoint behavior. Does anyone know what the
silicon does?

thanks,
Aaron Boxer
Millogic

All the 68000 debuggers I'm aware of use a TRAP instruction for breakpoint setting.

Once the breakpoint is hit the original word is replaced and the instruction can be traced before the breakpoint is set again.

You couldn't safely use an illegal instruction because it may not have been illegal across the whole family or on future parts. Not so much of a problem now of course.

Isn't ILLEGAL architecturally defined?

0100101011111100 ILLEGAL
$4AFC

According to the MC68000 user manual the current program counter is pushed on the stack.

_________________
Prof. Kelly

Confirmed on real hardware.

The Motorola Educational Computer Board.

2000: NOP
2002: NOP
2004: ILLEGAL
2006: NOP

2004 is pushed on the stack when the ILLEGAL instruction executes.

_________________
Prof. Kelly