Hello,
reading the current PC from the S12X CPU can be done (using "bsr" for example). But in the case of an access violation, this is probably not that useful since it points to whatever instruction the CPU executes next. This means that after an access violation occurred, the PC points to code from the MPU ISR, but not the code where the access violation actually occurred.
To know where the access violation originated, one needs to read the return-address from the exception stack-frame which has been generated on entry to the MPU ISR. However, the address from the stack-frame does not point to the exact place where the access violation occurred. It contains the PC of the instruction after the point where the problem occcured (or, in some circumstances, even the PC after the next one). Together with the status address from the MPU, this is a starting point for debugging (i.e. disassemble the code before the Return-PC to identify the correct instruction).
MJW