
www.ti.com
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. If the request has been flow controlled, the peripheral will set the completion code status register and appropriate interrupt bit of the ICSR. The control/command registers can be released after the interrupt service routine completes.
For
1)until the response packet is routed back to the module and the appropriate completion code is set in the status register. One special case exists for outgoing
So the general flow is as follows:
∙LSU registers are written using the configuration bus
∙Flow control is determined
∙TX FIFO free buffer availability is determined
∙DMA bus read request for data payload
∙DMA bus response writes data to specified module buffer in the shared TX buffer space
∙DMA bus read response is monitored for last byte of payload
∙Header data in the LSU registers is written to the shared TX buffer space
∙Payload and header are transferred to the TX FIFO
∙The LSU registers are released if no RapidIO response is needed
∙Transfer from the TX FIFO to external device based on priority
READ Transactions:
The flow for generating READ transactions is similar to
Again, the control/command registers cannot be released (BSY = 1) until the response packet is routed back to the module and appropriate completion code is set in the status register.
So the general flow would be:
∙LSU registers are written using the configuration bus
∙Flow control is determined
∙TX FIFO buffer is allocated
∙Header data in the LSU registers is written to the shared TX buffer
∙Payload and header are transferred to the TX FIFO
∙The LSU registers are released if no RapidIO response is needed
∙Transfer from the TX FIFO to external device based on priority
For all transactions, the shared TX buffers are released as soon as the packet is forwarded to the TX FIFOs. If an ERROR or RETRY response is received for a
38 | Serial RapidIO (SRIO) | SPRU976 |