Texas Instruments TMS320DM646 Series User manual

TMS320DM646x DMSoCVLYNQ Port
User's Guide
Literature Number: SPRUER8December 2007

2 SPRUER8 – December 2007Submit Documentation Feedback

Contents
Preface ............................................................................................................................... 71 Introduction ................................................................................................................ 91.1 Purpose of the Peripheral ....................................................................................... 91.2 Features ........................................................................................................... 91.3 Functional Block Diagram ..................................................................................... 101.4 Industry Standard(s) Compliance Statement ............................................................... 102 Architecture .............................................................................................................. 112.1 Clock Control .................................................................................................... 112.2 Signal Descriptions ............................................................................................. 122.3 Protocol Description ............................................................................................ 122.4 VLYNQ Functional Description ............................................................................... 132.5 Initialization ...................................................................................................... 162.6 Auto Negotiation ................................................................................................ 162.7 Address Translation ............................................................................................ 162.8 Flow Control ..................................................................................................... 192.9 Reset Considerations .......................................................................................... 202.10 Interrupt Support ................................................................................................ 202.11 DMA Event Support ............................................................................................ 232.12 Power Management ............................................................................................ 232.13 Emulation Considerations ..................................................................................... 242.14 Programming Guide ............................................................................................ 243 Registers .................................................................................................................. 243.1 Revision Register (REVID) .................................................................................... 253.2 Control Register (CTRL) ....................................................................................... 263.3 Status Register (STAT) ........................................................................................ 283.4 Interrupt Priority Vector Status/Clear Register (INTPRI) .................................................. 303.5 Interrupt Status/Clear Register (INTSTATCLR) ............................................................ 303.6 Interrupt Pending/Set Register (INTPENDSET) ............................................................ 313.7 Interrupt Pointer Register (INTPTR) ......................................................................... 313.8 Transmit Address Map Register (XAM)...................................................................... 323.9 Receive Address Map Size 1 Register (RAMS1) .......................................................... 333.10 Receive Address Map Offset 1 Register (RAMO1) ........................................................ 333.11 Receive Address Map Size 2 Register (RAMS2) .......................................................... 343.12 Receive Address Map Offset 2 Register (RAMO2) ........................................................ 343.13 Receive Address Map Size 3 Register (RAMS3) .......................................................... 353.14 Receive Address Map Offset 3 Register (RAMO3) ........................................................ 353.15 Receive Address Map Size 4 Register (RAMS4) .......................................................... 363.16 Receive Address Map Offset 4 Register (RAMO4) ........................................................ 363.17 Chip Version Register (CHIPVER) ........................................................................... 373.18 Auto Negotiation Register (AUTNGO) ....................................................................... 374 Remote Configuration Registers ................................................................................. 38Appendix A VLYNQ Protocol Specifications ........................................................................ 39A.1 Special 8b/10b Code Groups ................................................................................. 39A.2 Supported Ordered Sets ....................................................................................... 39
SPRUER8 – December 2007 Table of Contents 3Submit Documentation Feedback

A.3 VLYNQ 2.0 Packet Format .................................................................................... 40A.4 VLYNQ 2.X Packets ............................................................................................ 42Appendix B Write/Read Performance .................................................................................. 44B.1 Write Performance.............................................................................................. 44B.2 Read Performance ............................................................................................. 46
4Contents SPRUER8 – December 2007Submit Documentation Feedback

