TI MSP430

From SEGGER Knowledge Base
Jump to navigation Jump to search

The Texas Instruments TI MSP430 family is a series of ultra-low-power 16-bit microcontrollers based on the MSP430 CPU architecture. These devices combine low-power operation with integrated peripherals such as timers, ADCs, communication interfaces, and GPIOs, making them suitable for a wide range of embedded applications.

Supported devices

Refer to the supported device list for a full list of all supported MSP430 family devices, their corresponding names and connection diagrams.

Target interfaces

Interface J-Link support Flasher support
JTAG

Flash banks

Flash bank Base address J-Link support Flasher support Loader
Name Bank size
Information Memory 0x00001000 Default 256 B
Code Memory 256B 0x00003100 Default 256 B
Code Memory 0x00002200 Default up to 120 kB

Device specifics

JTAG unlock for FR5x and FR6x

The JTAG access can be unlocked on MSP430FR devices with 2 methods:

Without password

If this method is chosen, the device is bulk erased during the login phase. This method does not work when a lock with password is configured.

With password

A variable length password can be configured to lock the JTAG interface.
When address 0xFF80 contains a 0xAAAA the JTAG interface is locked with a password.
Address 0xFF82 contains the low and high byte numbers of password codes in words.
Addresses 0xFF88 and following contains the password in 16 bit word size with low an high byte.

caption
caption

The password codes have to be entered like this:

caption
caption

With '+' you can add an further password code.
With 'x' you can remove a password code.
Please make sure that the number of password codes entered in U-Flash matches the configured number of codes from the device.

Wiring

Chips with multiplexed JTAG pins (TEST pin required)

On many small and mid-range MSP430 devices (e.g., the MSP430F11x1, F12x, F20xx, or G2xx), the JTAG signals share general-purpose I/O pins, typically P1.4–P1.7. To enable JTAG communication with the debugger (e.g., the MSP-FET), the TEST pin must be driven high.

  • A high level on the TEST pin disconnects these pins from the GPIO logic and connects them to the JTAG block (the TAP controller).
  • The TEST pin is driven by the debugger. If it is not routed to the JTAG connector, the debugger cannot detect the JTAG interface.”

Chips with dedicated JTAG pins (no TEST pin needed)

Some larger MSP430 devices (e.g., the MSP430F149, F1611, or F449) provide dedicated pins for TMS, TCK, TDI, and TDO, which cannot be used as general-purpose I/O.
Because these pins serve exclusively as the JTAG interface, the JTAG logic does not need to be enabled by a hardware signal. It is always active, and the debugger connects directly via the four JTAG lines

Verify method

To speed up the verification of the device, CRC verification is enabled by default. But it is also possible to verify it byte by byte.

Read method

Generate test data (for read)

The "Generate test data file" and "Generate data file for read" generation in U-Flash is limited to the "Code memory" sections. So that it is possible to program and read the "Code memory".

It is also possible to read the "Information memory" if you are using a data file that contains (dummy) data for the information memory area. The #READ command always reads the memory areas for which data exists in the data file.

Limitations

Burning the JTAG Fuse

Burning the JTAG fuse is currently not supported.