5.2.5 Memory Violation
A Memory Execution Violation Reset occurs while executing an instruction that has been fetched from outside a valid execution area, clearing the MEMV bit. Refer to the “Memory Execution Violation” section for the available valid program execution areas and the PCON1 register definition for MEMV bit conditions.
| REG | Address | Partition | |||
|---|---|---|---|---|---|
|
BBEN = SAFEN = |
BBEN = SAFEN = |
BBEN = SAFEN = |
BBEN = SAFEN = |
||
| PFM | 00 0000h ... Last Block Memory Address | APPLICATION BLOCK(4) | APPLICATION BLOCK(4) | BOOT BLOCK(4) | BOOT BLOCK(4) |
Last Boot Block Memory Address +
1(1) ... Last Program Memory Address -
80h |
APPLICATION BLOCK(4) | APPLICATION BLOCK(4) | |||
| Last Program Memory Address - 7Fh(2) ... Last Program Memory Address | SAF(4) | SAF(4) | |||
| CONFIG | Config Memory Address(3) | CONFIG | |||
Note:
- Last Boot Block Memory Address is based on BBSIZE given in “Configuration Word 4”.
- Last Program Memory Address is the Flash size given in the “Program Memory Organization”.
- Config Memory Address are the address locations of the Configuration Words given in the “NVMREG Access to Device Information Area, Device Configuration Area, User ID, Device ID, EEPROM, and Configuration Words” section.
- Each memory block has a corresponding write protection fuse defined by the WRTAPP, WRTB and WRTC bits in the “Configuration Word 4”.