List of Figures
1 VLYNQ Port Functional Block Diagram ................................................................................. 102 External Clock Block Diagram ............................................................................................ 113 Internal Clock Block Diagram ............................................................................................. 114 VLYNQ Module Structure ................................................................................................. 135 Write Operations ........................................................................................................... 146 Read Operations ........................................................................................................... 157 Example Address Memory Map .......................................................................................... 178 Interrupt Generation Mechanism Block Diagram ....................................................................... 219 Revision Register (REVID) ................................................................................................ 2510 Control Register (CTRL) ................................................................................................... 2611 Status Register (STAT) .................................................................................................... 2812 Interrupt Priority Vector Status/Clear Register (INTPRI) .............................................................. 3013 Interrupt Status/Clear Register (INTSTATCLR) ........................................................................ 3014 Interrupt Pending/Set Register (INTPENDSET) ........................................................................ 3115 Interrupt Pointer Register (INTPTR) ..................................................................................... 3116 Transmit Address Map Register (XAM) ................................................................................. 3217 Receive Address Map Size 1 Register (RAMS1) ...................................................................... 3318 Receive Address Map Offset 1 Register (RAMO1) .................................................................... 3319 Receive Address Map Size 2 Register (RAMS2) ...................................................................... 3420 Receive Address Map Offset 2 Register (RAMO2) .................................................................... 3421 Receive Address Map Size 3 Register (RAMS3) ...................................................................... 3522 Receive Address Map Offset 3 Register (RAMO3) .................................................................... 3523 Receive Address Map Size 4 Register (RAMS4) ...................................................................... 3624 Receive Address Map Offset 4 Register (RAMO4) .................................................................... 3625 Chip Version Register (CHIPVER) ....................................................................................... 3726 Auto Negotiation Register (AUTNGO) ................................................................................... 37A-1 Packet Format (10-bit Symbol Representation) ........................................................................ 40
SPRUER8 – December 2007 List of Figures 5Submit Documentation Feedback

List of Tables
1 VLYNQ Port Pins ........................................................................................................... 122 Address Translation Example (Single Mapped Region) .............................................................. 173 Address Translation Example (Single Mapped Region) .............................................................. 184 VLYNQ Interrupt ............................................................................................................ 205 VLYNQ Register Address Space ......................................................................................... 246 VLYNQ Port Controller Registers ........................................................................................ 257 Revision Register (REVID) Field Descriptions ......................................................................... 258 Control Register (CTRL) Field Descriptions ............................................................................ 269 Status Register (STAT) Field Descriptions ............................................................................. 2810 Interrupt Priority Vector Status/Clear Register (INTPRI) Field Descriptions ........................................ 3011 Interrupt Status/Clear Register (INTSTATCLR) Field Descriptions .................................................. 3012 Interrupt Pending/Set Register (INTPENDSET) Field Descriptions ................................................. 3113 Interrupt Pointer Register (INTPTR) Field Descriptions ............................................................... 3114 Address Map Register (XAM) Field Descriptions ...................................................................... 3215 Receive Address Map Size 1 Register (RAMS1) Field Descriptions ................................................ 3316 Receive Address Map Offset 1 Register (RAMO1) Field Descriptions .............................................. 3317 Receive Address Map Size 2 Register (RAMS2) Field Descriptions ................................................ 3418 Receive Address Map Offset 2 Register (RAMO2) Field Descriptions .............................................. 3419 Receive Address Map Size 3 Register (RAMS3) Field Descriptions ................................................ 3520 Receive Address Map Offset 3 Register (RAMO3) Field Descriptions .............................................. 3521 Receive Address Map Size 4 Register (RAMS4) Field Descriptions ................................................ 3622 Receive Address Map Offset 4 Register (RAMO4) Field Descriptions .............................................. 3623 Chip Version Register (CHIPVER) Field Descriptions................................................................. 3724 Auto Negotiation Register (AUTNGO) Field Descriptions ............................................................ 3725 VLYNQ Port Remote Controller Registers .............................................................................. 38A-1 Special 8b/10b Code Groups ............................................................................................. 39A-2 Supported Ordered Sets .................................................................................................. 39A-3 Packet Format (10-bit Symbol Representation) Description .......................................................... 41B-1 Scaling Factors ............................................................................................................. 45B-2 Expected Throughput (VLYNQ Interface Running at 76.5 MHZ and 99 MHZ) .................................... 45B-3 Relative Performance with Various Latencies .......................................................................... 46
6List of Tables SPRUER8 – December 2007Submit Documentation Feedback

