Figure 6.Power supplies constraints (–0.3 V ≤ V
Figure 7.Independent ADC supply (–0.3 V ≤ V
Figure 8.Power supplies constraints (3.0 V ≤ V
Figure 9.Independent ADC supply (3.0 V ≤ V
This document provides electrical specifications, pin assignments, and package diagrams
for the SPC560P34/40 series of microcontroller units (MCUs). It also describes the device
features and highlights important electrical and physical characteristics. For functional
characteristics, refer to the device reference manual.
1.2 Description
This 32-bit system-on-chip (SoC) automotive microcontroller family is the latest achievement
in integrated automotive application controllers. It belongs to an expanding range of
automotive-focused products designed to address chassis applications—specifically,
electrical hydraulic power steering (EHPS) and electric power steering (EPS)—as well as
airbag applications.
This family is one of a series of next-generation integrated automotive microcontrollers
based on the Power Architecture technology.
The advanced and cost-efficient host processor core of this automotive controller family
complies with the Power Architecture embedded category. It operates at speeds of up to
64 MHz and offers high performance processing optimized for low power consumption. It
capitalizes on the available development infrastructure of current Power Architecture
devices and is supported with software drivers, operating systems and configuration code to
assist with users implementations.
1.3 Device comparison
Ta bl e 2
and their features—relative to full-featured version—to enable a comparison among the
family members and an understanding of the range of functionality offered within this family.
Table 2.SPC560P34/SPC560P40 device comparison
provides a summary of different members of the SPC560P34/SPC560P40 family
The e200z0 Power Architecture core provides the following features:
●High performance e200z0 core processor for managing peripherals and interrupts
●Single issue 4-stage pipeline in-order execution 32-bit Power Architecture CPU
●Harvard architecture
●Variable length encoding (VLE), allowing mixed 16- and 32-bit instructions
–Results in smaller code size footprint
–Minimizes impact on performance
●Branch processing acceleration using lookahead instruction buffer
●Load/store unit
–1-cycle load latency
–Misaligned access support
–No load-to-use pipeline bubbles
●Thirty-two 32-bit general purpose registers (GPRs)
●Separate instruction bus and load/store bus Harvard architecture
●Hardware vectored interrupt support
●Reservation instructions for implementing read-modify-write constructs
●Long cycle time instructions, except for guarded loads, do not increase interrupt latency
●Extensive system development support through Nexus debug port
●Non-maskable interrupt support
1.5.2 Crossbar switch (XBAR)
The XBAR multi-port crossbar switch supports simultaneous connections between three
master ports and three slave ports. The crossbar supports a 32-bit address bus width and a
32-bit data bus width.
The crossbar allows for two concurrent transactions to occur from any master port to any
slave port; but one of those transfers must be an instruction fetch from internal flash
memory. If a slave port is simultaneously requested by more than one master port,
arbitration logic will select the higher priority master and grant it ownership of the slave port.
All other masters requesting that slave port will be stalled until the higher priority master
completes its transactions. Requesting masters will be treated with equal priority and will be
granted access a slave port in round-robin fashion, based upon the ID of the last master to
be granted access.
●32-bit internal address, 32-bit internal data paths
●Fixed Priority Arbitration based on Port Master
●Temporary dynamic priority elevation of masters
1.5.3 Enhanced direct memory access (eDMA)
The enhanced direct memory access (eDMA) controller is a second-generation module
capable of performing complex data movements via 16 programmable channels, with
minimal intervention from the host processor. The hardware micro architecture 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.
The eDMA module provides the following features:
●16 channels support independent 8-, 16- or 32-bit single value or block transfers
●Supports variable-sized queues and circular queues
●Source and destination address registers are independently configured to either post-
increment or to 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 single value or block transfer
●DMA transfers possible between system memories, DSPIs, ADC, FlexPWM, eTimer
and CTU
●Programmable DMA channel multiplexer allows assignment of any DMA source to any
available DMA channel with as many as 30 request sources
●eDMA abort operation through software
1.5.4 Flash memory
The SPC560P34/SPC560P40 provides 320 KB of programmable, non-volatile, flash
memory. The non-volatile memory (NVM) can be used for instruction and/or data storage.
The flash memory module is interfaced to the system bus by a dedicated flash memory
controller. It supports a 32-bit data bus width at the system bus port, and a 128-bit read data
interface to flash memory. The module contains four 128-bit wide prefetch buffers. Prefetch
buffer hits allow no-wait responses. Normal flash memory array accesses are registered and
are forwarded to the system bus on the following cycle, incurring two wait-states.
The interrupt controller (INTC) provides priority-based preemptive scheduling of interrupt
requests, suitable for statically scheduled hard real-time systems. The INTC handles 128
selectable-priority interrupt sources.
For high-priority interrupt requests, the time from the assertion of the interrupt request by
the peripheral to the execution of the interrupt service routine (ISR) by the processor has
been minimized. The INTC provides a unique vector for each interrupt request source for
quick determination of which ISR has to be executed. It also provides a wide number of
priorities so that lower priority ISRs do not delay the execution of higher priority ISRs. To
allow the appropriate priorities for each source of interrupt request, the priority of each
interrupt request is software configurable.
When multiple tasks share a resource, coherent accesses to that resource need to be
supported. The INTC supports the priority ceiling protocol (PCP) for coherent accesses. By
providing a modifiable priority mask, the priority can be raised temporarily so that all tasks
which share the same resource can not preempt each other.
The INTC provides the following features:
●Unique 9-bit vector for each separate interrupt source
●8 software triggerable interrupt sources
●16 priority levels with fixed hardware arbitration within priority levels for each interrupt
source
●Ability to modify the ISR or task priority: modifying the priority can be used to
implement the priority ceiling protocol for accessing shared resources.
●1 external high priority interrupt (NMI) directly accessing the main core and I/O
processor (IOP) critical interrupt mechanism
1.5.7 System status and configuration module (SSCM)
The system status and configuration module (SSCM) provides central device functionality.
The FMPLL allows the user to generate high speed system clocks from a 4–40 MHz input
clock. Further, the FMPLL supports programmable frequency modulation of the system
clock. The PLL multiplication factor, output clock divider ratio are all software configurable.
●Reduced frequency divider (RFD) for reduced frequency operation without forcing the
FMPLL to relock
●Frequency-modulated PLL
–Modulation enabled/disabled through software
–Triangle wave modulation
●Programmable modulation depth (±0.25% to ±4% deviation from center frequency):
programmable modulation frequency dependent on reference frequency
●Self-clocked mode (SCM) operation
1.5.10 Main oscillator
The main oscillator provides these features:
●Input frequency range: 4–40 MHz
●Crystal input mode or oscillator input mode
●PLL reference
1.5.11 Internal RC oscillator
This device has an RC ladder phase-shift oscillator. The architecture uses constant current
charging of a capacitor. The voltage at the capacitor is compared by the stable bandgap
reference voltage.
The SPC560P34/SPC560P40 SIUL controls MCU pad configuration, external interrupt,
general purpose I/O (GPIO), and internal peripheral multiplexing.
The pad configuration block controls the static electrical characteristics of I/O pins. The
GPIO block provides uniform and discrete input/output control of the I/O pins of the MCU.
The SIUL provides the following features:
●Centralized general purpose input output (GPIO) control of up to 49 input/output pins
and 16 analog input-only pads (package dependent)
●All GPIO pins can be independently configured to support pull-up, pull-down, or no pull
●Reading and writing to GPIO supported both as individual pins and 16-bit wide ports
●All peripheral pins, except ADC channels, can be alternatively configured as both
general purpose input or output pins
●ADC channels support alternative configuration as general purpose inputs
●Direct readback of the pin value is supported on all pins through the SIUL
●Configurable digital input filter that can be applied to some general purpose input pins
for noise elimination
●Up to 4 internal functions can be multiplexed onto 1 pin
1.5.17 Boot and censorship
Different booting modes are available in the SPC560P34/SPC560P40: booting from internal
flash memory and booting via a serial link.
The default booting scheme uses the internal flash memory (an internal pull-down resistor is
used to select this mode). Optionally, the user can boot via FlexCAN or LINFlex (using the
boot assist module software).
A censorship scheme is provided to protect the content of the flash memory and offer
increased security for the entire device.
A password mechanism is designed to grant the legitimate user access to the non-volatile
memory.
Boot assist module (BAM)
The BAM is a block of read-only memory that is programmed once and is identical for all
SPC560Pxx devices that are based on the e200z0h core. The BAM program is executed
every time the device is powered on if the alternate boot mode has been selected by the
user.
The BAM provides the following features:
●Serial bootloading via FlexCAN or LINFlex
●Ability to accept a password via the used serial communication channel to grant the
legitimate user access to the non-volatile memory
1.5.18 Error correction status module (ECSM)
The ECSM provides a myriad of miscellaneous control functions regarding program-visible
information about the platform configuration and revision levels, a reset status register, a
software watchdog timer, wakeup control for exiting sleep modes, and information on
●Checker applied on PBRIDGE output toward periphery
●Byte endianess swap capability
1.5.20 Controller area network (FlexCAN)
The SPC560P34/SPC560P40 MCU contains one controller area network (FlexCAN)
module. This module is a communication controller implementing the CAN protocol
according to Bosch Specification version 2.0B. The CAN protocol was designed to be used
primarily as a vehicle serial data bus, meeting the specific requirements of this field: realtime processing, reliable operation in the EMI environment of a vehicle, cost-effectiveness
and required bandwidth. The FlexCAN module contains 32 message buffers.
●Programmable transmit-first scheme: lowest ID or lowest buffer number
●Time stamp based on 16-bit free-running timer
●Global network time, synchronized by a specific message
●Maskable interrupts
●Independent of the transmission medium (an external transceiver is assumed)
●High immunity to EMI
●Short latency time due to an arbitration scheme for high-priority messages
●Transmit features
–Supports configuration of multiple mailboxes to form message queues of scalable
depth
–Arbitration scheme according to message ID or message buffer number
–Internal arbitration to guarantee no inner or outer priority inversion
–Transmit abort procedure and notification
●Receive features
–Individual programmable filters for each mailbox
–8 mailboxes configurable as a 6-entry receive FIFO
–8 programmable acceptance filters for receive FIFO
●Programmable clock source
–System clock
–Direct oscillator clock to avoid PLL jitter
1.5.21 Safety port (FlexCAN)
The SPC560P34/SPC560P40 MCU has a second CAN controller synthesized to run at high
bit rates to be used as a safety port. The CAN module of the safety port provides the
following features:
●Identical to the FlexCAN module
●Bit rate up to 8 Mbit/s at 64 MHz CPU clock using direct connection between CAN
–Diagnostic features: Loop back; Self Test; LIN bus stuck dominant detection
–Interrupt-driven operation with 16 interrupt sources
●LIN slave mode features:
–Autonomous LIN header handling
–Autonomous LIN response handling
–Optional discarding of irrelevant LIN responses using ID filter
●UART mode:
–Full-duplex operation
–Standard non return-to-zero (NRZ) mark/space format
–Data buffers with 4-byte receive, 4-byte transmit
–Configurable word length (8-bit or 9-bit words)
–Error detection and flagging
–Parity, Noise and Framing errors
–Interrupt-driven operation with four interrupt sources
–Separate transmitter and receiver CPU interrupt sources
–16-bit programmable baud-rate modulus counter and 16-bit fractional
–2 receiver wake-up methods
1.5.23 Deserial serial peripheral interface (DSPI)
The deserial serial peripheral interface (DSPI) module provides a synchronous serial
interface for communication between the SPC560P34/SPC560P40 MCU and external
devices.
●Chip select strobe available as alternate function on one of the chip select pins for
deglitching
●FIFOs for buffering up to 4 transfers on the transmit and receive side
●Queueing operation possible through use of the I/O processor or eDMA
●General purpose I/O functionality on pins when not used for SPI
1.5.24 Pulse width modulator (FlexPWM)
The pulse width modulator module (PWM) contains four PWM submodules each of which is
set up to control a single half-bridge power stage. There are also three fault channels.
This PWM is capable of controlling most motor types: AC induction motors (ACIM),
permanent magnet AC motors (PMAC), both brushless (BLDC) and brush DC motors
(BDC), switched (SRM) and variable reluctance motors (VRM), and stepper motors.
●4 analog watchdogs comparing ADC results against predefined levels (low, high,
range) before results are stored in the appropriate ADC result location
●2 modes of operation: Motor Control mode or Regular mode
●Regular mode features
–Register based interface with the CPU: control register, status register and 1 result
register per channel
–ADC state machine managing 3 request flows: regular command, hardware
injected command and software injected command
–Selectable priority between software and hardware injected commands
–DMA compatible interface
●CTU-controlled mode features
–Triggered mode only
–4 independent result queues (1×16 entries, 2×8 entries, 1×4 entries)
–Result alignment circuitry (left justified and right justified)
–32-bit read mode allows to have channel ID on one of the 16-bit part
–DMA compatible interfaces
1.5.27 Cross triggering unit (CTU)
The cross triggering unit allows automatic generation of ADC conversion requests on user
selected conditions without CPU load during the PWM period and with minimized CPU load
for dynamic configuration.
It implements the following features:
●Double buffered trigger generation unit with up to 8 independent triggers generated
from external triggers
●Trigger generation unit configurable in sequential mode or in triggered mode
●Each trigger can be appropriately delayed to compensate the delay of external low
pass filter
●Double buffered global trigger unit allowing eTimer synchronization and/or ADC
command generation
●Double buffered ADC command list pointers to minimize ADC-trigger unit update
●Double buffered ADC conversion command list with up to 24 ADC commands
●Each trigger capable of generating consecutive commands
●ADC conversion command allows to control ADC channel, single or synchronous
sampling, independent result queue selection
1.5.28 Nexus Development Interface (NDI)
The NDI (Nexus Development Interface) block is compliant with Nexus Class 1 of the IEEEISTO 5001-2003 standard. This development support is supplied for MCUs without requiring
external address and data pins for internal visibility. The NDI block is an integration of
several individual Nexus blocks that are selected to provide the development support
interface for this device. The NDI block interfaces to the host processor and internal busses
to provide development support as per the IEEE-ISTO 5001-2003 Nexus Class 1 standard.
The development support provided includes access to the MCU’s internal memory map and
access to the processor’s internal registers.
The NDI provides the following features:
●Configured via the IEEE 1149.1
●All Nexus port pins operate at V
●Nexus Class 1 supports Static debug
(no dedicated power supply)
DDIO
1.5.29 Cyclic redundancy check (CRC)
The CRC computing unit is dedicated to the computation of CRC off-loading the CPU. The
CRC module features:
●Support for CRC-16-CCITT (
16
12
26
+
+
5
x
+ 1
23
x
+
–
x
+
x
●Support for CRC-32 (Ethernet protocol):
32
–
x
+
x
●Zero wait states for each write/read operations to the CRC_CFG and CRC_INP
x
25 protocol):
22
16
12
11
10
8
7
5
4
x
+
x
+
x
+
x
+
x
+
x
+
x
+
x
+
2
x
+
x
+ x + 1
registers at the maximum frequency
1.5.30 IEEE 1149.1 JTAG controller
The JTAG controller (JTAGC) block provides the means to test chip functionality and
connectivity while remaining transparent to system logic when not in test mode. All data
input to and output from the JTAGC block is communicated in serial format. The JTAGC
block is compliant with the IEEE standard.
The JTAG controller provides the following features:
●IEEE test access port (TAP) interface 4 pins (TDI, TMS, TCK, TDO)
●Selectable modes of operation include JTAGC/debug or normal system operation.
●5-bit instruction register that supports the following IEEE 1149.1-2001 defined
instructions:
–BYPASS
–IDCODE
–EXTEST
–SAMPLE
–SAMPLE/PRELOAD
●5-bit instruction register that supports the additional following public instructions:
–ACCESS_AUX_TAP_NPC
–ACCESS_AUX_TAP_ONCE
●3 test data registers:
–Bypass register
–Boundary scan register (size parameterized to support a variety of boundary scan
chain lengths)
–Device identification register
●TAP controller state machine that controls the operation of the data registers,