background image

Table 1. Automotive Power Architecture MCU technologies

Family

Manufacturing

technology

Transistor geometry

Cores used

MPC555

CDR1

350 nm

1

RCPU (Automotive RISC)

MPC56x Family

CDR3

250 nm

2

Qorivva MPC55xx
Family

HiP7

120 nm

e200z0, e200z1, e200z3, e200z6

Qorivva MPC56xx
Family

c90

90 nm

e200z0, e200z3, e200z4, e200z6, e200z7

Qorivva MPC57xx
Family

c55

55 nm

e200z0, e200z2, e200z4, e200z7

1. 0.35 micron
2. 0.25 micron

1.1 MPC57xx core instantiations

Many of the different devices in the MPC57xx family have a varying number of cores, including devices with different types
of cores. The following table shows the cores that are instantiated on the different devices in the family. In addition, it shows
the core that debuggers can access after reset with a blank flash (or when a valid reset configuration is not programmed into
the flash). The table also shows whether any of the cores has the option of enabling a lock-step core. On this generation of
MCUs, the lock-step core cannot be used as an independent core, it can only be enabled as a lock-step core. The lock-step
core can be disabled to save power, however, this is not a significant amount of power.

Table 2. MPC57xx core summary

Device

Revision

Core 0

Core 1

Core 2

Lock-Step core

1

MPC5726L

1

2

e200z215An3

MPC5744K

1

3

e200z420n3

e200z225n3

4

Core 0 (e200z419)

MPC5744K

2

2

e200z410Dn3

e200z225Bn3

4

Core 0 (e200z409)

MPC5744P

1

3

e200z4201n3

Core 0 (e200z419)

MPC5744P

2

e200z4251n3

Core 0 (e200z424)

MPC5746M

1.0/1.1

3

e200z420n3

e200z420n3

e200z425n3

4

Core 0 (e200z419)

MPC5746M

2

e200z410n3

e200z410n3

e200z425Bn3

4

Core 0 (e200z409)

Future device 1

1

3

e200z425n3

e200z425n3

4

Core 0 (e200z424)

Future device 1

2

e200z425n3

e200z425n3

4

Core 0 (e200z424)

MPC5748G

1

e200z4204n3

4

e200z4204n3

e200z210n3

MPC5775K

1/1.1

3

e200z4201n3

e200z7260n3

e200z7260n3

Core 0 (e200z419)

MPC5775K

2

e200z4201n3

e200z7260n3

e200z7260n3

Core 0 (e200z419)

Future device 2

1

e200z759n3

4

e200z759n3

Core 1 (e200z758)

MPC5777M

1

3

e200z720n3

e200z720n3

e200z425Bn3

4

Core 0 (e200z719)

MPC5777M

2

e200z710n3

e200z710n3

e200z425Bn3

4

Core 0 (e200z709)

1. This column shows which core the lock-step core is associated with.
2. This device will not be supported by Freescale.
3. This revision is not intended for production.

Introduction

Qorivva MPC57xx e200zx Core Differences, Rev 0, 10/2013

2

Freescale Semiconductor, Inc.

Summary of Contents for MPC57xx

Page 1: ...nces and gives a basic summary of the feature this document does not fully explain the feature in detail The core reference manuals should be consulted for additional information The table below shows...

Page 2: ...step core can be disabled to save power however this is not a significant amount of power Table 2 MPC57xx core summary Device Revision Core 0 Core 1 Core 2 Lock Step core1 MPC5726L 12 e200z215An3 MPC...

Page 3: ...ture wise and with the e200z759 being the most complex 2 1 e200zx core execution options The first set of options that are available to be integrated into the cores instantiated into a particular MCU...

Page 4: ...s Scalar MPC5777M 2 0 MPC5744P 2 0 Core 0 e200z4251n3 No Dual Delayed 32x32 LSP No Scalar e200z710 based cores MPC5777M 2 0 Core 0 1 e200z710n3 No Single Delayed 32x32 No Yes Scalar e200z720 based cor...

Page 5: ...The Lightweight Signal Processing Unit LSP supports a limited number of basic math instructions to speed digital signal processing algorithms Signal Processing Extension SPE 1 1 The Signal Processing...

Page 6: ...4I 64D 32K 16K No 8K Future device 1 1 0 Core 0 1 e200z425n3 24 Yes 64I 64D 32K 16K No 8K Future device 1 2 0 Core 0 1 e200z425n3 24 Yes 64I 64D 32K 16K No 8K MPC5777M 1 0 Core 2 e200z425Bn3 24 Yes 64...

Page 7: ...local memory The local data memory allows for fast access of variables that are required frequently by a single core Local Instruction Memory ITCM Some cores support a fast local instruction memory S...

Page 8: ...0n3 3 No 30 Variable MPC5746M 1 0 1 1 Core 0 1 MPC5744P 1 0 Core 0 e200z4201n3 3 No 30 or 4 Fixed Fixed MPC5775K 1 0 1 1 2 0 Core 0 e200z4201n3 3 Yes buffered 30 or 16 Fixed Fixed MPC5748G 1 0 Core 1...

Page 9: ...s Aurora Router NAR as the Nexus output controller Devices that instantiate the Nexus Port Controller NPC use the buffered timestamps This difference is due to the minimal time that messages spend in...

Page 10: ...e Machine Reset In some cases the Nexus state machine in the e200zx core does not get properly reset when the JTAG TAP is changed to a different JTAG client to a different core or other client Previou...

Page 11: ...ithout limitation consequential or incidental damages Typical parameters that may be provided in Freescale data sheets and or specifications can and do vary in different applications and actual perfor...

Reviews: