Device Description: MSPM0 Unlock and BSL Programming
This document outlines the methods for unlocking and programming MSPM0 devices, focusing on two primary approaches: Method 0 for forcing the device into Bootloader (BSL) mode and Method 1 for initiating a DSSM Mass Erase, followed by Method 2 for BSL unlock and firmware download. These methods are crucial for initial device programming, recovery from locked states, and field updates.
Function Description
The MSPM0 device, likely a microcontroller, requires specific procedures to enter BSL mode or undergo a mass erase operation. BSL mode allows for firmware updates and programming via a serial interface, while a mass erase is essential for clearing existing firmware and device configurations, often used for recovery or initial programming. The provided methods detail both hardware connections and software steps using the Code Composer Studio (CCS) integrated development environment and a dedicated BSL GUI tool.
Important Technical Specifications
The procedures rely on the XDS110 debug probe for hardware connections and communication. The XDS110 is a common debug and programming tool for Texas Instruments microcontrollers, providing JTAG/SWD and serial communication capabilities. Specific pins on the MSPM0 device are critical for these operations:
- PA18: Used in Method 0 to force the device into BSL mode. Pulling PA18 high (up) during power-up is a key step.
- GND, DIO, CLK: Essential for establishing a debug connection with the XDS110.
- 3.3V, RXD, TXD, RST, BSL: Used in Method 2 for BSL unlock and programming. RXD and TXD are for serial communication, RST for device reset, and BSL for activating the bootloader.
The BSL GUI tool supports different MSPM0 device variants, specifically L1306 (PA23 for TXD, PA22 for RXD, PA18 for BSL) and G3507 (PA10 for TXD, PA11 for RXD, PA18 for BSL). These pin assignments are critical for correct hardware connections.
The software environment for these operations includes:
- Code Composer Studio (CCS): A robust IDE for embedded development, used for target configuration, debugging, and initiating mass erase operations.
- MSPM0 SDK: Provides necessary tools and firmware for MSPM0 development, including the BSL GUI.
- BSL GUI: A dedicated graphical user interface for simplified BSL programming, firmware download, and XDS110 firmware updates.
- Python 3.10.4: The version of Python used to develop the BSL GUI, indicating its underlying technology.
Usage Features
Method 0: Forcing Device into BSL Mode
This method is a hardware-centric approach to ensure the MSPM0 device enters BSL mode.
- Hardware Connection: Connect GND, DIO, and CLK from the XDS110 debug probe (referred to as "burner") to the target MSPM0 board using DuPont cables.
- Power Down: Ensure the MCU is powered off by unplugging the burner's power cord.
- Pull PA18 Up: Connect PA18 to a high logic level (e.g., 3.3V) and ensure the connection is secure. On a Launchpad, this might involve pressing a specific button (PA18 button) and ensuring a jumper cap is in place.
- Power On: Re-apply power to the MCU by plugging in the burner's power cord.
- Burn within 10 seconds: With PA18 held high, initiate the burning process within 10 seconds. If this fails, Method 1 is recommended.
Method 1: Force a DSSM Mass Erase
This method uses CCS to perform a mass erase, often necessary when the device is in an unknown or locked state.
- Hardware Connection: Connect the XDS110 to the target board.
- Remove Jumper Cap: If applicable, remove any jumper caps that might interfere with the debug connection.
- DuPont Cable Connection: Connect GND, 3.3V, DIO, CLK, and RST from the XDS110 to the target board. For Launchpad users, this step and the previous one might be unnecessary as the connections are typically integrated.
- Software Steps (CCS):
- Open Target Configurations: In CCS, navigate to "Target Configurations" (Alt+Shift+Q, O).
- Find ccxml File: Locate and select the
.ccxml file corresponding to your project (e.g., MSPM0G3507.ccxml).
- Launch Selected Configuration: Click "Launch Selected Configuration" to establish a debug session.
- Show All Cores: In the debug view, ensure "Show all cores" is selected to view all available debug interfaces.
- Connect DAP: Connect to the Debug Access Port (DAP). If this fails, Method 2 might be required.
- Mass Erase: In the "Scripts" menu, select "MSPM0 DAP Commands" and then "MSPM0_MassErase."
- Press Reset Button: If the console prompts "Press the reset button...", press the reset button on the XDS110 debug probe.
- Console Prompts: After a successful mass erase, the console will indicate "Mass erase executed." Terminate the debug session, power-cycle the device, and restart the debug session.
- Force Reset (if error): If an "Error connecting to the target" occurs, select "Force Reset" while ensuring a reset connection. This attempts to re-establish communication.
Method 2: BSL Unlock
This method utilizes the BSL GUI tool for unlocking and programming the device.
- Hardware Connection: Connect the XDS110 to the target board.
- Remove Jumper Cap: If applicable, remove any jumper caps.
- DuPont Cable Connection: Connect GND, 3.3V, RXD, TXD, RST, and BSL from the XDS110 to the target board. For Launchpad users, a jumper might be needed to connect RXD and TXD. Refer to the table for specific pin assignments for L1306 and G3507 devices.
- Software Steps (BSL GUI):
- Download MSPM0 SDK: Obtain and install the MSPM0 SDK.
- Open BSL GUI: Navigate to the
bsl folder within the SDK and launch BSL_GUI_EXE.
- Select Firmware: Choose the appropriate firmware file (
.txt or .app) from the Input folder within the BSL GUI's directory, matching your specific MSPM0 chip (e.g., LP_MSPM0G3507_PB27_Toggle_demo_app.txt).
- Update XDS110 Firmware (Optional): If necessary, select "Update XDS110 firmware" from the "MoreOption" menu.
- Download Firmware and Unlock: Click "Download" to initiate the firmware download and unlock process. The console will display "Operation success!" and "Download finished!" upon completion.
Maintenance Features
- XDS110 Firmware Updates: The BSL GUI provides an option to update the XDS110 firmware, ensuring compatibility and optimal performance with the latest MSPM0 devices and software. This is a crucial maintenance step to prevent communication issues.
- SDK Updates: Regularly updating the MSPM0 SDK ensures access to the latest BSL GUI versions, bug fixes, and device support.
- Cable Integrity: Maintaining good quality DuPont cables and ensuring secure connections are vital for reliable hardware operations. Loose or faulty connections can lead to programming failures.
- Power Cycling: Power cycling the MCU after a mass erase or programming operation is a standard practice to ensure the device resets correctly and loads the new firmware.
- Troubleshooting: The console output in CCS and the BSL GUI provides valuable feedback for troubleshooting. Error messages like "Error connecting to the target" or "Device Connection Error" indicate issues that might require re-checking hardware connections, forcing a reset, or trying an alternative method. The BSL GUI also provides specific error messages like "Error: Please choose a password file" or "Error: Password format is not correct!" if password-protected firmware is used incorrectly.
Need help?
To Next Page
General