PrefaceSPRUER8 – December 2007
Read This First
About This Document
This document describes the VLYNQ™ communications interface port in the TMS320DM646x DigitalMedia System-on-Chip (DMSoC).
Notational Conventions
This document uses the following conventions.•Hexadecimal numbers are shown with the suffix h. For example, the following number is 40hexadecimal (decimal 64): 40h.•Registers in this document are shown in figures and described in tables.– Each register figure shows a rectangle divided into fields that represent the fields of the register.Each field is labeled with its bit name, its beginning and ending bit numbers above, and itsread/write properties below. A legend explains the notation used for the properties.– Reserved bits in a register figure designate a bit that is used for future device expansion.
Related Documentation From Texas InstrumentsThe following documents describe the TMS320DM646x Digital Media System-on-Chip (DMSoC). Copiesof these documents are available on the Internet at www.ti.com .Tip: Enter the literature number in thesearch box provided at www.ti.com.
The current documentation that describes the DM646x DMSoC, related peripherals, and other technicalcollateral, is available in the C6000 DSP product folder at: www.ti.com/c6000 .
SPRUEP8 —TMS320DM646x DMSoC DSP Subsystem Reference Guide. Describes the digital signalprocessor (DSP) subsystem in the TMS320DM646x Digital Media System-on-Chip (DMSoC).
SPRUEP9 —TMS320DM646x DMSoC ARM Subsystem Reference Guide. Describes the ARMsubsystem in the TMS320DM646x Digital Media System-on-Chip (DMSoC). The ARM subsystem isdesigned to give the ARM926EJ-S (ARM9) master control of the device. In general, the ARM isresponsible for configuration and control of the device; including the DSP subsystem and a majorityof the peripherals and external memories.
SPRUEQ0 —TMS320DM646x DMSoC Peripherals Overview Reference Guide. Provides an overviewand briefly describes the peripherals available on the TMS320DM646x Digital MediaSystem-on-Chip (DMSoC).
SPRAA84 —TMS320C64x to TMS320C64x+ CPU Migration Guide. Describes migrating from theTexas Instruments TMS320C64x digital signal processor (DSP) to the TMS320C64x+ DSP. Theobjective of this document is to indicate differences between the two cores. Functionality in thedevices that is identical is not included.
SPRU732 —TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide. Describes the CPUarchitecture, pipeline, instruction set, and interrupts for the TMS320C64x and TMS320C64x+ digitalsignal processors (DSPs) of the TMS320C6000 DSP family. The C64x/C64x+ DSP generationcomprises fixed-point devices in the C6000 DSP platform. The C64x+ DSP is an enhancement ofthe C64x DSP with added functionality and an expanded instruction set.
SPRU871 —TMS320C64x+ DSP Megamodule Reference Guide. Describes the TMS320C64x+ digitalsignal processor (DSP) megamodule. Included is a discussion on the internal direct memory access(IDMA) controller, the interrupt controller, the power-down controller, memory protection, bandwidthmanagement, and the memory and cache.
SPRUER8 – December 2007 Preface 7Submit Documentation Feedback

www.ti.com
Related Documentation From Texas Instruments
Trademarks
VLYNQ is a trademark of Texas Instruments.
8Read This First SPRUER8 – December 2007Submit Documentation Feedback

1 Introduction
1.1 Purpose of the Peripheral
1.2 Features
User's GuideSPRUER8 – December 2007
VLYNQ Port
The VLYNQ™ communications interface port is a serial interface with a low pin count, high-speedpoint-to-point serial interface in the TMS320DM646x Digital Media System-on-Chip (DMSoC) forconnecting to host processors and other VLYNQ compatible devices. The VLYNQ port is a full-duplexserial bus where transmit and receive operations occur separately and simultaneously withoutinterference.
VLYNQ enables the extension of an internal bus segment to one or more external physical devices. Theexternal devices are mapped to local physical address space and appear as if they are on the internal busof the DM646x DMSoC. The external devices must also have a VLYNQ interface.
VLYNQ uses a simple block code (8b/10b) packet format and supports in-band flow control so that noextra terminals are needed to indicate that overflow conditions might occur.
The VLYNQ module on the DM646x DMSoC serializes a write transaction to the remote/external deviceand transfers the write via the VLYNQ port (TX pins). The remote VLYNQ module deserializes thetransaction on the other side.
The read transactions to the remote/external device follow the same process, but the remote device'sVLYNQ module serializes the read return data and transfers it to the VLYNQ port (RX pins). The readreturn data is finally deserialized and released to the device internal bus.
The external device can also initiate read and write transactions.
The general features of the VLYNQ port are:•Low pin count (10 pin interface, scalable to as low as 3 pins)•No tri-state signals– All signals are dedicated and driven by only one device– Necessary to allow support for high-speed PHYs•Scalable Performance
– Programmable frequency and 1 to 4 bits for TX and RX data– Performance increases linearly as the data port width increases•Simple packet-based transfer protocol for memory-mapped access– Write request/data packet– Read request packet– Read response data packet– Interrupt request packet•Auto width negotiation
SPRUER8 – December 2007 VLYNQ Port 9Submit Documentation Feedback

