Page 5
5.72 Local Configuration Space Base Address 0 CSR (LCL_CFG_HBAR) 5.73 Local Configuration Space Base Address 1 CSR (LCL_CFG_BAR) 5.74 Base Device ID CSR (BASE_ID) 5.75 Host Base Device ID Lock CSR (HOST_BASE_ID_LOCK) 5.76 Component Tag CSR (COMP_TAG) 5.77 1x/4x LP_Serial Port Maintenance Block Header Register (SP_MB_HEAD) 5.78 Port Link Time-Out Control CSR (SP_LT_CTL) 5.79...
Page 6
RapidIO Architectural Hierarchy RapidIO Interconnect Architecture Serial RapidIO Device to Device Interface Diagrams SRIO Peripheral Block Diagram Operation Sequence 1x/4x RapidIO Packet Data Stream (Streaming-Write Class) Serial RapidIO Control Symbol Format SRIO Conceptual Block Diagram Load/Store Data Transfer Diagram Load/Store Registers for RapidIO (Address Offset: LSU1 0x400-0x418, LSU2 0x420-0x438, LSU3 0x440-0x458, LSU4 0x460-0x478) LSU Registers Timing Example Burst NWRITE_R...
Page 7
Load/Store Module Interrupt Condition Routing Registers Error, Reset, and Special Event Interrupt Condition Routing Registers Sharing of ISDR Bits Example Diagram of Interrupt Status Decode Register Mapping INTDSTn_Decode Interrupt Status Decode Register INTDSTn_RATE_CNTL Interrupt Rate Control Register Peripheral ID Register (PID) Peripheral Control Register (PCR) Peripheral Settings Control Register (PER_SET_CNTL) Peripheral Global Enable Register (GBL_EN)
Page 9
Port Error Rate Threshold CSR n (SPn_ERR_THRESH) Port IP Discovery Timer in 4x mode (SP_IP_DISCOVERY_TIMER) Port IP Mode CSR (SP_IP_MODE) Serial Port IP Prescalar (IP_PRESCAL) Port-Write-In Capture CSR n (SP_IP_PW_IN_CAPTn) Port Reset Option CSR n (SPn_RST_OPT) Port Control Independent Register n (SPn_CTL_INDEP) Port Silence Timer n (SPn_SILENCE_TIMER) Port Multicast-Event Control Symbol Request Register n (SPn_MULT_EVNT_CS) Port Control Symbol Transmit n (SPn_CS_TX)
Page 10
RapidIO Documents and Links Packet Type Pin Description Bits of SERDES_CFGn_CNTL Register (0x120 - 0x12c) Line Rate versus PLL Output Clock Frequency RATE Bit Effects Frequency Range versus MPY Bits of SERDES_CFGRXn_CNTL Registers EQ Bits Bits of SERDES_CFGTXn_CNTL Registers SWING Bits DE Bits Control/Command Register Field Mapping Status Fields...
Page 11
TX CPPI Interrupt Status Register (TX_CPPI_ICSR) Field Descriptions TX CPPI Interrupt Clear Register (TX_CPPI_ICCR) Field Descriptions LSU Status Interrupt Register (LSU_ICSR) Field Descriptions LSU Clear Interrupt Register (LSU _ICCR) Field Descriptions Error, Reset, and Special Event Status Interrupt Register (ERR_RST_EVNT_ICSR) Field Descriptions Error, Reset, and Special Event Clear Interrupt Register (ERR_RST_EVNT_ICCR) Field Descriptions DOORBELLn Interrupt Condition Routing Register (DOORBELLn_ICRR) Field Descriptions DOORBELLn Interrupt Condition Routing Register 2 (DOORBELLn_ICRR2) Field Descriptions...
Page 12
Source Operations CAR (SRC_OP) Field Descriptions Destination Operations CAR (DEST_OP) Field Descriptions Processing Element Logical Layer Control CSR (PE_LL_CTL) Field Descriptions Local Configuration Space Base Address 0 CSR (LCL_CFG_HBAR) Field Descriptions Local Configuration Space Base Address 1 CSR (LCL_CFG_BAR) Field Descriptions Base Device ID CSR (BASE_ID) Field Descriptions Host Base Device ID Lock CSR (HOST_BASE_ID_LOCK) Field Descriptions Component Tag CSR (COMP_TAG) Field Descriptions...
TMS320C645x DSP Peripherals Overview Reference Guide (literature number SPRUE52) provides a brief description of the peripherals available on the TMS320C645x digital signal processors (DSPs). TMS320C6455 Chip Support Libraries (CSL) (literature number SPRC234) is a download with the latest chip support libraries.
Overview The RapidIO peripheral used in the TMS320C645x is called a serial RapidIO (SRIO). This chapter describes the general operation of a RapidIO system, how this module is connected to the outside world, the definitions of terms used within this document, and the features supported and not supported for SRIO.
www.ti.com Figure 1. RapidIO Architectural Hierarchy Logical specification Information necessary for the end point to process the transaction (i.e., transaction type, size, physical address) Transport specification Information to transport packet from end to end in the system (i.e., routing address) Physical specification Information necessary to move packet between two physical devices (i.e., electrical...
www.ti.com Figure 3. Serial RapidIO Device to Device Interface Diagrams Serial RapidIO 1x Device to 1x Device Interface Diagram Serial RapidIO 4x Device to 4x Device Interface Diagram RapidIO Feature Support in SRIO Features Supported in SRIO: RapidIO Interconnect Specification V1.2 compliance, Errata 1.2 LP-Serial Specification V1.2 compliance 4X Serial RapidIO with auto-negotiation to 1X port, optional operation for four 1X ports Integrated clock recovery with TI SERDES...
Overview Features Not Supported: Compliance with the Global Shared Memory specification (GSM) 8/16 LP-LVDS compatible Destination support of RapidIO Atomic Operations Simultaneous mixing of frequencies between 1X ports (all ports must be the same frequency) Target atomic operations (including increment, decrement, test-and-swap, set, and clear) for internal L2 memory and registers Standards The SRIO peripheral is compliant to V1.2 of the RapidIO Interconnect Specification and V1.2 of the...
www.ti.com SRIO Functional Description Overview 2.1.1 Peripheral Data Flow This peripheral is designed to be an external slave module that is capable of mastering the internal DMA. This means that an external device can push (burst write) data to the DSP as needed, without having to generate an interrupt to the CPU.
SRIO Functional Description 1.25-3.125 Gbps differential data Rx Clock recovery Clock recovery Clock recovery Clock recovery Within the physical layer, the data next goes to the 8b/10b decode block. 8b/10b encoding is used by RapidIO to ensure adequate data transitions for the clock recovery circuits. Here the 20% encoding overhead is removed as the 10-bit data is decoded to the raw 8-bit data.
www.ti.com SRIO endpoints are typically not connected directly to each other but instead have intervening connection fabric devices. Control symbols are used to manage the flow of transactions in the SRIO physical interconnect. Control symbols are used for packet acknowledgment, flow control information, and maintenance functions.
SRIO Functional Description Figure 6. 1x/4x RapidIO Packet Data Stream (Streaming-Write Class) address rsrv xamsbs prio tt ftype destID acklD rsv sourcelD acklD sourcelD address rsrv xamsbs destiD prio ftype Note: Figure 6 assumes that addresses are 32-bit and device IDs are 8-bit. The device ID, being an 8-bit field, will address up to 256 nodes in the system.
www.ti.com The type of received packet determines how the packet routing is handled. Reserved or undefined packet types are destroyed before being processed by the logical layer functional blocks. This prevents erroneous allocation of resources to them. Unsupported packet types are responded to with an error response packet.
SRIO Functional Description SRIO Pins The SRIO device pins are high-speed differential signals based on Current-Mode Logic (CML) switching levels. The transmit and receive buffers are self-contained within the clock recovery blocks. The reference clock input is not incorporated into the SERDES macro. It uses a common LVDS input buffer that aligns interfaces with crystal oscillator manufacturers.
www.ti.com Figure 8. SRIO Conceptual Block Diagram DMA bus 128-bit Load/store unit (LSU) Tx direct I/O Maintenance 4.5 KB Tx shared buffer 128-bit TX buffering 32 x 276B 8 buffers per 1X port - all priorities 32 buffers per 4X port - 8 per priority Port 0 8 x 276 TX 8 x 276 RX...
SRIO Functional Description 2.3.2 SERDES and its Configurations SRIO offers many benefits to customers by allowing a scalable non-proprietary interface. With the use of TI’s SERDES macros, the peripheral is very adaptable and bandwidth scalable. The same peripheral can be used for all three frequency nodes specified in V1.2 of the RapidIO specification (1.25, 2.5, and 3.125 Gbps).
SRIO Functional Description Here is the frequency range versus MPY: RIOCLK and RIOCLK Range (MHz) 250 - 425 200 - 425 167 - 354.167 125 - 265.625 100 - 212.5 83.33 - 177.08 12.5x 80 - 170 66.67 - 141.67 50 - 106.25 40 - 85 25 - 42.5...
Page 29
www.ti.com Table 8. Bits of SERDES_CFGRXn_CNTL Registers (continued) Field Value 15:14 13:12 ALIGN Reserved 10:8 TERM INVPAIR RATE BUS- WIDTH Reserved ENRX SPRU976 – March 2006 Submit Documentation Feedback Description Loss of signal. Enables loss of signal detection with 2 selectable thresholds. Disabled.
SRIO Functional Description CFGRX[22:19] 0000 0001 001x 01xx 1000 1001 1010 1011 1100 1101 1110 1111 2.3.2.3 Enabling the Transmitter To enable a transmitter for serialization, the ENTX bit of the associated SERDES_CFGTXn_CNTL registers (0x110 – 0x10c) must be set high. When ENTX is low, all digital circuitry within the transmitter will be disabled, and clocks will be gated off, with the exception of the transmit clock (TXBCLK[n]) output, which will continue to operate normally.
SRIO Functional Description 2.3.2.4 SERDES Configuration Example rdata = SRIO_REGS->SERDES_CFG0_CNTL; wdata = 0x00000001; mask = 0x00000FFF; mdata = (wdata & mask) | (rdata & ~mask); SRIO_REGS->SERDES_CFG0_CNTL SRIO_REGS->SERDES_CFG1_CNTL SRIO_REGS->SERDES_CFG2_CNTL SRIO_REGS->SERDES_CFG3_CNTL SRIO_REGS->SERDES_CFGRX0_CNTL SRIO_REGS->SERDES_CFGRX1_CNTL SRIO_REGS->SERDES_CFGRX2_CNTL SRIO_REGS->SERDES_CFGRX3_CNTL SRIO_REGS->SERDES_CFGTX0_CNTL SRIO_REGS->SERDES_CFGTX1_CNTL SRIO_REGS->SERDES_CFGTX2_CNTL SRIO_REGS->SERDES_CFGTX3_CNTL 2.3.3 DirectIO The DirectIO (Load/Store) module serves as the source of all outgoing direct I/O packets. With Direct I/O, the RapidIO packet contains the specific address where the data should be stored or read in the destination device.
SRIO Functional Description Table 13. Control/Command Register Field Mapping (continued) Control/Command Register RapidIO Packet Header Field Field Packet Type 4 msb = 4b ftype field for all packets and 4 lsb = 4b trans field for packet types 2,5,8. OutPortID Not available in RapidIO header.
www.ti.com LSU_Reg1 LSU_Reg2 LSU_Reg3 LSU_Reg4 LSU_Reg5 Rdy/BSY Completion The following code illustrates an LSU registers programming example. SRIO_REGS->;LSU1_Reg0 = //poll mode, extended address type 2,5,6 SRIO_REGS->;LSU1_Reg1 = //32bit = type 2,5,6. 24bit = type 8 SRIO_REGS->;LSU1_Reg2 = SRIO_REGS->;LSU1_Reg3 = SRIO_REGS->;LSU1_Reg4 = SRIO_REGS->;LSU1_Reg5 = Figure 12 illustrates an example of the data flow and field mappings for a burst NWRITE_R transaction:...
SRIO Functional Description Priority OutPortID LSUn_REG5 Drbll Hop Count Packet 16 15 ackID prio ftype destID sourceID For WRITE commands, the payload is combined with the header information from the control/command registers and buffered in the shared TX buffer resource pool. Finally, it is forwarded to the TX FIFO for transmission.
www.ti.com UDI interface RapidIO transport and physical layers Port x transmission FIFO queues FIFO FIFO 2.3.3.2 TX Operation WRITE Transactions: The TX buffers are implemented in a single SRAM and shared between multiple cores. A state machine arbitrates and assigns available buffers between the LSUs. When the DMA bus read request is transmitted, the appropriate TX buffer address is specified within it.
Page 38
SRIO Functional Description For posted WRITE operations, which do not require a RapidIO response packet, a core may submit multiple outstanding requests. For instance, a single core may have many streaming write packets buffered at any given time, given outgoing resources. In this application, the control/command registers can be released (BSY = 0) to the CPU as soon as the header info is written into the shared TX buffer pool.
Page 39
www.ti.com Segmentation: The LSU handles two types of segmentation of outbound requests. The first type is when the Byte_Count of Read/Write requests exceeds 256 bytes (up to 4KB). The second type is when Read/Write request RapidIO address is non-64b aligned. In both cases, the outgoing request must be broken up into multiple RapidIO request packets.
Page 40
SRIO Functional Description So the general flow is as follows: Previously, the control/command registers were written and the request packet was sent Response Packet Type13, Trans != 0001b arrives at module interface, and is handled sequentially (not based on priority) targetTID is examined to determine routing of a response to the appropriate core The status field of the response packet is checked for ERROR, RETRY or DONE If the field is DONE, it submits DMA bus request and transmits the payload (if any) to DSP address.
www.ti.com 2.3.4.1 RX Operation As message packets are received by the RapidIO ports, the data must be written into memory while maintaining accurate state information that is needed for future processing. For instance, if a message spans multiple packets, information must be saved that allows re-assembly of those packets by the CPU. The CPPI module provides a scheme for tracking single and multi-packet messages, linking messages in queues, and generating interrupts.
SRIO Functional Description This allows the letter and mailbox fields to instead allow four concurrent single-segment messages to sixty-four possible mailboxes (256 total locations) for a source and destination pair. The mailbox mapper directs the inbound messages to the appropriate queue based on a pre-programmed routing table. It bases the decision on the SOURCEID, MSGLEN, MBOX, LETTER, and XMBOX fields of the RapidIO packet.
www.ti.com Figure 17. Queue Mapping Register RXU_MAP_Ln Letter Mask Mailbox Mask R/W-11 R/W-111111 LEGEND: R = Read, W = Write, n = value at reset Figure 18. Queue Mapping Register RXU_MAP_Hn Reserved LEGEND: R = Read, W = Write, n = value at reset The packet manager maintains the RX DMA state of free and used data buffers within the memory space.
SRIO Functional Description If a multi-segment buffer descriptor queue is not currently free, and an Rx port receives another multi-segment message that is destined for that queue, the RX CPPI must send a RETRY RESPONSE packet (Type 13) to the sender, indicating that an internal buffering problem exists. If a multi-segment buffer descriptor queue is busy and there is another incoming multi-segment message with the same SOURCEID, MAILBOX, and LETTER, an ERROR response is sent.
www.ti.com Table 17. RX Buffer Descriptor Field Descriptions Field next_descriptor_pointer buffer_pointer Sop = 1 Eop = 1 ownership Teardown_Complete message_length Src_id SPRU976 – March 2006 Submit Documentation Feedback Description Next Descriptor Pointer: The 32-bit word aligned memory address of the next buffer descriptor in the RX queue.
Page 46
SRIO Functional Description Table 17. RX Buffer Descriptor Field Descriptions (continued) Field mailbox Although the switch fabric must deliver the segments of multi-packet messages in the order they were sent, buffer resources at the receiving endpoint may only become available after the initial segment(s) of a message have had to be retried.
www.ti.com Scenario A - Default Open Switch Retry Scenario B - In order mode Open Switch Retry In addition, multiple messages can be interleaved at the receive port due to ordering within a connected switch’s output queue. This can occur when using a single or multiple priorities. The RX CPPI block must handle simultaneous interleaved multi-segment messages.
SRIO Functional Description Teardown of an Rx queue causes the following actions: If teardown is issued by software during the time when the RX state machine is idle, then the state machine will immediately start the teardown procedure: – If the queue to be torn down is in-message (waiting for one or more segments), then the queue will be torn down and reported with the current buffer descriptor (teardown bit set, ownership bit cleared, CC = 100b).
www.ti.com 2.3.4.2 TX Operation Outgoing messages are handled similarly, with buffer descriptor queues that are assigned by the CPUs. The queues are configured and initialized upon reset. When a CPU wants to send a message to an external RapidIO device, it writes the buffer descriptor information via the configuration bus into the SRAM.
Page 50
SRIO Functional Description Table 20. TX Buffer Descriptor Field Definitions (continued) Field ownership Teardown_Complete retry_count message_length Dest_id Serial RapidIO (SRIO) Description Ownership: Indicates ownership of the message and is valid only on sop. This bit is set by the host and cleared by the port when the message has been transmitted. The host uses this bit to reclaim buffers.
Page 51
www.ti.com Table 20. TX Buffer Descriptor Field Definitions (continued) Field PortID SSIZE mailbox Once the port controls the buffer descriptor, the DEST_ID field can be queried to determine flow control. If the transaction has been flow controlled, the DMA bus READ request is postponed so that the TX buffer space is not wasted.
Page 53
www.ti.com Table 21. Weighted Round Robin Programming Registers (Address Offset 0x7E0 – 0x7EC) Name Access TX_Queue_Map10 [23:16] TX_Queue_Map11 [31:24] TX_Queue_Map12 [7:0] TX_Queue_Map13 [15:8] TX_Queue_Map14 [23:16] TX_Queue_Map15 [31:24] The TX queues are treated differently than the RX queues. A TX queue can mix single and multi-segment message buffer descriptors.
Page 54
SRIO Functional Description Essentially, instead of the 24-bit value representing the period of the response timer, the period is now defined as P = (2^24 x 16)/F. This means the countdown timer frequency needs to be 44.7 – 89.5Mhz for a 6 –...
Page 55
www.ti.com The CPPI module can be powered down if the message passing protocol is not being supported in the application. For example, if the direct I/O protocol is being used for data transfers, powering down the CPPI module will save power. In this situation, the buffer descriptor queue SRAMs and mailbox mapper logic should be powered down.
SRIO Functional Description This value is compared against the port written value in the TX DMA State CP register, if equal, the interrupt is deasserted. Initialization Example SRIO_REGS->Queue0_RXDMA_HDP SRIO_REGS->Queue1_RXDMA_HDP SRIO_REGS->Queue2_RXDMA_HDP SRIO_REGS->Queue3_RXDMA_HDP SRIO_REGS->Queue4_RXDMA_HDP SRIO_REGS->Queue5_RXDMA_HDP SRIO_REGS->Queue6_RXDMA_HDP SRIO_REGS->Queue7_RXDMA_HDP SRIO_REGS->Queue8_RXDMA_HDP SRIO_REGS->Queue9_RXDMA_HDP SRIO_REGS->Queue10_RXDMA_HDP SRIO_REGS->Queue11_RXDMA_HDP SRIO_REGS->Queue12_RXDMA_HDP SRIO_REGS->Queue13_RXDMA_HDP SRIO_REGS->Queue14_RXDMA_HDP SRIO_REGS->Queue15_RXDMA_HDP...
SRIO Functional Description Descriptor Descriptor Start Message Passing SRIO_REGS->Queue0_RXDMA_HDP SRIO_REGS->Queue0_TxDMA_HDP 2.3.5 Maintenance The type 8 MAINTENANCE packet format accesses the RapidIO capability registers (CARs), command and status registers (CSRs), and data structures. Unlike other request formats, the type 8 packet format serves as both the request and the response format for maintenance operations.
www.ti.com 2.3.6 Doorbell The doorbell operation, consisting of the DOORBELL and RESPONSE transactions (typically a DONE response), as shown in Figure another processing element through the interconnect fabric. The DOORBELL transaction contains the info field to hold information and does not have a data payload. This field is software-defined and can be used for any desired purpose;...
Page 60
SRIO Functional Description 2.3.7 Congestion Control The RapidIO Flow Control specification is referenced in and implementation of congestion control within the peripheral. The peripheral is notified of switch fabric congestion through type 7 RapidIO packets. The packets are referred to as Congestion Control Packets (CCPs). The purpose of these packets is to turn off (Xoff), or turn on (Xon) specific flows defined by DESTID and PRIORITY of outgoing packets.
www.ti.com 2.3.8 Endianness RapidIO is based on big endian. This is discussed in detail in section 2.4 of the RapidIO Interconnect specification. Essentially, big endian specifies the address ordering as the most significant bit/byte first. For example, in the 29-bit address field of a RapidIO packet (shown in transmitted first in the serial bit stream is the MSB of the address.
SRIO Functional Description DMA Example The desired operation is to send a Type 8 maintenance request to an external device. The goal is to read 16B of RapidIO MMR from an external device, starting offset 0x0000. This operation involves the LSU block and utilizes the DMA for transferring the response packet payload.
www.ti.com 2.3.9.1 Reset Summary After reset, the state of the peripheral depends on the default register values and the BLKn_EN_INIT tieoff values. You can also perform a hard reset using the software of each logical block within the peripheral via the GBL_EN and BLKn_EN bits.
SRIO Functional Description LEGEND: R = Read, W = Write, n = value at reset LEGEND: R = Read, W = Write, n = value at reset LEGEND: R = Read, W = Write, n = value at reset LEGEND: R = Read, W = Write, n = value at reset LEGEND: R = Read, W = Write, n = value at reset Table 24.
Page 67
www.ti.com Table 24. Enable and Enable Status Bit Field Descriptions (continued) Name BLK1_EN BLK1_EN_STAT BLK2_EN BLK2_EN_STAT BLK3_EN BLK3_EN_STAT BLK4_EN BLK4_EN_STAT BLK5_EN BLK5_EN_STAT BLK6_EN BLK6_EN_STAT BLK7_EN BLK7_EN_STAT BLK8_EN SPRU976 – March 2006 Submit Documentation Feedback Access Description Controls reset to logical block 1, which is the LSU. 0 = Logical block 1 disabled (held in reset, clocks disabled) 1 = Logical block 1 enabled Indicates state of BLK1_EN reset signal.
SRIO Functional Description Table 24. Enable and Enable Status Bit Field Descriptions (continued) Name BLK8_EN_STAT The GBL_EN register is implemented with a single ENABLE bit. This bit is logically ORd with the reset input to the module and is fanned out to all logical blocks within the peripheral. 2.3.9.3 Software Shutdown Details Power consumption must be minimized for all logical blocks that are in shutdown.
www.ti.com Name Access Free Soft PEREN Reserved 31:3 Free Run Mode: (default mode) Peripheral does not respond to EMUSUSP assertion. Module functions normally, irrespective of CPU emulation state. Soft Stop Mode: Peripheral gracefully halts operations. The peripheral halts operation at a point that makes sense both to the internal DMA/data access operation and to the pin interface as described below, after finishing packet reception or transmission in progress: DMA bus DMA master: DMA bus requests in progress are allowed to complete (DMA bus has no...
Page 70
SRIO Functional Description 2.3.11.2 PLL, Ports, Device ID and Data Rate Initializations For example, Enable pll, 333MHz, 4p1x, x20. 3.125 Gbps, full rate, ½ rate, ¼ rate: if (srio4p1x_mode){ rdata = SRIO_REGS->PER_SET_CNTL; wdata = 0x0000014F; 4p1x mask = 0x000001FF; mdata = (wdata & mask) | (rdata & ~mask); SRIO_REGS->PER_SET_CNTL = mdata ;...
SRIO Functional Description 2.3.12 Bootload Capability 2.3.12.1 Configuration It is assumed that an external device will initiate the bootload data transfer and master the DMA interface. Upon reset, the following sequence of events must occur: 1. DSP is placed in SRIO boot mode by HW mode pins. 2.
Interrupt Conditions Interrupt Conditions This section defines the CPU interrupt capabilities and requirements of the peripheral. CPU Interrupts The following interrupts are supported by the RIO peripheral. Error Status: Event indicating that a run-time error was reached. The CPU should reset/resynchronize the peripheral.
www.ti.com The DOORBELL packet’s 16-bit INFO field indicates which DOORBELL register interrupt bit to set. There are four DOORBELL registers, each currently with 16 bits, allowing 64 interrupt sources or circular buffers. Each bit can be assigned to any core as described by the Interrupt Condition Routing Registers. Additionally, each status bit is user-defined for the application.
www.ti.com Where ICS0 - TX CPPI interrupt, buffer descriptor queue 0, through ICS15 - TX CPPI interrupt, buffer descriptor queue 15. Clearing of any ICSR bit is dependent on the CPU writing to the TX DMA State CP. The CPU acknowledges the interrupt after reclaiming all available buffer descriptors by writing the CP value.
Interrupt Conditions Bit 21- Transaction was not sent due to DMA data transfer error, LSU3 Bit 22- Retry Doorbell response received or Atomic Test-and-swap was not allowed (semaphore in use), LSU3 Bit 23- Packet not sent due to unavailable outbound credit at given priority, LSU3 Bit 24- Transaction complete, No Errors (Posted/Non-posted), LSU4 –...
www.ti.com The interrupt conditions are programmable to select the interrupt output that will be driven. Each condition is independently programmable to use any of the interrupt destinations supported by the device. For example, a quad core device may support four CPU servicing interrupt destinations, one per core (INTDST0 for Core0, INTDST1 for Core1, INTDST2 for Core2, and INTDST3 for Core3).
Interrupt Conditions Figure 52. Load/Store Module Interrupt Condition Routing Registers ICR7 R/W-0000 ICR3 R/W-0000 LEGEND: R = Read, W = Write, n = value at reset ICR15 R/W-0000 ICR11 R/W-0000 LEGEND: R = Read, W = Write, n = value at reset ICR23 R/W-0000 ICR19...
www.ti.com Figure 53. Error, Reset, and Special Event Interrupt Condition Routing Registers ERR_RST_EVNT_ICRR (Address Offset 0x02F0) Reserved LEGEND: R = Read, W = Write, n = value at reset ERR_RST_EVNT_ICRR2 (Address Offset 0x02F4) ICR11 R/W-0000 LEGEND: R = Read, W = Write, n = value at reset ERR_RST_EVNT_ICRR3 (Address Offset 0x02F8) LEGEND: R = Read, W = Write, n = value at reset Interrupt Status Decode Registers...
Interrupt Conditions ISDR bits: ISDR bits: As an example, if bit 29 of the ISDR is set, this indicates that there is a pending interrupt on either the TX CPPI queue 2 or RX CPPI queue 2. Figure 55. Example Diagram of Interrupt Status Decode Register Mapping TX CPPI ICRR TX CPPI ICSR TX CPPI ICRR...
www.ti.com LSU bits within the ICSR are logically grouped for a given core and ORd together into a single bit of the decode register. Similarly, the Error/Reset/Special event bits within the ICSR are ORd together into a single bit of the decode register. When either of these bits are set in the decode register, the CPU must make additional reads to the corresponding ICSRs to determine that exact interrupt source.
SRIO Registers SRIO Registers Introduction Table 28 lists the memory-mapped registers for the Serial Rapid IO (SRIO). See the device-specific data manual for the memory address of these registers. Offset Acronym 0x0000 0x0004 0x0020 PER_SET_CNTL 0x0030 GBL_EN 0x0034 GBL_EN_STAT 0x0038 BLK0_EN 0x003C BLK0_EN_STAT...
www.ti.com Peripheral Identification Register (PID) The peripheral identification register (PID) is a constant register that contains the ID and ID revision number for that peripheral. The PID stores version information used to identify the peripheral. All bits within this register are read-only (writes have no effect) meaning that the values within this register should be hard-coded with the appropriate values and must not change from their reset state.
SRIO Registers Peripheral Control Register (PCR) The peripheral control register (PCR) contains a bit that enables or disables the entire peripheral and one bit for every module within the peripheral where this level of control is desired. The module control bits can only be written when the peripheral itself is enabled.
www.ti.com Peripheral Settings Control Register (PER_SET_CNTL) Figure 60. Peripheral Settings Control Register (PER_SET_CNTL) 31-27 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset 14-12 TX_P TX_PRI0_WM CBA_TRANS_PRI RI1_W RW-0x03 0x02 LEGEND: R = Read only; -n = value after reset Table 31.
Page 102
SRIO Registers Table 31. Peripheral Settings Control Register (PER_SET_CNTL) Field Descriptions (continued) Field Value Description 17-15 TX_PRI1_WM Transmit credit threshold. Sets the required number of logical layer TX buffers needed to send priority 1 packets across the UDI interface. This is valid for all ports in 1X mode only. Required buffer count for transmit credit threshold 1 value TX_PRI1_WM: 000 8, 7, 6, 5, 4, 3, 2, 1 001 8, 7, 6, 5, 4, 3, 2...
Page 103
www.ti.com Table 31. Peripheral Settings Control Register (PER_SET_CNTL) Field Descriptions (continued) Field Value Description ENPLL3 Drives SERDES Macro 3 PLL Enable signal Disables macro 3 PLL Enables macro 3 PLL ENPLL2 Drives SERDES Macro 2 PLL Enable signal Disables macro 2 PLL Enables macro 2 PLL ENPLL1 Drives SERDES Macro 1 PLL Enable signal...
SRIO Registers Peripheral Global Enable Register (GBL_EN) Figure 61. Peripheral Global Enable Register (GBL_EN) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 32. Peripheral Global Enable Register (GBL_EN) Field Descriptions Field Value Description...
www.ti.com Peripheral Global Enable Status Register (GBL_EN_STAT) Figure 62. Peripheral Global Enable Status Register (GBL_EN_STAT) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 33. Peripheral Global Enable Status Register (GBL_EN_STAT) Field Descriptions Field Value Description...
SRIO Registers Block n Enable Register (BLKn_EN) There are nine of these registers, one for each of nine logical blocks in the peripheral. LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 34.
www.ti.com Block n Enable Status Register (BLKn_EN_STAT) There are nine of these registers, one for each of nine logical blocks in the peripheral. Figure 64. Block n Enable Status Register (BLKn_EN_STAT) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.11 Packet Forwarding Register n for 16b DeviceIDs (PF_16B_CNTLn) There are four of these registers, to support four ports. Figure 67. Packet Forwarding Register n for 16b DeviceIDs (PF_16B_CNTLn) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
www.ti.com 5.12 Packet Forwarding Register n for 8b DeviceIDs (PF_8B_CNTLn) There are four of these registers, to support four ports. Figure 68. Packet Forwarding Register n for 8b DeviceIDs (PF_8B_CNTLn) LEGEND: R = Read only; -n = value after reset 15-8 8BIT_DEVID_UP_BOUND RW-0xFF...
SRIO Registers 5.13 SERDES Receive Channel Configuration Registers n (SERDES_CFGRXn_CNTL) There are four of these registers, to support four ports. Figure 69. SERDES Receive Channel Configuration Registers n (SERDES_CFGRXn_CNTL) Reserved ALIGN Reserv R/W-0 R/W-0 LEGEND: R = Read, W = Write, n = value at reset Table 40.
www.ti.com Table 40. SERDES Receive Channel Configuration Registers n (SERDES_CFGRXn_CNTL) Field Field Value Description Reserved Reserved. 10:8 TERM Termination. Selects input termination options suitable for a variety of AC or DC coupled scenarios. Common point connected to VDDT. This configuration is for DC coupled systems using CML transmitters.
SRIO Registers 5.14 SERDES Transmit Channel Configuration Registers n (SERDES_CFGTXn_CNTL) There are four of these registers, to support four ports. Figure 70. SERDES Transmit Channel Configuration Registers n (SERDES_CFGTXn_CNTL) R/W-0 LEGEND: R = Read, W = Write, n = value at reset Table 42.
SRIO Registers 5.15 SERDES Macro Configuration Register n (SERDES_CFGn_CNTL) There are four of these registers, to support four ports. Figure 71. SERDES Macros CFG (0-3) Registers (SERDES_CFGn_CNTL) Reserved LEGEND: R = Read, W = Write, n = value at reset Table 45.
www.ti.com 5.16 DOORBELLn Interrupt Status Register (DOORBELLn_ICSR) Each of the four doorbells is supported by a register of this type. Figure 72. DOORBELLn Interrupt Status Register (DOORBELLn_ICSR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 46.
SRIO Registers 5.17 DOORBELLn Interrupt Clear Register (DOORBELLn_ICCR) Each of the four doorbells is supported by a register of this type. Figure 73. DOORBELLn Interrupt Clear Register (DOORBELLn_ICCR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 47.
www.ti.com 5.18 RX CPPI Interrupt Status Register (RX_CPPI_ICSR) Figure 74. RX CPPI Interrupt Status Register (RX_CPPI_ICSR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 48. RX CPPI Interrupt Status Register (RX_CPPI_ICSR) Field Descriptions Field Value Description...
www.ti.com 5.20 TX CPPI Interrupt Status Register (TX_CPPI_ICSR) Figure 76. TX CPPI Interrupt Status Register (TX_CPPI_ICSR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 50. TX CPPI Interrupt Status Register (TX_CPPI_ICSR) Field Descriptions Field Value Description...
www.ti.com 5.22 LSU Status Interrupt Register (LSU_ICSR) Figure 78. LSU Status Interrupt Register (LSU_ICSR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 52. LSU Status Interrupt Register (LSU_ICSR) Field Descriptions Field Value Description...
www.ti.com 5.24 Error, Reset, and Special Event Status Interrupt Register (ERR_RST_EVNT_ICSR) Figure 80. Error, Reset, and Special Event Status Interrupt Register (ERR_RST_EVNT_ICSR) LEGEND: R = Read only; -n = value after reset 15-12 Reserved ICS11 R-0x00 R/W- 0x00 LEGEND: R = Read only; -n = value after reset Table 54.
SRIO Registers 5.25 Error, Reset, and Special Event Clear Interrupt Register (ERR_RST_EVNT_ICCR) Figure 81. Error, Reset, and Special Event Clear Interrupt Register (ERR_RST_EVNT_ICCR) LEGEND: R = Read only; -n = value after reset 15-12 Reserved ICC11 R-0x00 0x00 LEGEND: R = Read only; -n = value after reset Table 55.
www.ti.com 5.26 DOORBELLn Interrupt Condition Routing Register (DOORBELLn_ICRR) Each of the four doorbells is supported by a register of this type. Figure 82. DOORBELLn Interrupt Condition Routing Register (DOORBELLn_ICRR) ICR7 R/W-0x00 ICR3 R/W-0x00 LEGEND: R = Read, W = Write, n = value at reset Table 56.
SRIO Registers 5.27 DOORBELLn Interrupt Condition Routing Register 2 (DOORBELLn_ICRR2) Each of the four doorbells is supported by a register of this type. Figure 83. DOORBELLn Interrupt Condition Routing Register 2 (DOORBELLn_ICRR2) ICR15 R/W-0x00 ICR11 R/W-0x00 LEGEND: R = Read, W = Write, n = value at reset Table 57.
www.ti.com 5.36 Error, Reset, and Special Event Interrupt Condition Routing Register (ERR_RST_EVNT_ICRR) Figure 92. Error, Reset, and Special Event Interrupt Condition Routing Register LEGEND: R = Read only; -n = value after reset 15-12 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset Table 66.
www.ti.com 5.38 Error, Reset, and Special Event Interrupt Condition Routing Register 3 (ERR_RST_EVNT_ICRR3) Figure 94. Error, Reset, and Special Event Interrupt Condition Routing Register 3 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 68.
SRIO Registers 5.39 INTDSTn Interrupt Status Decode Registers (INTDSTn_DECODE) There are eight of these registers. Figure 95. INTDSTn Interrupt Status Decode Registers (INTDSTn_DECODE) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 69.
www.ti.com 5.40 INTDSTn Interrupt Rate Control Registers (INTDSTn_RATE_CNTL) There are eight of these registers. Figure 96. INTDSTn Interrupt Rate Control Registers (INTDSTn_RATE_CNTL) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 70.
SRIO Registers 5.41 LSUn Control Register 0 (LSUn_REG0) There are four of these registers, one for each LSU. Figure 97. LSUn Control Register 0 (LSUn_REG0) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 71.
www.ti.com 5.42 LSUn Control Register 1 (LSUn_REG1) There are four of these registers, one for each LSU. Figure 98. LSUn Control Register 1 (LSUn_REG1) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 72.
SRIO Registers 5.43 LSUn Control Register 2 (LSUn_REG2) There are four of these registers, one for each LSU. Figure 99. LSUn Control Register 2 (LSUn_REG2) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 73.
www.ti.com 5.44 LSUn Control Register 3 (LSUn_REG3) There are four of these registers, one for each LSU. Figure 100. LSUn Control Register 3 (LSUn_REG3) LEGEND: R = Read only; -n = value after reset 15-12 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset Table 74.
SRIO Registers 5.45 LSUn Control Register 4 (LSUn_REG4) There are four of these registers, one for each LSU. Figure 101. LSUn Control Register 4 (LSUn_REG4) 31-30 29-28 27-26 OUTPORTID PRIORITY XAMBS RW-0x00 RW-0x00 RW-0x00 LEGEND: R = Read only; -n = value after reset 15-8 DESTID RW-0x00...
www.ti.com 5.46 LSUn Control Register 5 (LSUn_REG5) There are four of these registers, one for each LSU. Figure 102. LSUn Control Register 5 (LSUn_REG5) LEGEND: R = Read only; -n = value after reset 15-8 HOP_COUNT RW-0x00 LEGEND: R = Read only; -n = value after reset Table 76.
SRIO Registers 5.47 LSUn Control Register 6 (LSUn_REG6) There are four of these registers, one for each LSU. Figure 103. LSUn Control Register 6 (LSUn_REG6) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 77.
www.ti.com 5.48 LSU Congestion Control Flow Mask n (LSU_FLOW_MASKS n) Figure 104. LSU Congestion Control Flow Mask n (LSU_FLOW_MASKS n) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 78.
SRIO Registers 5.49 Queue Transmit DMA Head Descriptor Pointer Registers (QUEUEn_TXDMA_HDP) There are sixteen of these registers. Figure 105. Queue Transmit DMA Head Descriptor Pointer Registers (QUEUEn_TXDMA_HDP) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 79.
www.ti.com 5.50 Queue Transmit DMA Completion Pointer Registers (QUEUEn_TXDMA_CP) There are sixteen of these registers. Figure 106. Queue Transmit DMA Completion Pointer Registers (QUEUEn_TXDMA_CP) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 80.
SRIO Registers 5.51 Queue Receive DMA Head Descriptor Pointer Registers (QUEUEn_RXDMA_HDP) There are sixteen of these registers. Figure 107. Queue Receive DMA Head Descriptor Pointer Registers (QUEUEn_RXDMA_HDP) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 81.
www.ti.com 5.52 Queue Receive DMA Completion Pointer Registers (QUEUEn_RXDMA_CP) There are sixteen of these registers. Figure 108. Queue Receive DMA Completion Pointer Registers (QUEUEn_RXDMA_CP) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 82.
SRIO Registers Transmit CPPI Supported Flow Mask Register 7 (TX_CPPI_FLOW_MASKS7) 31-16 QUEUE15_FLOW_MASK RW-0x01 LEGEND: R = Read only; -n = value after reset Table 84. Transmit CPPI Supported Flow Mask Registers n (TX_CPPI_FLOW_MASKSn) Field Field Value Description QUEUEn_FLOW_ Flow mask queue n MASK Transmit source does not support flow n from table entry for QUEUEn Transmit source does support flow n from table entry for QUEUEn...
www.ti.com 5.63 Flow Control Table Entry Registers (FLOW_CNTLn) There are sixteen of these registers. Figure 119. Flow Control Table Entry Registers (FLOW_CNTLn) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 93.
SRIO Registers 5.64 Device Identity CAR (DEV_ID) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 94. Device Identity CAR (DEV_ID) Field Descriptions Field Value Description 31-16 DEVICEIDENTIT Identifies the type of device.
www.ti.com 5.65 Device Information CAR (DEV_INFO) Figure 121. Device Information CAR (DEV_INFO) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 95. Device Information CAR (DEV_INFO) Field Descriptions Field Value Description...
SRIO Registers 5.66 Assembly Identity CAR (ASBLY_ID) Figure 122. Assembly Identity CAR (ASBLY_ID) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 96. Assembly Identity CAR (ASBLY_ID) Field Descriptions Field Value Description...
www.ti.com 5.67 Assembly Information CAR (ASBLY_INFO) Figure 123. Assembly Information CAR (ASBLY_INFO) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 97. Assembly Information CAR (ASBLY_INFO) Field Descriptions Field Value Description...
SRIO Registers 5.68 Processing Element Features CAR (PE_FEAT) Figure 124. Processing Element Features CAR (PE_FEAT) BRIDG MEMO PROC SWIT ESSO 0x00 0x00 0x01 0x00 LEGEND: R = Read only; -n = value after reset 15-8 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset Table 98.
www.ti.com 5.71 Processing Element Logical Layer Control CSR (PE_LL_CTL) Figure 127. Processing Element Logical Layer Control CSR (PE_LL_CTL) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 101. Processing Element Logical Layer Control CSR (PE_LL_CTL) Field Descriptions Field Value Description...
SRIO Registers 5.72 Local Configuration Space Base Address 0 CSR (LCL_CFG_HBAR) Figure 128. Local Configuration Space Base Address 0 CSR (LCL_CFG_HBAR) Reserv 0x00 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 102.
www.ti.com 5.73 Local Configuration Space Base Address 1 CSR (LCL_CFG_BAR) Figure 129. Local Configuration Space Base Address 1 CSR (LCL_CFG_BAR) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 103.
SRIO Registers 5.74 Base Device ID CSR (BASE_ID) 31-24 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 104. Base Device ID CSR (BASE_ID) Field Descriptions Field Value Description...
www.ti.com 5.75 Host Base Device ID Lock CSR (HOST_BASE_ID_LOCK) See Section 2.4.2 of the RapidIO Specification for description of this register. It provides a lock function that is write-once/reset-able. Figure 131. Host Base Device ID Lock CSR (HOST_BASE_ID_LOCK) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.76 Component Tag CSR (COMP_TAG) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 106. Component Tag CSR (COMP_TAG) Field Descriptions Field Value Description 31-0 COMPONENT_T Software defined component Tag for PE.
SRIO Registers 5.78 Port Link Time-Out Control CSR (SP_LT_CTL) Figure 134. Port Link Time-Out Control CSR (SP_LT_CTL) LEGEND: R = Read only; -n = value after reset 15-8 TIMEOUT_VALUE RW-0xFFFFFF LEGEND: R = Read only; -n = value after reset Table 108.
www.ti.com 5.79 Port Response Time-Out Control CSR (SP_RT_CTL) Figure 135. Port Response Time-Out Control CSR (SP_RT_CTL) LEGEND: R = Read only; -n = value after reset 15-8 TIMEOUT_VALUE RW-0xFFFFFF LEGEND: R = Read only; -n = value after reset Table 109. Port Response Time-Out Control CSR (SP_RT_CTL) Field Descriptions Field Value Description...
SRIO Registers 5.80 Port General Control CSR (SP_GEN_CTL) Figure 136. Port General Control CSR (SP_GEN_CTL) HOST MAST DISCO ER_E VERE NABL 0x00 0x00 0x00 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 110.
www.ti.com 5.81 Port Link Maintenance Request CSR n (SPn_LM_REQ) Each of the four ports is supported by a register of this type. Figure 137. Port Link Maintenance Request CSR n (SPn_LM_REQ) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.82 Port Link Maintenance Response CSR n (SPn_LM_RESP) Each of the four ports is supported by a register of this type. Figure 138. Port Link Maintenance Response CSR n (SPn_LM_RESP) RESP ONSE _VALI 0x00 LEGEND: R = Read only; -n = value after reset 15-10 Reserved R-0x00...
www.ti.com 5.83 Port Local AckID Status CSR n (SPn_ACKID_STAT) Each of the four ports is supported by a register of this type. Figure 139. Port Local AckID Status CSR n (SPn_ACKID_STAT) 31-29 Reserved INBOUND_ACKID R-0x00 LEGEND: R = Read only; -n = value after reset 15-13 Reserved OUTSTANDING_ACKID...
SRIO Registers 5.84 Port Error and Status CSR n (SPn_ERR_STAT) Each of the four ports is supported by a register of this type. Figure 140. Port Error and Status CSR n (SPn_ERR_STAT) 31-27 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset 15-11 Reserved R-0x00...
Page 187
www.ti.com Table 114. Port Error and Status CSR n (SPn_ERR_STAT) Field Descriptions (continued) Field Value Description PORT_OK The input and output ports are initialized and the port is exchanging error-free control symbols with the attached device (read-only). PORT_UNINITIA Input and output ports are not initialized. This bit and bit 1 are mutually exclusive (read-only). LIZED SPRU976 –...
SRIO Registers 5.85 Port Control CSR n (SPn_CTL) Each of the four ports is supported by a register of this type. 31-30 29-27 PORT_WIDTH INITIALIZED_PORT_WI PORT_WIDTH_OVERRI PORT R-0x01 R-0x00 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 115.
Page 189
www.ti.com Table 115. Port Control CSR n (SPn_CTL) Field Descriptions (continued) Field Value Description INPUT_PORT_E Input port receive enable NABLE Port is stopped and only enabled to route or respond I/O logical MAINTENANCE packets, depending upon the functionality of the processing element. Other packets generate packet-not-accepted control symbols to force an error condition to be signaled by the sending device.
www.ti.com 5.89 Logical/Transport Layer High Address Capture CSR (H_ADDR_CAPT) Figure 145. Logical/Transport Layer High Address Capture CSR (H_ADDR_CAPT) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 119. Logical/Transport Layer High Address Capture CSR (H_ADDR_CAPT) Field Descriptions Field Value Description...
www.ti.com 5.93 Port-Write Target Device ID CSR (PW_TGT_ID) Figure 149. Port-Write Target Device ID CSR (PW_TGT_ID) 31-24 DEVICEID_MSB RW-0x00 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 123. Port-Write Target Device ID CSR (PW_TGT_ID) Field Descriptions Field Value Description...
SRIO Registers 5.94 Port Error Detect CSR n (SPn_ERR_DET) Each of the four ports is supported by a register of this type. Figure 150. Port Error Detect CSR n (SPn_ERR_DET) 30-24 ERR_I Reserved MP_S PECIF R-0x00 0x00 LEGEND: R = Read only; -n = value after reset 15-6 Reserved R-0x00...
www.ti.com 5.95 Port Error Rate Enable CSR n (SPn_RATE_EN) Each of the four ports is supported by a register of this type. Figure 151. Port Error Rate Enable CSR n (SPn_RATE_EN) 30-24 EN_IM Reserved P_SPE CIFIC R-0x00 0x00 LEGEND: R = Read only; -n = value after reset 15-6 Reserved R-0x00...
SRIO Registers 5.96 Port n Attributes Error Capture CSR 0 (SPn_ERR_ATTR_CAPT_DBG0) Each of the four ports is supported by a register of this type. Figure 152. Port n Attributes Error Capture CSR 0 (SPn_ERR_ATTR_CAPT_DBG0) 31-30 INFO_TYPE Reserv ERROR_TYPE R-0x00 0x00 LEGEND: R = Read only;...
www.ti.com 5.97 Port n Packet/Control Symbol Error Capture CSR 1 (SPn_ERR_CAPT_DBG1) Each of the four ports is supported by a register of this type. Figure 153. Port n Packet/Control Symbol Error Capture CSR 1 (SPn_ERR_CAPT_DBG1) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.98 Port n Packet/Control Symbol Error Capture CSR 2 (SPn_ERR_CAPT_DBG2) Each of the four ports is supported by a register of this type. Figure 154. Port n Packet/Control Symbol Error Capture CSR 2 (SPn_ERR_CAPT_DBG2) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
www.ti.com 5.99 Port n Packet/Control Symbol Error Capture CSR 3 (SPn_ERR_CAPT_DBG3) Each of the four ports is supported by a register of this type. Figure 155. Port n Packet/Control Symbol Error Capture CSR 3 (SPn_ERR_CAPT_DBG3) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.100 Port n Packet/Control Symbol Error Capture CSR 4 (SPn_ERR_CAPT_DBG4) Each of the four ports is supported by a register of this type. Figure 156. Port n Packet/Control Symbol Error Capture CSR 4 (SPn_ERR_CAPT_DBG4) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
www.ti.com 5.101 Port Error Rate CSR n (SPn_ERR_RATE) Each of the four ports is supported by a register of this type. Figure 157. Port Error Rate CSR n (SPn_ERR_RATE) 31-24 ERROR_RATE_BIAS RW-0xFF LEGEND: R = Read only; -n = value after reset 15-8 PEAK_ERROR_RATE RW-0x00...
SRIO Registers 5.102 Port Error Rate Threshold CSR n (SPn_ERR_THRESH) Each of the four ports is supported by a register of this type. Figure 158. Port Error Rate Threshold CSR n (SPn_ERR_THRESH) 31-24 ERROR_RATE_FAILED_THRESHOLD RW-0xFF LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
www.ti.com 5.103 Port IP Discovery Timer in 4x mode (SP_IP_DISCOVERY_TIMER) Figure 159. Port IP Discovery Timer in 4x mode (SP_IP_DISCOVERY_TIMER) 31-28 DISCOVERY_TIMER RW-0x09 LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 133.
SRIO Registers 5.104 Port IP Mode CSR (SP_IP_MODE) 31-30 SP_MODE IDLE_ TX_FI PW_DI TGT_I SELF_ ERR_ FO_B YPAS R-0x00 0x00 0x00 0x00 LEGEND: R = Read only; -n = value after reset 15-6 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset Table 134.
Page 209
www.ti.com Table 134. Port IP Mode CSR (SP_IP_MODE) Field Descriptions (continued) Field Value Description RST_EN Reset Interrupt Enable. If enabled, the interrupt signal is High when the 4 reset control symbols are received in a sequence Reset interrupt disable Reset interrupt enable RST_CS Reset received status bit.
SRIO Registers 5.105 Serial Port IP Prescalar (IP_PRESCAL) Figure 161. Serial Port IP Prescalar (IP_PRESCAL) LEGEND: R = Read only; -n = value after reset 15-8 Reserved R-0x00 LEGEND: R = Read only; -n = value after reset Table 135. Serial Port IP Prescalar (IP_PRESCAL) Field Descriptions Field Value Description...
www.ti.com 5.106 Port-Write-In Capture CSR n (SP_IP_PW_IN_CAPTn) Each of the four ports is supported by a register of this type. Figure 162. Port-Write-In Capture CSR n (SP_IP_PW_IN_CAPTn) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only; -n = value after reset Table 136.
SRIO Registers 5.107 Port Reset Option CSR n (SPn_RST_OPT) Each of the four ports is supported by a register of this type. Figure 163. Port Reset Option CSR n (SPn_RST_OPT) LEGEND: R = Read only; -n = value after reset 15-8 Reserved R-0x00...
www.ti.com 5.108 Port Control Independent Register n (SPn_CTL_INDEP) Each of the four ports is supported by a register of this type. Figure 164. Port Control Independent Register n (SPn_CTL_INDEP) 28-27 Reserv TX_FL SOFT Reserved _REC R-0x00 0x00 0x00 0x00 LEGEND: R = Read only; -n = value after reset 15-8 MAX_RETRY_THR RW-0x00...
Page 214
SRIO Registers Table 138. Port Control Independent Register n (SPn_CTL_INDEP) Field Descriptions (continued) Field Value Description MAX_RETRY_EN Max_retry_error report enable. If enabled, the Port-Write and interrupt are reported as errors. Max retry error report enable Max retry error report disable MAX_RETRY_ER Max_retry_error bit is set when max_retry_cnt is equal to max_retry_threshold.
www.ti.com 5.109 Port Silence Timer n (SPn_SILENCE_TIMER) Each of the four ports is supported by a register of this type. Figure 165. Port Silence Timer n (SPn_SILENCE_TIMER) 31-28 SILENCE_TIMER RW-0x0B LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
SRIO Registers 5.110 Port Multicast-Event Control Symbol Request Register n (SPn_MULT_EVNT_CS) Each of the four ports is supported by a register of this type. Figure 166. Port Multicast-Event Control Symbol Request Register n (SPn_MULT_EVNT_CS) LEGEND: R = Read only; -n = value after reset LEGEND: R = Read only;...
www.ti.com 5.111 Port Control Symbol Transmit n (SPn_CS_TX) Each of the four ports is supported by a register of this type. Figure 167. Port Control Symbol Transmit n (SPn_CS_TX) 31-29 STYPE_0 RW-0x00 LEGEND: R = Read only; -n = value after reset 15-13 CS_E RW-0x00...
TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions:...
Need help?
Do you have a question about the TMS320C645X and is the answer not in the manual?
Questions and answers