The MSP430 bootloader (BSL) provides a way to communicate with an MSP430 microcontroller and modify its flash memory or RAM without relying on the JTAG interface. For industrial automation teams, this can support device programming during prototyping and production, as well as updates to equipment already in service. Successful implementation depends on more than sending firmware: engineers must account for how the BSL is entered, which protocol the device family uses, and how access is protected.
What the MSP430 bootloader does
The BSL is firmware that accepts commands for operations such as writing or reading memory, erasing flash, and transferring control to a user program. Its code is held in ROM or specially protected flash, depending on the device. This protected location helps prevent accidental overwriting of the bootloader itself.
The BSL is distinct from a mechanism that automatically copies a program from external memory at startup. Instead, a host or other controller initiates a BSL session, establishes communication, and sends commands. The session can end by directing execution to a defined user-program address or by resetting the microcontroller.
Entering a BSL session
Before the BSL can accept commands, the target must receive the entry sequence appropriate to its hardware. On devices with shared JTAG pins, the sequence uses the RST/NMI and TEST pins. Devices with dedicated JTAG pins use TCK with RST/NMI. USB-equipped devices have separate invocation conditions, including cases involving USB power and the reset vector or PUR pin.
These sequences are timing- and device-dependent. For example, the documented shared-pin method requires transitions on TEST while RST/NMI is held low, followed by release of reset with TEST at the required level. The dedicated-pin method uses negative transitions on TCK. Pin timing recommendations and device errata should be checked for the specific MCU; some device revisions have additional entry requirements. JTAG control, an NMI configuration on the reset pin, or a power-on reset can also prevent BSL startup under the described conditions.
In a host-controlled setup, serial-port control signals may drive the entry pins through appropriate level shifters. This makes the reset and entry circuitry part of the programming interface design, not merely a software concern.
Choose the protocol for the device family
MSP430 BSL implementations are not all interchangeable. The 1xx, 2xx, and 4xx families use a command and data-frame protocol, while F5xx and F6xx devices use a layered packet structure in which peripheral-interface code wraps a BSL core command. The peripheral interface carries details needed for communication over a particular transport.
UART and USB considerations
For the 1xx, 2xx, and 4xx protocol described in the guide, UART communication starts at 9600 baud in half-duplex mode, with an acknowledge character used for handshaking. A synchronization character must be sent before each command. The BSL responds to confirm synchronization, after which the host sends the command frame. The specified UART format uses eight data bits, least-significant bit first, even parity, and one stop bit.
Timing matters: the documented protocol specifies a minimum delay before sending further characters after receiving data from the BSL. It also warns that using an unsupported baud rate during initialization can create communication problems and may compromise flash write or erase reliability. Some versions support a baud-rate change command, but availability and supported rates depend on the BSL version and device.
USB-equipped devices use a USB HID interface with input and output endpoints. For F5xx and F6xx devices, the BSL packet’s peripheral interface may support UART, I2C, or USB, depending on the device and configuration. Confirm the relevant family documentation and BSL version before building host software or selecting a programming fixture.
Plan for command framing and recovery
In the older protocol, a command frame includes a header, command identifier, length fields, command-specific data, and a checksum. The length fields must match, and the checksum is calculated across the frame content. A positive acknowledgement indicates successful reception and execution; a negative acknowledgement can indicate an invalid frame, unsupported or locked command, or unsuccessful operation.
Commands differ in their access requirements. Reading memory, writing data blocks, and erasing individual segments are password protected. Other commands, including password reception and mass erase, are not protected in the same way. If communication control is lost because of a line fault or an invalid frame sequence, the documented recovery method for the older protocol is to repeat the BSL entry sequence and begin a new session.
When writing host software, handle acknowledgements and error responses explicitly. Do not treat a correctly transmitted packet as proof that the requested flash operation completed. Where supported, erase-check or verification functions can help confirm memory state. Command availability varies by BSL version, so host logic should not assume every device implements the same command set.
Understand password protection and application handoff
For the 1xx, 2xx, and 4xx devices covered in the guide, the BSL password corresponds to the contents of the interrupt vector table. Supplying the correct password unlocks commands that permit memory access; that unlocked state lasts until another BSL entry. Modifying interrupt vectors can therefore affect the password expected in a later session.
Disabling JTAG does not necessarily remove BSL access, but BSL memory access remains subject to password protection. Some BSL versions also provide additional security behavior tied to a flash word beneath the interrupt vectors. The applicable device documentation should be consulted before setting this value, since its contents can affect password-error handling or whether the BSL starts through the default sequence.
When the BSL transfers execution to an application, it does not necessarily reset the MCU. The application may inherit register settings from the bootloader, and password protection is no longer active at that point. Application startup code and the handoff procedure should account for this, including ensuring flash protection is restored where required.
Practical implications for automation teams
A reliable MSP430 programming workflow begins with device-specific verification. Before integrating a BSL into a production or service process:
- Identify the MCU family and BSL version, then use the matching protocol and command set.
- Design and validate the required reset, entry-pin, and voltage-level circuitry.
- Implement synchronization, framing, checksums, timing, acknowledgements, and recovery behavior as specified.
- Manage passwords and interrupt-vector changes as part of the firmware release process.
- Check erase and programming results, and account for the MCU state when handing control to the application.
The MSP430 BSL can provide a practical path for programming and maintaining embedded devices, including when JTAG access is unavailable. Its use is not a one-size-fits-all process: entry conditions, interfaces, commands, and security details vary across families and versions. Matching the host implementation and hardware design to the target device is essential for dependable programming in development, production, and service.