www.ti.com
1.3 Functional Block Diagram
Slave
config
bus
Interface
Master
config
Interface
bus
VLYNQ module
VLYNQ register
access
CPU/EDMA initiated
transfers to
remote device
Off chip
(remote)
device access
ARM/EDMA
memory
System
VLYNQ_SCRUN
VLYNQ_CLOCK
VLYNQ_RXD[3:0]
VLYNQ_TXD[3:0]
INT38
ARM interrupt
controller
VLQINT
1.4 Industry Standard(s) Compliance Statement
Introduction
•Symmetric Operations– Transmit (TX) pins on the first device connect to the receive (RX) pins on the second device andvice-versa.
– Data pin widths are automatically detected after reset– Re-request packets, response packets, and flow control information are all multiplexed and sentacross the same physical pins.– Supports both host/peripheral and peer-to-peer communication models•Simple block code packet formatting (8b/10b)•Supports in-band and flow control– No extra pins are needed– Allows the receiver to momentarily throttle the transmitter back when overflow is about to occur– Uses the special built-in block code capability to interleave flow control information seamlessly withuser data•Automatic packet formatting optimizations•Internal loopback modes are provided
Figure 1 shows a functional block diagram of the VLYNQ port.
Figure 1. VLYNQ Port Functional Block Diagram
VLYNQ is an interface defined by Texas Instruments and does not conform to any other industry standard.
VLYNQ Port10 SPRUER8 – December 2007Submit Documentation Feedback

www.ti.com
2 Architecture
2.1 Clock Control
CLKDIR=0
VLYNQ
DMxxx device
VLYNQ.CLK
CLKDIR=0
VLYNQ
VLYNQ device
CLKDIR=1
VLYNQ
DMxxx device
VLYNQ.CLK
CLKDIR=0
VLYNQ
VLYNQ device
Don't
care
VLYNQ
internal
sys clk
Architecture
This section discusses the architecture and basic functions of the VLYNQ peripheral.
The VLYNQ internal system clock is derived from SYSCLK3, which is the PLL0 clock divided by 4. Fordetailed information on the PLLs and clock distribution on the processor, see the TMS320DM646x DMSoCARM Subsystem Reference Guide (SPRUEP9 ). The module's serial clock direction and frequency aresoftware configurable through the CLKDIR and CLKDIV bits in the VLYNQ control register (CTRL). TheVLYNQ serial clock can be sourced from the internal system clock (CLKDIR = 1) or by an external clocksource (CLKDIR = 0) for its serial operations.
The CLKDIV bit can divide the serial clock (1/1 to 1/8) down when the internal clock is selected as thesource. The serial clock is not affected by the CLKDIV bit values if the serial clock is externally sourced.For the maximum serial clock the VLYNQ supports, see the device-specific data manual.
The reset value of the CLKDIR bit is 0 (external clock source).
The external clock source is shown in Figure 2 . The internal clock source is shown in Figure 3 .
Figure 2. External Clock Block Diagram
Figure 3. Internal Clock Block Diagram
SPRUER8 – December 2007 VLYNQ Port 11Submit Documentation Feedback

www.ti.com
2.2 Signal Descriptions
2.3 Protocol Description
Architecture
The VLYNQ module on the DM646x device is configurable for a 1 to 4 bit-wide RX/TX.
If the configured width does not match the number of transmit/receive lines that are available on theremote device, negotiation between the two VLYNQ devices automatically configures the width (seeSection 2.6 ).
The VLYNQ interface signals are shown in Table 1 .
Table 1. VLYNQ Port Pins
Pin Name Signal Name I/O Description
VLYNQ_CLOCK VLYNQ serial clock I/O The VLYNQ reference clock supports the internally or externally generatedclock.VLYNQ_SCRUN VLYNQ serial clock I/O The VLYNQ serial clock run request allows remote requests for the VLYNQrun request serial clock to be turned off for system power management.(Active low) Low: The request VLYNQ serial clock is active.High: The VLYNQ serial clock is requested to be high when all transactions arecomplete.VLYNQ_RXD[0:3] VLYNQ receive data I VLYNQ receive data is synchronous with the VLYNQ serial clock.VLYNQ_TXD[0:3] VLYNQ transmit data O VLYNQ transmit data is synchronous with the VLYNQ serial clock.
VLYNQ relies on 8b/10b block coding to minimize the number of serial pins and allows for in-band packetdelineation and control.
Appendix A provides general information on 8b/10b coding definitions and their implementation within theVLYNQ module in the DM646x device.
VLYNQ Port12 SPRUER8 – December 2007Submit Documentation Feedback

www.ti.com
2.4 VLYNQ Functional Description
Address
translation commands
Outbound Outbound
command
FIFO
data
Return
FIFO
data
FIFO
Return
command
Inbound
FIFO
Registers
translation
Address
TxSM 8B/10B
encoding Serializer
commands
Inbound RxSM Deserializer
decoding
8B/10B
Serial
TxData
Serial
TxClk
Serial
RxClk
Serial
RxData
Master
config bus
interface
System clock VLYNQ clock
Slave
config bus
interface
(FIFO3)
(FIFO2)
(FIFO0)
(FIFO1)
2.4.1 Write Operations
Architecture
The VLYNQ core supports both host-to-peripheral and peer-to-peer communication models and issymmetrical. The VLYNQ module structure is shown in Figure 4 .
Figure 4. VLYNQ Module Structure
The VLYNQ core module implements two 32-bit configuration bus interfaces. Transmit operations andcontrol register access require the slave configuration bus interface. The master configuration businterface is required for receive operations. Converting to and from the 32-bit bus to the external serialinterface requires serializer and deserializer blocks.
8b/10b block coding encodes data on the serial interface. Frame delineation, initialization, and flow controluse special overhead code groups.
FIFOs buffer the entire burst on the bus for maximum performance, thus minimizing bus latency. Usingwrite operations of each VLYNQ module interfaced is typically recommended to ensure the bestperformance on both directions of the link.
Write requests that initiate from the slave configuration bus interface of the local device write to theoutbound command (CMD) FIFO. Data is subsequently read from the FIFO and encapsulated in a writerequest packet. The address is translated, and the packet is encoded and serialized before beingtransmitted to remote device. The remote device subsequently deserializes and decodes the receive dataand writes it into the inbound CMD FIFO. A write operation initiates on the remote device’s masterconfiguration bus interface after reading the address and data from the FIFO.
The data flow between two VLYNQs that are connected is shown in Figure 5 . In the example shown inFigure 5 , the write originates from the DM646x device.
SPRUER8 – December 2007 VLYNQ Port 13Submit Documentation Feedback

www.ti.com
Address
translation commands
Outbound Outbound
command
FIFO
data
Return
FIFO
data
FIFO
Return
command
Inbound
FIFO
Registers
translation
Address
TxSM 8B/10B
encoding Serializer
commands
Inbound RxSM Deserializer
decoding
8B/10B
Serial
TxData
Serial
RxData
System clock
Address
translation
Registers
commands
Inbound
translation
Address
commands
Outbound
8B/10B
decoding
FIFO
FIFO
command
Inbound
data
Return
FIFO
RxSM Deserializer
RxData
Serial
encoding
8B/10B
VLYNQ Clock
command
Return
data
FIFO
Outbound
TxSM Serializer
TxData
Serial
Slave
config bus
interface
System clock VLYNQ clock
Local VLYNQ
Remote VLYNQ
Master
config bus
interface
Master
config bus
interface
Slave
config bus
interface
2.4.2 Read Operations
Architecture
Figure 5. Write Operations
Read requests from the slave configuration bus interface are written to the outbound CMD FIFO (similar tothe write requests). Data is subsequently read from the FIFO and encapsulated into a read requestpacket. The packet is encoded and serialized before it is transmitted to the remote device. Next, theremote device deserializes, decodes the receive data, and writes the receive data to the inbound CMDFIFO. After reading the address from the FIFO, a master configuration bus interface read operationinitiates in the remote device. When the remote master configuration bus interface receives the read data,the data is written to the return data FIFO before it is encoded and serialized. When the receive datareaches the local VLYNQ module, it is deserialized, decoded, and written to the return data FIFO (localdevice). Finally, the read data is transferred on the local device’s slave configuration interface.
The data flow between two connected VLYNQ devices with read requests that originate from the DM646xdevice is shown in Figure 6 . The remote VLYNQ device returns the read data. Read data is shown withdotted arrows.
14 VLYNQ Port SPRUER8 – December 2007Submit Documentation Feedback

