A high level view of the communication logger feature and all the layers involved from Table 3-1 is shown below. The Communication Logger feature displays each element of the received FSI frame in a seperate column of the logging table in the Control Center GUI. The steps needed to add this functionality to a CCS project are described in the following walk-through.

Software Layers

Figure 7-2 Communication Logger Software Layer

Sysconfig Configurations

Figure 7-3 MCU Control Center Module

Figure 7-4 Enable FSI Logger and Communication Logger

Figure 7-5 FSI Communication Logger Configurations

Include Files

//
// Included Files
//
...
#include "export/export.h"
#include "logger/coms_logger.h"

Communication Logger Initialization

//
// Logging Inits
//
EXPORT_init();
COMSLOG_init();

Communication Logger Application Code

while(1)
{
    COMSLOG_transferBufferData();
}

Communication Logger Error Handling (Optional)

void COMSLOG_transferBufferOverflow() {

    //
    // Received too much data too quickly. The transfer buffer overflowed
    // Make the buffer larger
    //
    ESTOP0;

}

void COMSLOG_comsLinkError(uint16_t status) {

    //
    // FSI receive error occurred
    // Bad frames received
    //
    ESTOP0;
}

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 Communication Logger Tool

1. Flash the Communication Logger application to the bridge device
2. Connect the bridge device's FSIRX pins to the primary device 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 Application Logger application project on the primary device
5. Open the generated GUI from inside CCS
6. The final output appears as shown below

Figure 7-6 Final Output