User manual

www.ti.com
A.4 VLYNQ 2.X Packets
VLYNQ 2.X Packets
The CMD2 bit is only included in the packet if the packet type indicates extended command (PKTTYPE =
0110).
Use configuration packet types to remotely access VLYNQ module registers. The configuration packet
types do not depend on control register bit settings.
An example of what can happen to a write burst due to remote and local FIFO state changes and the link
pulse timer expiring is shown in Example A-1 . This protocol can be extended to apply to multiple channels;
therefore, the data return channel is logically isolated from the command channel.
Example A-1. A Write Burst Due to Remote and Local FIFO State Changes and the Link Pulse
Timer expiring
Basic packets:
Read32 - caaaaT
Write32 - caaaaddddT
ReadCfg - claaaaT
WriteCfg - claaaadddd ddddT
ReadBurst - claaaaT
WriteBurst - claaaadddddddd ddddT
Int - cddddT
ReadReturn - cldddd ddddT
Where
I - Idle
T - EndOfPacket
d - data
a - address
c - command
l - length
M - Byte mask
I[#] - Flowed, # is used when exiting flowed for a channel, the # is actually the current
channel command.
P# - Flow Enable for a channel
C# - Flow Disable for a channel
L - Link pulse
and what is in italics is optional data up to 16 words total.
Packet with byte enables:
WriteBurst - claaaaMMddMMdd MMddT
The above packet wrote to the LS half words from the specified address.
Packet that has been flowed due to remote FIFO status:
WriteBurst - claaaaMMddM IIIIIIIIIIIII#Mdd MMddT
The packet was extended using the I code. The # is used to
indicate that the same channel was continued.
To the same packet, the potential flowing of the local FIFO’s is added:
WriteBurst - claaaaMMddMIIP# IIIIIIIIIIIII#Mdd MMdC# dT
Link pulse to the stream is added:
WriteBurst - claaLaaMMddMIIP# IIIIIIIIIII#Mdd MMdC# dT
48 VLYNQ Protocol Specifications SPRUF89 – October 2007
Submit Documentation Feedback