Using PEmicro interfaces with MSPM0

1. Introduction

These steps will walk the user through how to use PEmicro’s programming tools with TI’s MSPM0 devices.

2. Prerequisites

Before proceeding, the user should be sure they are using the latest PEmicro drivers. These are available at the link below:

3. Configuring TI’s Code Composer Studio (CCS) IDE

3.1. Installing PEmicro’s Plug-In

  1. Download the PEmicro GDB Server Plug-in.

  2. In the CCS Menu bar, click on Help → Install New Software.

  3. Add the PEmicro repository as demonstrated below. Click the Add button to open the Add Repository dialog.

  4. Then click Archive to navigate to the downloaded plug-in file and select it.

  5. The user can name the repository whatever they wish. The options will then appear in the Available Software window.

  6. Select the appropriate plug-ins and follow the instructions to continue installation

    Note: If the plug-ins do not appear in the window, the user can try adjusting the CCS proxy settings.

  7. Select “GNU ARM PEmicro Debugging Support” and “PEmicro ARM Device Expansion Plug-in”

3.2. Debug Configuration

  1. Right-click on the project name (“Test” for this example) in the Project Explorer to bring up the dialog shown below:

  2. Then select Debug Configurations to open that window.

  3. Double click on “GDB PEmicro Interface Debugging” to create a debug instance of “Test” project.

  4. Program and debug the device

3.3. Setup and Physical Connection

  1. In order to use PEmicro’s Multilink or Cyclone as a debug interface, the user must make sure the TI MSPM0 target board is configured to use this option instead of the internal XDS110-ET debug probe. The procedure involves removing any jumpers from the J101 isolation block, then attaching an Arm debug probe such as PEmicro’s Multilink to the J103 header. There is also a jumper that affects power considerations. We recommend that the user carefully follow TI’s explicit instructions, which can be found in TI’s MSPM0 Launchpad User Guides in the section “Using an External Debug Probe Instead of the Onboard XDS110-ET.”

  2. The PC connects to the Multilink or Cyclone (typically via USB cable), and then the 10-pin mini Arm header on the Multilink or Cyclone is connected to the J103 header on the TI board via a ribbon cable. A bare Multilink is shown below connected to the TI MSPM0 target board:

    Bare Multilink connected via ribbon cable to the J103 header on a TI MSPM0 board

    Fig. 1 Bare Multilink connected via ribbon cable to the J103 header on a TI MSPM0 board

4. Using PEmicro Tools with TI’s MSPM0 on Keil’s uVision IDE

  1. The dropdown box in Options for Target -> Use allows the user to select the “Pemicro Debugger”, as seen below:

5. Using PEmicro Tools with TI’s MSPM0 on IAR’s Workbench for Arm IDE

  1. Under Options for Node MSPM0x_security, in the Debugger category, the user should select “PE micro” from the Driver drop down box, as shown below: