FSI CPU controlled data frame transfers with Internal Loopback

Table of Contents

• Introduction
• Configurable Parameters
• Watch Variables
• External Connections
• Steps to Run the Example
• See Also

Introduction

Example sets up infinite data frame transfers where trigger happens through CPU. Automatic(Hw triggered) Ping frame transmission is also setup along with data.

For any errors during transfers i.e. error events such as Frame Overrun, Underrun, Watchdog timeout and CRC/EOF/TYPE errors, execution will stop immediately and status variables can be looked into for more details. Execution will also stop for any mismatch between received data and sent ones and also if transfers takes unusually long time (detected through software counters - txTimeOutCntr and rxTimeOutCntr)

Configurable Parameters

User can edit some of configuration parameters as per usecase. These are as below. Default values can be referred in code where these globals are defined

• txUserData - User data to be sent with Data frame
• txDataFrameTag - Frame tag used for Data transfers
• txPingFrameTag - Frame tag used for Ping transfers

Watch Variables

• dataFrameCntr - Number of Data frames transferred
• error - Non zero in case of transmit/receive data mismatch

External Connections

• None

Steps to Run the Example

• When using CCS projects to build, import the CCS project for the required combination and build it using the CCS project menu (see CCS Build Project).
• When using makefiles to build, note the required combination and build using make command (see Makefile based Build)
• Establish connections as mentioned in External Connections section.
• Launch a CCS debug session and run the executable, see Build, Load and Run
• Wait for transmissions to complete, then check error flag and received data + count

See Also

FSI