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

2.1 Device Package and Pinout

The good news is that a 64-pin LQFP MSP430F261x device directly drops into an existing MSP430F16x-based 64-pin LQFP PCB footprint. The package and the PCB footprint are identical. However, in case of a hardware-level redesign of the application to be migrated, the use of the 80-pin LQFP (PN) MSP430F261x device can be considered as an alternative option, as it offers more I/O pins. No direct drop-in replacement is available for a 64-pin MSP430F16x in the QFN package.

While almost all MSP430F261x pins can be used for the same purpose as the pins on their MSP430F16x counterparts (which includes all analog and digital modules, as well as power supply and JTAG pins), there is one exception.

When migrating a design that uses the F16x USART hardware module in I2C mode, special care must be taken, as the pin assignments are different on the MSP430F261x. This is the only pin mismatch that would prevent a direct drop-in of an MSP430F261x into an existing MSP430F16x design (see Table 2).

Table 2. I2C Module Connections Migration

I2C Signal Name Pin and Signal on F16x
(USART0) 		Pin and Signal on F261x
(USCI_B0) 		Comment
SDA Pin 29 (P3.1/SIMO0/SDA) Pin 29 (P3.1/UCB0SIMO/UCB0SDA) No conflict
SCL Pin 31 (P3.3/UCLK0/SCL) Pin 30 (P3.2/UCB0SOMI/UCB0SCL) Pin changed

Details regarding packaging and pinout can be found in the device-specific data sheets. [3][4]