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.2 Serial Communication – USART and USCI

One of the major differences between F13x/F14x and F23x/F24x MCUs is the serial communication module. On the F23x/F24x, the USCI module is implemented. USCI is the next-generation MSP430 communication module, offering more features and functionality to the user. USART (F13x/F14x) and USCI (F23x/F24x) modules are not software compatible and, therefore, F13x/F14x software using the USART module must be adapted to make use of the USCI module.

The F24x MCUs have two independent and identical USCI modules, both of which provide two communication channels that operate simultaneously. With the F24x, for example, it is possible to service four SPI communication channels or two I2C channels and two UART channels, simultaneously. The F23x MCUs have one USCI module and support two independent communication channels. I2C operation is not available on F13x/F14x MCUs.

It is not in the scope of this application report to discuss all possible aspects regarding migrating application code to use the USCI interface; however, a few items are outlined to highlight major differences between the devices (and the modules). In general, it is strongly recommended to carefully review both module descriptions in the appropriate device family user’s guide [1][2], as well as to use the USCI code examples provided in the product folders on the MSP430 website as a starting point for any code that is newly created.