SLAA396A June 2008 – September 2018 MSP430F5131 , MSP430F5132 , MSP430F5151 , MSP430F5152 , MSP430F5171 , MSP430F5172 , MSP430F5232 , MSP430F5234 , MSP430F5237 , MSP430F5239 , MSP430F5242 , MSP430F5244 , MSP430F5247 , MSP430F5249 , MSP430F5252 , MSP430F5253 , MSP430F5254 , MSP430F5255 , MSP430F5256 , MSP430F5257 , MSP430F5258 , MSP430F5259 , MSP430F5304 , MSP430F5308 , MSP430F5309 , MSP430F5310 , MSP430F5324 , MSP430F5325 , MSP430F5326 , MSP430F5327 , MSP430F5328 , MSP430F5329 , MSP430F5333 , MSP430F5336 , MSP430F5338 , MSP430F5340 , MSP430F5341 , MSP430F5342 , MSP430F5418 , MSP430F5418A , MSP430F5419 , MSP430F5419A , MSP430F5435 , MSP430F5435A , MSP430F5436 , MSP430F5436A , MSP430F5437 , MSP430F5437A , MSP430F5438 , MSP430F5438A , MSP430F5500 , MSP430F5501 , MSP430F5502 , MSP430F5503 , MSP430F5504 , MSP430F5505 , MSP430F5506 , MSP430F5507 , MSP430F5508 , MSP430F5509 , MSP430F5510 , MSP430F5630 , MSP430F5631 , MSP430F5632 , MSP430F5633 , MSP430F5634 , MSP430F5635 , MSP430F5636 , MSP430F5637 , MSP430F5638
The MSP430F5xx series of devices is the latest addition to the MSP430™ family of microcontrollers. Although there are many common features between the MSP430F5xx and MSP430F2xx and MSP430F4xx offerings, there are also several differences. This document gives a brief overview of differences between the device families. Detailed information regarding specific differences can be found in the respective module chapters in the MSP430F5xx and MSP430F6xx Family User's Guide.
MSP430 is a trademark of Texas Instruments.
All other trademarks are the property of their respective owners.
This document is a snapshot of major functional differences between the MSP430F5xx family of devices and its predecessor device families, MSP430F2xx and MSP430F4xx.
In this document, the term core refers to the key subsystem modules that are common to all MSP430F5xx devices. These include the central processing unit (CPUX), the Power Management module (PMM), the Unified Clock System module (UCS), the System module (SYS), as well as memory mapping and allocation.
Most of the core changes to the MSP430F5xx were required primarily to support the growing demands of microcontroller applications, which include higher levels of integration, higher performance levels at lower power, increased flexibility, and extensions for future enhancements. Although these changes were necessary, the intent was to maintain as much look and feel, as well as compatibility, with earlier MSP430 generations.
This application report contains three major sections. The first section describes the memory mapping present on the MSP430F5xx. The second section describes the core modules and any key differences from existing MSP430F2xx and MSP430F4xx devices. The last section describes each of the peripheral modules that exists on the first MSP430F5xx offerings along with any key differences from similar modules found on MSP430F2xx and MSP430F4xx devices.
The MSP430F5xx family memory space has changed significantly from the MSP430F2xx and MSP430F4xx device families. Changes were required to support future peripheral expansion, increased memory options, and future extensions.
The peripheral space has been expanded up to 4KB to support current peripheral set and future additions. There is no longer byte-only peripheral space. In general, most peripheral registers can be accessed in byte or word formats, however, there are some exceptions.
RAM space now begins at 01C00h for all MSP430F5xx devices. There is a moving boundary between RAM and program space depending on the size of the RAM.
The interrupt vector space still resides up to the upper boundary of the 64-KB address space, however, the number of vectors has been increased to support up to 64 interrupt vectors. All interrupt vectors should be used with symbolic programming, because the order and number of vectors can change from device to device. See the device-specific data sheet for allocated vectors and their priorities.
The bootloader (BSL) memory allocation has been increased to 2KB to support various BSL options, including the capability for a user-generated BSL.
The core modules consist of the CPUX, PMM, UCS, SYS, JTAG, and EEM modules. The core remains consistent among all devices in the MSP430F5xx family.