SLAA380B December   2007  – September 2018 MSP430F2616 , MSP430F2617 , MSP430F2618 , MSP430F2619

 

  1.   Migrating From MSP430F16x MCUs to MSP430F261x MCUs
    1.     Trademarks
    2. 1 Comparison of MSP430F1xx and MSP430F2xx Families
    3. 2 Hardware Considerations for MSP430F16x to MSP430F261x 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 MSP430F16x to MSP430F261x Migration – Firmware Considerations
      1. 3.1 CPU and Memory Considerations
        1. 3.1.1 Extended Memory Architecture
        2. 3.1.2 Subroutine Parameter Passing and Stack Frame
        3. 3.1.3 MSP430X Instruction Cycle Count Optimizations
        4. 3.1.4 Device Memory Map
        5. 3.1.5 Information Flash Memory
      2. 3.2 Serial Communication – USART Versus USCI
        1. 3.2.1 UART Mode
        2. 3.2.2 SPI Mode
        3. 3.2.3 I2C 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
      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.4 Device Memory Map

The memory maps of the MSP430F16x and MSP430F261x devices are different. This applies both to the location and size of RAM and to flash memory. Therefore, most applications need to be rebuilt 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 and have the file name extension CMD (for TI Code Composer Essentials) and XCL (for IAR Embedded Workbench). While an MSP430F261x device memory map can be considered as a superset of the MSP430F16x (it can fit any MSP430F16x program), the following two exceptions apply.

The MSP430F1611 has 10 KB of RAM, and the largest MSP430F261x devices at the time of publishing this application report have only 8KB. This requires software modifications if all of the 10KB of RAM are used in an MSP430F1611-based design.

In addition to that, the interrupt vector table of MSP430F261x devices spans 32 memory word locations, and the table in MSP430F16x devices spans 16 memory word locations. Furthermore, the word memory location 0xFFBE on MSP430F261x devices is reserved for special bootloader purposes. See Section 3.5 for more details regarding the interrupt vector table.

Further details regarding the devices' memory maps can be found in device data sheets. [3][4]