Texas Instruments MSP430 User Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Microcontrollers
  5. Serial Programming Adapter MSP430
  6. User manual
Texas Instruments MSP430 User Manual

Texas Instruments MSP430 User Manual

Fram devices bootloader
Hide thumbs Also See for MSP430:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
The bootloader (BSL) on MSP430™ microcontrollers (MCUs) lets users communicate with embedded
memory in the MSP430 MCU during the prototyping phase, final production, and in service. Both the
programmable memory (FRAM memory) and the data memory (RAM) can be modified as required.
Do not confuse the bootloader with programs found in some digital signal processors (DSPs) that
automatically load program code (and data) from external memory to the internal memory of the DSP.
These programs are often referred to as bootloaders as well.
...................................................................................................................
1
1.1
1.2
2
3
3.1
3.2
3.3
3.4
3.5
4
4.1
4.2
5
5.1
5.2
5.3
5.4
5.5
5.6
6
7
7.1
7.2
7.3
7.4
7.5
1
2
3
....................................................................................................................
4
1
2
BSL Data Packet
SLAU550M - January 2014 - Revised February 2018
MSP430™ FRAM Devices Bootloader (BSL)
.....................................................................................................
......................................................................................
..................................................................................................
.............................................................................................................
..........................................................................................
.........................................................................................................
......................................................................................................
..............................................................................................
...............................................................................................
.................................................................................................................
....................................................................................................
.......................................................................................................
.................................................................................................
........................................................................................
.......................................................................................
................................................................................................
.....................................................................................
..........................................................................................
........................................................................................
......................................................................................................
.......................................................................................................
..............................................................................................
..............................................................................................
............................................................................................
..............................................................................................
...............................................................................................
.......................................................................................................
................................................................................................................
.............................................................................................................
SLAU550M - January 2014 - Revised February 2018
.............................................................................
List of Figures
..............................................................................
List of Tables
MSP430™ FRAM Devices Bootloader (BSL)
User's Guide
2
2
2
4
5
5
5
6
8
8
9
9
23
24
24
25
25
25
25
26
26
27
27
27
28
28
29
7
7
9
24
4
9
1

Advertisement

Table of Contents
loading

Related Manuals for Texas Instruments MSP430

