The DLT tool can be found under the MCU Mission Control and Transfer Module within SysConfig.

The first step to adding DLT tooling support is adding the MCU Mission Control module. Once this module is added, there are a few files that get generated to create the final GUI that is shown in CCS. All these files create the front end of the GUI Composer application and the back end required to process incoming data to the GUI.

This sub module generates all the necessary GUI elements needed for the visualization of the DLT tool. The next item to add is to enable Custom Export Logger.

This module assists with defining a package mode that is used to send out the DLT packet to the GUI and what communication peripheral to use. Once enabled, the next option to enable is the DLT Logger.

Once Enable Custom Export Logger is enabled, there are a few configurable options that can be selected. The options can be viewable under the Exporter tab. The tab looks like Figure 6-6.

Change the Package Mode to be START/END. SysConfig generates a software layer to send out data through simple APIs that can be found under the following generated files.

The files being generated are used to package the data in a specified format before exporting the data out of the device. Under export and export_package.c, there are various functions that can be used to export data out of the device. In this application note, the focus is on the DLT support API being generated out of SysConfig. Below are the main files used to export a DLT log and visualize through the GUI.

Inside of dlt/export_dltpackage.h, there is a high level API that can be used to export a uint32_t array of size 2 to the GUI.

Under the Exporter module, open the Transmit Frame Definition and add a new key type called DLTlog where the value type is 32-bit unsigned int. The hash table ID must be 49 for GUI composer to know what packet is being received on the GUI side.

For the correct pinmux to use the UART on the controlSOM, select GPIO42 for UART_TX and GPIO43 for UART_RX.

Once the MCU Mission Control is added and enable customer export logger is selected. Under the Enable DLT Logger checkbox, the CPU Clock Freq must be added that is being used by the device. The clock frequency is used to determine the timer values that is associated with each log.

When enabling the Enable DLT Logger checkbox, the dlt/generate_assoc_table_v1.01.00.js javascript file gets generated and is used to parse source code information through the compiler tool’s Abstract Syntax Tree (AST) dump. This javascript file is used to find the DLT intrinsics that are being used and to be able to display them on the GUI.

The header files must be included to add to application project to use the generated SysConfig support.