www.ti.com
Address
translation commands
Outbound Outbound
command
FIFO
data
Return
FIFO
data
FIFO
Return
command
Inbound
FIFO
Registers
translation
Address
TxSM 8B/10B
encoding Serializer
commands
Inbound RxSM Deserializer
decoding
8B/10B
Serial
TxData
Serial
RxData
System clock
Address
translation
Registers
commands
Inbound
translation
Address
commands
Outbound
8B/10B
decoding
FIFO
FIFO
command
Inbound
data
Return
FIFO
RxSM Deserializer
RxData
Serial
encoding
8B/10B
VLYNQ Clock
command
Return
data
FIFO
Outbound
TxSM Serializer
TxData
Serial
Slave
config bus
interface
VLYNQ Clock
System clock
Local VLYNC
Remote VLYNQ
Master
config bus
interface
Slave
config bus
interface
Master
config bus
interface
Architecture
Figure 6. Read Operations
Note: Not servicing read operations results in deadlock. The only way to recover from a deadlocksituation is to perform a hard reset. Read operations are typically not serviced due to readrequests that are issued to a non-existent remote VLYNQ device or they are not serviceddue to trying to perform reads on the VLYNQ memory-map prior to establishing the link.
Generally, you should not use read operations to transfer data packets since the serial nature of theinterface could potentially result in longer latencies.
SPRUER8 – December 2007 VLYNQ Port 15Submit Documentation Feedback

www.ti.com
2.5 Initialization
2.6 Auto Negotiation
2.7 Address Translation
Architecture
Since VLYNQ devices can be controlled solely over the serial interface (that is, no local CPU exists), anautomatic reliable initialization sequence (without user configuration) establishes a connection betweentwo VLYNQ devices, just after a VLYNQ module is enabled and auto-negotiation occurs. Auto-negotiationis defined in Section 2.6 . The same sequence is used to recover from error conditions.
Bit 0 in the VLYNQ status register (LINK bit) is set to 1 when a link is established.
A link pulse timer generates a periodic link code every 2048 serial clock cycles. The link is lost when timeexpires and no link code has been detected during a period of 4096 serial clock cycles.
Auto-negotiation occurs after reset. It involves placing a negotiation protocol in the outbound data andprocessing the inbound data to establish connection information. The width of the data pins on the serialinterface is automatically determined at reset as a part of the initialization sequence. For a connectionbetween two VLYNQ devices of version 2.0 and later (VLYNQ on DM646x device is version 2.6), thenegotiation protocol using the available serial pins is used to convey the maximum width capability of eachdevice. The TXD data pins are not required to have the same width as the RXD data pins.
The auto width negotiation does not occur until after completion of the VLYNQ 1.x legacy widthconfiguration, which involves a period of 2000 VLYNQ 1.x system clock cycles for connection to VLYNQ1.x devices. After the VLYNQ 1.x has determined its width, it receives the VLYNQ2.x auto widthnegotiation protocol. The VLYNQ 1.x device does not recognize this protocol and transmits error codesover the serial interface. The received error codes allow the VLYNQ 2.x devices to determine how manyserial pins are valid on the connected VLYNQ 1.x device.
Once the width is established, VLYNQ further identifies the version (version 1.x or version 2.x ) of theremote VLYNQ. This better determines the capabilities of the connected VLYNQ device. This is softwarereadable via the VLYNQ auto-negotiation register (AUTNGO), bit 16 (0 = Ver 1.x , 1 = Ver 2.x), after thelink has been established.
Once a link is established, remote VLYNQ device(s) are memory mapped into the local (host) device'saddress space, similar to any other on chip peripherals. Part of the initialization sequence is to enumeratethe VLYNQ devices (single or multiple) into a coherent memory map for accessing each device.
After the enumeration, the host (local) device can access the remote device address map using localdevice addresses. The VLYNQ module in the host device manages the address translation of the localaddress to the remote address. A remote VLYNQ device is mapped to the local device’s address via theaddress map registers (TX address map, RX address map size n, RX address map offset n, where n= 1to 4). The transmit side has a contiguous map; the size of the map is the same as the remote device map.Figure 7 illustrates this mapping.
In the local device, the address of the VLYNQ Remote Memory Map in the local configuration space willbe the transmit address accessing remote device's over the serial interface and is programmed in the TXAddress Map (XAM) register. When the local device transmits, it first strips off the transmit address offsetin local device memory map. Then sends the data with an address offset from the transmit address.
VLYNQ allows each receive packet address to be translated into one of the four mapped regions. The sizeand offset of each memory region must be aligned to 32-bit words. No restriction is placed onprogramming the size or on the offset of each mapped region, as long as the total memory that is mappedinto these one to four regions is not more then 64 MBytes.
Note: Care should be taken while programming the receive address map size register (RAMS n)and the receive address map offset register (RAMO n) values. These registers should beprogrammed with valid address locations and memory size to match the devicespecifications. See the Memory Map Summary and the System Interconnect sections in yourdevice-specific data manual to identify the valid memory regions that can be accessed by anoff-chip peer device through the VLYNQ interface.
16 VLYNQ Port SPRUER8 – December 2007Submit Documentation Feedback

