MSP430FR58xx59xx68xx69xx-.zip_www59xx_wwwxx69xxcon_xx59cOm_xx68x

Application Report

SLAA559B–April 2014

Migrating from the MSP430F2xx and MSP430G2xx

Families to the MSP430FR58xx/FR59xx/68xx/69xx Family

Priya Thanigai and William Goh .............................................................................. MSP430 Applications

ABSTRACT

This application report enables easy migration from MSP430F2xx flash-based MCUs to the

MSP430FR58xx/FR59xx/68xx/69xx family of FRAM-based MCUs. For the migration guide to

MSP430FR57xx, see Migrating From the MSP430F2xx Family to the MSP430FR57xx Family (SLAA499).

Contents

1 Introduction ................................................................................................................... 2

2 In-System Programming of Nonvolatile Memory ........................................................................ 2

3 Hardware Migration Considerations....................................................................................... 4

4 Device Calibration Information ............................................................................................. 4

5 Important Device Specifications ........................................................................................... 5

6 Core Architecture Considerations ......................................................................................... 5

7 Peripheral Considerations................................................................................................. 10

8 Conclusion .................................................................................................................. 14

9 References ................................................................................................................. 15

Introduction

changes and slight variations in instruction cycle times, while the instruction set remains the same.

For any specific information, see the device-specific data sheet and errata.

Using FRAM nonvolatile memory is very similar to using static RAM (SRAM). FRAM's first introduction as

an embedded memory in a general-purpose ultra-low power MCU was on Texas Instruments 16-bit

MSP430 product line, the MSP430FR57xx family.

• FRAM is not segmented and each bit is individually erasable, writable, and addressable.

• FRAM segments do not require an erase before a write.

• FRAM write accesses are low power, because writing to FRAM does not require a charge pump.

• FRAM writes can be performed across the full voltage range of the device.

• FRAM write speeds can reach up to 8 MBps with a typical write speed of approximately 2 MBps. The

A single FRAM cell can be considered a dipole capacitor that consists of a film of ferroelectric material

process of reading the data, the crystal that is polarized in the direction of the applied field loses its current

state. Hence, every read must be accompanied by a write-back to restore the state of the memory

location. With TI's MSP430 FRAM MCUs, this is inherent to the FRAM implementation and is completely

transparent to the application. The write-back mechanism is also protected from power loss and is

guaranteed to complete safely under all power-fail events. The FR59xx power management system

achieves this by isolating the FRAM power rails from the device supply rails in the event of a power loss.

The FRAM power circuitry also uses built-in low dropout regulator (LDO) and a capacitor that store

sufficient charge to complete the current write-back in the event of a power failure.

In-System Programming of Nonvolatile Memory

Because FRAM is very easy to reprogram, it also makes it easy for erroneous code execution to

constant data or application code that is not expected to change over the device lifetime. Code examples

on how to configure the MPU are provided in the MSP430FR5969 product folder online:

(http://www.ti.com/product/msp430fr5969).

2.3.1 Dynamically Partitioning FRAM

One unique property of FRAM is that when it is used in conjunction with the MPU, it provides the user the

ability to dynamically shift the boundaries of code, data, and constant memory. This is done by setting up

the MPU to establish read-only (constant), read-write only (variable), and read-execute only (code)

segments. The resolution of each block depends on the total available FRAM. For example, on the 64kB

MSP430FR5969, a segment can be as small as 16 bytes [2].

When using the Code Composer Studio™ IDE, the device linker command file automatically assigns MPU

2. Configure MCLK ≥ 8 MHz.

For more information, see the Wait State Control section of the FRAM Controller (FRCTRL) chapter in

MSP430FR58xx, MSP430FR59xx, MSP430FR68xx, and MSP430FR69xx Family User's Guide

(SLAU367).

The BSL is software that is used to reprogram the MCU; for example, during field firmware updates. On

the F2xx family of devices, the BSL uses a Timer_A-based UART and is located in ROM. The BSL is not

erasable or customizable by the user.

The FR59xx family follows a similar approach wherein the BSL software is located in ROM. It occupies the

MSP430FR68xx, and MSP430FR69xx Family User's Guide [2]. Note that the location and length of the

BSL signature is different from the F2xx family.

FR59xx device variants using an I2C hardware interface for the BSL are also available. However, for a

given device variant, only the factory-configured interface can be used.

On F2xx devices, the JTAG port is secured by blowing a physical fuse on one of the JTAG lines by

subjecting it to a high voltage through a special procedure. This action is irreversible, and further access to

the device is only possible via the BSL.

In-System Programming of Nonvolatile Memory

On the FR59xx devices, the physical fuse has been replaced by a programmable JTAG fuse. Securing the

device involves writing a specific signature to the JTAG signature location. When the fuse is programmed,

incorrect password prevents JTAG access. When a password is verified, complete JTAG access is

possible until the next BOR event.

When using the Code Composer Studio IDE V5.2 or higher, this option is available by editing the

MSP430Fxxx.CCXML file under Target Configurations in the Advanced Setup Section, Advanced target

Configuration. The procedure is described in the Code Composer Studio User's Guide for MSP430

(SLAU157).

MSP-GANG430 will not support FR59xx. This production programmer has been superseded with MSP-

GANG (http://www.ti.com/tool/msp-gang).

• For JTAG and SBW connections on the FR59xx devices, see the MSP430 Hardware Tools User's