Embedded module TQMa117xL

Deploying

To deploy the examples on the STKa117xL this is currently possible either via JTAG or Serial Downloader. Below you can choose which option is most suitable for you.

Preface

The following instructions describe how to prepare and generate the project and writing an image via flashloader with MCUXpresso Secure Provisioning tool.

In this guide, we assume that the repository with examples was either built in advance or downloaded from GitHub. The instructions on this page refer to the TQMa117xL repository and ancillary tools listed in the following table:
Tool Version
GitHub Repository MBa117xL.SW.MCU.BSP
VS-Code Version 1.88.1
MCUXpresso Secure Provisioning Version 8.0
MCUXpresso Config Tools Version 15.1

Booting from flash

Writing the examples

STEP 1 - Rebuilding the image

To be able to write the Image with the MCU Secure Provisioning Tool the project has to be rebuilt with the option: 
DXIP_BOOT_HEADER_ENABLE=0

STEP 2 - Generating the dcd.bin

This step is to generate a dcd.bin file of your current hardware configuration. Start the MCUXpresso Config Tool and open the MBa117xL.SW.PQ.mex pinmuxing file from your project.

By default this file is located in examples/board in the project. Afterwards you need to select the Device Configuration tab from the menu icons. Select binary as output format in the DCD window and update the the code. The dcd.bin file should now be saved in the board folder.

STEP 3 - Building

After rebuilding the project with disabled XIP boot header and building the dcd.bin file from your muxing configuration, the MCUXpresso Secure Provisioning tool can be started.
Within the MCUXpresso Secure Provisioning tool main window select FlexSPI NOR – simplified to setup the NOR flash properly. Setup the NOR Flash in the Boot Memory Configuration window.

Afterwards the image for flashing can be built by clicking the Build image button.

STEP 3 - Building

Please ensure that the corresponding DIP Switches are configured for Serial Downloader mode.

Serial Downloader

S3

S4

S5

S6

Setup the target Hardware connection properly (USB or UART1). If UART1 is used for flashing the corresponding COM Port and a baudrate of 115200 has to be configured.

Next, select the write image tab, start the flashloader and finally write the image.

After successfully writing the image, set the DIP Switches to internal boot and perform a powercycle.

Internal Boot

S3

S4

S5

S6

Preface

The aim of this guide is to debug a “Hello World” demo on the Cortex-M7 core of the TQMa117xL using VS code and a SEGGER J-Link.

The instructions on this page refer to the TQMa117xL repository and the associated building guide
Keep in mind that the paths specified in these instructions refer to the test system. Your paths may differ.

Prerequisites

Software/Extention Versions

If not already, please install the following Software and install the Serial Console VS-CODE extention listed in the tables below.

Tool/Extention Version
GitHub Repository MBa117xL.SW.MCU.BSP
VS-Code Version 1.88.1
Segger J-Link for debugging Version v8.83 
ms-vscode.cmake-tools
 CMake tools (from Microsoft): v1.16.3 
marus25.cortex-debug
 Cortex-Debug (from marus25): v1.12.0 
ms-vscode.vscode-serial-monitor
 Serial Monitor (from Microsoft): 0.13.1
Advice: Check if the 'Status-Bar-Visibility' option by the CMAKE extention is set to 'visible'.

Debugging

Debugging

Debugging

Make sure you installed the CP210x Serial to USB driver. If not, please refer to the instructions Starterkit Quicksteps guide.

Set the DIP switches of the MBa117xL as follows to debug via JTAG:

DIP-Switch-Settings

S3

S4

S5

S6

  1. Connect your SEGGER J-Link to JTAG connector X39 on the MBa117xL.
  2. Connect a Micro USB cable to Serial Debug connector X1.
  3. Open your MBa117xL workspace in VS-Code and build a example.
  4. Select Terminal > New Terminal in the top bar
  5. Finaly debug your desired example following the istructions in the video below:

The information provided on this wiki page is subject to change due to circumstances beyond our control. While we strive to keep all details as accurate and up-to-date as possible, it is possible that certain updates or changes may go unnoticed for some time. As a result, some sections of this page may contain outdated information. If you notice any mistakes in the documentation, we kindly ask you to inform the TQ Support through our ticket system.