A high level overview of the Rapid Time Logger feature and all the layers involved from Table 3-1 is shown below. The steps to enable the Rapid Time Logger feature on the primary device as well as the enhance Communication Logger feature on the bridge device are described in the following walk-through.

Software Layers

Figure 8-1 Rapid-Time Logger Software Layer

Sysconfig Configurations

Figure 8-2 Rapid-Time Logger SysConfig

For this walk-through, two example message structures have been added in the GUI. Under the Log Message Structure view, add two instances. Each instance represents a specific message structure that is designated in the packet. Different message structure definitions can be used for various application specific purposes (for example: message type 0 is sent before some event and message type 1 is sent after some event in the application). For this example, add four variables named a, b, c, and d in the first log message structure definition. In the second log message structure definition, add another variable named e.

In the above figure, each log variable can have a unique name, variable type, and size. The size is automatically calculated based on the variable type. For this walk-through configure a, b, c, d, and e according to the table for each structure type.

Figure 8-3 Log Message Structure 0 Definitions

Figure 8-4 Log Message Structure 1 Definitions

Include Files and Global Variables

//
// Included Files
//
...
#include "logger/rt_log.h"
uint16_t a = 0;
uint32_t b = 6798004;
float c = -189.4934;
uint16_t d[2] = {19872, 290};
float e[8] = {
                   1243.43, -4399.24, -23.392, 0.0213,
                   -2093, 238.4993, -2390.300, 329.401
            };
volatile uint16_t toggle = 0;

Rapid Time Logger Initialization

//
// Logging Inits
//
RTLOG_init();

Add Rapid Time Logs in Application Code

// Insert delay if required for debugging purposes
DEVICE_DELAY_US(1000000);
if (toggle == 0)
{
    RTLOG_writeLog_0(a, b, c, d);
}
else {
    RTLOG_writeLog_1(e);
}
    toggle ^= 1;

Communication Logger Additional Steps

The only steps left are setting up the communication logger feature for the bridge device as described in Section 7.1 and add some additional steps. TI provides a JSON file that contains encodings for all the variables sent over the FSI TX frame that the communication logger uses to decode the Rapid Time Logger messages. The steps below are needed after the primary project has been configured and the steps from the Section 5.1 have been followed on the bridge project.

1. Select Enable Rapid Time Logger in the MCU Control Center Sysconfig module.
   Figure 8-5 Enable Rapid Time Logger
2. Search for the rt_log.json file located in the build folder of the Rapid Time Logger project.
   1. For example, <workspace_ccs>/<name_of_project>/<build_folder>/syscfg/logger/rt_log.json
   Figure 8-6 Navigate to JSON rt_log.json file

Build the Project

Build the communication logger application code, and make sure to follow the steps in Section 4 to generate the GUI inside CCS.

Testing the Real Time Logger Feature

1. Flash the Communication Logger application project on the bridge device
2. Connect the communication logging device's FSIRX pins to the real time logging device's FSITX pins
   1. Connect primary device FSITX_CLK to bridge device FSIRX_CLK
   2. Connect primary device FSITX_D0 to bridge device FSIRX_D0
   3. Connect primary device FSITX_D1 to bridge device FSIRX_D1 (Optional - if dual data lane is configured in Frame Configuration)
3. Connect the bridge device to the PC by using the USB connector
4. Run the Rapid Time Logger application project on the primary device
5. Open the generated GUI inside CCS
6. The final output appears as shown below

Final Output

Figure 8-7 View the Rapid-Time Log Data in the PC GUI