RapidIO Message Unit
MSC8144E Reference Manual, Rev. 3
Freescale Semiconductor
16-71
7.
By reading the inbound message status register (IMxSR[MIQI]), software detects that
the message-in-queue interrupt bit is set and determines that the message-in-queue event
caused the interrupt.
8.
Software processes the frame queue entry to which the frame dequeue pointer address
registers (IMxFQDPAR) are pointing.
9.
Software increments the dequeue pointer address registers (IMxFQDPAR) by setting the
message increment bit (IMxMR[MI]). Software determines whether there are any more
messages to process by reading the queue empty bit (IMxSR[QE]). If the queue is not
empty, the previous two steps are repeated.
10.
Optionally, software reads the enqueue pointer address registers (IMxFQEPAR) and
processes all the received messages. After message processing is complete, the dequeue
pointer address registers (IMxFQDPAR) are written.
11.
Software clears the message-in-queue interrupt bit (IMxSR[MIQI]) by writing a 1 to the
IMxSR[MIQI] bit.
16.3.3.3 Message Steering
Messages are forwarded to the inbound message controllers as follows:
Messages directed to mailbox 0 are forwarded to message controller 0.
Messages directed to mailbox 1, 2, or 3 are forwarded to message controller 1.
16.3.3.4 Retry Response Conditions
The conditions to generate a logical layer retry (response retry) are as follows:
The local memory circular queue is full and a message is received.
The inbound message controller has received at least one segment of a multiple-segment
message but has not received all message segments (as determined by a different RapidIO
source ID, RapidIO destination ID, or mailbox).
A message is received with a higher priority than all previous messages being written to
memory, but it has not completed.
Note:
If all inbound messages have the same RapidIO priority, this condition for generating a
retry does not occur.
16.3.3.5 Inbound Message Controller Interrupts
The inbound message controller generates the inbound message interrupt for several different
events. Each event can be individually enabled:
Message-In-Queue interrupt is generated under one of the following conditions:
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 ...