MSC8144E Reference Manual, Rev. 3
16-52
Freescale
Semiconductor
Serial RapidIO
®
Controller
All message segment transfers for a message transaction must complete before the next
message transaction begins.
Pipelined transmission of a full message in each message controller but all responses must
be received before the next message can be transmitted.
In Chaining mode, the next descriptor can be fetched before the current message
completes (descriptor prefetching).
The message unit supports two inbound message controllers with the following features:
Reception of any mailbox and letter for a single- or multi-segment message.
Segment size up to 256 bytes.
Up to sixteen segment messages with a total payload of up to 4 KB.
Full inbound line rate performance.
Back-to-back message reception of the same or lower priority.
Out-of-order message segment reception.
Concurrent inbound message controller operation.
16.3.2
Outbound Message Controller Operation
The outbound message controller sends messages stored in local memory, and it can operate in
three different modes:
Direct mode. Software programs the necessary registers to point to the beginning of the
message in memory.
Chaining mode. Software programs the necessary registers to point to the beginning of the
first valid descriptor in memory. The descriptor provides all the necessary registers to start
the message transfer.
Multicast mode. A single-segment message can be sent to multiple destinations. Multicast
mode is supported in Direct or Chaining mode.
Each outbound message controller uses a unique identifying number. For example, if there are
two outbound message controllers, message controller 0 uses number 0 and message controller 1
uses number 1.
16.3.2.1 Direct Mode
In Direct mode (OMxMR[MUTM] = 1; see page 16-167) the outbound message controller does
not read descriptors from memory. Instead, it uses the parameters programmed in the outbound
message controller registers to start the transfer. Software initializes all the parameters to start the
message transmission. The message transfer starts when the outbound message controller start
bit, OMxMR[MUS] changes from 0 to 1 and the outbound message controller is not busy. If it is
busy, OMxMR[MUS] the transition from 0 to 1 is ignored. Software should program all the
appropriate registers before setting OMxMR[MUS].
Summary of Contents for MSC8144E
Page 1: ...MSC8144E Reference Manual Quad Core Media Signal Processor MSC8144ERM Rev 3 July 2009 ...
Page 48: ...MSC8144E Reference Manual Rev 3 xlviii Freescale Semiconductor ...
Page 86: ...MSC8144E Reference Manual Rev 3 1 38 Freescale Semiconductor Overview ...
Page 168: ...MSC8144E Reference Manual Rev 3 3 60 Freescale Semiconductor External Signals ...
Page 242: ...MSC8144E Reference Manual Rev 3 5 26 Freescale Semiconductor Reset ...
Page 314: ...MSC8144E Reference Manual Rev 3 8 24 Freescale Semiconductor General Configuration Registers ...
Page 414: ...MSC8144E Reference Manual Rev 3 10 14 Freescale Semiconductor MSC8144E SC3400 DSP Subsystem ...
Page 452: ...MSC8144E Reference Manual Rev 3 11 38 Freescale Semiconductor Internal Memory Subsystem ...
Page 520: ...MSC8144E Reference Manual Rev 3 12 68 Freescale Semiconductor DDR SDRAM Memory Controller ...
Page 1070: ...MSC8144E Reference Manual Rev 3 21 28 Freescale Semiconductor Timers ...