www.ti.com
Map region 1
Map region 2
Map region 3
Map region 4
4C00 0000h
4C40 0000h
4C3F FFFFh
4C40 0100h
4C40 00FFh
4C41 0100h
4C41 00FFh
4C42 00FFh
Map region 1
Map region 2
Map region 3
Map region 4
Local device Remote device
0000 0000h
003F FFFFh
0040 0000h
0040 00FFh
0500 0000h
0500 FFFFh
0B00 0000h
0B00 FFFFh
ArchitectureAt the remote device, the transmitted address is used to determine, which remote mapped region is beingaccessed. This is achieved by summing each memory size sequentially until the memory size is largerthan the transmitted address. The last memory size added is the region targeted. The remote map isspecified by a memory size and an offset, programmed in the RX Address Map Size (RAMS n) registerand RX Address Map Offset (RAMO n) in the remote device. Figure 7 illustrates one possible memorymap.
Figure 7. Example Address Memory Map
The following section shows an example illustrating the address translation used in each VLYNQ module.
Table 2 illustrates address map register configuration when the DM646x device is transmitting data to theremote device.
Table 2. Address Translation Example (Single Mapped Region)
Register DM646x VLYNQ Module Remote VLYNQ Module
TX Address Map 4C00 0000h Do not careRX Address Map Size 1 Do not care 0000 0100hRX Address Map Offset 1 Do not care 0800 0000h
SPRUER8 – December 2007 VLYNQ Port 17Submit Documentation Feedback

www.ti.com
Architecture
DM646x VLYNQ Module:
4C00 0054h Initial address at the slave configuration bussubtract 4C00 0000h TX Address Map Register (no need to change the reset value for DM646x , forthis register)0000 0054h Translated address to remote device via serial interface
Remote VLYNQ Module:
0000 0054h Initial address from the RX serial interfacecompare 0000 0100h RX address map size 1 register0000 0054hadd 0800 0000h RX address map offset 1 register0800 0054h Translated address to remote device
The local address 4C00 0054h was translated to 0800 0054h on the remote VLYNQ device in Table 3 .
Table 3 illustrates the address map register configuration when the DM646x device is receiving data fromthe remote device.
Table 3. Address Translation Example (Single Mapped Region)
Register DM646x VLYNQ Module Remote VLYNQ Module
TX Address Map Do not care 0400 0000hRX Address Map Size 1 0000 0100h Do not careRX Address Map Offset 1 0200 0000h Do not careRX Address Map Size 2 0000 0100h Do not careRX Address Map Offset 2 8200 0000h Do not care
Remote VLYNQ Module:
0400 0154h Initial address at the slave configuration bus of the remote devicesubtract 0400 0000h TX address map register0000 0154h Translated address to remote device via serial interface
DM646x VLYNQ Module:
0000 0154h Initial address from the RX serial interfacecompare 0000 0100h RX address map size 1 register0000 0154h The RX packet address is greater than the value in the RX address map size 1registercompare 0000 0200h RX address map size 1 register + RX address map size 2Since the RX packet address < the RX address map size 1 register +RX address map size 2 registeradd 8200 0000h RX address map offset 2 registersubtract 0000 0100h RX address map size 1 register8200 0054h Translated address to DM646x device
VLYNQ Port18 SPRUER8 – December 2007Submit Documentation Feedback

www.ti.com
2.8 Flow Control
Architecture
Example 1. Address Translation Example
The remote address 0400 0154h (or 0000 0054h) was translated to 8200 0054h on the DM646x (local)device.
The translated address for packets received on the serial interface is determined as follows:
If ( RX Packet Address < RX Address Map Size 1 Register) {Translated Address = RX Packet Address +RX Address Map Offset 1 Register
} else if ( RX Packet Address < (RX Address Map Size 1 Register +RX Address Map Size 2 Register)) {Translated Address = RX Packet Address +RX Address Map Offset 2 Register -RX Address Map Size 1 Register} else if ( RX Packet Address < (RX Address Map Size 1 Register +RX Address Map Size 2 Register +RX Address Map Size 3 Register)) {Translated Address = RX Packet Address +RX Address Map Offset 3 Register -RX Address Map Size 1 Register -RX Address Map Size 2 Register
} else if ( RX Packet Address < (RX Address Map Size 1 Register +RX Address Map Size 2 Register +RX Address Map Size 3 Register +RX Address Map Size 4 Register)) {Translated Address = RX Packet Address +RX Address Map Offset 4 Register -RX Address Map Size 1 Register -RX Address Map Size 2 Register -RX Address Map Size 3 Register} else {Translated Address = 0x0
}
Multiple VLYNQ modules may be included on any device so that VLYNQ serial interfaces aredaisy-chained effectively. The only requirement is that the address translation registers are configuredto include the outbound VLYNQ module of the remote device.
The VLYNQ module includes flow control features. The VLYNQ module automatically generates flowcontrol enable requests, /P/, when the RX/inbound FIFOs (FIFO1 and FIFO2) resources are consumed.The FIFOs can take up to 16 32-bit words.
The remote device will begin transmitting idles, /I/, starting on the first byte boundary following reception ofthe request. When sufficient RX FIFO resources have been made available, a flow control disable request,/C/, is transmitted to the remote device. In response, the remote device will resume transmission of data.See Appendix A .
SPRUER8 – December 2007 VLYNQ Port 19Submit Documentation Feedback

www.ti.com
2.9 Reset Considerations
2.9.1 Software Reset Considerations
2.9.2 Hardware Reset Considerations
2.10 Interrupt Support
2.10.1 Interrupt Events and Requests
Architecture
Peripheral clock and reset control is done through the power and sleep controller (PSC) module that isincluded with the device. For more information, refer to the power management section (Section 2.12 ).Additionally, there is a software reset (the reset bit in the VLYNQ control register, CTRL) within theperipheral itself. Writing a 1 to the reset bit resets all of the internal state machines of the VLYNQ module,the serial interface is disabled, and the link is lost. The VLYNQ module remains in reset until the softwareclears the bit.
Note: When setting the reset bit, the VLYNQ status register (STAT) value is the only value that isset to the default value. All of the other VLYNQ memory-mapped registers retain their valuesprior to the software reset.
When a hardware reset occurs, the VLYNQ peripheral resets its register values to the default values andthe serial interface is disabled. After a hardware reset, the VLYNQ memory mapped registers and anychip-level registers that are associated with VLYNQ (for example, pin multiplexing registers) must beconfigured appropriately before data transmission can resume.
CAUTION
Be cautious when only resetting one of the VLYNQ devices after two or moreVLYNQ devices have established a link. If only one of the VLYNQ devices is inreset, then no data activity can occur across the serial interface during the timeof reset.
The VLYNQ module has a single interrupt source (Table 4 ) mapped to the ARM interrupt controller(AINTC). For more information on the ARM interrupt controller (AINTC), see the TMS320DM646x DMSoCARM Subsystem Reference Guide (SPRUEP9 ).
Table 4. VLYNQ Interrupt
ARM Event Acronym Source
38 VLQINT VLYNQ
Interrupts generate when bits are set in the VLYNQ interrupt pending/set register (INTPENDSET). Bits areset in the INTPENDSET register when any of the following occur:•Writing directly to the INTPENDSET•Remote interrupt (via the serial interrupt packet)•Serial bus error
When the VLYNQ interrupt pending/set register (INTPENDSET) is a non-zero value, the method offorwarding the interrupt status depends on the state of the INTLOCAL bit in the VLYNQ control register(CTRL).
20 VLYNQ Port SPRUER8 – December 2007Submit Documentation Feedback