Summary of Contents for Texas Instruments MSP430

  • Page 1: Table Of Contents

    The bootloader (BSL) on MSP430™ microcontrollers (MCUs) lets users communicate with embedded memory in the MSP430 MCU during the prototyping phase, final production, and in service. Both the programmable memory (FRAM memory) and the data memory (RAM) can be modified as required.

  • Page 2: Contents 1 Introduction

    All other trademarks are the property of their respective owners. Introduction The MSP430 BSL lets users communicate with embedded memory in the MSP430 microcontroller (MCU) during the prototyping phase, final production, and in service. Both the programmable memory (FRAM memory) and the data memory (RAM) can be modified as required. Do not confuse the bootloader with programs found in some digital signal processors (DSPs) that automatically load program code (and data) from external memory to the internal memory of the DSP.
  • Page 3 Tools and Application Notes MSP BSL Tool Folder Training Videos MSP BSL Overview MSP BSL Options MSP Crypto Bootlaoder Training Series SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 4: Overview Of Bsl Features

    Some devices can disable mass erase on incorrect password. See the device family user's guide. The decryption of the payload is performed by the device bootcode. Firmware validation through CRC. MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback...

  • Page 5: Bsl Architecture

    C BSL I2C protocol used by BSL is defined as: • The MSP430 BSL is the slave, and the master must request data from the BSL slave. • 7-bit addressing mode is used, and the slave address is 0x48. •...

  • Page 6: Bsl Invocation

    RAM that is cleared is listed in the tables in Section BSL Invocation The following methods can be used to invoke the BSL application on the MSP430 FRAM devices: • The BSL can be called by application software (see Section 3.3.1)

  • Page 7: Standard Reset Sequence

    3.3.2 Hardware BSL Invocation Applying an appropriate entry sequence on the RST/NMI and TEST pins forces the MSP430 to start program execution at the BSL RESET vector instead of at the RESET vector located at address FFFEh. If the application interfaces with a computer UART, these two pins may be driven by the DTR and RTS signals of the serial communication port (RS232) after passing level shifters.

  • Page 8: Bsl Time-Out Feature

    The version number for the section of code that interprets BSL core commands. Byte 3: API Version The version number for the section of code that reads and writes to MSP430 memory. Reserved bits: 0x00 to 0x0F: Indicates that this BSL API interfaces with flash.

  • Page 9: Bsl Protocol

    Length Length BSL Core Response ACK from BSL 0x80 Section 4.1.4 BSL Core Response is not always included. SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 10: C Bsl Command

    Unknown baud rate. The supplied data for baud rate change is not a known value. 0x57 Packet Size Error. Not supported for FR4xx, FR21xx, and FR20xx. MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 11: Bsl Core Response Structure (Has The Bsl Core Message Byte)

    BSL password error. An incorrect password was supplied to the BSL when attempting an unlock. 0x07 Unknown command. The command given to the BSL was not recognized. SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 12: Bsl Core Commands

    CRC. In the case of multiple length bytes, they are combined together as described to form a larger value describing the number of required bytes. MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback...
  • Page 13 BSL response for a successful data write: Header Length Length S/A/R 0x00 0x80 0x02 0x00 0x3B 0x00 0x60 0xC4 STOP SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 14 0xE6 BSL response for a successful password: Header Length Length 0x00 0x80 0x02 0x00 0x3B 0x00 0x60 0xC4 MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 15 BSL response for a successful password: Header Length Length S/A/R 0x00 0x80 0x02 0x00 0x3B 0x00 0x60 0xC4 STOP SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 16 0xA3 BSL response (successful operation): Header Length Length S/A/R 0x00 0x80 0x02 0x00 0x3B 0x00 0x60 0xC4 STOP MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 17 Length (low byte), Length (high byte) Description The MSP430 performs a 16-bit CRC check using the CCITT standard. The address given is the first byte of the CRC check. Two bytes are used for the length. See the CRC chapter of each family user's...
  • Page 18 0x00 0x17 0x00 0x44 0x00 0x42 0x0F STOP The BSL does not respond once the application gains control. MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 19 BSL response where D1..D4 are the data bytes requested: Header Length Length S/A/R 0x00 0x80 0x05 0x00 0x3A 0x11 0x33 0x55 0x77 0x90 0x55 STOP SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 20 BSL response (version 00.07.34.B2 of the BSL): Header Length Length S/A/R 0x00 0x80 0x05 0x00 0x3A 0x00 0x07 0x34 0xB2 0x14 0x90 STOP MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 21 0x80 0x08 0x00 0x10 0x00 0x00 0x01 0x10 0x32 0x54 0x76 0x93 0xCA BSL Response: S/A/R 0x00 STOP SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 22 Change baud rate to 115200: Header Length Length 0x80 0x02 0x00 0x52 0x06 0x14 0x15 BSL Response: 0x00 MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 23: Bsl Security

    Read and execute access to the rest of the BSL code is not possible. Section 3.2.2 for more information about the Z-Area. SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 24: Common Bsl Use Cases

    Common BSL Use Cases This section explains the flow of how a host programmer can establish a connection to the MSP430 BSL. Overview and Flow Chart A common BSL use case is to erase a device and load new firmware onto it. This can be accomplished by issuing a mass erase either through a failed RX Password command or by the Mass Erase command.

  • Page 25: Establishing A Connection

    This step uses the RX Data Block command to download the application code to the device. A common file format that can easily be generated by MSP430 IDEs is TI-TXT. The download is split into smaller packets and sent with repeated RX Data Block commands. After all bytes have been sent and there is no remaining data, the host programmer can continue to the next step.

  • Page 26: Executing The Application

    Customizing the BSL The BSL in MSP430 FRAM devices resides in ROM and does not allow for a custom BSL to be loaded into the standard BSL space. The standard BSL can be bypassed, and a custom start-up sequence that acts like a BSL can be used.

  • Page 27: Bootloader Versions

    Clock configuration Runs at 8 MHz Peripheral UART eUSCI_A Peripheral I Timer module for time-out Known bugs None SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 28: Fr57Xx Bsl Versions

    Peripheral UART (FR5xxx or FR6xxx) eUSCI_A0 Peripheral I (FR5xxx1 or FR6xxx1) eUSCI_B0 Timer module for time-out Known bugs None MSP430™ FRAM Devices Bootloader (BSL) SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...

  • Page 29: Fr6Xx Bsl Versions

    Peripheral UART (FR5xxx or FR6xxx) eUSCI_A0 Peripheral I (FR5xxx1 or FR6xxx1) eUSCI_B0 Timer module for time-out Known bugs None SLAU550M – January 2014 – Revised February 2018 MSP430™ FRAM Devices Bootloader (BSL) Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 30 Changes from January 23, 2018 to February 26, 2018 ....................Page • Added Section 3.3.2.1, Factors That Prevent Hardware BSL Invocation, and moved information from previous section Revision History SLAU550M – January 2014 – Revised February 2018 Submit Documentation Feedback Copyright © 2014–2018, Texas Instruments Incorporated...
  • Page 31 IMPORTANT NOTICE FOR TI DESIGN INFORMATION AND RESOURCES Texas Instruments Incorporated (‘TI”) technical, application or other design advice, services or information, including, but not limited to, reference designs and materials relating to evaluation modules, (collectively, “TI Resources”) are intended to assist designers who are developing applications that incorporate TI products;...

Table of Contents