SLAZ283AA October 2012 – May 2021 MSP430F5435
CPU Module
Compiler-Fixed
An unexpected Vacant Memory Access Flag (VMAIFG) can be triggered due to the CPU autoincrement of the MAB+2 outside the range of a valid memory block.
The VMAIFG can be triggered under the following conditions:
1. If an interrupt is requested, fetched by the CPU, but lost before excution of the interrupt service routine.
OR
2. If a PC-modifying instruction (e.g. - ret, push, call, pop, jmp, br) is fetched from the last address of a section of memory (e.g.- FLASH, RAM) that is not continguous to a higher, valid section on the memory map.
For case 1 - None.
For case 2 - If code is affected, edit the linker command file to make the last four bytes of affected memory sections unavailable.
Refer to the table below for compiler-specific fix implementation information.
| IDE/Compiler | Version Number | Notes |
|---|---|---|
| IAR Embedded Workbench | IAR EW430 v6.40 or later | |
| TI MSP430 Compiler Tools (Code Composer Studio) | Not affected | |
| MSP430 GNU Compiler (MSP430-GCC) | Not affected |