SLAA381C December   2007  – September 2018 MSP430F233 , MSP430F235 , MSP430F2410 , MSP430F247 , MSP430F248 , MSP430F249

 

  1.   Migrating From MSP430F13x and MSP430F14x MCUs to MSP430F23x and MSP430F24x MCUs
    1.     Trademarks
    2. 1 Comparison of MSP430F1xx and MSP430F2xx Families
    3. 2 Hardware Considerations for F13x/F14x to F23x/F24x Migration
      1. 2.1 Device Package and Pinout
      2. 2.2 Current Consumption
      3. 2.3 Operating Frequency and Supply Voltage
      4. 2.4 Device Errata
    4. 3 Firmware Considerations for F13x/F14x to F23x/F24x Migration
      1. 3.1 Memory Considerations
        1. 3.1.1 Device Memory Map
        2. 3.1.2 Information Flash Memory
      2. 3.2 Serial Communication – USART and USCI
        1. 3.2.1 UART Mode
        2. 3.2.2 SPI Mode
      3. 3.3 Clock System
        1. 3.3.1 LFXT1 and XT2 Oscillators
        2. 3.3.2 Digitally Controlled Oscillator (DCO)
      4. 3.4 Bootloader (BSL)
      5. 3.5 Interrupt Vectors
      6. 3.6 Beware of Reserved Bits!
      7. 3.7 Timers
      8. 3.8 Analog Comparator
    5. 4 References
  2.   Revision History

3.1.1 Device Memory Map

The memory maps of the F13x/F14x and F23x/F24x are almost identical. This applies to the location and size of RAM as well as flash memory, allowing an application to keep the same linker command file during migration, in most cases. However, there are two exceptions that apply and, therefore, TI strongly recommends that you rebuild the application to accommodate for the difference in the memory map. The build process makes use of the memory map information stored in the IDE linker command file and automatically accommodates these changes. The linker command files are found within the folder where the IDE was installed.

The interrupt vector table of F23x/F24x MCUs spans 32 memory word locations, and the table in F13x/F14x MCUs spans 16 memory word locations. The word memory location 0xFFBE on F23x/F24x MCUs is reserved for special bootloader (BSL) purposes. See Section 3.5 for more details regarding the interrupt vector table.

Furthermore, the MSP430F247(1) and MSP430F248(1) devices all have an increased RAM size of 4KB compared to their MSP430F14x family counterparts. The application should be rebuilt to take advantage of this increased memory size. In addition, the MSP430F24x device family has a device with a memory configuration previously unavailable. The MSP430F2410 has 4KB of RAM and 56KB of flash memory. This device can be considered as an alternative migration option for applications that can benefit from having more RAM. In this case, the differences in memory organization are more drastic and the application code must be rebuilt.

For details of the device memory maps, see the device-specific data sheets. [3][4]