SPRUIW9C October 2021 – March 2024 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1
Once the transmitter and receiver modules have been configured, some synchronization must occur before the modules exchange data. Since the receiver accepts data on any clock transition, the receiver core logic must be flushed to properly interpret the start of a new, valid frame. This is especially true when the FSI modules reside on separate devices and are possibly isolated.
The following example provides a suggested approach for establishing a clean communication link on two separate devices that power up in an arbitrary order. Note that this is only a sample synchronization. Depending on application requirements, a different approach can be followed. The single, most important aspect of synchronization is to make sure that the receiver is properly flushed and ready to receive a complete frame without error. How to achieve this is up to the application.
Figure 31-18 shows the connection of the devices in this example. While there is no true concept of a master device or a slave device node in the FSI protocol, the example uses this nomenclature as a simple way to describe the data flow.
Device 1 is the master node; it is the driver of the initialization sequence. Device 2 is the slave node; it responds to the master device commands. In this example, as well as in a real world use-case, neither the master device nor the slave device knows precisely when the other is ready to receive communication.
Sample sequences for both the master device and slave device are provided in the following subsections.