SPRADM0 August 2025 F28E120SC , F29H850TU , F29H859TU-Q1 , TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384S , TMS320F28386D , TMS320F28386S , TMS320F28388D , TMS320F28388S , TMS320F28P550SG , TMS320F28P550SJ , TMS320F28P559SG-Q1 , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
A high-level overview of the Application Logging implementation and all the layers involved from Table 3-1 is shown below. Application Logging allows the user to print out strings and arrays of various data types such as signed, unsigned integers and floats.
The following steps can be done to easily add this feature into a CCS project.
Configure the Exporter module settings for the required communication peripheral. For this walk-through example, SCI is used as the communication peripheral. Under the Transfer Communication Link setting, SysConfig automatically adds a communication peripheral available on the device with some default settings that can be edited.
All the configurable communication peripheral settings associated when adding the exporter submodule are shown below.
Additional settings that can be added to enhance the data log captures are under the Export Custom Logs Configuration. Export Log Support check box generates functions that can be used under the export or export_log.h generated files.
Export Log Timestamp is another feature that can be added to log the time that a log was captured. If Export Log Timestamp is enabled, SysConfig automatically adds a CPU Timer module to be configured.
These are all the modules required to be added for the GUI and data logging software layer. The only remaining steps needed to data log strings or variables is to call the export/export_log.h layer helper functions from the application code. Make sure to include the export/export_log.h file at the top of the main code.
//
// Included Files
//
...
#include "export/export_log.h"
Before building the project, make sure to go over Section 4 to enable GUI_SUPPORT. Once this is enabled, build the project and open the GUI within CCS.
EXPORTLOG_log("Logging entry 1");
EXPORTLOG_log("Next log entry 2");
EXPORTLOG_log("last entry 3");
Load the .out file but do not run yet. Verify the correct COM port is selected for the GUI by going to Options → Serial Port Settings...→ <COM Port>
Once the correct COM Port is selected, run the application code. The below image shows the final output. The user can modify these print messages as well as move where in the application the EXPORTLOG_log() functions are called however needed for the specific application and debugging scenario. See Section 9 for a description of other Application Logging examples provided by the C2000ware SDK.