background image

1 Introduction

Freescale's Qorivva MPC57xx devices are the latest
generation of Automotive microcontrollers (MCU) based on
the Power Architecture™ core. This generation is
manufactured in a 55 nm wafer processing flow (c55).
Previous generations of devices were manufactured in larger
geometry technologies.

In addition to being manufactured in a smaller technology, the
e200zx cores used in the c55 devices have been updated for
higher speeds, lower power, and better die size utilization
(equating to lower cost for the core itself). Many features of
the cores are selectable by the definition requirements of the
individual devices that use these cores. This document outlines
major differences in the e200zx cores based on the options
selected for devices in the MPC57xx family. While it lists the
differences 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 the different technologies, as well as
the different types of cores that are used by the different
families of devices, starting with the first fully integrated
Power Architecture core with embedded nonvolatile flash
memory and peripherals (MPC555). There was an earlier
Automotive Power Architecture, the MPC505/MPC509,
however, it did not have integrated flash or peripherals.

Freescale Semiconductor

Document Number:AN4802

Application Note

Rev 0, 10/2013

Qorivva MPC57xx e200zx Core

Differences

c55 process migration

by: Randy Dees

© 2013 Freescale Semiconductor, Inc.

Contents

1

Introduction................................................................1

1.1

MPC57xx core instantiations..... ....................2

2

Differences between MPC57xx e200zx
cores...........................................................................3

2.1

e200zx core execution options....................... 3

2.2

e200zx bus interface and memory
options........................................... ................ 5

2.3

e200zx debug options............. ....................... 7

A

Revision history.......................... ............................ 10

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: