Echelon FTXL Hardware - Manual (Page 84)

76 Using the Bring-Up Application to Verify FTXL Hardware Design
Read Handshake Read length = 0
Handshake (D0)
busy
Handshake (D0)
ready
A0 low -> D0 is
data
A0 high -> D0
is handshake
Read Null Token
Figure 32. Reading Null Token from the Transceiver
Data Passing Test
The Data Passing Test exercises full two-way communication between the Nios II
processor and the FTXL Transceiver. As with the previous test, this test is
dependent on the proper function of the reset and status registers. However, in
this test, both the Nios II processor and the FTXL Transceiver pass non-zero data
patterns that are sufficient to test each bit of the data register.
At the end of the test, the application purposely causes a transmission timeout,
which causes the FTXL Transceiver to reset, and verifies that the reset capture
register detects this condition. This test, like the others, restores the state of the
FTXL Transceiver so that it is ready for subsequent tests.
This test and the Interrupt Test use the following data declarations for the data
to be sent and received:
/* The host sends downlinkMessage to the */
/* FTXL Transceiver */
const byte downlinkMessage[] = {0x09, 0x52, 0x01, 0x02,
0x04, 0x08, 0x10, 0x20, 0x40, 0x80};
/* The FTXL Transceiver should respond by sending */
/* expectedReply */
const byte expectedReply[] = {0x09, 0x53, 0x69, 0xd8,
0xd7, 0x77, 0x14, 0xd7, 0x3d, 0xf6};
These messages are in the form of a message frame, starting with the length byte
and followed by the data bytes. The null terminator is not included.
These two tests also use a utility function (readUplinkMessage()) to read a
message from the FTXL Transceiver and verify its contents.