MPC8536E-ANDROID Freescale Semiconductor, MPC8536E-ANDROID Datasheet - Page 1199

• Manufacturer Part Number: MPC8536E-ANDROID
• Description: HARDWARE/SOFTWARE ANDROID OS
• Manufacturer: Freescale Semiconductor
• Series: PowerQUICC ™r
• Type: MPUr

Specifications of MPC8536E-ANDROID

• Contents: Board
• For Use With/related Products: MPC8536
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

17.4.1.7
As an initiator, the controller supports both type 0 and type 1 configuration cycles when configured in RC
mode. There are two methods of generating a configuration transaction; refer to
Express Configuration Space Access,”
controller’s internal configuration space, it can be sent out on the PCI Express link, or it can be internally
terminated. The PCI Express TLP header for a type 0 configuration read transaction has
TYPE[4:0] = 00100 and FMT[1] = 0; the PCI Express TLP header for a type 0 configuration write
transaction has TYPE[4:0] = 00100 and FMT[1] = 1. The PCI Express TLP header for a type 1
configuration read transaction has TYPE[4:0] = 00101 and FMT[1] = 0; the PCI Express TLP header for
a type 1 configuration write transaction has TYPE[4:0] = 00101 and FMT[1] = 1. Note that all
configuration transactions sent on PCI Express require a response regardless whether they are read or a
write configuration transactions.
The controller does not generate configuration transactions in EP mode. Only inbound configuration
transactions are supported in EP mode.
17.4.1.8
Configuration and I/O writes are serialized by the controller. The logic after issuing a configuration write
or IO write does not issue any new transactions until the outstanding configuration or I/O write is finished.
This means that an acknowledgement packet from the link partner in the form of a CpL TLP packet must
be seen or the transaction has timed out. If the CpL packet contains a CRS status, then the logic re-issues
the configuration write transaction. It keeps retrying the request until either a status other than CRS is
returned or the transaction times out.
Note that it is possible for outbound configuration read request to be requeued and be placed at the end of
the request queue due to CRS condition.
17.4.1.9
Software message generation is supported in both RC and EP modes.
17.4.1.9.1
Software can choose to send a message by programming PEXOWARn[WTT] = 0x5. A message is sent by
writing a 4-byte transaction in big-endian format that hits in an outbound window configured to send
messages.
Part of the 4-byte data is used to store information such as message code and routing information.
Table 17-121
Freescale Semiconductor
16–18
0–15
Bits
Configuration Space Addressing
Serialization of Configuration and I/O Writes
Messages
describes the message data format.
Outbound ATMU Message Generation
Routing
Name
MPC8536E PowerQUICC III Integrated Processor Reference Manual, Rev. 1
—
Table 17-121. Internal Platform (OCeaN) Message Data Format
Reset Value
—
x
for more information. A configuration transaction can hit into the
Reserved
Routing mechanism. Contains the message’s routing information
Description
PCI Express Interface Controller
Section 17.3.7, “PCI
17-103