[Tutorial] MSPM0L1306 development board tutorial development environment setup

The development of TI's MSPM0L series can use development environments such as KEIL, IAR, and CCS. The emulator can use JLINK, which is commonly used in ARM development, and TI's XDS emulator.

Next, I will give an explanation on the most commonly used combination development of KEIL and JLINK.

“

1.

Download SDK, MSPM0-SDK from TI’s official website

Download the code configuration tool, SYSCONFIG。

After downloading, you can install it. It is recommended to install it in the default path, which is C:\ti. After installation, open the SDK directory. At present, we need to pay attention to these three folders.

RTOS-less routine directory for MSPM0L1306:

\examples\nortos\LP_MSPM0L1306\driverlib

Open the keil folder in the routine to open this routine. Keil will also prompt you to install the MSPM0L1306 patch package at this time, or you can install it manually in keil's Pack Installer.

“

2.Configure the SYSCONFIG tool

This tool is an initialization code generation tool, similar to STM32's cubeMX.

First, in the SDK directory, under /tools/keil/, open the syscfg.bat file and modify the corresponding SYSCONFIG installation path.

Save it in the same directory.

Open the MSPM0_SDK_syscfg_menu_import.cfg file and modify the SYSCONFIG version and path. The red and blue parts in the figure below must be modified to be consistent with the path names of the SDK and SYSCONFIG.

In keil, select Tools → Customize Tools Menu in the menu

点击import。

Select the SDK directory.

MSPM0_SDK_syscfg_menu_import.cfg file.Click to open.

Click OK.

At this time, the SYSCONFIG option will appear in the Tool directory of keil.

When we need to modify the MCU peripheral initialization options, we need to double-click to open the .syscfg file in the project and let the file appear in front of you. Click Sysconfig in Tool to open the SYSCONFIG tool to configure the current project.

“

3. The role of the SYSCONFIG tool

Although SYSCONFIG is a code configuration tool like cubeMX used for STM32, SYSCONFIG does not generate code, it only generates 4 files.

The first and second files in the picture above are the C and H files of the initialization code. In an empty project, the most basic program is like this.

The SYSCFG_DL_init function here is in ti_msp_dl_config.c.

It is not recommended to modify any code here, because every time the SYSCONFIG configuration is saved, this file will be modified by SYSCONFIG.

The Event.dot file saves the MCU Event routing. You can copy the information in this file through an online page to generate an Event routing map.

Click to view：

https://dreampuf.github.io/GraphvizOnline/

The last syscfg file is the file that we open every time we start SYSCONFIG. SYSCONFIG relies on this file to identify what parameters are configured.