This case consists of two 16-bit external transactions, the first writing OP0 and OP1,
the second writing OP2 and OP3.
OP1/OP3
DMA RequestChannelSourceDescription
eSCIA_COMBTX18ESCIA.SR[TDRE] ||
ESCIA.SR[TC] ||
ESCIA.SR[TXRDY]
eSCIA combined DMA
request of the Transmit
Data Register Empty
and LIN Transmit Data
Ready DMA requests
1Addendum for Revision 1.0
Table 1. MPC5565RM Rev 1.0 addendum
LocationDescription
Section 12.4.2.7/Page 12-42 Change sentence “The bytes indicated as ‘—’ are not driven during that write cycle” to read “The
bytes indicated as ‘—’ are indeterminate and may be driven during that write cycle.”
Table 12-19, “Data Bus
Contents for Write
Cycles”/Page 12-43
Table 9-23, “DMA Request
Summary for eDMA”/Page
9-39
Replace table with the one below to correct information about data bus contents for write cycles.
Note that only two columns have changed: under “32-Bit Port Size,” columns “D0:D7” and
“D8:D15.”
Change one row in the table to correct information about eSCI COMBTX DMA request. Only the
Transmit Data Register Empty and LIN Transmit Data Ready flags drive the DMA request. The
Transmit Complete flag is not used.
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor2
Page 4
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Hardware Vector
Mode Offset
Vector
Number
SourceDescription
0x0850133DSPI_BSR[TFFF] DSPI B transfer FIFO fill flag
0x0860134DSPI_BSR[TCF]DSPI B transfer complete flag
0x0870135DSPI_BSR[RFDF] DSPI B receive FIFO drain flag
16171819202122232425262728293031
R
W
Reset011 1 01110111011 1
Access Field 4
Access Field 5
Access Field 6
Access Field 7
ModuleBase AddressPage
Peripheral Bridge A (PBRIDGE_A)0xC3F0_0000Page A-2
Peripheral Bridge B (PBRIDGE_B)0xFFF0_0000Page A-31
LocationDescription
Addendum for Revision 1.0
Table 10-9, “MPC5565
Interrupt Request
Sources”/Page 10-19
Figure 5-2, “Master Privilege
Control Registers”/Page 5-5
Change three rows in the table to correct DSPI_B information. The three interrupt requests were
not assigned to the correct channel numbers.
Change read status for bits 16–31 from zero to reserved.
Table A-1, “Module Base
Addresses”/Page A-1
Freescale Semiconductor3
Correct names of peripheral bridge modules by adding underscore (PBRIDGEA becomes
PBRIDGE_A, PBRIDGEB becomes PBRIDGE_B). Only two rows of the table are changed.
MPC5565 Reference Manual Addendum, Rev. 2
Page 5
Addendum for Revision 1.0
Register DescriptionRegister Name
Used
Size
Address
Peripheral bridge A master privilege
control register
PBRIDGE_A_MPCR32-bitBase + 0x0000
Reserved——Base +
(0x0004-0x001F)
Peripheral bridge A peripheral access
control register 0
PBRIDGE_A_PACR032-bitBase + 0x0020
Reserved——Base +
(0x0024-0x003F)
Peripheral bridge A off-platform
peripheral access control register 0
PBRIDGE_A_OPACR0 32-bitBase + 0x0040
Peripheral bridge A off-platform
peripheral access control register 1
PBRIDGE_A_OPACR1 32-bitBase + 0x0044
Peripheral bridge A off-platform
peripheral access control register 2
PBRIDGE_A_OPACR2 32-bitBase + 0x0048
Reserved——Base + (0x004C-
0xC3F7_FFFF)
LocationDescription
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Table A-2, “MPC5565
Detailed Register
Map”/Page A-2
Correct names of peripheral bridge A control registers by adding underscore (PBRIDGEA_x
becomes PBRIDGE_A_x).
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor4
Page 6
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Register DescriptionRegister Name
Used
Size
Address
Peripheral bridge B master privilege
control register
PBRIDGE_B_MPCR32-bitBase + 0x0000
Reserved——Base +
(0x0004-0x001F)
Peripheral bridge B peripheral access
control register 0
PBRIDGE_B_PACR032-bitBase + 0x0020
Reserved——Base +
(0x0024-0x0027)
Peripheral bridge B peripheral access
control register 2
PBRIDGE_B_PACR232-bitBase + 0x0028
Reserved——Base +
(0x002C-0x003F)
Peripheral bridge B off-platform
peripheral access control register 0
PBRIDGE_B_OPACR0 32-bitBase + 0x0040
Peripheral bridge B off-platform
peripheral access control register 1
PBRIDGE_B_OPACR1 32-bitBase + 0x0044
Peripheral bridge B off-platform
peripheral access control register 2
PBRIDGE_B_OPACR2 32-bitBase + 0x0048
Peripheral bridge B off-platform
peripheral access control register 3
PBRIDGE_B_OPACR3 32-bitBase + 0x004C
Reserved——(Base + 0x0050)-
0xFFF0_3FFF)
LocationDescription
Addendum for Revision 1.0
Table A-2, “MPC5565
Detailed Register
Map”/Page A-23
Correct names of peripheral bridge B control registers by adding underscore (PBRIDGEB_x
becomes PBRIDGE_B_x).
Freescale Semiconductor5
MPC5565 Reference Manual Addendum, Rev. 2
Page 7
Addendum for Revision 1.0
LocationDescription
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Figure 16-13,” Unified
Channel Block
Diagram”/Page 16-26
Reverse the arrow between the "Programmable Filter" and "Edge Detect".
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor6
Page 8
Addendum for Revision 1.0
Table 1. MPC5565RM Rev 1.0 addendum (continued)
LocationDescription
Section13.3/ Page 13-4Remove cross-reference to Table 13-2. Add the following table and update the cross-reference.
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor7
Page 9
Addendum for Revision 1.0
eMIOS ChannelDMA = 0DMA = 1
0InterruptDMA request
1InterruptDMA request
2InterruptDMA request
3InterruptDMA request
4InterruptDMA request
5InterruptReserved
6InterruptReserved
7InterruptReserved
8InterruptDMA request
9InterruptDMA request
10InterruptReserved
11InterruptReserved
12InterruptReserved
13InterruptReserved
14InterruptReserved
15InterruptReserved
16InterruptReserved
17InterruptReserved
18InterruptReserved
19InterruptReserved
20InterruptReserved
21InterruptReserved
22InterruptReserved
23InterruptReserved
Table 1. MPC5565RM Rev 1.0 addendum (continued)
LocationDescription
Table 16-9/ Page 16-15Bit 7—DMA: Replace the table that shows the eMIOS channels that don’t support DMA with the
following table.
Section 9.3.1, “eDMA
Microarchitecture”/ Page
9-29
In the Memory controller sub-bullet, delete the line "The hooks to a BIST controller for the local
TCD memory are included in this module".
Enters checkstop state. A reset is
required to resume processing.
01Instruction or
data
Machine check interrupt (IVOR1).
1XDataData storage interrupt (IVOR2).
External interrupt must be enabled.
Machine check can be enabled or
disabled.
1XInstructionInstruction storage interrupt
(IVOR3).
LocationDescription
Addendum for Revision 1.0
Section 9.2.2.13: eDMA
Interrupt Request Register
(EDMA_IRQRL)/ Page 9-17
Section 8.3: Initialization and
Application
Information/Page 8-14
In the second paragraph, remove the last line "without the need to perform a read-modify-write
sequence to the EDMA_IRQRL".
Replace the whole section with the following information:
The Error Correction Code (ECC) is used to verify the contents of the internal SRAM and flash
memories. This is done by generating ECC check bits. Typically ECC check bits are calculated
on writes and then used on reads to detect and correct errors.
• SRAM—Eight ECC check bits for each 64-bit SRAM data doubleword.
• Flash—Eight ECC check bits for each 64-bit flash data doubleword.
After Power on Reset (POR), the contents of internal SRAM is random and the corresponding
ECC check bits are unknown. To prevent generating ECC errors during reads, an initialization
routine must perform 64 bit writes to all SRAM locations. Because the flash module is
non-volatile, the ECC check bits are calculated and stored when the flash is programmed.
Transparent to the application, the ECC uses the check bits to automatically correct single-bit
memory errors. Multi-bit memory errors are not correctable. If the ECC detects a multi-bit error,
an exception is generated. The type of exception generated by a multi-bit error depends on the
settings of the EE and ME in the Machine State Register (MSR), as shown in the following table.
When error reporting is enabled, as long as its priority is 0, an interrupt request is generated to
the interrupt controller (INTC) even though the INTC request is not serviced.
A non-correctable data ECC error executes one of the following actions, regardless of whether
non-correctable reporting is enabled:
Freescale Semiconductor9
MPC5565 Reference Manual Addendum, Rev. 2
Page 11
Addendum for Revision 1.0
LocationDescription
Table 1. MPC5565RM Rev 1.0 addendum (continued)
When the device is in the checkstop state, processing is suspended and cannot resume without
a reset. When a debug request is presented to the core while it is in the checkstop state, the core
temporarily exits the checkstop state and enters debug mode. When debug mode exits, the core
re-enters the checkstop state.
If the external interrupt bit in the MSR is enabled, data or instruction stage interrupts are reported
when the ECC errors are a result of CPU accesses, regardless of whether non-correctable
reporting is enabled.
ECC errors generated by other masters (eDMA, etc.) do not generate data or instruction storage
exceptions, and the ECSM is used to report these errors. You must initialize the ECSM to enable
non-correctable reporting with interrupt generation to detect and report ECC interrupts from the
ECSM.
Error reporting details can be independently enabled for flash memory and SRAM. To enable
non-correctable error reporting and save the error details for:
• SRAM—set the ERNCR bit in the ECSM Error Configuration Register (ECSM_ECR).
• Flash—set the EFNCR bit in ECSM_ECR.
When these bits are set and a non-correctable ECC error occurs, error information is recorded
in other ECSM registers and an interrupt request is generated on vector 9 of the interrupt
controller (INTC).
• CPU data access error—Generates data storage exception (IVOR2).
• CPU instruction access error—Generates instruction storage exception (IVOR3).
• Vector 9 of INTC enabled—Generates an external exception (IVOR4)
Section 11.4.3.3, "FM
Calibration Routine"/ Page
11-29
Table 6-135, “SIU_DISR
Field Descriptions”/ Page
6-108
Correct the equation at the end of the third paragraph: change value of M from 640 to 480.
• Bit 14-15–TRIGSELB: Correct the input select description as follows:
00: Replace the term “Invalid value” with “No Trigger”
01: Replace the term “Invalid value” with “No Trigger”
• Bit 22-23–TRIGSELC: Correct the input select description as follows
00: Replace the term “Invalid value” with “No Trigger”
01: Replace the term “Invalid value” with “No Trigger”
• Bit 30-31–TRIGSELD: Correct the input select description as follows
00: Replace the term “Invalid value” with “No Trigger”
01: Replace the term “Invalid value” with “No Trigger”
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor10
Page 12
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Addre
ss:
Base + 0x0004Access: User R/W
012345 6 7 8 9 10 11 12 13 14 15
R 0000000 0 000 0 0000
W
Reset0000000 0 000 0 0000
16 17 18 19 20 2122232425262728293031
R
000000LOLFLOC
MODEPLL
SEL
PLL
REF
LOCKSLOCKLOC
F
CAL
DO
NE
CAL
PA S
S
W
w1cw1c
Reset000000 00 —1—1—1—1—2000
1
Reset state determined during reset configuration.
2
Reset state determined during reset.
Note: “w1c” signifies that this bit is cleared by writing a 1 to it.
Synthesizer Status Register (FMPLL_SYNSR)
LocationDescription
Addendum for Revision 1.0
Figure 11-9, “Synthesizer
Status Register
(FMPLL_SYNSR)”/Page
11-16
Section 10.5.5.2, “Ensuring
Coherency”/ Page 10-33
Correct the figure to reflect bits 23:28 and bits 30:31 as read-only.
Add the following sentence before GetResource source code:
“Processor recognition of interrupts must be enabled before executing the GetResource code
sequence.”
Insert a blank line between the GetResource and ReleaseResource code sequences:
GetResource:
raise PRI
mbar
isync
ReleaseResource:
mbar
lower PRI
Section 10.3.1.3, “INTC
Interrupt Acknowledge
Register
(INTC_IACKR)”/Page 10-11
Table 10-3. INTC Memory
Map/Page 10-8
Freescale Semiconductor11
Remove the first paragraph from the “Note”:
“The INTC_IACKR must not be read speculatively while in software vector mode. Therefore, for
future compatibility, the TLB entry covering the INTC_IACKR must be configured to be guarded.”
Add the following note at the end of this table:
Note:
To ensure compatibility with all PowerPC processors, the TLB entry covering the INTC memory
map must be configured as guarded, both in software and hardware vector modes.
• In software vector mode, the INTC_IACKR must not be read speculatively.
• In hardware vector mode, guarded writes to the INTC_CPR or INTC_EOIR complete before
the interrupt acknowledge signal from the processor asserts.
MPC5565 Reference Manual Addendum, Rev. 2
Page 13
Addendum for Revision 1.0
LocationDescription
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Table 10-9. MPC5565
Interrupt Request
Sources/Page 10-23
Section 10.4.2.1.4, “Priority
Comparator Submodule”/
Page 10-25
Section 10.5.5.2, “Ensuring
Coherency”/ Page 10-32
Note:
Update the note at the end of this table as follows:
The INTC has no spurious vector support. Therefore, if an asserted peripheral or software
settable interrupt request (whose PRI value in INTC_PSRn is higher than the PRI value in
INTC_CPR) negates before the interrupt request to the processor for that peripheral or software
settable interrupt request is acknowledged, the interrupt request to the processor still can assert
or remain asserted for that peripheral or software settable interrupt request. If the interrupt
request to the processor does assert or does remain asserted:
• The interrupt vector will correspond to that peripheral or software settable interrupt request.
• The PRI value in the INTC_CPR will be updated with the corresponding PRI value in
INTC_PSRn.
Furthermore, clearing the peripheral interrupt request's enable bit in the peripheral or,
alternatively, setting its mask bit has the same consequences as clearing its flag bit.Setting its
enable bit or clearing its mask bit while its flag bit is asserted has the same effect on the INTC
as an interrupt event setting the flag bit.
Add the following paragraph to this section: One consequence of the priority comparator design
is that once a higher priority interrupt is captured, it must be acknowledged by the CPU before a
subsequent interrupt request of even higher priority can be captured. For example, if the CPU is
executing a priority level 1 interrupt, and a priority level 2 interrupt request is captured by the
INTC, followed shortly by a priority level 3 interrupt request to the INTC, the level 2 interrupt must
be acknowledged by the CPU before a new level 3 interrupt will be generated.
Move the content of this section under a new heading Section 10.5.5.2.1, “Interrupt with Blocked
Priority”.
Add the following paragraph to this section:
Section 10.5.5.2.2: Raised Priority Preserved
Before the instruction after the GetResource system service executes, all pending transactions
have completed. These pending transactions can include an ISR for a peripheral or software
settable interrupt request whose priority was equal to or lower than the raised priority. Also,
during the epilog of the interrupt exception handler for this preempting ISR, the raised priority
has been restored from the LIFO to PRI in INTC_CPR. The shared coherent data block now can
be accessed coherently. Following figure shows the timing diagram for this scenario, and the
table explains the events. The example is for software vector mode, but except for the method of
retrieving the vector and acknowledging the interrupt request to the processor, hardware vector
mode is identical.
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor12
Page 14
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Last In / First Out
Entry in LIFO
Write
INTC_CPR
Clock
Interrupt Request
to Processor
Hardware Vector
Enable
Interrupt
Acknowledge
Interrupt Vector
Read
INTC_IACKR
Write
INTC_EOIR
INTVEC in
INTC_IACKR
PRI in
INTC_CPR
Peripheral Interrupt
Request 100
0
108
1
208
23
Peripheral Interrupt
Request 200
030
3
A
B
C
D
E
F
G
H
I
Raised Priority Preserved Events
EventDescription
APeripheral interrupt request 200 asserts during execution of ISR108 running at
priority 1.
BInterrupt request to processor asserts. INTVEC in INTC_IACKR updates with vector
for that peripheral interrupt request.
CISR108 writes to INTC_CPR to raise priority to 3 before accessing shared coherent
data block.
DPRI in INTC_CPR now at 3, reflecting the write. This write, just before accessing
data block, is the last instruction the processor executes before being interrupted.
EInterrupt exception handler prolog acknowledges interrupt by reading INTC_IACKR.
FPRI of 3 pushed onto LIFO. PRI in INTC_CPR updates to 2, the priority of ISR208.
GISR208 clears its flag bit, deasserting its peripheral interrupt request.
HInterrupt exception handler epilog writes to INTC_EOIR.
ILIFO pops 3, restoring the raised priority onto PRI in INTC_CPR. Next value to pop
from LIFO is the priority from before peripheral interrupt request 100 interrupted.
ISR108 now can access data block coherently after interrupt exception handler
executes rfi instruction.
LocationDescription
.
Addendum for Revision 1.0
Raised Priority Preserved Timing Diagram
Freescale Semiconductor13
MPC5565 Reference Manual Addendum, Rev. 2
Page 15
Addendum for Revision 1.0
LocationDescription
Table 1. MPC5565RM Rev 1.0 addendum (continued)
Section 6.3.1.118 “Pad
Configuration Register 218
(SIU_PCR218)”
Section 11.3.1.1
Synthesizer Control Register
(FMPLL_SYNCR)
• Change PA field from two bits to one bit
• Figure 6-119: Change note 2 to “... set the PA field to 0b0.”
• Table 6-119. PCR218 “PA Field Definition” change as shown below:
0b0 FCK
0b1 AN[15]
Changed the last note in PREDIV field description from
“To use the 8-20 MHz OSC, the PLL predivider must be configured for divide-by-two operation
by tying PLLCFG[2] low (set PREDIV to 0b000).” to
“When using an 8 to 20 MHz reference clock (crystal or external clock), PLLCFG[2] should be
set low for devices that have a PLLCFG[2] pin. This sets the default predivider (PREDIV) to
0b000. To use a crystal or external reference greater than 20 MHz (up to 40 MHz), the PLL
predivider must be configured for divide-by-2 operation by setting PLLCFG[2] high. This sets the
default predivider (PREDIV) to 0b001. After reset, PREDIV must not be configured to a value
less than divide-by-2 (with a 40 MHz crystal/reference).”
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor14
Page 16
Revision history
2Revision history
Table 2 provides a revision history for this document.
Table 2. Revision history
RevisionSubstantive changesDate of release
1.0 • Initial release. Corrected errors in chapter 12, “External Bus Interface (EBI).”10/2009
2.0 • Corrected error in chapter 9, “Enhanced Direct Memory Access (eDMA).”
• Corrected errors in chapter 10, “Interrupt Controller (INTC).”
• Corrected errors in chapter 5, “Peripheral Bridge (PBRIDGE A and PBRIDGE B).”
• Corrected peripheral bridge name errors in appendix A, “MPC5565 Register Map.”
• Corrected the table shown in EMIOS_CCRn: DMA bit description.
• Clarified the description in Section 9.4.1, “eDMA Microarchitecture”.
• Clarified the description in Section 9.3.1.13, “eDMA Interrupt Request Registers
(EDMA_IRQRL).
• Corrected the ECSM initialization information in Section 8.3: Initialization and
Application Information.
• Clarified the code sequence in Section 10.5.5.2: Ensuring Coherency.
• Clarified note in the INTC Interrupt Acknowledge Register .
• Added a note in the INTC Memory Map table.
• Clarified note at the end of the MPC5565 Interrupt Request Sources table.
• Added a paragraph to the Section 10.4.2.1.4, “Priority Comparator Submodule”.
• Updated Section 10.5.5.2, “Ensuring Coherency”.
• Corrected table “PCR218 PA Field Definition” and figure “AN[15]_FCK Pad
Configuration Register (SIU_PCR218)” and update note 2.
• Updated the last note in PREDIV field description of Synthesizer Control Register
(FMPLL_SYNCR).
04/2012
MPC5565 Reference Manual Addendum, Rev. 2
Freescale Semiconductor15
Page 17
How to Reach Us:
Home Page:
www.freescale.com
Web Support:
http://www.freescale.com/support
USA/Europe or Locations Not Listed:
Freescale Semiconductor, Inc.
Technical Information Center, EL516
2100 East Elliot Road
Tempe, Arizona 85284
+1-800-521-6274 or +1-480-768-2130
www.freescale.com/support
Freescale Semiconductor Japan Ltd.
Headquarters
ARCO Tower 15F
1-8-1, Shimo-Meguro, Meguro-ku,
Tokyo 153-0064
Japan
0120 191014 or +81 3 5437 9125
[email protected]
Asia/Pacific:
Freescale Semiconductor China Ltd.
Exchange Building 23F
No. 118 Jianguo Road
Chaoyang District
Beijing 100022
China
+86 10 5879 8000
[email protected]
For Literature Requests Only:
Freescale Semiconductor Literature Distribution Center
1-800-441-2447 or 303-675-2140
Fax: 303-675-2150
[email protected]
Information in this document is provided solely to enable system and
software implementers to use Freescale Semiconductor products. There are
no express or implied copyright licenses granted hereunder to design or
fabricate any integrated circuits or integrated circuits based on the
information in this document.
Freescale Semiconductor reserves the right to make changes without further
notice to any products herein. Freescale Semiconductor makes no warranty,
representation or guarantee regarding the suitability of its products for any
particular purpose, nor does Freescale Semiconductor assume any liability
arising out of the application or use of any product or circuit, and specifically
disclaims any and all liability, including without limitation consequential or
incidental damages. “Typical” parameters that may be provided in Freescale
Semiconductor data sheets and/or specifications can and do vary in different
applications and actual performance may vary over time. All operating
parameters, including “Typicals”, must be validated for each customer
application by customer’s technical exper ts. Freescale Semiconductor does
not convey any license under its patent rights nor the rights of others.
Freescale Semiconductor products are not designed, intended, or authorized
for use as components in systems intended for surgical implant into the body,
or other applications intended to support or sustain life, or for any other
application in which the failure of the Freescale Semic onductor product could
create a situation where personal injury or death may occur. Should Buyer
purchase or use Freescale Semiconductor products for any such unintended
or unauthorized application, Buyer shall indemnify and hold Freescale
Semiconductor and its officers, employees, subsidiaries, affiliates, and
distributors harmless against all claims, costs, damages, and expenses, and
reasonable attorney fees arising out of, directly or indirectly, any claim of
personal injury or death associated with such unintended or unauthorized
use, even if such claim alleges that Freescale Semiconductor was negligent
regarding the design or manufacture of the part.
Freescale Semiconductor
Technical Information Center, CH370
1300 N. Alma School Road
Chandler, Arizona 85224
+1-800-521-6274 or +1-480-768-2130
[email protected]
Freescale Semiconductor Japan Ltd.
Headquarters
ARCO Tower 15F
1-8-1, Shimo-Meguro, Meguro-ku,
Tokyo 153-0064, Japan
0120 191014 or +81 3 5437 9125
[email protected]
Asia/Pacific:
Freescale Semiconductor Hong Kong Ltd.
Technical Information Center
2 Dai King Street
Tai Po Industrial Estate
Tai Po, N.T., Hong Kong
+800 26668334
[email protected]
For Literature Requests Only:
Freescale Semiconductor Literature Distribution Center
P.O. Box 5405
Denver, Colorado 80217
1-800-441-2447 or 303-675-2140
Fax: 303-675-2150
[email protected]
Information in this document is provided solely to enable system and
software implementers to use Freescale Semiconductor products. There are
no express or implied copyright licenses granted hereunder to design or
fabricate any integrated circuits or integrated circuits based on the
information in this document.
Freescale Semiconductor reserves the right to make changes without further
notice to any products herein. Freescale Semiconductor makes no warranty,
representation or guarantee regarding the suitability of its products for any
particular purpose, nor does Freescale Semiconductor assume any liability
arising out of the application or use of any product or circuit, and specifically
disclaims any and all liability, including without limitation consequential or
incidental damages. “Typical” parameters that may be provided in Freescale
Semiconductor data sheets and/or specifications can and do vary in different
applications and actual performance may vary over time. All operating
parameters, including “Typicals”, must be validated for each customer
application by customer’s technical exper ts. Freescale Semiconductor does
not convey any license under its patent rights nor the rights of others.
Freescale Semiconductor products are not designed, intended, or authorized
for use as components in systems intended for surgical implant into the body,
or other applications intended to support or sustain life, or for any other
application in which the failure of the Freescale Semico nductor product could
create a situation where personal injury or death may occur. Should Buyer
purchase or use Freescale Semicondu ctor products for any such unintended
or unauthorized application, Buyer shall indemnify and hold Freescale
Semiconductor and its officers, employees, subsidiaries, affiliates, and
distributors harmless against all claims, costs, damages, and expenses, and
reasonable attorney fees arising out of, directly or indirectly, any claim of
personal injury or death associated with such unintended or unauthorized
use, even if such claim alleges that Freescale Semiconductor was negligent
regarding the design or manufacture of the part.
The MPC5565 microcontroller (MCU) is a member of the MPC5500 family of next generation powertrain
microcontrollers built on Power Architecture™ technology. The MPC5500 family contains a host
processor core that complies with the Power Architecture embedded category, which is 100 percent user
mode compatible with the original Power PC™ user instruction set architecture (UISA). This family of
parts contains many new features coupled with high-performance CMOS technology to provide significant
performance improvement over the MPC565.
The e200z6 CPU of the MPC5500 family is part of the family of CPU cores that implement versions built
on the Power Architecture embedded category . This core also has additional instructions, including digital
signal processing (DSP) instructions, beyond the classic PowerPC instruction set.
The MPC5565 has two levels of memory hierarchy. The fastest accesses are to the 8 KB unified cache.
The next level in the hierarchy contains up to 80 KB of internal SRAM and 2 MB flash memory . Both the
internal SRAM and the flash memory can hold instructions and data. The external bus interface is designed
to support most of the standard memories used with the MPC5xx family.
The complex I/O timer functions of the MPC5500 family are performed by an enhanced time processor
unit engine (eTPU). The eTPU engine controls 32 hardware channels. The eTPU has been enhanced over
the TPU by providing 24-bit timers, double-action hardware channels, a variable number of parameters
per channel, angle clock hardware, and additional control and arithmetic instructions. The eTPU can be
programmed using a high-level programming language. The less complex timer functions of the MPC5500
family are performed by the enhanced modular input/output system (eMIOS). The eMIOS’ 24 hardware
channels are capable of single action, double action, pulse-width modulation (PWM), and modulus counter
operation. Motor control capabilities include edge-aligned and center-aligned PWM.
Off-chip communication is performed by a suite of serial protocols including: three controller area
networks (FlexCANs); three enhanced deserial/serial peripheral interface (DSPIs); and two enhanced
serial communications interfaces (eSCIs).
The DSPIs support pin reduction through hardware serialization and deserialization of timer channels and
general-purpose input/output (GPIO) signals.
The MCU has two on-chip 40-channel enhanced queued dual analog to digital converters (eQADC).
The system integration unit (SIU) performs several chip-wide configuration functions. Pad configuration
and general-purpose input and output (GPIO) are controlled from the SIU. External interrupts and reset
control are also found in the SIU. The internal multiplexer submodule (SIU_DISR) provides multiplexing
of eQADC trigger sources, daisy chaining the DSPIs, and external interrupt signal multiplexing.
Peripheral bridge B (PBRIDGE_B)Peripheral bridge A (PBRIDGE_A)
Master
Master
Slave
BAM
NDI
x3
x2
x3x2
1 engine
Legend
e200z6e core components
APU– Auxiliary processing unit
BIU– Bus interface unit
BPU– Branch processing unit
DEC– Decrementer
FIT– Fixed interval timer
GPR– General-purpose register
JTAG– JTAG controller
LSU– Load/store unit
MMU– Memory management unit
PCU– Program counter unit
SPE– Signal processing engine
SPR– Special purpose register
TB– Time base
VLE– Variable length encoding
WDT– Watchdog timer
Slave
MPC5565 device modules
BAM– Boot assist module
CAN– Controller area network (FlexCAN)
DSPI– Deserial/serial peripheral interface
EBI – External bus interface
ECSM – Error correction status module
eDMA – Enhanced direct memory access
eMIOS – Enhanced modular I/O system
eQADC – Enhanced queued analog/digital converter
eSCI– Enhanced serial communications interface
eTPU– Enhanced time processing unit
FBIU– Flash bus interface unit
FMPLL – Frequency modulated phase-locked loop
INTC– Interrupt controller
NDI– Nexus developmental interface
SIU– System integration unit
SRAM – Internal static RAM
VRC– Voltage regulator controller
XBAR – System bus crossbar switch
This section provides a high-level description of the features found in the MPC5565.
•Operating parameters
— Fully static operation, up to 132 MHz
— –40 to 150 °C junction temperature
— Low-power design
– Less than 1.2 Watts power dissipation
– Designed for dynamic power management of core and peripherals
– Software-controlled clock gating of peripherals
– Separate power supply for stand-by operation for portion of internal SRAM
— Fabricated in 0.13 μm process
— 1.5 V internal logic
— Input and output pins with 3.0–5.25 V range
– 35% or 65% V
– Selectable hysteresis
– Selectable slew rate control
— External bus support 1.62–3.6 V operation and Nexus pins support 2.5–3.6 V operation
– Selectable drive strength control
CMOS switch levels (with hysteresis)
DDEH
Introduction
– Unused pins configurable as GPIO
— Designed with EMI reduction techniques
– Frequency modulated phase-locked loop
– On-chip bypass capacitance
– Selectable slew rate and drive strength
•High-performance e200z6 core processor
— 32-bit CPU built on Power Architecture™ technology
— Freescale Variable Length Encoding (VLE) enhancements for code size footprint reduction
— Thirty-two 64-bit general-purpose registers (GPRs)
— Memory management unit (MMU) with 32-entry fully-associative translation look-aside
buffer (TLB)
— Branch processing unit
— Fully pipelined load/store unit
— Eight KB unified cache with line locking
– Two-way set associative
– Two 32-bit fetches per clock
– Eight-entry store buffer
– Way locking
– Supports assigning cache as instruction or data only on a per-way basis
– Supports tag and data parity
— Vectored interrupt support
— Interrupt latency is less than 70 ns @132 MHz (measured from interrupt request to execution
of first instruction of interrupt exception handler)
— Reservation instructions for implementing read-modify-write constructs
(internal SRAM and flash)
— Signal processing engine (SPE) auxiliary processing unit (APU) operating on 64-bit GPRs
— Floating point
–IEEE® 754 compatible with software wrapper
– Single precision in hardware, double precision with software library
– Conversion instructions between single precision floating point and fixed point
— Long cycle time instructions, except for guarded loads, do not increase interrupt latency in the
MPC5565; to reduce latency, long cycle time instructions are aborted upon interrupt requests
— Extensive system development support through Nexus debug module
•System bus crossbar switch (XBAR)
— Three master ports, five slave ports.
— 32-bit address bus, 64-bit data bus
— Simultaneous accesses from different masters to different slaves (there is no clock penalty
when a parked master accesses a slave)
•Enhanced direct memory access (eDMA) controller
— 32 channels support independent 8-, 16-, 32-bit single value or block transfers
— Supports variable sized queues and circular queues
— Source and destination address registers are independently configured to post-increment or
remain constant
— Each transfer is initiated by a peripheral, CPU, or eDMA channel request
— Each eDMA channel can optionally send an interrupt request to the CPU on completion of a
– 16 reserved
— Unique 9-bit vector per interrupt source
— 16 priority levels with fixed hardware arbitration within priority levels for each interrupt source
— Priority elevation for shared resources
1. Although this device has a maximum of 231interrupts, the logic requires that the total number of interrupts be divisible by four.
Therefore, the total number of interrupts specified for this device is 232.
— Current controlled oscillator (ICO) range from 48 MHz to maximum device frequency
— Reduced frequency divider (RFD) for reduced frequency operation without re-lock
— Four selectable modes of operation
— Programmable frequency modulation
— Lock detect circuitry continuously monitors lock status
— Loss-of-clock (LOC) detection for reference and feedback clocks
— Self-clocked mode (SCM) operation
— On-chip loop filter (reduces number of external components required)
— Engineering clock output configurable to divide-by-2 to 126 of the system clock frequency
•External bus interface (EBI)
— 1.8–3.3 V nominal I/O voltage
— 324 BGA: 16-bit data bus, 20-bit address bus is default, but configurable to 24-bit address bus.
Although this device is designed to support a 32-bit EBI data bus, only 16 data bus pins are
available and connected on the 324 BGA package. The 496-pin VertiCal assembly provides the
calibration functionality.
— Memory controller with support for various memory types
– Non-burst SDR flash and SRAM
Introduction
– Asynchronous/legacy flash and SRAM
– Most standard memories used with the MPC5xx family
— Configurable bus speed modes
– 50% of system frequency
– 25% of system frequency
— Support for external master accesses to internal addresses
— Burst support
— Bus monitor
– User selectable
– Programmable timeout period (with eight external bus clock resolution)
— Four chip selects: CS
[0:3] multiplexed with ADDR[8:11].
— T wo write/byte enable (WE/BE[0:1]) signals in the 324-pin package and the 496 pin assembly.
— Configurable wait states (via chip selects)
— Optional automatic CLKOUT gating to save power and reduce EMI
— Compatible with MPC5xx external bus (with some limitations):
— Memory controller shared with EBI
— 16-bit data bus
— 21-bit address bus with no support for the least significant address bit (ADDR31)
— Up to 22 bit address space providing a 4 MB addressing range (the two most significant bits
shared with CAL_CS
[2:3])
— Chip selects: up to three chip selects (CAL_CS
[0] and CAL_CS[2:3] shared with
CAL_ADDR[10:11])
•System integration unit (SIU)
— Centralized GPIO control of bus pins: 324 BGA package with 150 pins
— Centralized pad control on a per-pin basis
— System reset monitoring and generation
— External interrupt inputs, filtering and control
•Error correction status module (ECSM)
Configurable error-correcting codes (ECC) reporting for internal SRAM and flash memories
•On-chip flash
— Two MB burst flash memory
— 256 KB × 64-bit configuration
— Censorship protection scheme to prevent flash content visibility
— Hardware read-while-write feature that can erase/program blocks while other blocks are read
(used for EEPROM emulation and data calibration)
— 20 blocks with sizes ranging from 16–128 KB to support features such as boot block, operating
system block, and EEPROM emulation. Blocks are structured as follows:
– 2 x 16 KB
– 2 x 48 KB
– 2 x 64 KB
– 14 x 128 KB
— Read while write with multiple partitions
— Page programming mode to support rapid end of line programming
— Hardware programming state machine
•Configurable cache memory, 0–8 KB
— Two-way set-associative unified (instruction and data) cache
— Decouples processor performance from system memory performance
•On-chip internal static RAM (SRAM)
— 80 KB general-purpose SRAM of which 32 KB are on standby power
— ECC performs single-bit correction, double-bit error detection
•Boot assist module (BAM)
— Enables and manages the transition of MCU from reset to user code execution in the following
– User application can boot from internal or external flash memory
– Download and execution of code via FlexCAN or eSCI
– User application can boot with either classic Power Architecture code or VLE code
•Enhanced modular I/O system (eMIOS)
— 24 orthogonal channels with double action, PWM, and modulus counter functionality
— Supports all DASM and PWM modes of MIOS14 (MPC5xx)
— Four selectable time bases plus a shared time or angle counter bus
— DMA and interrupt request support
— Motor control capability
•Enhanced time processor unit (eTPU)
— One engine 32-channel engine
— 24-bit timer resolution
— 12 KB shared code memory, 2.5 KB shared data memory
— Event-triggered timer subsystem
— High-level assembler/compiler
— Variable number of parameters to allocate per channel
Introduction
— Double match/capture channels
— Angle clock hardware support
— Shared time or angle counter bus for all eTPU and eMIOS modules
— DMA and interrupt request support
— Nexus class 3 debug support (with some class 4 support)
•Enhanced queued analog/digital converter (eQADC)
— Two independent ADCs with 12-bit A/D resolution
— Common mode conversion range of 0–5 V
— 40 single-ended input channels, expandable to 65 channels with external multiplexers on the
324 BGA package
— Eight channels can be used as four pairs of differential analog input channels
— 10-bit accuracy at 400 ksamples/sec., 8-bit accuracy at 800 ksamples/sec.
— Supports six FIFO queues with fixed priority
— Queue modes with priority-based preemption; initiated by software command, internal
(eTPU and eMIOS), or external triggers
— DMA and interrupt request support
— Supports all functional modes from QADC (MPC5xx family)
•Three deserial serial peripheral interface modules (DSPI)
— Serial peripheral interface (SPI)
– Full duplex communication ports with interrupt and eDMA request support
– Supports all functional modes from QSPI submodule of QSMCM (MPC5xx family)
– Support for queues in RAM
– Six chip selects, expandable to 64 with external demultiplexers
– Programmable frame size, baud rate, clock delay, and clock phase on a per-frame basis
– Modified SPI mode for interfacing to peripherals with longer setup time requirements
— Deserial serial interface (DSI)
– Pin reduction by hardware serialization and deserialization of eTPU and eMIOS channels
– Chaining of DSI submodules
– Triggered transfer control and change in data transfer control (for reduced EMI)
•Two enhanced serial communication interface (eSCI) modules
— UART mode provides NRZ format and half or full duplex interface
— eSCI bit rate up to 1 Mb/s
— Advanced error detection, and optional parity generation and detection
— Word length programmable as 8 or 9 bits
— Separately enabled transmitter and receiver
— LIN support
— DMA support
— Interrupt request support
•Three FlexCANs
— 64 message buffers each
— Full implementation of the CAN protocol specification, Version 2.0B
— Based on and including all existing features of the Freescale TouCAN module
— Programmable acceptance filters
— Individual receive filtering per message buffer
— Short latency time for high-priority transmit messages
— Arbitration scheme according to message ID or message buffer number
— Listen-only mode capabilities
— Programmable clock source: system clock or oscillator clock
— Reception queue possible by setting more than one receive message buffer with the same ID
— Backwards compatibility with previous FlexCAN modules
•Nexus development interface (NDI)
— Per IEEE®-ISTO 5001-2003
— Real-time development support for Power Architecture core and eTPU engine through Nexus
class 3 (some class 4 support)
— Data trace of eDMA accesses
— Read and write access
— Configured via the IEEE® 1149.1 (JTAG) port
— High-bandwidth mode for fast message transmission
— Reduced bandwidth mode for reduced pin usage
•IEEE® 1149.1 JTAG controller (JTAGC)
—IEEE® 1149.1-2001 test access port (TAP) interface
— JCOMP input that provides the ability to share the T AP; selectable modes of operation include
JTAGC/debug or normal system operation
— 5-bit instruction register that supports IEEE® 1149.1-2001 defined instructions
— 5-bit instruction register that supports additional public instructions
— Three test data registers: a bypass register, a boundary scan register , and a device identification
register
— TAP controller state machine that controls the operation of the data registers, instruction
register and associated circuitry
•Voltage regulator controller (VRC)
Provides a low-cost solution to power the core logic; it reduces the number of power supplies
required from the customer power supply chip
•POR block
Provides initial reset condition up to the voltage at which pins (RESET) can be read safely; it does
not guarantee the safe operation of the chip at specified minimum operating voltages
1.3MPC5500 Family Comparison
The following table compares the product features of the MPC5554 and the MPC5565:
The following sections provide detailed information about each of the on-chip modules.
1.4.1e200z6 Core Overview
The device uses the e200z6 core explained in detail in the e200z6 PowerPCTM Core Reference Manual.
The e200z6 CPU uses a seven-stage pipeline for instruction execution:
•Instruction fetch 1
•Instruction fetch 2
•Instruction decode and register file read
•Execute 1
•Execute 2 and memory access 1
•Execute 3 and memory access 2
•Register writeback
The operation of the pipeline stages overlap so that most instructions execute in a single-clock.
The integer execution unit consists of a 32-bit arithmetic unit (AU), a logic unit (LU), a 32-bit barrel
shifter, a mask-insertion unit (MIU), a condition register manipulation unit (CRU), a count-leading-zeros
unit (CLZ), a 32 x 32 hardware multiplier array, result feed-forward hardware, and support hardware for
division.
Most arithmetic and logical operations are executed in a single cycle with the exception of multiply and
divide instructions, which are implemented with a pipelined hardware array. The CLZ unit operates in a
single clock cycle.
The instruction unit contains an incremental program counter (PC) and a dedicated branch address adder
to minimize delays during change of flow operations. Sequential prefetching is performed to ensure a
supply of instructions into the execution pipeline. Branch target prefetching is performed to accelerate
taken branches. Prefetched instructions are placed into an instruction buffer capable of holding six
sequential instructions and two branch target instructions.
Branch target addresses are calculated in parallel with branch instruction decode, resulting in execution
time of three clocks. Conditional branches which are not taken execute in a single clock. Branches with
successful look-ahead and target prefetching have an effective execution time of one clock.
Memory load and store operations are provided for byte, halfword, word (32-bits), and doubleword
(64-bits) data with automatic zero or sign extension of byte and halfword load data. These instructions can
be pipelined to allow effective single cycle throughput. Load and store multiple word instructions allow
low overhead context save and restore operations. The load/store unit contains a dedicated effective
address adder to allow effective address generation to be optimized.
The condition register unit supports the condition register (CR) and condition register operations defined
by the Power Architecture technology. The condition register consists of eight 4-bit fields that reflect the
results of certain operations, such as move, integer and floating-point compare, arithmetic, and logical
instructions, and provide a mechanism for testing and branching.
Vectored and auto-vectored interrupts are supported by the CPU. Vectored interrupt supports unique
interrupt handlers invoked with no software overhead for multiple interrupt sources.
The signal processing extension (SPE) APU supports vector instructions (SIMD) operating on 16- and
32-bit fixed-point data types, as well as 32-bit IEEE®-754 single-precision floating-point formats, and
supports single-precision floating-point operations in a pipelined fashion. The 64-bit general-purpose
register file is used for source and destination operands, and there is a unified storage model for
single-precision floating-point data types of 32-bits and the normal integer type. Low latency fixed-point
and floating-point add, subtract, multiply, divide, compare, and conversion operations are provided, and
most operations can be pipelined.
The CPU includes support for Variable Length Encoding (VLE) instruction enhancements that have
modified instruction set that uses a combination of 16- and 32-bit instructions from the classic Power
Architecture instruction. This reduces the code size without noticeably affecting performance. The classic
Power Architecture instruction set and VLE instruction set are available concurrently. Regions of the
memory map are designated as PPC or VLE using an additional configuration bit in each table look-aside
buffer (TLB) entry in the MMU.
1.4.2System Bus Crossbar Switch (XBAR)
The system bus’ multi-port crossbar (XBAR) switch supports simultaneous connections between three
master ports and five slave ports. The crossbar supports a 32-bit address bus width and a 64-bit data bus
width on all master and slave ports.
The crossbar allows concurrent transactions from any master port to any slave port. It is possible to use all
master ports and slave ports at the same time as a result of independent master requests. If a slave port is
simultaneously requested by more than one master port, arbitration logic selects the highest priority master
and grants it ownership of the slave port. All other masters requesting that slave port must wait until the
higher priority master completes its transactions. By default, masters requests’ have equal priority and are
granted access to a slave port in round-robin fashion based on the last master ID granted access.
1.4.3Enhanced Direct Memory Access (eDMA)
The enhanced direct memory access (eDMA) controller is a second-generation module capable of
performing complex data movements via 32 programmable channels, with minimal intervention from the
CPU. The hardware microarchitecture includes a DMA engine which performs source and destination
address calculations, and the actual data movement operations, along with an SRAM-based memory
containing the transfer control descriptors (TCD) for the channels. This implementation is used to
minimize the overall module size.
The interrupt controller (INTC) provides priority-based preemptive scheduling of interrupt requests,
suitable for statically scheduled real-time systems. The INTC allows interrupt request servicing from 231
total interrupt vectors.
For high-priority interrupt requests, the time from when the peripheral interrupt request asserts to when
the processor executes the interrupt service routine (ISR) is minimized. A unique vector for each interrupt
request source is used to quickly determine which ISR to execute. The INTC module provides a number
of priorities to ensure that lower priority ISRs do not delay the execution of higher priority ISRs. Software
is used to configure the interrupt priorities for each interrupt source.
When multiple tasks share a resource, coherent accesses to that resource must be supported. The INTC
supports the priority ceiling protocol for coherent accesses. By providing a modifiable priority mask, the
priority level can be raised temporarily so that no task can preempt another task that shares the same
resource.
Multiple processors can assert interrupt requests to each other through software settable interrupt requests
(by using application software to assert requests). These maskable interrupt requests can divide the
software into a high-priority portion and a low-priority portion for servicing the interrupt requests. The
high-priority portion is initiated by a peripheral interrupt request, but then the ISR asserts a software
settable interrupt request to finish the servicing in a lower priority ISR.
The frequency modulated phase-locking loop (FMPLL) generates high-speed system clocks from an
8–20 MHz crystal oscillator or an external clock generator. Furthermore, the FMPLL supports
programmable frequency modulation of the system clock. The PLL multiplication factor, output clock
divider ratio, modulation depth, and modulation rate are all software configurable.
1.4.6External Bus Interface (EBI)
The external bus interface (EBI) controls data transfer across the crossbar switch to/from memories or
peripherals in the external address space. The EBI is available on the 324 BGA package only . The EBI also
enables an external master to access internal address space. The EBI includes a memory controller that
generates interface signals to support a variety of external memories. The memory controller supports
single data rate (SDR) burst mode flash, external SRAM, and asynchronous memories. In addition, the
EBI supports up to four regions (via chip selects), along with programmed region-specific attributes.
1.4.7Calibration Bus Interface (CBI)
The calibration bus controls data transfer across the crossbar switch to/from memories or peripherals
connected to the VertiCal connector. The calibration bus is only available when the silicon is packaged in
the VertiCal calibration assembly . The bus shares the memory controller and most of the control logic with
the EBI but the two buses use separate pads. The calibration bus memory controller supports single data
rate (SDR) non-burst mode flash, SRAM, and asynchronous memories. In addition, the bus supports up to
three regions via dedicated calibration chip selects (two chip selects multiplexed with two address bits),
along with programmed region-specific attributes.
1.4.8System Integration Unit (SIU)
The device’s system integration uni t (SIU) controls MCU reset configuration, pad configuration, external
interrupt, general-purpose I/O (GPIO), internal peripheral multiplexing, and the system reset operation.
The reset configuration module contains the external pin boot configuration logic. The pad configuration
module controls the static electrical characteristics of I/O pins. The GPIO module provides uniform and
discrete input/output control of the I/O pins of the MCU. The reset controller performs reset monitoring
of internal and external reset sources, and drives the RSTOUT pin. The SIU is accessed by the e200z6 core
through the crossbar switch.
1.4.9Error Correction Status Module (ECSM)
The error correction status module (ECSM) provides status information regarding platform memory errors
reported by error-correcting codes.
1.4.10Flash Memory
The MPC5565 provides 2 MB of programmable, non-volatile, flash memory storage. Non-volatile
memory (NVM) can be used for instruction and/or data storage.
The flash memory has a flash bus interface unit (FBIU) that connects the system bus to a dedicated flash
memory array controller. The FBIU supports a 64-bit data bus width at the system bus port, and a 256-bit
read data interface to flash memory. The FBIU contains two 256-bit prefetch buffers, and a prefetch
controller that prefetches sequential lines of data from the flash array into the buffer. Prefetch buffer hits
allow no-wait responses. Normal flash array accesses are registered in the FBIU and are forwarded to the
system bus on the following cycle, incurring three wait-states. Prefetch operations can be automatically
controlled, as well as restricted to servicing a single bus master. Prefetches can also require a trigger for
instruction or data accesses.
1.4.11Cache
The e200z6 core supports an eight-KB, two-way set-associative, unified (instruction and data) cache with
a 32-byte line size. The cache improves system performance by providing low-latency data to the e200z6
instruction and data pipelines, which decouples processor performance from system memory performance.
The cache is virtually indexed and physically tagged. The e200z6 does not provide hardware support for
cache coherency in a multi-master environment. Software must be designed to maintain cache coherency
with other possible bus masters.
Both instruction and data accesses are performed using a single bus connected to the cache. The processor
uses virtual addresses to index the cache array. The memory management unit (MMU) provides the
virtual-to-physical address conversion to perform the cache tag compare. The MMU can pass the virtual
addresses to the cache as the physical address without the conversion. If the physical address matches a
valid cache tag entry, the access hits in the cache. For a read operation, the cache supplies the data to the
processor, and for a write operation, the data from the processor is written to cache. If the access does not
match a valid cache tag entry (misses in the cache), or a write access is required to memory, the cache
performs a bus cycle on the system bus.
1.4.12Static RAM (SRAM)
The MPC5500 family internal SRAM module provides a general-purpose memory block that supports
mapped read/write accesses from any master . The SRAM size is 80 KB. Included within the SRAM block
is a 32-KB block powered by a separate supply for standby operation and ECC error correction and
detection.
1.4.13Boot Assist Module (BAM)
The boot assist module (BAM) is read-only memory programmed by Freescale and is identical for all
MCUs with an e200z6 core. The BAM program executes every time the MCU is powered on, or when
reset in normal mode. The BAM supports theseboot modes:
•Booting from internal flash memory
•Single master booting from external memory
•Serial boot loading (program is downloaded to SRAM over an eSCI or FlexCAN peripheral and
then executed)
The BAM reads the reset configuration halfword (RCHW) from flash memory (either internal or external)
to configure the device hardware. The MMU is then configured for all resources and maps all physical
addresses to logical addresses with the minimum address translation, to allow application boot code to
execute as either Classic Power Architecture Book E code (default) or as Freescale VLE code.
1.4.14Enhanced Management Input/Output System (eMIOS)
The enhanced modular I/O system (eMIOS) module generates or measures time events. A unified channel
(UC) module provides a consistent interface to a superset of all the MIOS channel functionality. This
allows more flexibility to program each unified channel for different functions in different applications.
T o identify up to two timed events, each UC uses two comparators, a time base selector , and registers. This
structure can produce match events to measure or generate a waveform. Alternatively, input events can
capture the time base, allowing measurement of an input signal.
1.4.15Enhanced Time Processing Unit (eTPU)
The enhanced time processing unit (eTPU) is an enhanced coprocessor designed for timing control.
Operating in parallel with the host CPU, the eTPU processes instructions and real-time input events,
performs output waveform generation, and accesses shared data without host intervention. Consequently ,
for each timer event, the CPU setup and service times are minimized or eliminated. In the MCU, the TPU
engine is combined with shared instruction and data RAM to form a powerful time processing subsystem.
The MPC5565 has one eTPU engine. High-level assembler/compiler and documentation can be used to
develop customized functions for the eTPU. The eTPU supports several features of older TPU versions,
making it easy to port older applications.
The enhanced queued analog to digital converter (eQADC) module provides accurate and fast conversions
for a wide range of applications. The eQADC provides a parallel interface to two on-chip analog to digital
converters (ADCs), and a single master-to-single slave serial interface to an off-chip external device. The
two on-chip ADCs are designed to access all the analog channels.
The eQADC transfers commands from multiple command FIFOs (CFIFOs) to the on-chip ADCs or to the
external device. The module can also receive data from the on-chip ADCs or from an off-chip external
device into multiple result FIFOs (RFIFOs) in parallel, independently of the CFIFOs. The eQADC
supports software and external hardware triggers from other modules to initiate transfers of commands
from the CFIFOs to the on-chip ADCs or to the external device. It also monitors the fullness of CFIFOs
and RFIFOs, and accordingly generates eDMA or interrupt requests to control data movement between the
FIFOs and the system memory, which is external to the eQADC.
1.4.17Deserial/Serial Peripheral Interface (DSPI)
The deserial serial peripheral interface (DSPI) module provides a synchronous serial interface for
communication between the MCU and external devices. The DSPI supports pin-count reduction through
serialization and deserialization of eTPU channels, eMIOS channels and memory-mapped registers. The
channels and register content are transmitted using a SPI-like protocol.
The MPC5565 has three DSPI modules (B, C, and D). The DSPIs have three configurations:
•Serial peripheral interface (SPI) configuration where the DSPIs operate as serial ports only with
support for queues.
•Deserial serial interface (DSI) configuration where the DSPIs serialize eTPU and eMIOS output
channels, and deserialize the input data by passing it to the eTPU and eMIOS input channels.
•Combined serial interface (CSI) configuration where the DSPIs operate in both SPI and DSI
configurations, interleaving DSI frames with SPI frames, and giving priority to SPI frames.
For queued operations, the SPI queues reside in system memory external to the DSPI. Data transfers
between the memory and the DSPI FIFOs use the eDMA controller or the host software.
1.4.18Enhanced Serial Communications Interface (eSCI)
The enhanced serial communications interface (eSCI) allows asynchronous serial communications with
peripheral devices and other MCUs. It includes special support to interface to local interconnect network
(LIN) slave devices. The MPC5565 has two eSCI modules (A and B).
1.4.19Flexible Controller Area Network (FlexCAN)
The MCU contains three controller area network (FlexCAN) modules. Each FlexCAN module is a
communication controller implementing the CAN protocol according to CAN Specification version 2.0B.
The CAN protocol is designed to be used primarily as a vehicle serial data bus, meeting the specific
requirements of this field: real-time processing, reliable operation in the EMI environment of a vehicle,
cost-effectiveness, and required bandwidth. Each FlexCAN module contains 64 message buffers.
The Nexus development interface (NDI) module provides real-time development support capabilities for
the MPC5500 family’s MCU built on the Power Architecture in compliance with the IEEE®-ISTO
5001-2003 standard. This development support is supplied for MCUs without requiring external address
and data pins for internal visibility. The NDI module integrates several Nexus modules to provide the
development support interface for the MPC5500 family . The NDI module interfaces to the host processor ,
single or dual eTPU processors, and internal buses to provide development support as per the
IEEE®-ISTO 5001-2003 standard. The development support provided includes program trace, data trace,
watchpoint trace, ownership trace, run-time access to the MCU internal memory map, Nexus trace of
eDMA transfers, and access to the Power Architecture and eTPU internal registers during halt, via the
auxiliary port. The Nexus interface also supports a JTAG only mode using only the JTAG pins.
1.4.21JTAG Controller (JTAGC)
The JT AG controller (JT AGC) module provides the means to test chip functionality and connectivity while
remaining transparent to system logic when not in test mode. Testing is performed via a boundary scan
technique, as defined in the IEEE® 1149.1-2001 standard. All data input to and output from the JTAGC
module is communicated in serial format. The JT AGC module is compliant with the IEEE® 1149.1-2001
standard.
1.5MPC5500 Family Memory Map
This section describes the MPC5500 family memory map. All addresses in the device, including those that
are reserved, are identified in the tables. The addresses represent the physical addresses assigned to each
module. Logical addresses are translated by the MMU into physical addresses.
Reserved register bits are allocated for future products and have a default value of zero. When writing to
a register, the reserved bits default values must be written as well. Most device features are activated by
writing a non-zero value to them.
Reserved memory is allocated for future products, therefore do not write to memory segments that are
designated as reserved.
Under software control of the MMU, the logical addresses allocated to modules can be changed on a
minimum of a 4 KB boundary. Peripheral modules may be redundantly mapped. The customer must use
the MMU to prevent corruption.
Table 1-2 shows an overview of the device memory map. It is intended to illustrate how the crossbar switch
integrates into the memory map.
Table 1-2. MPC5565 Memory Map (Single-Chip or Single-Master Mode)
Base AddressXBAR Slave PortADDR[0:2]Size Use
0x0000_0000Flash0b0002 MBFlash memory array
0x0020_0000Reserved0b00014 MB–512 bytesReserved
0x00FF_FC00
1 KBFlash shadow row
Flash0b000
0x0100_0000496 MBEmulation mapping of flash
0x2000_0000EBI and calibration
1
0b001512 MB
2
External bus interface
0x4000_0000Internal SRAM0b01080 KBInternal SRAM
0x4001_4000Reserved0b010512 MB–80 KBReserved
0x6000_0000Reserved0b011– 0b1011536 MBReserved
0xC000_0000Reserved0b011– 0b10163 MBReserved
0xC3F0_0000
Bridge A peripherals 0b110
512 KB
Platform A peripherals
0xC3F8_0000512 KB
0xC400_0000Reserved0b110512 MB–64 MBReserved
0xE000_0000Reserved0b111512 MB–64 MBReserved
0xFC00_0000Reserved0b11163 MBReserved
0xFFF0_0000
Bridge B peripherals
0b111512 KB
Platform B peripherals
0xFFF8_00000b111512 KB
1
One method is to assign 0x2000_0000 to 0x2FFF_FFFF to the EBI and assign 0x3000_0000 to 0x3FFF_FFFF to calibration.
Hardware, however, does not force any restriction on EBI memory versus calibration memory.
2
Using four chip select signals and 24 address bus signals, 64 MB can be mapped into the external memory space in
single-master mode. Using four chip select signals and 26 address bus signals, 256 MB can be mapped into the external
memory space in single-master mode.
Table 1-3 shows a detailed list of the device memory map.
If the allocated size is more than the used size, then the base address for the module is the lowest address of the listed address
range, unless noted otherwise.
2
A suggested convention to follow is to place EBI from 0x2000_0000 to 0x2FFF_FFFF and to place calibration space from
0x3000_0000 to 0x3FFF_FFFF. Hardware, however, does not force any restriction on EBI versus calibration space.
3
BAM address range is configured so that 4 KB BAM occupies 0xFFFF_F000–0xFFFF_FFFF.
When multi-master mode is enabled, the bus is permanently granted to the
external master; therefore, the MPC5565 MCU cannot be a master on a
multi-master bus, only a slave.
When the MCU acts as a slave in a multi-master system, the external bus interface (EBI) translates the
24-bit external address to a 32-bit internal address. Table 1-4 lists the translation parameters.
Table 1-4. External to Internal Memory Map Translation Table for Slave Mode
0b11100b1100_0011_11111 MBBridge A peripherals0xC3F0_0000–0xC3FF_FFFF
0b11110b1111_1111_11111 MBBridge B peripherals0xFFF0_0000–0xFFFF_FFFF
1
Only the lower 24 address signals (ADDR[8:31]) are available off-chip for external master accesses.
2
Reserved for a future module that requires its own crossbar slave port.
Internal Address[0:11]BytesInternal SlaveInternal Address Range
2
0x6000_0000–0x600F_FFFF
Table 1-5 shows the memory map for the MCU acting as a slave in a multi-master system from the point
of view of the external master.
Table 1-5. MPC5565 Family Slave Memory Map as Seen from an External Master
External Address Range
0x0000_0000
0x0080_0000–0x009F_FFFF2 MBSlave flash
0x00A0_0000–0x00BF_FFFF2 MBReserved
0x00C0_0000–0x00C1_3FFF80 KBSlave internal SRAM
0x00C1_4000–0x00CF_FFFF1 MB–80 KB (less total SRAM)Reserved
0x00D0_0000–0x00DF_FFFF1 MBReserved
0x00E0_0000–0x00EF_FFFF1 MBSlave bridge A peripherals
0x00F0_0000–0x00FF_FFFF1 MBSlave bridge B peripherals
1
Only the lower 24 address signals (ADDR[8:31]) are available off-chip for external master accesses.
2
This address range is not part of the MPC5500 family slave memory map, rather it is shown to illustrate the addressing
scheme for off-chip accesses in multi-master mode.
3
The shadow row of the slave flash is not accessible by an external master.
Table 1-6. Changes Between MPC5565RM Revisions 0.1 and 1
In Features, changed “Parallel programming mode to support rapid end of line programming” to “Page programming mode to
support rapid end of line programming”
Figure 1-1 Changed SRAM to 80 KB, eQADC to 2.
Section 1.5, “MPC5500 Family Memory Map” Added the following text about reserved bits and memory: Reserved register
bits are allocated for future products and have a default value of zero. When writing to a register, the reserved bits default
values must be written as well. Most device features are activated by writing a non-zero value to them.
Reserved memory is allocated for future products, therefore do not write to memory segments that are designated as
reserved.
Section 1.2, “Features”: Added page footnote to read: Although this device has a maximum of 231interrupts, the logic requires
that the total number of interrupts be divisible by four. Therefore, the total number of interrupts specified for this device is 232.
Added: Although this device is designed to support a 32-bit data bus, only 16-pins are available and connected on the 324
BGA package. (the 496-pin VertiCal assembly has the calibration functionality) to the subbullet 324 BGA: 16-bit data bus,
20-bit address bus is default, but configurable to 24-bit address bus under the External Bus Interface bullet in the features list.
Ta bl e 1 - 1 MPC5500 Family Product Comparison: Removed MPC5553 (Moccasin) and MPC5567 (Tiger) and left just
MPC5554 (Copperhead) for comparison. Removed footnote 4: Select either ADDR[8:31] or ADDR[6:29] to configure a 24-bit
address bus from the 32-bit EBI data bus row and added it on the address bus row. Added footnote 5 to the MPC5565 EBI
data bus row that reads: The EBI is limited to a 16-bit data bus on the 324 package.
This chapter describes the external device signals, including a table of signal properties, detailed
descriptions of the available signals, and the I/O pin power/ground segmentation.
2.1Block Diagram
To provide an extensive feature set as well as compatibility between the MPC5500 family of devices, the
majority of balls are assigned multiplexed signal functions. Figure 2-1 shows only the signals that are
available on the device. Signal functions that are not available on this device are not shown in the diagram.
Primary signal functions that are not available on the device but are used as pin labels in the Ball Grid
Array (BGA) map are listed in Table 2-2.
The 324 package has a limited number of balls which affects the following signals and features:
Table 2-1. MPC5565 324 Package Limitations
Feature SignalsMPC5565 Design324 Package
ADDR[8:31]_GPIO[4:27]; ADDR[8:11] are muxed
as alternate signals with the chip select signals
Maximum 24-bit EBI address bus
Maximum 32-bits wide EBI data bus DATA[0:31]_GPIO[28:59]
Four EBI write enable/byte enableWE
EBI transfer error acknowledgeTEA
EBI bus busyBB
EBI bus grantBG
EQADC Event trigger inputs 0 and 1ETRIG[0:1]_GPIO[111:112]No balls available
General Purpose Input/outputGPIO[205]No ball available
Calibration bus
CS
[0:3]_ADDR[8:11]_GPIO[0:3]. ADDR[8:11] is
also muxed with GPIO[4:7], providing four chip
selects and 24-bit address bits.
/BE[0:3]Only two balls available (WE/BE[0:1])
_GPIO[71]No ball available
signal not available. GPIO is available.BB_GPIO[72] no ball available
signal not available GPIO is available.BG_GPIO[73] no ball available
Calibration bus is separate from the EBI but uses
the EBI controller. Refer to Figure 2-1 for the
calibration bus signals.
ADDR[8:11]_GPIO[4:7] no balls available.
Use CS
[0:3]_ADDR[8:11]_GPIO[0:3] to
choose between using chip select signals or
maximizing the number of output address
signals ADDR[8:31]_GPIO[0:3, 8:31] for a
24-bit EBI address bus.
16 balls available for a 16-bits wide
DATA[0:15]_GPIO[28:43]. There are no balls
available for DATA[16:31]_GPIO[44:59].
No balls availables. These signals are only
available in the VertiCal assembly.
Refer to the last two columns in Table 2-2 for a comparison of available signals on the 324 package
compared to the VertiCal assembly.
NOTE
The Vertical assembly has ball connections for all the available signals on
the device.
The 324 package does not support all muxed signals designed for this
device. Refer to Tab le 2 - 1 for a list of the signals that are not supported
on the 324 package.
2
The calibration signals only function when using the VertiCal assembly.
This section summarizes the external signal functions, their static electrical characteristics, and pad
configuration settings for this device. The signal properties and their electrical characteristics are set in the
System Integration Unit (SIU) Pad Configuration (PCR) registers.
Signal functions are multiplexed to each ball on the BGA in a function hierarchy: Primary , Main Primary,
Alternate, Second Alternate, and General Purpose Input/Output (I/O). For example, in the signal
PCSA[3]_SIND_GPIO[99], the primary signal function is PCSA[3], the first alternate signal function is
SIND, and the GPIO function is a generic General Purpose I/O signal. Multiplexing signal functions
allows for more flexibility when configuring the device, as well as providing compatibility with other
devices in the MPC5500 product family.
The primary signal function name is used in the Ball Grid Array (BGA) map to identify the location of the
ball, however, the primary signal function is not always valid for all devices. As shown in Figure 2-2, when
the primary signal function is not available on the device, a dash appears in the following Signal table
columns: Signal Functions, P/A/G, and I/O Type.
The entries in the P/A/G column designate the position in the signal function hierarchy for multiplexed
functions. These symbols correspond to binary values for the Pin Assignment (PA) field in the SIU_PCR
registers that determine the active signal function. The PA field is from 1- to 3-bits wide, depending on the
PCR register. Figure 2-3 explains the symbol definitions used in the P/A/G column for Table 2-2.
Freescale Semiconductor2-3
Figure 2-2. Primary Function Not Available on Device
Figure 2-3. Understanding the P/A/G Column Entries
Because more than one signal is often multiplexed to one pin, each line in the signal name column is a separate function. For all MPC5565 I/O pins the
selection of the primary pin function, alternate function, or GPIO is determined in the SIU_PCR registers.
2
Each line in the signal name column corresponds to a separate signal function on the pin. For all device I/O pins, the primary, alternate, or GPIO signal
functions are designated in the PA field of the system integration unit (SIU) PCR registers except where explicitly noted.
3
V
(fast I/O) and V
DDE
3.3–5.0 V (+5% and –10%) power supply input. Each segment of V
of the V
4
The pad type is indicated by one of the abbreviations; F for fast, MH for medium (high voltage), SH for slow (high voltage), A for analog, AE for analog
DDE2
and V
No connectN/AN/AN/AN/AN/AN/AW18, Y19
(slow I/O) power supply inputs are grouped into segments. Each segment of V
DDEH
segments that are shorted together and must use the same power supply input. This segment is labeled V
DDE3
pins can connect to a separate 1.8–3.3 V (±10%) power supply, with the exception
DDE
pins can connect to a separate
DDEH
DDE2
with ESD protection circuitry. Some pads have two types, depending on which pad function is selected.
The 496 assembly contains the VertiCal base and includes 324 pins.
6
The Status During Reset pin is sampled after the internal POR is negated. Prior to exiting POR, the signal has a high impedance.
Terminology is O - output, I - input, Up - weak pullup enabled, Down - weak pulldown enabled, Low - output driven low, High - output driven high. A dash
on the left side of the slash denotes that both the input and output buffers for the pin are off. A dash on the right side of the slash denotes that there is
no weak pullup/down enabled on the pin. The signal name to the left or right of the slash indicates the pin is enabled.
7
Function after reset of GPI is general purpose input. A dash on the left side of the slash denotes that both the input and output buffers for the pin are off.
A dash on the right side of the slash denotes that there is no weak pullup/down enabled on the pin.
8
Tie PLLCFG[2] to ground.
9
The EBI is specified and tested at 1.8–3.3 V.
10
Do not configure both the primary function in ADDR[8:11]_GPIO[4:7] and the secondary function in CS[0:3]_ADDR[8:11]_GPIO[0:3] pins to be the
address input. Only configure one set of pins for the address input.
11
When using the EBI functions, select the function in the SIU_PCR register, and then enable the EBI functions in the EBI registers for these pins. Both
the SIU and EBI configurations must match to operation correctly.
12
The function and state of this pin(s) after execution of the BAM program is determined by the BOOTCFG[0:1] pins. Refer to Table 15-7 for detail on the
External Bus Interface (EBI) configuration after execution of the BAM program.
13
These signals are not available on the 324 package.
14
The functions for the WE/BE[0:1]_GPIO[64:65] and WE/BE[2:3]_CAL_WE/BE[0:1]_GPIO[66:67] pins are specified in the SIU. When configured for EBI,
the write enable or byte enable operation is specified in the EBI_BR0 through EBI_BR3 registers. When configured for the calibration bus, the write
enable or byte enable operation is specified in the EBI_CAL_BR0 through EBI_CAL_BR3 registers for each chip select region.
15
The BR and BG primary signal functions are not implemented on the MPC5565 324 package, however the pin labels remain BR and BG on the BGA
map of the 496 assembly.
16
These signals are available on the Vertical assembly only.
17
MCKO is only enabled if debug mode is enabled. Debug mode can be enabled before or after exiting System Reset (RSTOUT negated).
18
MDO[0] is driven high following a power-on reset until the system clock achieves lock, at which time it is then negated. There is an internal pullup on
MDO[0].
19
The function of the MDO[11:4]_GPIO[82:75] pins is selected during a debug port reset by the EVTI pin or by selecting FPM in the NPC_PCR. When
functioning as MDO[11:4] the pad configuration specified by the SIU does not apply. Refer to 2.3.3.4 for more detail on MDO[11:4] pin operation.
20
The function and state of the FlexCAN A pins after execution of the BAM program is determined by the BOOTCFG[0:1] pins. Refer to Ta bl e 1 5 - 9 for
details on the FlexCAN pin configurations after the BAM executes.
21
The primary signal is not available on this device and is listed only for reference to the pin label in the BGA Map.
22
For compatibility to the MPC5554, always power V
different operating voltage, connect V
23
All analog input channels are connected to both ADC blocks. The supply designation for this pin(s) specifies only the ESD rail used.
24
Because the primary signal function designations for the analog functions AN[12] through AN[15] are internally reserved, the PA field of the
corresponding SIU_PCR registers must be set to the main primary function value of 0b011 to use analog functions AN[12] through AN[15].
25
To use the serial data strobe functions, the PA field in the SIU_PCR registers must be set to 0b00. Because SDS, SDO, SDI, and FCK use the GPIO
setting, a G is shown in the P/A/G column. However, these signals do not support GPIO functionality.
26
If analog features are used, tie V
27
Because other balls already are named EMIOS[14:15], the balls for these signals are named GPIO[203:204].
28
The GPIO[205] pin is a protect-for-pin for configuring an external boot for a double data rate (DDR) memory.
29
The GPIO[206:207] pins are protect-for-pins for double data rate (DDR) memory data strobes. These pins can be selected as the source for the eQADC
trigger in the eQADC Trigger Input Select Register (SIU_ETISR).
30
The Function After Reset of the XTAL pin is determined by the value of the signal on the PLLCFG[1] pin. Ground the XTAL pin when using bypass mode.
31
When the FMPLL is configured for external reference mode, the V
Section 11.1.4.2, “External Reference Mode.”
32
The function after reset of the EXTAL_EXTCLK pin is determined by the value of the signal on the PLLCFG[1] pin. The operating voltage for the EXTAL
function is 3.3 V; the operating voltage for the EXTCLK function is 1.62–3.6 V.
33
V
is the 3.3 V input for the voltage regulator control.
RC33
34
The V
provides isolation between the analog and digital sections within each ADC.
35
Can be tied to 5.0 V for both read operation and program / erase.
36
Tie the V
37
Both V
38
The V
specifications (4.5–5.25 V) for analog input functions.
39
All pins with pad type F (pad_fc) are driven to the high state if their V
40
The pins are reserved for the clock and inverted clock outputs for the DDR memory interface.
and V
DDAn
STBY
and V
DDE2
segment can be powered by 3.0–5.0 V for mux addresses or SSI functions, however the V
DDEH9
supply inputs are split into separate traces in the package substrate. Each trace is bonded to a separate pad location, which
SSAn
pin to V
SSA0
pins are labeled as V
DDE3
DDEH9
if the battery backed SRAM is not used.
DDEH6
to V
and V
DDA1
DDE2
and V
DDEH6
DDEH10
DDEH10
to separate power supplies, but this configuration is not compatible with the MPC5554,
.
DDE5
pins on the BGA maps. V
DDE
from the same power supply 3.0–5.25 V. To allow one DSPI to operate at a
supply affects the acceptable signal levels for the external reference. Refer to
This section provides detailed descriptions of the signal functions available for the device.
2.3.1Reset and Configuration Signals
2.3.1.1External Reset Input
RESET
The RESET input is asserted by an external device to reset the all modules of the device MCU. The RESET
pin must be asserted during a power-on reset.
Refer to Section 4.2.1, “Reset Input (RESET).”
2.3.1.2External Reset Output
RSTOUT
The RSTOUT output is a push/pull output that is asserted during an internal device reset. The pin can also
be asserted by software without causing an internal reset of the device MCU.
Refer to Section 4.2.2, “Reset Output (RSTOUT).”
NOTE
During a power-on-reset (POR), RSTOUT is tri-stated.
PLLCFG[0]_IRQ[4]_GPIO[208] are sampled on the negation of the RESET input pin, if the RSTCFG pin
is asserted at that time. The values are used to configure the FMPLL mode of operation. The alternate
function is an external interrupt request input.
PLLCFG[1]_IRQ[5]_SOUTD_GPIO[209] — If the RSTCFG signal is asserted, these functions are
sampled at that time when the RESET input pin negates. The values are used to configure the FMPLL
operation mode. The alternate function is an external interrupt request input, and the second alternate
function is the data output for the DSPI module D.
[5]_SOUTD GPIO[209]
2.3.1.5Phase Locked-Loop Configuration
PLLCFG[2]
The MPC5565 does not use PLLCFG[2], therefore it must be tied low.
Refer to Section 11.3.1.1, “Synthesizer Control Register (FMPLL_SYNCR).”
The RSTCFG input is used to enable the BOOTCFG[0:1] and PLLCFG[0:1] pins during reset. If RSTCFG
is negated during reset, the BOOTCFG and PLLCFG pins are not sampled at the negation of RSTOUT . In
that case, the default values for BOOTCFG and PLLCFG are used. If RSTCFG
the values on the BOOTCFG and PLLCFG pins are sampled and configure the boot and FMPLL modes.
BOOTCFG[0:1]_IRQ[2:3]_GPIO[211:212] are sampled on the negation of the RSTOUT pin, if the
RSTCFG pin is asserted at that time. The values are used by the Boot Assist Module (BAM) program to
determine the boot configuration of the device. The alternate functions are the external interrupt request
inputs (IRQs).
CS[0]_ADDR[8]_GPIO[0] is an external bus interface (EBI) chip select output signals. ADDR[8] is the
alternate signal function and is an external bus address function.
CS[1:3]_ADDR[9:11]_GPIO[1:3] are the external bus interface (EBI) chip select output signals. The
alternate function is the ADDR[9:11] and is an external bus address function.
RD_WR_GPIO[62] indicates whether an external bus transfer is a read or write operation.
_GPIO[62]
2.3.2.24External Burst Data In Progress / GPIO
BDIP
BDIP_GPIO[63] indicates that an EBI burst transfer is in progress.
_GPIO[63]
2.3.2.25External Write/Byte Enable / GPIO
WE
/BE[0:3]_GPIO[64:67]
WE/BE[0:3]_GPIO[64:67] specify which data pins contain valid data for an external bus transfer. Only
WE/BE[0:1]_GPIO[64:65] are supported on the 324 package.
2.3.2.26External Output Enable / GPIO
OE
_GPIO[68]
OE_GPIO[68] indicates that the EBI is ready to accept read data.
2.3.2.27External Transfer Start / GPIO
TS
_GPIO[69]
TS_GPIO[69] is asserted by the EBI owner to indicate the start of a transfer.
2.3.2.28External Transfer Acknowledge / GPIO
TA
_GPIO[70]
TA_GPIO[70] is asserted by the EBI owner to acknowledge that the slave has completed the current
transfer.
2.3.2.29External Transfer Error Acknowledge / GPIO
TEA
_GPIO[71]
TEA_GPIO[71] indicates that an error occurred in the current external bus transfer. These signals are not
supported in the 324 package.
2.3.2.30External Bus Request / GPIO
BR
_GPIO[72]
BR__GPIO[72] is the bus request.Because the BR primary signal function is reserved on this device, there
is no primary signal function for this ball. GPIO[72] pin has GPIO functionality only. These signals are
not supported in the 324 package.
BG_GPIO[73] is the bus grant.Because the BG primary signal function is reserved on this device, there is
no primary signal function for this ball. GPIO[72] pin has GPIO functionality only. These signals are not
supported in the 324 package.
2.3.3Nexus Signals
2.3.3.1Nexus Event In
EVTI
EVTI is an input that is read during a debug port reset to enable or disable the Nexus Auxiliary port for
data trace. After reset, the EVTI pin is used to initiate program and data trace synchronization messages
or generate a breakpoint.
2.3.3.2Nexus Event Out
EVTO
EVTO is an output that provides timing to a development tool for a single watchpoint or breakpoint
occurrence.
2.3.3.3Nexus Message Clock Out
MCKO
MCKO is a free running clock output to the development tools which is used for timing of the MDO and
MSEO signals.
2.3.3.4Nexus Message Data Out
MDO[0]
MDO[0] is a trace message output to the development tools. In addition, MDO[0] indicates the lock status
of the system clock following a power-on reset. MDO[0] is driven high following a power-on-reset until
the system clock achieves lock, at which time it is then negated. There is an internal pullup on MDO[0].
2.3.3.5Nexus Message Data Out
MDO[3:1]
MDO[3:1] are the trace message outputs to the development tools.
2.3.3.6Nexus Message Data Out / GPIO
MDO[11:4]_GPIO[82:75]
MDO[11:4]_GPIO[82:75] are the trace message outputs to the development tools for full port mode. These
pins function as GPIO when the Nexus port controller (NPC) operates in reduced port mode.
2.3.5.1FlexCAN A Transmit / eSCI Transmit / GPIO
CNTXA_TXDA_GPIO[83]
CNTXA_TXDA_GPIO[83] is the transmit pin for the FlexCAN A module. The alternate function is the
transmit pin for the eSCI A module.
2.3.5.2FlexCAN A Receive / eSCI Receive / GPIO
CNRXA_RXDA_GPIO[84]
CNRXA_RXDA_GPIO[84] is the receive pin for the FlexCAN A module. The alternate function is the
receive pin for the eSCI A module.
2.3.5.3FlexCAN B Transmit / DSPI C Chip Select / GPIO
CNTXB_PCSC[3]_GPIO[85]
CNTXB_PCSC[3]_GPIO[85] is the transmit pin for the FlexCan B module. The alternate function is a
peripheral chip select output for the DSPI C module.
2.3.5.4FlexCAN B Receive / DSPI C Chip Select / GPIO
CNRXB_PCSC[4]_GPIO[86]
CNRXB_PCSC[4]_GPIO[86] is the receive pin for the FlexCan B module. The alternate function is a
peripheral chip select output for the DSPI C module.
2.3.5.5FlexCAN C Transmit / DSPI D Chip Select / GPIO
CNTXC_PCSD[3]_GPIO[87]
CNTXC_PCSD[3]_GPIO[87] is the transmit pin for the FlexCAN C module. The alternate function is
PCSD[3], a peripheral chip select for the DSPI D module.
2.3.5.6FlexCAN A Receive / DSPI D Chip Select / GPIO
CNRXC_PCSD[4]_GPIO[88]
CNRXC_PCSD[4]_GPIO[88] is the receive pin for the FlexCAN C module. The alternate function is
PCSD[4], a peripheral chip select for the DSPI D module.
2.3.6Serial Communication Interface (eSCI) Signals
2.3.6.1eSCI A Transmit / GPIO
TXDA_GPIO[89]
TXDA_GPIO[89] is the transmit pin for the eSCI A module.
RXDA_GPIO[90] is the receive pin for the eSCI A module. The pin is an input only for the RXD function,
but as GPIO the pin is input or output based on the SIU PCR configuration.
2.3.6.3eSCI B Transmit / DSPI D Chip Select / GPIO
TXDB_PCSD[1]_GPIO[91]
TXDB_PCSD[1]_GPIO[91] is the transmit pin for the eSCI B module. The alternate function is a
peripheral chip select output for the DSPI D module.
2.3.6.4eSCI B Receive / DSPI D Chip Select / GPIO
RXDB_PCSD[5]_GPIO[92]
RXDB_PCSD[5]_GPIO[92] is the transmit pin for the eSCI B module. The secondary function is a
peripheral chip select for the DSPI D module.
2.3.7.1DSPI A Clock / DSPI C Chip Select / GPIO
SCKA_PCSC[1]_GPIO[93]
SCKA_PCSC[1]_GPIO[93] — Because the SCKA primary signal function is reserved on this device,
there is no primary signal function for this ball. The alternate signal function is the PCSC[1], a peripheral
chip select for the DSPI C module and is available on this device.
2.3.7.2DSPI A Data Input / DSPI C Chip Select / GPIO
SINA_PCSC[2]_GPIO[94]
SINA_PCSC[2]_GPIO[94] — Because the SINA primary signal function is reserved on this device, there
is no primary signal function for this ball.Therefore, the alternate signal function is the PCSC[2], a
peripheral chip select for the DSPI C module and is available on this device.
2.3.7.3DSPI A Data Output / DSPI C Chip Select / GPIO
SOUTA_PCSC[5]_GPIO[95]
SOUTA_PCSC[5]_GPIO[95] — Because the SOUTA primary function is reserved on this device, there
is no primary signal function for this ball. Therefore, the alternate function is the PCSC[5], a peripheral
chip select for the DSPI C module and is available on this device.
2.3.7.4DSPI A Chip Select / DSPI D Chip Select / GPIO
PCSA[0]_PCSD[2]_GPIO[96]
PCSA[0]_PCSD[2]_GPIO[96] — Because the PCSA[0] primary function is reserved on this device, there
is no primary signal function for this ball. Therefore, the alternate function is the PCSD[2], a peripheral
chip select for the DSPI D module.
2.3.7.5DSPI A Chip Select / DSPI B Chip Select / GPIO
PCSA[1]_PCSB[2]_GPIO[97]
PCSA[1]_PCSB[2]_GPIO[97] — Because the PCSA[1] primary function is reserved on this device, there
is no primary signal function for this ball. Therefore, the alternate function is the PCSB[2], a peripheral
chip select for the DSPI B module.
2.3.7.6DSPI A Chip Select / DSPI D Clock / GPIO
PCSA[2]_SCKD_GPIO[98]
PCSA[2]_SCKD_GPIO[98] — Because the PCSA[2] primary function is reserved on this device, there is
no primary signal function. Therefore, the alternate function is the SCKD, a DSPI clock pin for the DSPI D
module.
2.3.7.7DSPI A Chip Select / DSPI D Data Input / GPIO
PCSA[3]_SIND_GPIO[99]
PCSA[3]_SIND_GPIO[99] — Because the PCSA[3] primary function is reserved on this device, there is
no primary signal function. Therefore, the alternate function is the SIND, a data input pin for the DSPI D
module.
2.3.7.8DSPI A Chip Select / DSPI D Data Output / GPIO
PCSA[4]_SOUTD_GPIO[100]
PCSA[4]_SOUTD_GPIO[100] — Because the PCSA[4] primary function is reserved on this device, there
is no primary signal function. Therefore, the alternate function is the SOUTD, a data output pin for the
DSPI D module.
2.3.7.9DSPI A Chip Select / DSPI B Chip Select / GPIO
PCSA[5]_PCSB[3]_GPIO[101]
PCSA[5]_PCSB[3]_GPIO[101] — Because the PCSA[5] primary function is reserved on this device,
there is no primary signal function. Therefore, the alternate function is PCSB[3], a peripheral chip select
output pin for the DSPI B module.
2.3.7.10DSPI B Clock / DSPI C Chip Select / GPIO
SCKB_PCSC[1]_GPIO[102]
SCKB_PCSC[1]_GPIO[102] — SCKB is the primary function, and is the SPI clock pin for the DSPI B
module. The alternate function is PCSC[1], a chip select output for the DSPI C module.
2.3.7.11DSPI B Data Input / DSPI C Chip Select / GPIO
SINB_PCSC[2]_GPIO[103]
SINB_PCSC[2]_GPIO[103] — SINB is the primary function and is the data input pin for the DSPI B
module. The alternate function is a chip select output for the DSPI C module.
2.3.7.12DSPI B Data Output / DSPI C Chip Select / GPIO
SOUTB_PCSC[5]_GPIO[104]
SOUTB_PCSC[5]_GPIO[104] — SOUTB is the primary function and is the data output pin for the DSPI
B module. The alternate function is a chip select output for the DSPI C module.
2.3.7.13DSPI B Chip Select / DSPI D Chip Select / GPIO
PCSB[0]_PCSD[2]_GPIO[105]
PCSB[0]_PCSD[2]_GPIO[105] — PCSB[0] is the primary function and is a DSPI B peripheral chip select
output pin. It also is a Slave Select (SS) input pin for the DSPI B module slave mode operation. The
alternate function is PCSD[2] and is a chip select output for the DSPI D module.
2.3.7.14DSPI B Chip Select / DSPI D Chip Select / GPIO
PCSB[1]_PCSD[0]_GPIO[106]
PCSB[1]_PCSD[0]_GPIO[106] — PCSB[1] is the primary a peripheral chip select output pin for the DSPI
B module. The alternate function is PCSD[0] and is a DSPI D peripheral chip select output that also is a
Slave Select (SS) input pin for DSPI D module slave mode operation.
2.3.7.15DSPI B Chip Select / DSPI C Data Output / GPIO
PCSB[2]_SOUTC_GPIO[107]
PCSB[2]_SOUTC_GPIO[107] — PCSB[2] is the primary function and is a peripheral chip select output
pin for the DSPI B module. SOUTC is the alternate function and is the data output for the DSPI C module.
2.3.7.16DSPI B Chip Select / DSPI C Data Input / GPIO
PCSB[3]_SINC_GPIO[108]
PCSB[3]_SINC_GPIO[108] — PCSB[3] is the primary function and is a peripheral chip select output pin
for the DSPI B module. SINC is the alternate function and is the data input for the DSPI C module.
2.3.7.17DSPI B Chip Select / DSPI C Clock / GPIO
PCSB[4]_SCKC_GPIO[109]
PCSB[4]_SCKC_GPIO[109] — PCSB[4] is the primary function and is a peripheral chip select output pin
for the DSPI B module. SCKC is the alternate function and is the SPI clock for the DSPI C module.
2.3.7.18DSPI B Chip Select / DSPI C Chip Select / GPIO
PCSB[5]_PCSC[0]_GPIO[110]
PCSB[5]_PCSC[0]_GPIO[110] — PCSB[5] is the primary function and is a peripheral chip select output
pin for the DSPI B module. PCSC[0] is the alternate function and is a DSPI C peripheral chip select output
but also is a Slave Select (SS
) input pin for DSPI C module slave mode operation.
2.3.8.7Analog Input / Differential Analog Input
AN[6]_DAN3+
AN[6] is a single-ended analog input to the two on-chip ADCs. DAN3+ is the positive terminal of the
differential analog input DAN3 (DAN3+ to DAN3–).
2.3.8.8Analog Input / Differential Analog Input
AN[7]_DAN3–
AN[7] is a single-ended analog input to the two on-chip ADCs. DAN3– is the negative terminal of the
differential analog input DAN3 (DAN3+ to DAN3–).
2.3.8.9Analog Input / Multiplexed Analog Input
AN[8]_ANW
AN[8] is an analog input pin. ANW is an analog input in external multiplexed mode.
2.3.8.10Analog Input / Multiplexed Analog Input
AN[9]_ANX
AN[9] is an analog input pin. ANX is an analog input in external multiplexed mode.
2.3.8.11Analog Input / Multiplexed Analog Input
AN[10]_ANY
AN[10] is an analog input pin. ANY is an analog input in external multiplexed mode.
2.3.8.12Analog Input / Multiplexed Analog Input
AN[11]_ANZ
AN[11] is an analog input pin. ANZ is an analog input in external multiplexed mode.
NOTE
Attempts to convert the input voltage applied to AN[12], AN[13], AN[14],
and AN[15] while a non-eQADC function is selected causes an undefined
conversion result.
2.3.8.13Analog Input / Mux Address 0 / eQADC Serial Data Strobe
AN[12]_MA[0]_SDS
AN[12]_MA[0]_SDS is an analog input pin. The alternate function, MA[0], is a MUX address pin. SDS
is the serial data strobe for the eQADC SSI; this function is selected by setting the PA field of
SIU_PCR215 to GPIO. This pin has reduced analog to digital conversion accuracy as compared to the
AN[0:7] and AN[16:39] analog input pins because they are powered by V
pins for the synchronous serial interface (SSI) to external ADCs or used as the multiplexor digital outputs
(MA[0]).
SDS is the serial data select output that is muxed with AN[12] and MA[0]. It indicates to the external
(slave) device when it can latch incoming serial data, when it can output its own serial data, and when it
must abort a data transmission. SDS corresponds to the chip select signal in a conventional SPI interface.
This pin is configured by setting the pad configuration register, SIU_PCR215.
2.3.8.14Analog Input / Mux Address 1 / eQADC Serial Data Out
AN[13]_MA[1]_SDO
AN[13]_MA[1]_SDO is an analog input pin. The alternate function, MA[1], is a MUX address pin. SDO
is the serial data output for the eQADC SSI; this function is selected by setting the PA field of
SIU_PCR216 to GPIO. This pin has reduced analog to digital conversion accuracy as compared to the
AN[0:7] and AN[16:39] analog input pins because they are powered by V
DDEH9
and can be used as digital
pins for the synchronous serial interface (SSI) to external ADCs or used as the multiplexor digital outputs
(MA[1]).
This pin is configured by setting the pad configuration register, SIU_PCR216.
2.3.8.15Analog Input / Mux Address 2 / eQADC Serial Data In
AN[14]_MA[2]_SDI
AN[14]_MA[2]_SDI is an analog input pin. The alternate function, MA[2], is a MUX address pin. SDI is
the serial data input for the eQADC SSI; this function is selected by setting the PA field of SIU_PCR217
to GPIO. This pin has reduced analog to digital conversion accuracy as compared to the AN[0:7] and
AN[16:39] analog input pins because they are powered by V
DDEH9
and can be used as digital pins for the
synchronous serial interface (SSI) to external ADCs or used as the multiplexor digital outputs (MA[2]).
This pin is configured by setting the pad configuration register, SIU_PCR217.
2.3.8.16Analog Input / eQADC Free Running Clock
AN[15]_FCK
AN[15]_FCK is an analog input pin. The alternate function is the free running clock for the eQADC SSI.
This pin has reduced analog to digital conversion accuracy as compared to the AN[0:7] and AN[16:39]
analog input pins.
This pin is configured by setting the pad configuration register, SIU_PCR218.
External trigger signals trigger a software or hardware event. The eQADC can detect rising edge, falling
edge, high level, and low level on each of the external trigger signals. The eQADC also supports
configurable digital filters for these external trigger signals.
The eQADC external trigger input pins can be connected to the eTPU, the eMIOS, or an external signal.
The source is selected by configuring the eQADC trigger source in the SIU_ETISR register. Refer to
Table 6-132.
ETRIG[0] is the external trigger for CFIFO0, CFIFO2, and CFIFO4, and ETRIG[1] serves as the external
trigger for CFIFO1, CFIFO3, and CFIFO5.
GPIO[111:112] are general purpose input/output functions.
These signals are not supported in the 324 package.
2.3.8.19Voltage Reference High
V
RH
VRH is the voltage reference high input pin for the eQADC.
2.3.8.20Voltage Reference Low
V
RL
VRL is the voltage reference low input pin for the eQADC.
2.3.8.21Reference Bypass Capacitor
REFBYPC
REFBYPC is a bypass capacitor input for the eQADC. The REFBYPC pin is used to connect an external
bias capacitor between the REFBYPC pin and VRL. The value of this capacitor must be 100nF . This bypass
capacitor is used to provide a stable reference voltage for the ADC.
2.3.9Enhanced Time Processing Unit (eTPU) Signals
2.3.9.1eTPU A TCR Clock / External Interrupt Request / GPIO
TCRCLKA_IRQ
TCRCLKA_IRQ[7]_GPIO[113] is the TCR clock input for the eTPU A module. The alternate function is
an external interrupt request input for the SIU module.
2.3.9.2eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[0]_ETPUA[12]_GPIO[114]
ETPUA[0]_ETPUA[12]_GPIO[114] is an input/output channel pin for the eTPU A module. ETPUA[0] is
the primary function and is an input/output channel for the eTPU A module. The alternate function,
ETPUA[12], is an output channel for the eTPU A module. When configured as ETPUA[12], the pin
functions as output only. ETPUA[12] is an alternate function and is only for eTPU A module output
channels.
2.3.9.3eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[1]_ETPUA[13]_GPIO[115]
ETPUA[1]_ETPUA[13]_GPIO[115] is an input/output channel pin for the eTPU A module. ETPUA[1] is
the primary function and is an input/output channel for the eTPU A module. The alternate function,
ETPUA[13], is an output channel for the eTPU A module. When configured as ETPUA[13], the pin
functions as output only.
2.3.9.4eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[2]_ETPUA[14]_GPIO[116]
ETPUA[2]_ETPUA[14]_GPIO[116] is an input/output channel pin for the
eTPU A module. ETPUA[2] is the primary functions and is an input/output channel for the eTPU A
module. The alternate function is an output channel for the eTPU A module. When configured as
ETPUA[14], the pin functions as output only.
2.3.9.5eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[3]_ETPUA[15]_GPIO[117]
ETPUA[3]_ETPUA[15]_GPIO[117] is an input/output channel pin for the eTPU A module. ETPUA[3] is
the primary functions and is an input/output channel for the eTPU A module. The alternate function is an
output channel for the eTPU A module. When configured as ETPUA[15], the pin functions as output only .
2.3.9.6eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[4]_ETPUA[16]_GPIO[118]
ETPUA[4]_ETPUA[16]_GPIO[118] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[16], is an output channel for the eTPU A module. When configured as ETPUA[16], the
pin functions as output only.
2.3.9.7eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[5]_ETPUA[17]_GPIO[119]
ETPUA[5]_ETPUA[17]_GPIO[119] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[17], is an output channel for the eTPU A module. When configured as ETPUA[17], the
pin functions as output only.
2.3.9.8eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[6]_ETPUA[18]_GPIO[120]
ETPUA[6]_ETPUA[18]_GPIO[120] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[18], is an output channel for the eTPU A module. When configured as ETPUA[18], the
pin functions as output only.
2.3.9.9eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[7]_ETPUA[19]_GPIO[121]
ETPUA[7]_ETPUA[19]_GPIO[121] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[19], is an output channel for the eTPU A module. When configured as ETPUA[19], the
pin functions as output only.
2.3.9.10eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[8]_ETPUA[20]_GPIO[122]
ETPUA[8]_ETPUA[20]_GPIO[122] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[20], is an output channel for the eTPU A module. When configured as ETPUA[20], the
pin functions as output only.
2.3.9.11eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[9]_ETPUA[21]_GPIO[123]
ETPUA[9]_ETPUA[21]_GPIO[123] is an input/output channel pin for the eTPU A module. The alternate
function, ETPUA[21], is an output channel for the eTPU A module. When configured as ETPUA[21], the
pin functions as output only.
2.3.9.12eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[10]_ETPUA[22]_GPIO[124]
ETPUA[10]_ETPUA[22]_GPIO[124] is an input/output channel pin for the eTPU A module. The
alternate function, ETPUA[22], is an output channel for the eTPU A module. When configured as
ETPUA[22], the pin functions as output only.
2.3.9.13eTPU A Channel / eTPU A Channel (Output Only) / GPIO
ETPUA[11]_ETPUA[23]_GPIO[125]
ETPUA[11]_ETPUA[23]_GPIO[125] is an input/output channel pin for the eTPU A module. The
alternate function, ETPUA[23], is an output channel for the eTPU A module. When configured as
ETPUA[23], the pin functions as output only.
2.3.9.14eTPU A Channel / DSPI B Chip Select / GPIO
ETPUA[12]_PCSB[1]_GPIO[126]
ETPUA[12]_PCSB[1]_GPIO[126] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI B module.
2.3.9.15eTPU A Channel / DSPI B Chip Select / GPIO
ETPUA[13]_PCSB[3]_GPIO[127]
ETPUA[13]_PCSB[3]_GPIO[127] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI B module.
2.3.9.16eTPU A Channel / DSPI B Chip Select / GPIO
ETPUA[14]_PCSB[4]_GPIO[128]
ETPUA[14]_PCSB[4]_GPIO[128] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI B module.
2.3.9.17eTPU A Channel / DSPI B Chip Select / GPIO
ETPUA[15]_PCSB[5]_GPIO[129]
ETPUA[15]_PCSB[5]_GPIO[129] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI B module.
2.3.9.18eTPU A Channel / DSPI D Chip Select / GPIO
ETPUA[16]_PCSD[1]_GPIO[130]
ETPUA[16]_PCSD[1]_GPIO[130] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI D module.
2.3.9.19eTPU A Channel / DSPI D Chip Select / GPIO
ETPUA[17]_PCSD[2]_GPIO[131]
ETPUA[17]_PCSD[2]_GPIO[131] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI D module.
2.3.9.20eTPU A Channel / DSPI D Chip Select / GPIO
ETPUA[18]_PCSD[3]_GPIO[132]
ETPUA[18]_PCSD[3]_GPIO[132] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI D module.
2.3.9.21eTPU A Channel / DSPI D Chip Select / GPIO
ETPUA[19]_PCSD[4]_GPIO[133]
ETPUA[19]_PCSD[4]_GPIO[133] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI D module.
2.3.9.22eTPU A Channel / External Interrupt / GPIO
ETPUA[20]_IRQ
[8]_GPIO[134]
ETPUA[20]_IRQ[8]_GPIO[134] is an input/output channel pin for the eTPU A module. The alternate
functions are an external interrupt request inputs for the SIU module.
2.3.9.23eTPU A Channel / External Interrupt / GPIO
ETPUA[21]_IRQ
ETPUA[21]_IRQ[9]_GPIO[135] is an input/output channel pin for the eTPU A module. The alternate
functions are an external interrupt request inputs for the SIU module.
[9]_GPIO[135]
2.3.9.24eTPU A Channel / External Interrupt / GPIO
ETPUA[22]_IRQ
ETPUA[22]_IRQ[10]_GPIO[136] is an input/output channel pin for the eTPU A module. The alternate
functions are an external interrupt request inputs for the SIU module.
[10]_GPIO[136]
2.3.9.25eTPU A Channel / External Interrupt / GPIO
ETPUA[23]_IRQ
ETPUA[23]_IRQ[11]_GPIO[137] is an input/output channel pin for the eTPU A module. The alternate
functions are an external interrupt request inputs for the SIU module.
[11]_GPIO[137]
2.3.9.26eTPU A Channel (Output Only) / External Interrupt / GPIO
ETPUA[24:27]_IRQ
[12:15]_GPIO[138:141]
ETPUA[24:27]_IRQ[12:15]_GPIO[138:141] are output channel pins for the eTPU A module. The
alternate function is external interrupt request inputs for the SIU module.
2.3.9.27eTPU A Channel (Output Only) / DSPI C Chip Select / GPIO
ETPUA[28]_PCSC[1]_GPIO[142]
ETPUA[28]_PCSC[1]_GPIO[142] is an output channel pin for the eTPU A module. The alternate function
is a peripheral chip select for the DSPI C module.
2.3.9.28eTPU A Channel (Output Only) / DSPI C Chip Select / GPIO
ETPUA[29]_PCSC[2]_GPIO[143]
ETPUA[29]_PCSC[2]_GPIO[143] is an output channel pin for the eTPU A module. The alternate function
is a peripheral chip select for the DSPI C module.
2.3.9.29eTPU A Channel / DSPI C Chip Select / GPIO
ETPUA[30]_PCSC[3]_GPIO[144]
ETPUA[30]_PCSC[3]_GPIO[144] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI C module.
2.3.9.30eTPU A Channel / DSPI C Chip Select / GPIO
ETPUA[31]_PCSC[4]_GPIO[145]
ETPUA[31]_PCSC[4]_GPIO[145] is an input/output channel pin for the eTPU A module. The alternate
function is a peripheral chip select for the DSPI C module.
2.3.10Enhanced Management Input/Output System (eMIOS) Signals
2.3.10.1eMIOS Channel / eTPU A Channel (Output Only) / GPIO
EMIOS[0:9]_ETPUA[0:9]_GPIO[179:188]
EMIOS[0:9]_ETPUA[0:9]_GPIO[179:188] is an input/output channel pin for the eMIOS module. The
alternate function is output channels for the eTPU A module; that is, when configured as ETPUA[0:9], the
pins function as outputs only.
2.3.10.2eMIOS Channel / DSPI D Chip Select / GPIO
EMIOS[10:11]_PCSD[3:4]_GPIO[189:190]
EMIOS[10:11]_PCSD[3:4]_GPIO[189:190] is an input/output channel pin for the eMIOS module.
PCSD[3:4]_ is the alternate function is a peripheral chip select for the DSPI D module.
2.3.10.3eMIOS Channel (Output Only) / DSPI C Data Output / GPIO
EMIOS[12]_SOUTC_GPIO[191]
EMIOS[12]_SOUTC_GPIO[191] is an output channel pin for the eMIOS module. The alternate function
is the data output for the DSPI C module.
2.3.10.4eMIOS Channel (Output Only) / DSPI D Data Output / GPIO
EMIOS[13]_SOUTD_GPIO[192]
EMIOS[13]_SOUTD_GPIO[192] is an output channel pin for the eMIOS module. The alternate function
is the data output for the DSPI D module.
The EMIOS[14:15]_GPIO[203:204] pins’ primary function is EMIOS[14:15]. When configured as
EMIOS[14:15], the pins function as output channels for the eMIOS module. Because other balls on the
BGA map are already named EMIOS[14:15], the ball names on the BGA map for these signals are named
GPIO[203:204]. The general purpose I/O function for these pins is GPIO.
2.3.11.2General Purpose Input Output
GPIO[205]
The GPIO[205] only has GPIO functionality. This pin is reserved for double data rate memory interface
support. The pad type for GPIO[205] is MH (3.0–5.5 V). This signal is not supported in the 324 package.
GPIO[206:207] have GPIO functionality. The GPIO pins are reserved for double data rate memory
(DDRAM) interface support. The pad types for GPIO[206:207] are F (1.62–3.6 V).
Refer to Section 6.3.1.108, “Pad Configuration Registers 206–207 (SIU_PCR206–SIU_PCR207).”
The GPIO[206:207] pins can be selected as sources for the ADC trigger in the SIU_ETISR.
2.3.12Calibration Bus Signals
Calibration signals function only when using the 496 pin assembly.
2.3.12.1Calibration Chip Select 0 / GPIO
CAL_CS
CAL_CS[0] is the primary function and selects the primary chip for calibration. It is functional only when
using the 496 pin assembly.
CAL_CS[2:3] are calibration chip selects and are the primary functions. CAL_ADDR[10:11] are the
alternate functions and are calibration addresses. It is functional only when using the 496 pin assembly.
[2:3]_CAL_ADDR[10:11]
2.3.12.3Calibration Address
CAL_ADDR[12:30]
CAL_ADDR[12:30] are the calibration addresses. They are functional only when using the 496 pin
assembly.
2.3.12.4Calibration Data
CAL_DATA[0:15]
CAL_DATA[0:15] is the primary function and is a calibration address. It is only functional on the 496
assembly.
2.3.12.5Calibration Read/Write
CAL_RD_WR
CAL_RD_WR is the primary function and is a calibration read/write signal function. It is only functional
on the 496 assembly.
EXT AL is the input pin for an external crystal oscillator or an external clock source. The alternate function
is the external clock input. The function of this pin is determined by the PLLCFG configuration pins.
2.3.13.3System Clock Output
CLKOUT
CLKOUT is the device system clock output.
2.3.13.4Engineering Clock Output
ENGCLK
ENGCLK is a 50% duty cycle output clock with a maximum frequency of the device system clock divided
by two. ENGCLK is not synchronous to CLKOUT.
is the 1.8–3.3 V, with a tolerance of +/– 10% external I/O supply input.
DDEn
2.3.14.12External I/O Supply Input
V
DDEHn
V
DDEHn
is the 3.3–5.0 V, with a tolerance of -10% to +5% external I/O supply input.
2.3.14.13Fixed 3.3 V Internal Supply Input
V
DD33
V
is the 3.3 V internal supply input.
DD33
2.3.14.14Ground
V
SS
VSS is the ground reference input.
2.3.15I/O Power and Ground Segmentation
Table 2-3 gives the preliminary power/ground segmentation. Each segment provides the power and ground
for the I/O pins and can be powered by any voltage within the allowed voltage range regardless of the
power on the other segments. The power/ground segmentation applies regardless of whether a particular
pin is configured for its primary function or GPIO.
Table 2-3. MPC5565 Power / Ground Segmentation for 324 Pin Package