Freescale Semiconductor
Technical Information Center, CH370
1300 N. Alma School Road
Chandler, Arizona 85224
+1-800-521-6274 or +1-480-768-2130
support@freescale.com
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
support.japan@freescale.com
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
support.asia@freescale.com
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
LDCForFreescaleSemiconductor@hibbertgroup.com
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 experts. 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.
Freescale™ and the Freescale logo are trademarks of Freescale
Semiconductor, Inc. All other product or service names are the property of their
respective owners.
Signal Descriptions
ColdFire Core
Enhanced Multiply-Accumulate Unit (EMAC)
Memory Management Unit (MMU)
Floating-Point Unit (FPU)
Local Memory
Debug Support
System Integration Unit (SIU)
Internal Clocks and Bus Architecture
General Purpose Timers (GPT)
Slice Timers (SLT)
Interrupt Controller (INTC)
Edge Port Module (EPORT)
General Purpose I/O (GPIO)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
System SRAM
FlexBus
SDRAM Controller (SDRAMC)
PCI Bus Controller (PCI)
PCI Bus Arbiter (PCIARB)
FlexCAN
Integrated Secuity Engine (SEC)
IEEE 1149.1 Test Access Port (JTAG)
Multichannel DMA (MCD)
Comm Timer Module (CTM)
Programmable Serial Controller (PSC)
2
C interface
I
DMA Serial Peripheral Interface (DSPI)
USB 2.0 Device Controller
30
31
A
IND
Fast Ethernet Controller (FEC)
Mechanical Data
Register Memory Map Quick Reference
Index
Contents
Paragraph
Number
Title
Page
Number
Chapter 1
Overview
1.1MCF548x Family Overview ........................................................................................... 1-1
The primary objective of this reference manual is to define the functionality of the MCF548x processors
for use by software and hardware developers.
The information in this book is subject to change without notice, as described in the disclaimers on the title
page of this book. As with any technical documentation, it is the readers’ responsibility to be sure they are
using the most recent version of the documentation.
To locate any published errata or updates for this document, refer to the world-wide web at
http://www.freescale.com/coldfire.
Audience
This manual is intended for system software and hardware developers and applications programmers who
want to develop products for the MCF548x. It is assumed that the reader understands operating systems,
microprocessor system design, basic principles of software and hardware, and basic details of the ColdFire
architecture.
Organization
Following is a summary and a brief description of the major sections of this manual:
•Chapter 1, “Overview,” includes general descriptions of the modules and features incorporated in
the MCF548x, focussing in particular on new features.
•Chapter 2, “Signal Descriptions,” provides an alphabetical listing of MCF548x signals, including
which are inputs or outputs, how they are multiplexed, and the state of each signal at reset.
•Part I, “Processor Core,” is intended for system designers who need to understand the operation of
the MCF548x ColdFire core and its enhanced multiply/accumulate (EMAC) execution unit. It
describes the programming and exception models, Harvard memory implementation, and debug
module. Part 1 contains the following chapters:
— Chapter 3, “ColdFire Core,” provides an overview of the microprocessor core of the
MCF548x. The chapter begins with a description of enhancements from the V3 ColdFire core,
and then fully describes the V4e programming model as it is implemented on the MCF548x. It
also includes a full description of exception handling, data formats, an instruction set summary,
and a table of instruction timings.
— Chapter 4, “Enhanced Multiply-Accumulate Unit (EMAC),” describes the MCF548x
enhanced multiply/accumulate unit, which executes integer multiply, multiply-accumulate, and
miscellaneous register instructions. The EMAC is integrated into the operand execution
pipeline (OEP).
— Chapter 5, “Memory Management Unit (MMU),” describes describes the ColdFire virtual
memory management unit (MMU), which provides virtual-to-physical address translation and
memory access control.
— Chapter 6, “Floating-Point Unit (FPU),” describes instructions implemented in the
floating-point unit (FPU) designed for use with the ColdFire family of microprocessors.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorxli
— Chapter 7, “Local Memory,” describes the MCF548x implementation of the ColdFire V4e
local memory specification.
— Chapter 8, “Debug Support,” describes the Revision C enhanced hardware debug support in the
MCF548x. This revision of the ColdFire debug architecture encompasses earlier revisions.
•Part II, “System Integration Unit,” describes the system integration unit, which provides overall
control of the bus and serves as the interface between the ColdFire core processor complex and
internal peripheral devices. It includes a general description of the SIU and individual chapters that
describe components of the SIU, such as the interrupt controller, general purpose timers, slice
timers, and GPIOs. Part II contains the following chapters:
— Chapter 9, “System Integration Unit (SIU),” describes the SIU programming model, bus
arbitration, and system-protection functions for the MCF548x.
— Chapter 10, “Internal Clocks and Bus Architecture,” describes the clocking and internal buses
of the MCF548x and discusses the main functional blocks controlling the XL bus and the XL
bus arbiter.
— Chapter 11, “General Purpose Timers (GPT),” describes the functionality of the four general
purpose timers, GPT0–GPT3.
— Chapter 12, “Slice Timers (SLT),” describes the two slice timers, shorter term periodic
interrupts, used in the MCF548x.
— Chapter 13, “Interrupt Controller,” describes operation of the interrupt controller portion of the
SIU. Includes descriptions of the registers in the interrupt controller memory map and the
interrupt priority scheme.
— Chapter 14, “Edge Port Module (EPORT),” describes EPORT module functionality.
— Chapter 15, “GPIO,” describes the operation and programming model of the parallel port pin
assignment, direction-control, and data registers.
•Part III, “On-Chip Integration,” describes the on-chip integration for the MCF548x device. It
includes descriptions of the system SRAM, FlexBus interface, SDRAM controller, PCI, and SEC
cryptography accelerator. Part III contains the following chapters:
— Chapter 16, “32-Kbyte System SRAM,” describes the MCF548x on-chip system SRAM
implementation. It covers general operations, configuration, and initialization.
— Chapter 17, “FlexBus,” describes data transfer operations, error conditions, and reset
operations. It describes transfers initiated by the MCF548x and by an external master, and
includes detailed timing diagrams showing the interaction of signals in supported bus
operations.
— Chapter 18, “SDRAM Controller (SDRAMC),” describes configuration and operation of the
synchronous DRAM controller component of the SIU. It includes a description of signals
involved in DRAM operations, including chip select signals and their address, mask, and
control registers.
— Chapter 19, “PCI Bus Controller,” details the operation of the PCI bus controller for the
MCF548x.
— Chapter 20, “PCI Bus Arbiter Module,” describes the MCF548x PCI bus arbiter module,
including timing for request and grant handshaking, the arbitration process, and the register in
the PCI bus arbiter programing model.
MCF548x Reference Manual, Rev. 3
xliiFreescale Semiconductor
Suggested Reading
— Chapter 21, “FlexCAN,” describes the MCF548 implementation of the controller area network
(CAN) protocol. This chapter describes FlexCAN module operation and provides a
programming model.
— Chapter 22, “Integrated Security Engine (SEC),” provides an overview of the MCF548x
security encryption controller.
— Chapter 23, “IEEE 1149.1 Test Access Port (JTAG),” describes configuration and operation of
the MCF548x JTAG test implementation. It describes the use of JTAG instructions and
provides information on how to disable JTAG functionality.
•Part IV, “Communications Subsystem,” contains chapters that discuss the operation and
configuration of the communications I/O subsystem including the MCF548x multichannel DMA,
communications timer, PSC, FEC, DSPI, and USB2, and I2C.
— Chapter 24, “Multichannel DMA,” provides an overview of the multichannel DMA controller
module including the operation of the external DMA request signals.
— Chapter 25, “Comm Timer Module (CTM),” contains a detailed description of the
communications timer module, which functions as a baud clock generator or as a DMA task
initiator.
— Chapter 26, “Programmable Serial Controller (PSC),” provides an overview of asynchronous,
synchronous, and IrDA 1.1 compliant receiver/transmitter serial communications of the
MCF548x.
— Chapter 27, “DMA Serial Peripheral Interface (DSPI),” describes the use of the DMA serial
peripheral interface (DSPI) implemented on the MCF548x processor, including details of the
DSPI data transfers. The chapter concludes with timing diagrams and the DSPI features that
support Tx and Rx FIFO queue management.
— Chapter 28, “I2C Interface,” describes the MCF548x I2C module, including I2C protocol,
clock synchronization, and the registers in the I2C programing model. It also provides
programming examples.
— Chapter 29, “USB 2.0 Device Controller,” provides an overview of the USB 2.0 device
controller module used in the MCF548x.
— Chapter 30, “Fast Ethernet Controller (FEC),” provides a feature-set overview, a functional
block diagram, and transceiver connection information for both MII (Media Independent
Interface) and 7-wire serial interfaces. It also provides describes operation and the
programming model.
•Part V, “Mechanical,” provides a pinout and both electrical and functional descriptions of the
MCF548x signals. It also describes how these signals interact to support the variety of bus
operations shown in timing diagrams.
— Chapter 31, “Mechanical Data,” provides a functional pin listing and package diagram for the
MCF548x.
Suggested Reading
This section lists additional reading that provides background for the information in this manual as well as
general information about the ColdFire architecture.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorxliii
General Information
The following documentation provides useful information about the ColdFire architecture and computer
architecture in general:
•ColdFire Programmers Reference Manual (CFPRM)
•Using Microprocessors and Microcomputers: The Motorola Family, William C. Wray, Ross
Bannatyne, Joseph D. Greenfield
•Computer Architecture: A Quantitative Approach, Second Edition, by John L. Hennessy and David
A. Patterson.
•Computer Organization and Design: The Hardware/Software Interface, Second Edition, David A.
Patterson and John L. Hennessy.
ColdFire Documentation
The ColdFire documentation is available from the sources listed on the back cover of this manual.
Document order numbers are included in parentheses for ease in ordering.
•Reference manuals—These books provide details about individual ColdFire implementations and
are intended to be used in conjunction with The ColdFire Programmers Reference Manual. These
include the following:
Additional literature on ColdFire implementations is being released as new processors become available.
For a current list of ColdFire documentation, refer to the World Wide Web at
http://www.freescale.com/coldfire.
Conventions
This document uses the following notational conventions:
MNEMONICSIn text, instruction mnemonics are shown in uppercase.
mnemonicsIn code and tables, instruction mnemonics are shown in lowercase.
italicsItalics indicate variable command parameters.
Book titles in text are set in italics.
0x0Prefix to denote hexadecimal number
0b0Prefix to denote binary number
REG[FIELD]Abbreviations for registers are shown in uppercase. Specific bits, fields, or ranges
appear in brackets. For example, RAMBAR[BA] identifies the base address field
in the RAM base address register.
nibble A 4-bit data unit
byte An 8-bit data unit
word A 16-bit data unit
MCF548x Reference Manual, Rev. 3
xlivFreescale Semiconductor
Acronyms and Abbreviations
longword A 32-bit data unit
xIn some contexts, such as signal encodings, x indicates a don’t care.
nUsed to express an undefined numerical value
¬NOT logical operator
&AND logical operator
|OR logical operator
Register Conventions
This reference manual uses the register diagram format shown below.
31302928272625242322212019181716
R0000000000000000
W
Reset0000000000000000
1514131211109876543210
R00000000000DFL
W
Reset0000000000000000
Reg
Addr
0x00C
Table i. Example Register Diagram
Acronyms and Abbreviations
Table ii lists acronyms and abbreviations used in this document.
Table ii. . Acronyms and Abbreviated Terms
Ter mMe a ning
ADCAnalog-to-digital conversion
ALUArithmetic logic unit
AVECAutovector
BDMBackground debug mode
BISTBuilt-in self test
BSDLBoundary-scan description language
CODECCode/decode
comm busInternal communications bus
DACDigital-to-analog conversion
DMADirect memory access
DSPDigital signal processing
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorxlv
Table ii. . Acronyms and Abbreviated Terms (continued)
Ter mMe a ning
EAEffective address
EDOExtended data output (DRAM)
FIFOFirst-in, first-out
GPIOGeneral-purpose I/O
2
CInter-integrated circuit
I
IEEEInstitute for Electrical and Electronics Engineers
IFPInstruction fetch pipeline
IPLInterrupt priority level
JEDECJoint Electron Device Engineering Council
JTAGJoint Test Action Group
LIFOLast-in, first-out
LRULeast recently used
LSBLeast-significant byte
lsbLeast-significant bit
MACMultiple accumulate unit
MBARMemory base address register
MSBMost-significant byte
msbMost-significant bit
MuxMultiplex
NOPNo operation
OEPOperand execution pipeline
PCProgram counter
PCLKProcessor clock
PLLPhase-locked loop
PLRUPseudo least recently used
PORPower-on reset
PQFPPlastic quad flat pack
RISCReduced instruction set computing
RxReceive
SIMSystem integration module
SOFStart of frame
TAPTest access port
TTLTransistor-to-transistor logic
TxTransmit
MCF548x Reference Manual, Rev. 3
xlviFreescale Semiconductor
Table ii. . Acronyms and Abbreviated Terms (continued)
Table iii shows notational conventions used throughout this document.
Table iii. Notational Conventions
InstructionOperand Syntax
Opcode Wildcard
ccLogical condition (example: NE for not equal)
Register Specifications
AnAny address register n (example: A3 is address register 3)
Ay,AxSource and destination address registers, respectively
DnAny data register n (example: D5 is data register 5)
Dy,DxSource and destination data registers, respectively
Terminology and Notational Conventions
RcAny control register (example VBR is the vector base register)
RmMAC registers (ACC, MAC, MASK)
RnAny address or data register
RwDestination register w (used for MAC instructions only)
Ry,RxAny source and destination registers, respectively
Xiindex register i (can be an address or data register: Ai, Di)
Register Names
ACCMAC accumulator register
CCRCondition code register (lower byte of SR)
MACSRMAC status register
MASKMAC mask register
PCProgram counter
SRStatus register
Port Name
PSTDDATAProcessor status/debug data port
Miscellaneous Operands
#<data>Immediate data following the 16-bit operation word of the instruction
<ea>Effective address
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorxlvii
Table iii. Notational Conventions (continued)
InstructionOperand Syntax
<ea>y,<ea>xSource and destination effective addresses, respectively
<label>Assembly language program label
<list>List of registers for MOVEM instruction (example: D3–D0)
<shift>Shift operation: shift left (<<), shift right (>>)
<size>Operand data size: byte (B), word (W), longword (L)
bcBoth instruction and data caches
dcData cache
icInstruction cache
# <vector>Identifies the 4-bit vector number for trap instructions
<>identifies an indirect data address referencing memory
<xxx>identifies an absolute address referencing memory
dnSignal displacement value, n bits wide (example: d16 is a 16-bit displacement)
SFScale factor (x1, x2, x4 for indexed addressing mode, <<1n>> for MAC operations)
Operations
+Arithmetic addition or postincrement indicator
–Arithmetic subtraction or predecrement indicator
xArithmetic multiplication
/Arithmetic division
~Invert; operand is logically complemented
&Logical AND
|Logical OR
^Logical exclusive OR
<<Shift left (example: D0 << 3 is shift D0 left 3 bits)
>>Shift right (example: D0 >> 3 is shift D0 right 3 bits)
→Source operand is moved to destination operand
←→Two operands are exchanged
sign-extendedAll bits of the upper portion are made equal to the high-order bit of the lower portion
If <condition>
then
<operations>
else
Test the condition. If true, the operations after ‘then’ are performed. If the condition is false and the
optional ‘else’ clause is present, the operations after ‘else’ are performed. If the condition is false
and else is omitted, the instruction performs no operation. Refer to the Bcc instruction description
as an example.
<operations>
Subfields and Qualifiers
{}Optional operation
()Identifies an indirect address
d
n
Displacement value, n-bits wide (example: d16 is a 16-bit displacement)
MCF548x Reference Manual, Rev. 3
xlviiiFreescale Semiconductor
Table iii. Notational Conventions (continued)
InstructionOperand Syntax
AddressCalculated effective address (pointer)
BitBit selection (example: Bit 3 of D0)
lsbLeast significant bit (example: lsb of D0)
LSBLeast significant byte
LSWLeast significant word
msbMost significant bit
MSBMost significant byte
MSWMost significant word
Condition Code Register Bit Names
CCarry
NNegative
VOverflow
XExtend
ZZero
Terminology and Notational Conventions
Table iv. MCF548x Revision History
Section/PageSubstantive Changes
Revision 1.0 (03/2004)
Initial release.
Revision 1.1 (03/2004
Figure 15-1/Page 15-2Changed instances of FEC2 to FEC1 and FEC1 to FEC0.
30.3.1/30-6–
30.3.3.1/30-10
Chapter 17Took out FlexCan chapter. Fixed timing diagrams in FlexBus chapter.
ThroughoutAdded all documentation errata from Revision 3 of the MCF5485RMAD document as described below.
Changed instances of FEC2 to FEC1 and FEC1 to FEC0.
Revision 1.2 (03/2004)
Revision 2.0 (10/2004)
Many content changes, the biggest being greatly enhancing the MC-DMA chapter and adding Clocks and
Internal Buses chapter. Many editorial changes.
Revision 2.1 (10/2004)
Revision 3.0 (01/2006)
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorxlix
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
Table 2-1/2-3Add column to indicate whether the signal has a pull-up resistor.
These signals have a pull-up resistor at all times:
DSCLK/TRST, BKPT/TMS, DSI/TDI
These signals have a pull-up resistor whenever configured for general-purpose input (default state after
reset):
PCIBR[4:3], PCIGNT[4:3], E1MDIO, E1MDC, E1TXCLK, E1TXEN, E1TXD[3:0], E1COL, E1RXCLK,
E1RXDV, E1RXD[3:0], E1CRS, E1TXER, E1RXER
Table 2-1/2-3Remove overbars from the following signals: FBADDR1, FBADDR0, SDDATA, SDADDR, SDBA, TIN3,
TOUT3
Table 2-1/2-3In entry AD6, remove overbar from ALE
enable”
Table 2-1/2-3Add overbars to IRQ[6:5].
Table 2-2/2-10 • Replace PPSCLn entries under the GPIO column with PPSC1PSC0n. There is no PPSCL port.
• Replace PPSCHn entries under the GPIO column with PPSC3PSC2n. There is no PPSCH port.
Table 2-2/2-10The GPIO bit number for each of the UART control signals are incorrect for Table 2-2. However, they are
correct for Table 2-1:
•Y23/PSC1RTS
•AB23/PSC3RTS
pin: Change GPIO entry from PPSCL7 to PPSC1PSC06.
pin: Change GPIO entry from PPSCH7 to PPSC3PSC26.
•AB26/PSC0RTS pin: Change GPIO entry from PPSCL3 to PPSC1PSC02.
• AC19/PSC2CTS pin: Change GPIO entry from PPSCH2 to PPSC3PSC23.
• AD26/PSC2RTS
pin: Change GPIO entry from PPSCH3 to PPSC3PSC22.
•AE23/PSC0CTS pin: Change GPIO entry from PPSCL2 to PPSC1PSC03.
• AF23/PSC3CTS pin: Change GPIO entry from PPSCH6 to PPSC3PSC27.
• AF25/PSC1CTS
pin: Change GPIO entry from PPSCL6 to PPSC1PSC07.
Table 2-2/2-10Remove overbars from the following signals: IVDD, TCK, PLLVDD, PSTDDATA1, PSTDDATA7, SDDATA21,
Table 2-2/2-10Add overbars to the following signals: IRQ3, IRQ2
and change description from “Transfer start” to “Address latch
Table 2-4/2-22Replace table with the following:
Table 1. MCF548x Divide Ratio Encodings
Clock
AD[12:8]
1
2
1
000111:241.6–50.083.33–100166.66–200
001011:225.0–41.550.0–83.0
011111:425.0100200
All other values of AD[12:8] are reserved.
Note that DDR memories typically have a minimum speed of 83 MHz. Some vendors specifiy
down to 75 MHz. Check with the memory component specifications to verify.
CLKIN–PCI and FlexBus
Ratio
Frequency Range (MHz)
Internal XLB, SDRAM
bus, and PSTCLK
Frequency Range (MHz)
2
Core Frequency
Range (MHz)
100.0–166.66
MCF548x Reference Manual, Rev. 3
lFreescale Semiconductor
Terminology and Notational Conventions
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
2.2.6.1/2-22Add the following after Table 2-4:
Figure 1 correlates CLKIN, internal bus, and core clock frequencies for the 1x–4x multipliers.
Figure 1. CLKIN, Internal Bus, and Core Clock Ratios
100.0
100.0
3.8.1/3-38Change the second sentence of the first paragraph from “The second holds the 32-bit program counter
address of the faulted instruction.“ to “The second holds the 32-bit program counter address of the faulted
or interrupted instruction.”
Table 3-23/3-40The “Interrupt exception” entry’s description is outdated. Change from “Interrupt exception processing, with
interrupt recognition and vector fetching, includes uninitialized and spurious interrupts as well as those
where the requesting device supplies the 8-bit interrupt vector. Autovectoring can optionally be configured
through the system interface module (SIM).” to “Please refer to Chapter 13 ‘Interrupt Controller.’”
Table 10-2/10-5Add missing table using Ta bl e 1 from this document.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorli
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
10.2/10-5Insert the following section before section 10.2 “XL Bus Arbiter”.
10.2 PLL
10.2.1 PLL Memory Map/Register Descriptions
MBAR OffsetNameByte0Byte1Byte2Byte3Access
0x300System PLL Control RegisterSPCRR/W
10.2.2 System PLL Control Register (SPCR)
The system PLL control register (SPCR) defines the clock enables used to control clocks to a set of peripherals. Unused peripherals
can have their clock stopped, reducing power consumption. In addition, the SPCR contains a read-only bit for the system PLL lock
status. At reset, the clock enables are set, enabling all system PLL gated output clocks.
31302928272625242322212019181716
RPLLK000000000000000
W
Reset1000000000000000
1514131211109876543210
R
W
Reset0111111111111111
AddrMBAR + 0x300
0
CORENCRY
ENB
CRY
ENA
Table 2. System PLL Memory Map
CAN1
EN
PSC
0
0
EN
USBENFEC1ENFEC0ENDMAENCAN0ENFBENPCIENMEM
EN
Figure 2. System PLL Control Register (SPCR)
Table 3. SPCR Field Descriptions
BitsName Description
31PLLKSystem PLL Lock Status - Read-only lock status of the system PLL.
30-15—Reserved, should be cleared.
14CORENCore & Communications Sub-System Clock Enable - Controls clocks for the CF4 Core, System SRAM, CommBus
13CRYENBCrypto Clock Enable B - Controls the fast clock to the SEC
12CRYENACrypto Clock Enable A - Controls the slow clock to the SEC
11CAN1ENCAN1 Clock Enable
10—Reserved, should be cleared.
9PSCENPSC Clock Enable - Controls clock for all PSC modules.
8—Reserved, should be cleared.
7USBENUSB Clock Enable
6FEC1ENFEC1 Clock Enable
5FEC0ENFEC0 Clock Enable
4DMAENMulti-channel DMA Clock Enable
3CAN0ENCAN0 Clock Enable
2FBENFlexBus Clock Enable
1PCIENPCI Bus Clock Enable
0MEMENMemory Clock Enable - Controls clocks of the SDRAM controller module
1 PLL has obtained frequency lock
0 PLL has not locked
Arbiter, I2C, Comm Timers, and External DMA modules
MCF548x Reference Manual, Rev. 3
liiFreescale Semiconductor
Terminology and Notational Conventions
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
Table 10-3/10-5Bits BA, DT, and AT: The 0 and 1 are switched. Setting each bit enables operation, while clearing disables
operation. The 0 and 1 (or the corresponding descriptions) need to be swapped for all three bits.
11.4.2/11-8Remove all text from bullet item #2 starting with “This scenario works for all pulses except....” This errata
does not apply to this processor.
13.1.1/13-1Correct the cross-reference link at top of page that reads “Section 3.8.1, ‘Exception Stack Frame
Definition.’”
Table 15-27/15-24In the bit 7-6, PAR1_E1MDC entry, change ‘11’ bit setting description from: “E1MDC pin configured for
FEC1 MDC function” to “E1MDC pin configured for FEC1 E1MDC function” to be consistent with rest of
section.
Table 15-34/15-30Remove extraneous “/” from “DSPICS0//SS
Table 16-1/16-2Extend SSCR entry to include bytes 2 & 3 as well as bytes 0 and 1, since it is a 32 bit register.
17.6.5.4.2/17-23Change “transfer start” to “address latch enable” in second sentence.
21.4.9/21-28Figure 21-14 and Table 21-18 are missing. Add them as shown below and correct the cross-references to
them.
NRZ Signal
” in second sentence of the PAR_CS0 bit description.
SYNC_SEG
14 ... 162 ... 8
Time Segment 1Time Segment 2
(PROP_SEG + PSEG1 + 2) (PSEG2 + 1)
8 ... 25 Time Quanta
= 1 Bit Time
Transmit Point
Sample Point
(single or triple sampling)
Figure 21-14. Segments within the Bit Time
Table 21-18. Time Segment Syntax
SyntaxDescription
SYNC_SEGSystem expects transitions to occur on the bus during this period.
Transmit PointA node in transmit mode transfers a new value to the CAN bus at this point.
Sample PointA node samples the bus at this point. If the three samples per bit option is selected,
then this point marks the position of the third sample.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorliii
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
21.4.9/21-28Add the following table below the note at the end of the section and correct the cross-reference pointing to
it:
Table 21-19. CAN Standard Compliant Bit Time Segment Settings
Time Segment 1Time Segment 2
5 .. 1021 .. 2
4 .. 1131 .. 3
5 .. 1241 .. 4
6 .. 1351 .. 4
7 .. 1461 .. 4
8 .. 1571 .. 4
9 .. 1681 .. 4
Re-synchronization
Table 23-5/23-7The JTAG IR codes are incorrect. Replace table with the following:
F
Instruction IR[5:0]Instruction Summary
EXTEST000000 Selects boundary scan register while applying fixed values to output
pins and asserting functional reset
SAMPLE000001 Selects boundary scan register for shifting, sampling, and preloading
without disturbing functional operation
IDCODE011101 Selects IDCODE register for shift
CLAMP011111 Selects bypass while applying fixed values to output pins and
asserting functional reset
HIGHZ111101
Selects bypass register while tri-stating all output pins and asserting
functional reset
Jump Width
ENABLE000010 Selects TEST_CTRL register
BYPASS111111 Selects bypass register for data operations
23.4.3/23-7Remove the TEST_LEAKAGE section, as the instruction is not supported.
23.4.3/23-7Remove the LOCKOUT_RECOVERY section, as the instruction is not supported.
Table 24-18/24-20Correct Base Address Mask Register 1 mnemonic from EREQMASK0 to EREQMASK1.
24.3.4.2/24-20Correct overbar in first sentence. From “After DREQ is asserted,
this register contains...” to “After DREQ
is asserted, this register contains...”
MCF548x Reference Manual, Rev. 3
livFreescale Semiconductor
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
25.1.2/25-2Add the following section after section 24.1.2:
24.1.3 Comm Timer External Clock[7:0]
The comm timer external clock is the alternate clock signal and is provided by the user. The user must write
a 1 to CTCR[S] in the variable channel and write a 1001 to CTCR[S] within the fixed channel to select this
signal. If this signal is selected, all timing will be with respect to this clock signal. This signal is restricted to
being half the frequency or less of the system bus clock.
Table 0-4. Comm Timers External Clock
Timer ChannelExternal Signal
0TIN0
1TIN1
2TIN2
3TIN3
4PSC3BCLK
5PSC2BCLK
6PSC1BCLK
7PSC0BCLK
Terminology and Notational Conventions
Table 25-3/25-5In the S bit description change the 1001 setting from “Reserved” to “External clock”
Table 25-4/25-6The S bit field is incorrect. Bits 31-29 should be reserved, and only bit 28 should be the S bit. And the S bit
description should be:
Clock enable source select. Selects the clock rate for the fixed timer channels. The clock rate for the timer
is the internal system clock divided by an 8-bit prescaler.
1 External Clock
0 Sysclk
Note: The external bus clock cannot be an faster than half the frequency of the system clock.
26.1/26-1Fix broken cross-reference to Figure 26-1.
Table 26-13/26-19In description of TXRDY change PSCTFALARM to PSCTFAR
Table 26-30/26-29In description of ALARM change instance of “less than alarm bytes” to “more than alarm bytes” and change
instance of “more than alarm bytes” to “less than alarm bytes”.
26.3.3.24/26-30Change bit 30 to reserved, as the WFR field is only one-bit wide.
Figure 26-22/Page
Remove shading from W field as the PSCRFARn and PSCTFARn
registers are R/W accessible.
26-32
26.4/26-35Add section 15.3.7 “PSC FIFO System” from the MPC5200 User’s Manual to before section 26.4.9
“Looping Modes.” Change the following text to apply to the MCF548x:
Figure 28-1/Page 28-1Change IFDR to I2FDR and IADR to I2ADR in figure.
28.3.2.1/28-3Change instances of I2AR to I2ADR.
28.3.2.3/28-5Change I2ICR to I2CR throughout section.
Chapter 28, “I2C
After section 27.3.2.4, change instances of R/W to R/W
throughout chapter.
Interface”
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorlv
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
27.6.1/27-5Remove instances of MDIS bit as it is not present on this version of the DSPI.
Table 29-3/29-11USBCR[APPLOCK] bit description, the bit setting numbers are incorrrect. When cleared (0), APPLOCK is
deasserted. When set (1), APPLOCK is asserted.
Table 29-29/29-30Endpoint status register’s PSTALL entry: the last sentence should be “Setting this bit also sets
USBAISR[EPSTALL].” instead of “Setting this bit also sets USBAISR[EPHALT].”
Table 29-37/29-36EPnISR[EOT] bit description, add a note to the last sentence of the first paragraph stating “The EOT
interrupt will not assert for an isochronous OUT packet that experiences a PID sequencing error.”
29.4.3.1/29-51Add a section below USB Packets entitled “Handshakes” with the following paragraphs:
“The USB device will return a NYET handshake packet to an OUT transaction if there is already data
present in the FIFO and there are less than 2*MAXPACKETSIZE bytes free in the FIFO.
In cases where the FIFO depth is larger than 2*MAXPACKETSIZE (i.e. 3x or 4x), the following behavior
will occur. If after a transfer that returned a NYET handshake there is at least 1*MAXPACKETSIZE of free
space in the FIFO, the device will ACK the first PING request from the host and accept another
MAXPACKETSIZE transfer from the host. The device will again send a NYET handshake.
The only time the device will NAK a PING is when there is less than 1*MAXPACKETSIZE of free space in
the FIFO.”
Table 30-41/30-42Change bit description of the FECFRST[SW_RST] bit to “Software Reset - This bit controls the soft reset
of the FEC FIFOs. A soft reset will reset the FIFO pointers and byte counters but not the status and control
registers. To cause a soft reset this bit should be set and then cleared by application software.”
Change bit description of the FECFRST[RST_CTL] bit to “Reset control - Setting this bit allows the FEC
controller to perform a soft reset of the FIFOs when the FEC is disabled (ECR[ETHER_EN] cleared).”
Table 31-1/31-1Add column to indicate whether the signal has a pull-up resistor.
These signals have a pull-up resistor at all times:
DSCLK/TRST, BKPT/TMS, DSI/TDI
These signals have a pull-up resistor whenever configured for general-purpose input (default state after
reset):
PCIBR[4:3], PCIGNT[4:3], E1MDIO, E1MDC, E1TXCLK, E1TXEN, E1TXD[3:0], E1COL, E1RXCLK,
E1RXDV, E1RXD[3:0], E1CRS, E1TXER, E1RXER
Table 31-1/31-1Ball P3 should be SD_VDD instead of EVDD.
Table 31-1/31-1The GPIO bit number for each of the UART control signals are incorrect for Table 31-1. However, they are
correct for Table 2-1:
•Y23/PSC1RTS
•AB23/PSC3RTS
•AB26/PSC0RTS pin: Change GPIO entry from PPSCL3 to PPSC1PSC02.
• AC19/PSC2CTS
• AD26/PSC2RTS
•AE23/PSC0CTS pin: Change GPIO entry from PPSCL2 to PPSC1PSC03.
• AF23/PSC3CTS
• AF25/PSC1CTS
Table 31-1/31-1Remove overbar from ALE
Table 31-1/31-1 • Replace PPSCLn entries under the GPIO column with PPSC1PSC0n. There is no PPSCL port.
• Replace PPSCHn entries under the GPIO column with PPSC3PSC2n. There is no PPSCH port.
pin: Change GPIO entry from PPSCL7 to PPSC1PSC06.
pin: Change GPIO entry from PPSCH7 to PPSC3PSC26.
pin: Change GPIO entry from PPSCH2 to PPSC3PSC23.
pin: Change GPIO entry from PPSCH3 to PPSC3PSC22.
pin: Change GPIO entry from PPSCH6 to PPSC3PSC27.
pin: Change GPIO entry from PPSCL6 to PPSC1PSC07.
at location AD6.
MCF548x Reference Manual, Rev. 3
lviFreescale Semiconductor
Table iv. MCF548x Revision History (continued)
Section/PageSubstantive Changes
Terminology and Notational Conventions
Figure 31-3/Page 31-10 Remove overbar from ALE
Figure 31-7/Page 31-14 Remove overbar from ALE
Figure 31-11/Page
Remove overbar from ALE
31-18
at location AD6.
at location AD6.
at location AD6.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductorlvii
MCF548x Reference Manual, Rev. 3
lviiiFreescale Semiconductor
Chapter 1
Overview
This chapter provides an overview of the MCF548x microprocessor features, including the major
functional components.
1.1MCF548x Family Overview
The MCF548x family is based on the ColdFire V4e core, a complex which comprises the ColdFire V4
central processor unit (CPU), an enhanced multiply-accumulate unit (EMAC), a memory management unit
(MMU), a double-precision floating point unit (FPU) conforming to standard IEEE-754, and controllers
for caches and local data memories. The MCF548x family is capable of performing at an operating
frequency of up to 200 MHz or 308 MIPS (Dhrystone 2.1).
To maximize throughput, the MCF548x family incorporates three independent external bus interfaces:
1. The general-purpose local bus (FlexBus) is used for system boot memories and simple peripherals
and has up to six chip selects.
2. Program code and data can be stored in SDRAM connected to a dedicated 32-bit double data rate
(DDR) bus that can run at up to one-half of the CPU core frequency. The glueless DDR SDRAM
controller handles all address multiplexing, input and output strobe timing, and memory bus clock
generation.
3. A 32-bit PCI bus compliant with the version 2.2 specification and running at a typical frequency
of 33 MHz or 66 MHz supports peripherals that require high bandwidth, the ability to arbitrate for
bus mastership, and access to internal MCF548x memory resources.
The MCF548x family provides substantial communications functionality by integrating the following
connectivity peripherals:
•Up to two 10/100 Mbps fast Ethernet controllers (FECs)
•One optional USB 2.0 device (slave) module with seven endpoints and an integrated transceiver
•Up to four UART/USART/IRDA/modem programmable serial controllers (PSCs)
•One DMA serial peripheral interface (DSPI)
•One inter-integrated circuit (I
•Two controller area network 2.0B (FlexCAN) interfaces with 16 message buffers each
Additionally, the MCF548x provides hardware support for a range of Internet security standards with an
optional bus-mastering cryptography accelerator. This module incorporates units to speed DES/3DES and
AES block ciphers, the RC4 stream cipher, bulk data hashing (MD5/SHA-1/SHA-256/HMAC), and
random number generation. Hardware acceleration of these functions is critical to avoiding the throughput
bottlenecks associated with software-only implementations of SSH, SSL/TLS, IPsec, SRTP, WEP, and
other security standards. The incorporation of cryptography acceleration makes the MCF548x family a
compelling solution for a wide range of office automation, industrial control, and SOHO networking
devices that must have the ability to securely transmit critical equipment control information across
typically insecure Ethernet data networks.
Additional features of MCF548x products include a watchdog timer, two 32-bit slice timers for RTOS
scheduling and alarm functionality, up to four 32-bit general-purpose timers with capture, compare, and
pulse width modulation capability, a multisource vectored interrupt controller, a phase-locked loop (PLL)
to generate the system clock, 32 Kbytes of SRAM for high-speed local data storage, and multiple
general-purpose I/O ports.
2C™
) bus controller
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-1
With on-chip support for multiple common communications interfaces, MCF548x products require only
the addition of memories and certain physical layer transceivers to be cost-effective system solutions for
many applications. Such applications include industrial routers, high-end POS terminals, building
automation systems, and process control equipment.
MCF548x products require four supply voltages: 1.5V for the high-performance, low power, internal core
logic, 2.5V for the DDR SDRAM bus interface, 1.25V for the DDR SDRAM V
, and 3.3V for all other
REF
I/O functionality, including the PCI and FlexBus interfaces.
1.2MCF548x Block Diagram
Figure 1-1 shows a top-level block diagram of the MCF548x products.
ColdFire V4e Core
FPU, MMU
EMAC
32K D-cache
32K I-cache
Interrupt
Controller
System
Watchdog
Integration Unit
Time r
Slice
Time rs x 2
GP
Time rs x 4
FlexCAN
x 2
Bus
Slave
PLL
DDR SDRAM
XL Bus
Arbiter
XL Bus
Master/Slave
Interface
Cryptography
Accelerator
32K System
SRAM
DMA
Read
3
R/W
Crypto
XL Bus
Read/Write
DMA
Write
Multichannel DMA
Master Bus Interface and FIFOs
Interface
Memory
Controller
FlexBus
Interface
FlexBus
Controller
PCI 2.2
Controller
PCI I/O Interface and Ports
PCI Interface
& FIFOs
CommBus
Perpheral I/O Interface & Ports
I/O Subsystem
DSPI
PSC x 4I2CFEC1
Perpheral Communications I/O Interface & Ports
1
Available in MCF5485, MCF5484, MCF5483, and MCF5482 devices.
2
Available in MCF5485, MCF5484, MCF5481, and MCF5480 devices.
3
Available in MCF5485, MCF5483, and MCF5481 devices.
FEC2
2
USB 2.0
DEVICE
USB 2.0
PHY
Communications
1
1
Figure 1-1. MCF548x Block Diagram
MCF548x Reference Manual, Rev. 3
1-2Freescale Semiconductor
MCF548x Family Products
1.3MCF548x Family Products
Table 1-1 summarizes the products available within the MCF548x product family. All products are
available in pin-compatible, 388-pin PBGA packaging allowing for ease of migration between products
within the family. A printed circuit board designed using the MCF5485/4 footprint is compatible with any
of the MCF548x family devices.
— Up to 200 MHz peak internal core frequency (308 Dhrystone 2.1 MIPS)
— Harvard architecture
– 32-Kbyte instruction cache
– 32-Kbyte data cache
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-3
— Memory management unit (MMU)
– Separate, 32-entry, fully-associative instruction and data translation lookahead buffers
— Floating point unit (FPU)
– Double-precision support that conforms to IEEE-754 standard
– Eight floating point registers
•Internal master bus (XLB) arbiter
— High performance split address and data transactions
— Support for various parking modes
•32-bit double data rate (DDR) synchronous DRAM (SDRAM) controller
— 66–133 MHz operation
— Supports both DDR and SDR DRAM
— Built-in initialization and refresh
— Up to four chip selects enabling up to 1 GB of external memory
•Version 2.2 peripheral component interconnect (PCI) bus
— 32-bit target and initiator operation
— Support for up to five external PCI masters
— 33–66 MHz operation with PCI bus to XLB divider ratios of 1:1, 1:2, and 1:4
•Flexible multi-function external bus (FlexBus)
— Supports operation with the following:
– Non-multiplexed 32-bit address and 32-bit data (32-bit address muxed over
PCI bus–PCI not usable)
– Multiplexed 32-bit address and 32-bit data (PCI usable)
– Multiplexed 32-bit address and 16-bit data
– Multiplexed 32-bit address and 8-bit data
— Provides a glueless interface to boot Flash/ROM, SRAM, and peripheral devices
— Up to six chip selects
— 33–66 MHz operation
•Communications I/O subsystem
— Intelligent 16-channel DMA controller
— Dedicated DMA channels for receive and transmit on all subsystem peripheral interfaces
— Up to two 10/100 Mbps fast Ethernet controllers (FECs), each with separate 2-Kbyte receive
and transmit FIFOs
— Universal serial bus (USB) version 2.0 device controller
– Support for one control and six programmable endpoints — interrupt, bulk, or isochronous
– 4 Kbytes of shared endpoint FIFO RAM and 1 Kbyte of endpoint descriptor RAM
– Integrated physical layer interface
— Up to four programmable serial controllers (PSCs) each with separate 512-byte receive and
transmit FIFOs for UART, USART, modem, codec, and IrDA 1.1 interfaces
—I2C peripheral interface
— Two FlexCAN controller area network 2.0B controllers each with 16 message buffers
— DMA serial peripheral interface (DSPI)
– Random number generator compliant with FIPS 140-1 standards for randomness and
non-determinism
— Dual-channel architecture permits single-pass encryption and authentication
•32-Kbyte system SRAM
— Arbitration mechanism shares bandwidth between internal bus masters (CPU, cryptography
accelerator, PCI, and DMA)
•System integration unit (SIU)
— Interrupt controller
— Watchdog timer
— Two 32-bit slice timers for periodic alarm and interrupt generation
— Up to four 32-bit general-purpose timers with capture, compare, and PWM capability
— General-purpose I/O ports multiplexed with peripheral pins
•Debug and test features
— Core debug support via ColdFire background debug mode (BDM) port
— Chip debug support via JTAG/ IEEE 1149.1 test access port
•PLL and clock generator
— 30–66.67 MHz input frequency range
•Operating Voltages
— 1.5V internal logic
— 2.5V DDR SDRAM bus I/O (1.25V V
REF
)
— 3.3V PCI, FlexBus, and all other I/O
•Estimated power consumption
— <1.5W
1.4.1ColdFire V4e Core Overview
The ColdFire V4e core is a variable-length RISC, clock-multiplied core that includes a Harvard memory
architecture, branch cache acceleration logic, and limited superscalar dual-instruction issue capabilities.
The limited superscalar design approaches dual-issue performance with the cost of a scalar execution
pipeline.
The ColdFire V4e processor core is comprised of two separate pipelines that are decoupled by an
instruction buffer. The four-stage instruction fetch pipeline (IFP) prefetches the instruction stream,
examines it to predict changes of flow, partially decodes instructions, and packages fetched data into
instructions for the operand execution pipeline (OEP). The IFP can prefetch instructions before the OEP
needs them, minimizing the wait for instructions. The instruction buffer is a 10 instruction, first-in-first-out
(FIFO) buffer that decouples the IFP and OEP by holding prefetched instructions awaiting execution in
the OEP. The OEP includes five pipeline stages: the first stage decodes instructions and selects operands
(DS), and the second stage generates operand addresses (OAG). The third and fourth stages fetch operands
(OC1 and OC2), and the fifth stage executes instructions (EX).
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-5
The ColdFire V4e processor contains a double-precision floating point unit (FPU). The FPU conforms to
the American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE)
Standard for Binary Floating-Point Arithmetic (ANSI/IEEE Standard 754). The FPU operates on 64-bit,
double-precision floating point data and supports single-precision and signed integer input operands. The
FPU programming model is like that in the MC68060 microprocessor. The FPU is intended to accelerate
the performance of certain classes of embedded applications, especially those requiring high-speed
floating point arithmetic computations.
The ColdFire V4e processor also incorporates the ColdFire memory management unit (MMU), which
provides virtual-to-physical address translation and memory access control. The MMU consists of
memory-mapped control, status, and fault registers that provide access to translation lookaside buffers
(TLBs). Software can control address translation and access attributes of a virtual address by configuring
MMU control registers and loading TLBs. With software support, the MMU provides demand-paged,
virtual addressing.
The ColdFire V4e core implements the ColdFire instruction set architecture revision B with support for
floating Point instructions. Additionally, the ColdFire V4e core includes the enhanced
multiply-accumulate unit (EMAC) for improved signal processing capabilities. The EMAC implements a
4-stage execution pipeline, optimized for 32 x 32-bit operations, with support for four 48-bit accumulators.
Supported operands include 16- and 32-bit signed and unsigned integers, as well as signed fractional
operands and a complete set of instructions to process these data types. The EMAC provides superb
support for execution of DSP operations within the context of a single processor at a minimal hardware
cost.
Refer to Chapter 3, “ColdFire Core,” for detailed information on the ColdFire V4e core architecture.
1.4.2Debug Module (BDM)
The ColdFire processor core debug interface is provided to support system debugging in conjunction with
low-cost debug and emulator development tools. Through a standard debug interface, users can access
real-time trace and debug information. This allows the processor and system to be debugged at full speed
without the need for costly in-circuit emulators.
The MCF548x debug module provides support in three different areas:
•Real-time trace support: The ability to determine the dynamic execution path through an
application is fundamental for debugging. The ColdFire solution implements an 8-bit parallel
output bus that reports processor execution status and data to an external BDM emulator system.
•Background debug mode (BDM): Provides low-level debugging in the ColdFire processor
complex. In BDM, the processor complex is halted and a variety of commands can be sent to the
processor to access memory and registers. The external BDM emulator uses a three-pin, serial,
full-duplex channel.
•Real-time debug support: BDM requires the processor to be halted, which many real-time
embedded applications cannot permit. Debug interrupts let real-time systems execute a unique
service routine that can quickly save key register and variable contents and return the system to
normal operation without halting. External development systems can access saved data, because
the hardware supports concurrent operation of the processor and BDM-initiated commands. In
addition, the option is provided to allow interrupts to occur.
1.4.3JTAG
The MCF548x family supports circuit board test strategies based on the Test Technology Committee of
IEEE and the Joint Test Action Group (JTAG). The test logic includes a test access port (TAP) consisting
of a 16-state controller, an instruction register, and three test registers (a 1-bit bypass register, a 256-bit
MCF548x Reference Manual, Rev. 3
1-6Freescale Semiconductor
MCF548x Family Features
boundary-scan register, and a 32-bit ID register). The boundary scan register links the device’s pins into
one shift register. Test logic, implemented using static logic design, is independent of the device system
logic. The MCF548x implementation can do the following:
•Perform boundary scan operations to test circuit board electrical continuity
•Sample MCF548x system pins during operation and transparently shift out the resultin the
boundary scan register
•Bypass the MCF548x for a given circuit board test by effectively reducing theboundary-scan
register to a single bit
•Disable the output drive to pins during circuit-board testing
•Drive output pins to stable levels
1.4.4On-Chip Memories
1.4.4.1Caches
There are two independent caches associated with the ColdFire V4e core complex: a 32-Kbyte instruction
cache and a 32-Kbyte data cache. Caches improve system performance by providing single-cycle access
to the instruction and data pipelines. This decouples processor performance from system memory
performance, increasing bus availability for on-chip DMA or external devices.
1.4.4.2System SRAM
The SRAM module provides a general-purpose 32-Kbyte memory block that the ColdFire core can access
in a single cycle. The location of the memory block can be set to any 32-Kbyte address boundary within
the 4-Gbyte address space. The memory is ideal for storing critical code or data structures, for use as the
system stack, or for storing FEC data buffers. Because the SRAM module is physically connected to the
processor's high-speed local bus, it can quickly service core-initiated accesses or memory-referencing
commands from the debug module.
The SRAM module is also accessible by multiple non-core bus masters, such as the DMA controller, the
encryption accelerator, and the PCI Controller.
1.4.5PLL and Chip Clocking Options
MCF548x products contain an on-chip PLL capable of accepting input frequencies from 30–66.66 MHz.
Table 1-2 contains the frequencies of the system buses for the members of the MCF548x family under
various core/SDRAM/PCI/Flexbus clocking options.
Table 1-2. MCF548x Family Clocking Options
Core
(MHz)
120.0–20060.0–10030.0–50.01:2
Internal XLB, SDRAM
Bus, and PSTCLK
Frequency (MHz)
CLKIN—PCI and FlexBus
Frequency (MHz)
Clock Ratio
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-7
1.4.6Communications I/O Subsystem
1.4.6.1DMA Controller
The communications subsystem contains an intelligent DMA unit that provides front line interrupt control
and data movement interface via a separate peripheral bus to the on-chip peripheral functions, leaving the
processor core free to handle higher level activities. This concurrent operation enables a significant boost
in overall system performance.
The communications subsystem can support up to 16 simultaneously enabled DMA tasks, with support for
up to two external DMA requests. It uses internal buffers to prefetch reads and post writes such that
bursting is used whenever possible. This optimizes both internal and external bus activity. The following
communications and computer control peripheral functions are integrated and controlled by the
communications subsystem:
•Up to two 10/100 Mbps fast Ethernet controllers (FECs)
•Optional universal serial bus (USB) version 2.0 device controller
•Up to four programmable serial controllers (PSCs)
•I2C peripheral interface
•DMA serial peripheral interface (DSPI)
•Two FlexCAN controller area network 2.0B controllers
1.4.6.210/100 Fast Ethernet Controller (FEC)
The FEC supports two standard MAC/PHY interfaces: 10/100 Mbps IEEE 802.3 MII and 10Mbps 7-wire
interface. The controller is full duplex, supports a programmable maximum frame length and
retransmission from the transmit FIFO following a collision.
Support for different Ethernet physical interfaces:
— 100 Mbps IEEE 802.3 MII
— 10 Mbps IEEE 802.3 MII
— 10 Mbps 7-wire interface
•IEEE 802.3 full-duplex flow control.
•Support for full-duplex operation (200 Mbps throughput) with a minimum system clock frequency
of 50 MHz.
•Support for half duplex operation (100 Mbps throughput) with a minimum system clock frequency
of 25 MHz.
•Retransmit from transmit FIFO following collision.
•Internal loopback for diagnostic purposes.
1.4.6.3USB 2.0 Device (Universal Serial Bus)
The USB module implementation on the MCF548x product family provides all the logic necessary to
process the USB protocol as defined by version 2.0 specification for peripheral devices. It features the
following:
•High-speed operation up to 480 Mbps, full-speed operation at 12 Mbps, and low-speed operation
at 1.5 Mbps
•Physical interface on chip
•Bulk, interrupt, and isochronous transport modes.
•Six programmable in/out endpoints and one control endpoint
MCF548x Reference Manual, Rev. 3
1-8Freescale Semiconductor
MCF548x Family Features
•4 Kbytes of shared endpoint FIFO RAM and 1 Kbyte of endpoint descriptor RAM
1.4.6.4Programmable Serial Controllers (PSCs)
The MCF548x product family supports four PSCs that can be independently configured to operate in the
following modes:
•Universal asynchronous receiver transmitter (UART) mode
— 5,6,7,8 bits of data plus parity
— Odd, even, none, or force parity
— Stop bit width programmable in 1/16 bit increments
— Parity, framing, and overrun error detection
— Automatic PSCCTS
•IrDA 1.0 SIR mode (SIR)
— Baud rate range of 2400–115200 bps
— Selectable pulse width: either 3/16 of the bit duration or 1.6 µs
•IrDA 1.1 MIR mode (MIR)
— Baud rate of 0.576 or 1.152 Mbps
•IrDA 1.1 FIR mode (FIR)
— Baud rate of 4.0 Mbps
•8-bit soft modem mode (modem8)
•16-bit soft modem mode (modem16)
•AC97 soft modem mode (AC97)
and PSCRTS modem control signals
Each PSC supports synchronous (USART) and asynchronous (UART) protocols. The PSCs can be used to
interface to external full-function modems or external codecs for soft modem support, as well as IrDA 1.1
or 1.0 interfaces. Both 8- and 16-bit data widths are supported. PSCs can be configured to support a
1200-baud plain old telephone system (POTS) modem, V.34 or V.90 protocols. The standard UART
interface supports connection to an external terminal/computer for debug support.
1.4.6.5I2C (Inter-Integrated Circuit)
The MCF548x product family provides an I2C two-wire, bidirectional serial bus for on-board
communication. It features the following:
•Multimaster operation with arbitration and collision detection
•Calling address recognition and interrupt generation
•Automatic switching from master to slave on arbitration loss
•Software-selectable acknowledge bit
•Start and stop signal generation and detection
•Bus busy status detection
1.4.6.6DMA Serial Peripheral Interface (DSPI)
The DSPI block operates as a basic SPI block with FIFOs providing support for external queue operation.
Data to be transmitted and data received reside in separate FIFOs. The FIFOs can be popped and pushed
by host software or by the system DMA controller. The DSPI supports these SPI features:
•Full-duplex, three-wire synchronous transfers
•Master and slave mode—two peripheral chip selects in master mode
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-9
•DMA support
1.4.6.7Controller Area Network (CAN)
The FlexCAN modules are communication controllers implementing the CAN protocol. The CAN
protocol can be used as an industrial control serial data bus, meeting the specific requirements of real-time
processing and reliable operation in a harsh EMI environment, while maintaining cost-effectiveness. Each
of the two CAN controllers on the MCF548x family products contains sixteen message buffers. The CAN
controllers can be configured to either function as an interface with two separate CAN networks, or as a
single 32 message buffer CAN network.
1.4.7DDR SDRAM Memory Controller
The DDR SDRAM memory controller is a glueless interface to DDR memories. The module uses a 32-bit
memory port and can address a maximum of 1 Gbyte of data with 16 64M x 8 (512-Mbit) devices, four
per chip select. The controller supplies two clock lines and respective inverted clock lines to help minimize
system complexity when using DDR. The module supports either DDR or SDR, but not both. This is due
to voltage differences between the memory technologies.
The supported memory clock rate is up to 133 MHz. At this memory clock rate, DDR memory can receive
data at an effective rate of up to 266 MHz.
•Support for up to 13 lines of row address, 11 lines of column address, two lines of bank address,
and up to four chip selects
•Memory bus width fixed at 32 bits
•Four chip selects support up to 1 GByte of SDRAM memory
•Support for page mode to maximize the data rate. Page mode remembers active pages for all four
chip selects
•Support for sleep mode and self refresh
•Cache line reads that can use critical word first. These reads can start in the center of a burst and
will wrap to the beginning. This allows the processor quicker access to a needed instruction.
All on-chip bus masters have access to DRAM. This includes PCI, the ColdFire V4e core, the
cryptography accelerator, and the DMA controller.
1.4.8Peripheral Component Interconnect (PCI)
The PCI controller is a PCI V2.2-compliant bus controller and arbiter. The PCI bus is capable of 66-MHz
operation with a 32-bit address/data bus and support for five external masters.
The PCI module includes an inbound FIFO to increase performance when using an external bus master.
The bus can address all 4 Gbytes of PCI-addressable space.
The PCI bus is also multiplexed with the flexible local bus (FlexBus) address lines. If 32-bit non-muxed
local address and data is required, it can be obtained at the expense of utilizing the PCI bus.
When implemented, the PCI controller acts as the central resource, bus arbiter, and configuring master on
the PCI bus.
1.4.9Flexible Local Bus (FlexBus)
The FlexBus module is intended to provide the user with basic functionality required to interface to
peripheral devices. The FlexBus interface is a multiplexed or non-multiplexed bus, with an operating
MCF548x Reference Manual, Rev. 3
1-10Freescale Semiconductor
MCF548x Family Features
frequency from 33–66 MHz. The Flexbus is targeted to support external Flash memories, boot ROMs,
gate-array logic, or other simple target interfaces. Up to six chip selects are supported by the FlexBus.
Possible combinations of address and data bits are the following:
•Non-multiplexed 32-bit address and 32-bit data (32-bit address muxed over
PCI bus–PCI not usable)
•Multiplexed 32-bit address and 32-bit data (PCI usable)
•Multiplexed 32-bit address and 16-bit data
•Multiplexed 32-bit address and 8-bit data
The non-multiplexed 32-bit address and 32-bit data mode is determined at chip reset. For all other modes,
the full 32-bit address is driven during the address phase. The number of bytes used for data are determined
on a chip select by chip select basis.
1.4.10Security Encryption Controller (SEC)
As consumers and businesses continue to embrace the Internet, the need for secure point-to-point
communications across what is an entirely insecure network has been met by the development of a range
of standard protocols. Computer cryptography fundamentally involves calculations with very large
numbers. Personal computers have sufficient processing power to implement these algorithms entirely in
software. When placed upon the embedded devices typically used for routing and remote access functions,
this same computational burden can potentially decrease the throughput of a 100 Mbps Ethernet interface
down to 10 Mbps.
Hardware acceleration of common cryptography algorithms is the solution to the computational bandwidth
requirements of Internet security standards. Discrete solutions currently address this problem, but the next
logical step is to integrate a cryptography accelerator on an embedded processor, such as the MCF548x
family.
Freescale has developed the SEC on the MCF548x family for this purpose. This block accelerates the core
cryptography algorithms that underlie standard Internet security protocols like SSL/TLS, IPSec, IKE, and
WTLS/WAP.
•The SEC includes execution units for the following:
— DES/3DES block cipher
— AES block cipher
— RC4 stream cipher
— MD5/SHA-1/SHA-256/HMAC hashing
— Random number generator compliant with FIPS 140-1 standards for randomness and
non-determinism
•Dual-channel architecture permits single-pass encryption and authentication
1.4.11System Integration Unit (SIU)
1.4.11.1Timers
The MCF548x family integrates several timer functions required by most embedded systems. Two internal
32-bit slice timers create short cycle periodic interrupts, typically utilized for RTOS scheduling and alarm
functionality. A watchdog timer resets the processor if not regularly serviced, catching software hang-ups.
Four 32-bit general purpose timers can perform input capture, output compare, and PWM functionality.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor1-11
1.4.11.2Interrupt Controller
The interrupt controller on the MCF548x family can support up to 63 interrupt sources. The interrupt
controller is organized as seven levels with nine interrupt sources per level. Each interrupt source has a
unique interrupt vector, and 56 of the 63 sources of a given controller provide a programmable level [1-7]
and priority within the level.
•Support for up to 63 interrupt sources organized as follows:
— 56 fully-programmable interrupt sources
— 7 fixed-level interrupt sources
•Seven external interrupt signals
•Unique vector number for each interrupt source
•Ability to mask any individual interrupt source or all interrupt sources (global mask-all)
•Support for hardware and software interrupt acknowledge (IACK) cycles
•Combinatorial path to provide wake-up from stop mode
1.4.11.3General Purpose I/O
All peripheral I/O pins on the MCF548x family are multiplexed with GPIO, adding flexibility and usability
to all signals on the chip.
MCF548x Reference Manual, Rev. 3
1-12Freescale Semiconductor
Chapter 2
Signal Descriptions
2.1Introduction
This chapter describes the MCF548x signals.
The terms ‘assertion’ and ‘negation’ are used to avoid confusion when
dealing with a mixture of active-low and active-high signals. The term
‘asserted’ indicates that a signal is active, independent of the voltage level.
The term ‘negated’ indicates that a signal is inactive.
Active-low signals, such as RAS and TA, are indicated with an overbar.
This pin is a “no connect” on the MCF5483 and MCF5482 devices.
2
This pin is a “no connect” on the MCF5481 and MCF5480 devices. On MCF5485, MCF5484, MCF5483, and MCF5482 device the pin
should be connected to the appriopriate power rail even is USB is not being used.
3
This pin is a “no connect” on the MCF5481 and MCF5480 devices.
1
E1RXD0PFEC1H1——
2.2MCF548x External Signals
2.2.1FlexBus Signals
2.2.1.1Address/Data Bus (AD[31:0])
The AD[31:0] bus carries address and data. The full 32-bit address is always driven on the first clock of a
bus cycle (address phase). The number of bytes used for data during the data phase is determined by the
port size associated with the matching chip select.
MCF548x Reference Manual, Rev. 3
2-16Freescale Semiconductor
MCF548x External Signals
2.2.1.2Chip Select (FBCS[5:0])
FBCS[5:0] are asserted to indicate which device is being selected. A particular chip select asserts when
the transfer address is within the device’s address space as defined in the base and mask address registers.
Each chip select can be programmed for a base address location, masking addresses, port size,
burst-capability indication, wait-state generation, and internal/external termination.
Reset clears all chip select programming; FBCS0 is the only chip select initialized out of reset. FBCS0 is
also unique because it can function at reset as a global chip select that allows boot ROM to be selected at
any defined address space. Port size and termination (internal vs. external) for boot FBCS0 are configured
by the levels on AD[2:0] on the rising edge of RSTI, as described in Section 2.2.6, “Reset Configuration
Pins.”
2.2.1.3Address Latch Enable (ALE)
The assertion of ALE indicates that the MCF548x has begun a bus transaction and that the address and
attributes are valid. ALE is asserted for one bus clock cycle. In multiplexed bus mode, ALE is used
externally as an address latch enable to capture the address phase of the bus transfer.
2.2.1.4Read/Write (R/W)
The MCF548x drives the R/W signal to indicate the direction of the current bus operation. It is driven high
during read bus cycles and driven low during write bus cycles.
2.2.1.5Transfer Burst (TBST)
Transfer burst indicates that a burst transfer is in progress. A burst transfer can be 2 to 16 beats depending
on the size of the transfer and the port size.
2.2.1.6Transfer Size (TSIZ[1:0])
For memory accesses, these signals along with TBST, indicate the data transfer size of the current bus
operation. The FlexBus interface supports byte, word, and longword operand transfers and allows accesses
to 8-, 16-, and 32-bit data ports.
For misaligned transfers, TSIZ[1:0] indicates the size of each transfer. For example, if a longword access
through a 32-bit port device occurs at a misaligned offset of 0x1, a byte is transferred first (TSIZ[1:0] =
01), a word is next transferred at offset 0x2 (TSIZ[1:0] = 10), then the final byte is transferred at offset 0x4
(TSIZ[1:0] = 01).
For aligned transfers larger than the port size, TSIZ[1:0] behaves as follows:
•If bursting is used, TSIZ[1:0] is driven to the size of transfer.
•If bursting is inhibited, TSIZ[1:0] first shows the size of the entire transfer and then shows the port
size.
Table 2-3. Data Transfer Size
TSIZ[1:0]Transfer Size
004 bytes (longword)
011 byte
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-17
Table 2-3. Data Transfer Size (Continued)
TSIZ[1:0]Transfer Size
102 bytes (word)
1116 bytes (line)
For burst-inhibited transfers, TSIZ[1:0] changes with each ALE assertion to reflect the next transfer size.
For transfers to port sizes smaller than the transfer size, TSIZ[1:0] indicates the size of the entire transfer
on the first access and the size of the current port transfer on subsequent transfers. For example, for a
longword write to an 8-bit port, TSIZ[1:0] = 2’b00 for the first transaction and 2’b01 for the next three
transactions. If bursting is used and in the case of longword write to an 8-bit port, TSIZ[1:0] is driven to
2’b00 for the entire transfer.
2.2.1.7Byte Selects (BE/BWE[3:0])
The four byte-enables are multiplexed with the byte-write-enable signals. Each pin can be individually
programmed through the chip select control registers (CSCRs). For each chip select, assertion of
byte-enables for reads and byte-write enables for write cycles can be programmed. Alternatively, users can
program byte-write enables to assert on writes and byte-enable to not assert on reads.
The byte strobe (BE/BWE[3:0]) outputs indicate that data is to be latched or driven onto a byte of the data.
BE/BWE[3:0] signals are asserted only to the memory bytes used during a read or write access.
2.2.1.8Output Enable (OE)
The output enable signal is sent to the interfacing memory and/or peripheral to enable a read transfer. OE
is asserted only when a chip select matches the current address decode.
2.2.1.9Transfer Acknowledge (TA)
The external system drives this input to terminate the bus transfer. For write cycles, the processor continues
to drive data at least one clock after FBCSx is negated. During read cycles, the peripheral must continue
to drive data until TA is recognized. The number of wait states is determined either by an internally
programmed auto acknowledgement or the external TA input. If the external TA is used, the peripheral has
total control over the number of wait states.
2.2.2SDRAM Controller Signals
These signals are used for SDRAM accesses.
2.2.2.1SDRAM Data Bus (SDDATA[31:0])
SDDATA[31:0] is the bidirectional, non-multiplexed data bus used for SDRAM accesses. Data is sampled
by the MCF548x on the rising edge of SDCLK when in SDR mode, and on both the rising and falling edge
of SDCLK when in DDR mode.
2.2.2.2SDRAM Address Bus (SDADDR[12:0])
The SDADDR[12:0] signals are the 13-bit address bus used for multiplexed row and column addresses
during SDRAM bus cycles. The address multiplexing supports up to 256 Mbits of SDRAM per chip select.
MCF548x Reference Manual, Rev. 3
2-18Freescale Semiconductor
MCF548x External Signals
2.2.2.3SDRAM Bank Addresses (SDBA[1:0])
Each SDRAM module has four internal row banks. The SDBA[1:0] signals are used to select the row bank.
It is also used to select the SDRAM internal mode register during power-up initialization.
2.2.2.4SDRAM Row Address Strobe (RAS)
This output is the SDRAM synchronous row address strobe.
2.2.2.5SDRAM Column Address Strobe (CAS)
This output is the SDRAM synchronous column address strobe.
2.2.2.6SDRAM Chip Selects (SDCS[3:0])
These signals interface to the chip select lines of the SDRAMs within a memory block. Thus, there is one
SDCS line for each memory block (the MCF548x supports up to four SDRAM memory blocks).
2.2.2.7SDRAM Write Data Byte Mask (SDDM[3:0])
These output signals are sampled by the SDRAM on both edges of SDDQS to determine which byte lanes
of the SDRAM data bus should be latched during a write cycle. In DDR mode, these bits are ignored during
read operations.
2.2.2.8SDRAM Data Strobe (SDDQS[3:0])
These bidirectional signals indicate when valid data is on the SDRAM data bus when in DDR mode.
2.2.2.9SDRAM Clock (SDCLK[1:0])
These signals are the output clock for SDRAM cycles.
2.2.2.10Inverted SDRAM Clock (SDCLK[1:0])
These signals are the inverted version of the SDRAM clock. They are used with SDCLK to provide the
differential clocks for DDR SDRAM.
2.2.2.11SDRAM Write Enable (SDWE)
The SDRAM write enable (SDWE) is asserted to signify that an SDRAM write cycle is underway. A read
cycle is indicated by the negation of SDWE.
2.2.2.12SDRAM Clock Enable (SDCKE)
This output is the SDRAM clock enable. SDCKE is negated to put the SDRAM into low-power,
self-refresh mode.
2.2.2.13SDR SDRAM Data Strobe (SDRDQS)
This signal is connected to SDDQS inputs. It is used in SDR mode only.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-19
2.2.2.14SDRAM Reference Voltage (VREF)
This is the input reference voltage for differential SSTL_2 inputs. It is used in both DDR and SDR modes.
2.2.3PCI Controller Signals
2.2.3.1PCI Address/Data Bus (PCIAD[31:0])
The PCIAD[31:0] lines are a time-multiplexed address data bus. The address is presented on the bus during
the address phase while the data is presented on the bus during one or more data phases.
If the FlexBus is used in 32-bit address or 32-bit data non-multiplexed mode, PCIAD[31:0] are used as a
32-bit address for FlexBus transfers.
2.2.3.2Command/Byte Enables (PCICXBE[3:0])
The PCICXBE[3:0] lines are time-multiplexed. The PCI command is presented during the address phase,
and the byte enables are presented during the data phase.
2.2.3.3Device Select (PCIDEVSEL)
The PCIDEVSEL signal is asserted active low when the MCF548x decodes that it is the target of a PCI
transaction from the address presented on the PCI bus during the address phase.
2.2.3.4Frame (PCIFRM)
The PCIFRM signal is asserted by a PCI initiator to indicate the beginning of a transaction. It is negated
when the initiator is ready to complete the final data phase.
2.2.3.5Initialization Device Select (PCIIDSEL)
The PCIIDSEL signal is asserted during a PCI type-0 configuration cycle to address the PCI configuration
header.
2.2.3.6Initiator Ready (PCIIRDY)
The PCIIRDY signal is asserted to indicate that the PCI initiator is ready to transfer data. During a write
operation, assertion indicates that the master is driving valid data on the bus. During a read operation,
assertion indicates that the master is ready to accept data.
2.2.3.7Parity (PCIPAR)
The PCIPAR signal indicates the parity of data on the PCIAD[31:0] and PCICXBE[3:0] lines.
2.2.3.8Parity Error (PCIPERR)
The PCIPERR signal is asserted when a data phase parity error is detected if enabled.
MCF548x Reference Manual, Rev. 3
2-20Freescale Semiconductor
MCF548x External Signals
2.2.3.9Reset (PCIRESET)
The PCIRESET signal is asserted active low by MCF548x to reset the PCI bus. This signal is asserted after
the MCF548x is reset and must be negated to enable usage of the PCI bus.
2.2.3.10System Error (PCISERR)
The PCISERR signal, if enabled, is asserted when an address phase parity error is detected.
2.2.3.11Stop (PCISTOP)
The PCISTOP signal is asserted by the currently addressed target to indicate that it wishes to stop the
current transaction.
2.2.3.12Target Ready (PCITRDY)
The PCITRDY signal is asserted by the currently addressed target to indicate that it is ready to complete
the current data phase.
2.2.3.13External Bus Grant (PCIBG[4:1])
The PCIBG signal is asserted to an external master to give it control of the PCI bus. If the internal PCI
arbiter is enabled, it asserts one of the PCIBG[4:1] lines to grant ownership of the PCI bus to an external
master. When the PCI arbiter module is disabled, PCIBG[4:1] is driven high and should be ignored.
2.2.3.14External Bus Grant/Request Output (PCIBG0/PCIREQOUT)
The PCIBG0 signal is asserted to external master device 0 to give it control of the PCI bus. When the PCI
arbiter module is disabled, the signal operates as the PCIREQOUT output. It is asserted when the
MCF548x needs to initiate a PCI transaction.
2.2.3.15External Bus Request (PCIBR[4:0])
The PCIBR signal is asserted by an external PCI master when it requires access to the PCI bus.
The PCIBR0 signal is asserted by external PCI master device 0 when it requires access to the PCI bus.
When the internal PCI arbiter module is disabled, this signal is used as a grant input for the PCI bus,
PCIGNTIN
. It is driven by an external PCI arbiter.
2.2.4Interrupt Control Signals
The interrupt control signals supply the external interrupt level to the MCF548x device.
2.2.4.1Interrupt Request (IRQ[7:1])
The IRQ[7:1] signals are the external interrupt inputs.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-21
2.2.5Clock and Reset Signals
The clock and reset signals configure the MCF548x and provide interface signals to the external system.
2.2.5.1Reset In (RSTI)
Asserting RSTI causes the MCF548x to enter reset exception processing. RSTO is asserted automatically
when RSTI is asserted.
2.2.5.2Reset Out (RSTO)
After RSTI is asserted, the PLL temporarily loses its lock, during which time RSTO is asserted. When the
PLL regains its lock, RSTO negates again. This signal can be used to reset external devices.
2.2.5.3Clock In (CLKIN)
CLKIN is the MCF548x input clock frequency to the on-board, phase-locked loop (PLL) clock generator.
CLKIN is used to internally clock or sequence the MCF548x internal bus interface at a selected multiple
of the input frequency used for internal module logic.
CLKIN is used as the clock reference for PCI and FlexBus transfers.
2.2.6Reset Configuration Pins
This section describes address/data pins, AD[12:0], that are read at reset to configure the MCF548x.
2.2.6.1AD[12:8]—CLKIN to SDCLK Ratio (CLKCONFIG[4:0])
The clock configuration inputs, CLKCONFIG[4:0], indicate the CLKIN to SDCLK ratio. CLKIN is used
as the external reference for both PCI and FlexBus cycles. The CLKIN to SDCLK ratio is selectable, where
SDCLK is the clock frequency used for SDRAM accesses and the internal XLB bus. The core is always
clocked at twice the SDCLK frequency.
These signals are sampled on the rising edge of RSTI. Table 2 -4 shows how the logic levels of AD[12:8]
correspond to the selected clock ratio.
Table 2- 4 . MCF 5 48x Divide Ratio Encodings
FB_AD[12:8]
000111:241.6–50.083.33–100166.66–200
001011:230.0–44.460.0–88.8120.0–177.66
1
All other values of FB_AD[12:8] are reserved.
1
Clock Ratio
CLKIN—PCI and FlexBus
Frequency Range
(MHz)
Figure 2-2 correlates CLKIN, internal bus, and core clock frequenciesi for the 1x–4x multipliers.
Figure 2-2. CLKIN, Internal Bus, and Core Clock Ratios
2.2.6.2AD5—FlexBus Size Configuration (FBSIZE)
At reset, the enabling and disabling of BE/BWE[3:0] versus TSIZ[1:0] and ADDR[1:0] is determined by
the logic level driven on AD5 at the rising edge of RSTI. FBSIZE is multiplexed with AD5 and sampled
only at reset. Table 2-5 shows how the AD5 logic level corresponds to the BE/BWE[3:0] function.
Table 2-5. AD5/FBSIZE Selection of BE/BWE[3:0] Signals
AD5FlexBus Byte Enable Mode
0BE/BWE[3:0] used as byte/byte write
enables.
1BE/BWE[3:2] configured as TSIZ[1:0].
/BWE[1:0] configured as FBADDR[1:0].
BE
2.2.6.3AD4—32-bit FlexBus Configuration (FBMODE)
During reset, the FlexBus can be configured to operate in a non-multiplexed 32-bit address with 32-bit data
mode. In this mode, the 32-bit FlexBus AD[31:0] is used for the data bus, and the PCI bus PCIAD[31:0]
is used as the address bus. The FlexBus operating mode is determined by the logic level driven on AD4 at
the rising edge of RSTI. Table 2-6 shows how the logic level of AD4 corresponds to the FlexBus mode.
Table 2-6. AD4/FBMODE Selection of Non-Multiplexed
32-bit Address/32-bit Data Mode
AD4FlexBus Operating Mode
0AD[31:0] used for data.
PCIAD[31:0] used for address
1PCIAD[31:0] used for PCI bus.
AD[31:0] used for both address and data.
1
If the non-multiplexed 32-bit address/32-bit data mode is selected, the PCI bus
cannot be used.
1
2.2.6.4AD3—Byte Enable Configuration (BECONFIG)
The default byte enable mode of the boot FBCS0 is determined by the logic level driven on AD3 at the
rising edge of RSTI. This logic level is reflected as the reset value of CSCR0[BEM]. Table 2-7 shows how
the logic level of AD3 corresponds to the byte enable mode for FBCS0 at reset.
At reset, the enabling and disabling of auto acknowledge for boot FBCS0 is determined by the logic level
driven on AD2 at the rising edge of RSTI. AACONFIG is multiplexed with AD2 and sampled only at reset.
The AD2 logic level is reflected as the reset value of CSCR0[AA]. Tab le 2-8 shows how the AD2 logic
level corresponds to the auto acknowledge timing for FBCS0 at reset. Auto acknowledge can be disabled
by driving a logic 0 on AD2 at reset.
Table 2-8. AD2/AA_CONFIG Selection of FBCS0 Automatic Acknowledge
AD2Boot FBCS0 AA Configuration at Reset
0Disabled
1Enabled with 63 wait states
2.2.6.6AD[1:0]—Port Size Configuration (PSCONFIG)
The default port size value of the boot FBCS0 is determined by the logic levels driven on AD[1:0] at the
rising edge of RSTI, which are reflected as the reset value of CSCR0[PS]. Table 2-9 shows how the logic
levels of AD[1:0] correspond to the FBCS0 port size at reset.
Table 2-9. AD[1:0]/PSCONFIG[1:0] Selection of FBCS0 Port Size
AD[1:0]Boot FBCS0 Port Size
0032-bit port
018-bit port
1X16-bit port
2.2.7Ethernet Module Signals
The following signals are used by the Ethernet module for data and clock signals.
2.2.7.1Management Data (E0MDIO, E1MDIO)
The bidirectional EMDIO signals transfer control information between the external PHY and the
media-access controller. Data is synchronous to EMDC and applies to MII mode operation. This signal is
an input after reset. When the FEC operates in 10 Mbps 7-wire interface mode, this signal should be
connected to VSS.
MCF548x Reference Manual, Rev. 3
2-24Freescale Semiconductor
MCF548x External Signals
2.2.7.2Management Data Clock (E0MDC, E1MDC)
EMDC is an output clock that provides a timing reference to the PHY for data transfers on the EMDIO
signal; it applies to MII mode operation.
2.2.7.3Transmit Clock (E0TXCLK, E1TXCLK)
This is an input clock that provides a timing reference for ETXEN, ETXD[3:0], and ETXER.
2.2.7.4Transmit Enable (E0TXEN, E1TXEN)
The transmit enable (ETXEN) output indicates when valid nibbles are present on the MII. This signal is
asserted with the first nibble of a preamble and is negated before the first ETXCLK following the final
nibble of the frame.
2.2.7.5Transmit Data 0 (E0TXD0, E1TXD0)
ETXD0 is the serial output Ethernet data and is only valid during the assertion of ETXEN. This signal is
used for 10 Mbps Ethernet data. This signal is also used for MII mode data in conjunction with ETXD[3:1].
2.2.7.6Collision (E0COL, E1COL)
The ECOL input is asserted upon detection of a collision and remains asserted while the collision persists.
This signal is not defined for full-duplex mode.
2.2.7.7Receive Clock (E0RXCLK, E1RXCLK)
The receive clock (ERXCLK) input provides a timing reference for ERXDV, ERXD[3:0], and ERXER.
2.2.7.8Receive Data Valid (E0RXDV, E1RXDV)
Asserting the receive data valid (ERXDV) input indicates that the PHY has valid nibbles present on the
MII. ERXDV should remain asserted from the first recovered nibble of the frame through to the last nibble.
Assertion of ERXDV must start no later than the SFD and exclude any EOF.
2.2.7.9Receive Data 0 (E0RXD0, E1RXD0)
ERXD0 is the Ethernet input data transferred from the PHY to the media-access controller when ERXDV
is asserted. This signal is used for 10 Mbps Ethernet data. This signal is also used for MII mode Ethernet
data in conjunction with ERXD[3:1].
2.2.7.10Carrier Receive Sense (E0CRS, E1CRS)
ECRS is an input signal that, when asserted, signals that transmit or receive medium is not idle, and applies
to MII mode operation.
2.2.7.11Transmit Data 1–3 (E0TXD[3:1], E1TXD[3:1])
These pins contain the serial output Ethernet data and are valid only during assertion of ETXEN in MII
mode.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-25
2.2.7.12Transmit Error (E0TXER, E1TXER)
When the ETXER output is asserted for one or more clock cycles while ETXEN is also asserted, the PHY
sends one or more illegal symbols. ETXER has no effect at 10 Mbps or when ETXEN is negated, and
applies to MII mode operation.
2.2.7.13Receive Data 1–3 (E0RXD[3:1], E1RXD[3:1])
These pins contain the Ethernet input data transferred from the PHY to the media-access controller when
ERXDV is asserted in MII mode operation.
2.2.7.14Receive Error (E0RXER, E1RXER)
ERXER is an input signal that, when asserted along with ERXDV, signals that the PHY has detected an
error in the current frame. When ERXDV is not asserted, ERXER has no effect and applies to MII mode
operation.
2.2.8Universal Serial Bus (USB)
2.2.8.1USB Differential Data (USBD+, USBD–)
USBD+ and USBD– are the outputs of the on-chip USB 2.0 transceiver. They provide differential data for
the USB 2.0 bus.
2.2.8.2USBVBUS
This is the USB cable Vbus monitor input.
2.2.8.3USBRBIAS
This is the connection for external current setting resistor. It should be connected to a 9.1kΩ +/– 1%
pull-down resistor.
For the MCF5481 and MCF5480 devices this pin should be connected to a 9.1kΩ +/– 20% pull-down
resistor.
2.2.8.4USBCLKIN
This is the input pin for 12-MHz USB crystal circuit.
2.2.8.5USBCLKOUT
This is the output pin for 12-MHz USB crystal circuit.
2.2.9DMA Serial Peripheral Interface (DSPI) Signals
2.2.9.1DSPI Synchronous Serial Data Output (DSPISOUT)
The DSPISOUT output provides the serial data from the DSPI and can be programmed to be driven on the
rising or falling edge of DSPISCK.
MCF548x Reference Manual, Rev. 3
2-26Freescale Semiconductor
MCF548x External Signals
2.2.9.2DSPI Synchronous Serial Data Input (DSPISIN)
The DSPISIN input provides the serial data to the DSPI and can be programmed to be sampled on the
rising or falling edge of DSPISCK.
2.2.9.3DSPI Serial Clock (DSPISCK)
DSPISCK is a serial communication clock signal. In master mode, the DSPI generates the DSPISCK. In
slave mode, DSPISCK is an input from an external bus master.
DSPICS5 is a peripheral chip select output signal. When the DSPI is in master mode and the
DMCR[PCSSE] bit is cleared, this signal is used to select which slave device the current transfer is
intended for.
PCSS provides a strobe signal that can be used with an external demultiplexer for deglitching of the
DSPICSn signals. When the DSPI is in master mode and DMCR[PCSSE] is set, the PCSS provides the
appropriate timing for the decoding of the DSPICS[0,2,3] signals which prevents glitches from occurring.
This signal is not used in slave mode.
2.2.10FlexCAN Signals
2.2.10.1FlexCAN Transmit (CANTX0, CANTX1)
Controller area network transmit data output.
2.2.10.2FlexCAN Receive (CANRX0, CANRX1)
Controller area network receive data input.
2.2.11I2C I/O Signals
The I2C serial interface module uses the signals in this section.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-27
2.2.11.1Serial Clock (SCL)
This bidirectional open-drain signal is the clock signal for the I2C interface. It is either driven by the I2C
module when the bus is in master mode, or it becomes the clock input when the I2C is in slave mode.
2.2.11.2Serial Data (SDA)
This bidirectional open-drain signal is the data input/output for the I2C interface.
2.2.12PSC Module Signals
The PSC modules use the signals in this section. The baud rate clock inputs are not supported.
2.2.12.1Transmit Serial Data Output (PSC0TXD, PSC1TXD, PSC2TXD, PSC3TXD)
PSCnTXD are the transmitter serial data outputs for the PSC modules. The output is held high (mark
condition) when the transmitter is disabled, idle, or in the local loopback mode. The PSCxTXD pins can
be programmed to be driven low (break status) by a command.
2.2.12.2Receive Serial Data Input (PSC0RXD, PSC1RXD, PSC2RXD, PSC3RXD)
PSCnRXD are the receiver serial data inputs for the PSC modules. When the PSC clock is stopped for
power-down mode, any transition on the pins restarts them.
2.2.12.3Clear-to-Send (PSCnCTS/PSCBCLK)
These signals either operate as the clear-to-send input signals in UART mode or the bit clock input signals
in modem modes and IrDA modes. In MIR and FIR mode, the frequency is a multiple of the input bit clock
frequency, and the bit clock frequency should be within +/-0.1% and +/-0.01% of the ideal one,
respectively.
2.2.12.4Request-to-Send (PSCnRTS/PSCFSYNC)
The PSCnRTS signals act as transmitter request-to-send (RTS) outputs in UART mode, the frame sync
input in modem8 and modem16 modes, or the RTS
mode.
output (which acts as frame sync) in AC97 modem
2.2.13DMA Controller Module Signals
The DMA controller module uses the signals in the following subsections to provide external requests for
either a source or destination.
2.2.13.1DMA Request (DREQ[1:0])
These inputs are asserted by a peripheral device to request an operand transfer between that peripheral and
memory by either channel 0 or 1 of the on-chip DMA module.
2.2.13.2DMA Acknowledge (DACK[1:0])
These outputs are asserted to acknowledge that a DMA request has been recognized.
MCF548x Reference Manual, Rev. 3
2-28Freescale Semiconductor
MCF548x External Signals
2.2.14Timer Module Signals
The signals in the following sections are external interfaces to the four general-purpose MCF548x timers.
These 32-bit timers can capture timer values, trigger external events or internal interrupts, or count
external events.
2.2.14.1Timer Inputs (TIN[3:0])
TINn can be programmed as clocks that cause events in the counter and prescalers. They can also cause
captures on the rising edge, falling edge, or both edges.
2.2.14.2Timer Outputs (TOUT[3:0])
The programmable timer outputs, TOUTn, pulse or toggle on various timer events.
2.2.15Debug Support Signals
The MCF548x complies with the IEEE 1149.1a JTAG testing standard. JTAG test pins are multiplexed
with background debug pins. Except for TCK, these signals are selected by the value of MTMOD0. If
MTMOD0 is high, JTAG signals are chosen; if it is low, debug module signals are chosen. MTMOD0
should be changed only while RSTI is asserted.
2.2.15.1Processor Clock Output (PSTCLK)
The internal PLL generates this output signal, and is the processor clock output that is used as the timing
reference for the debug bus timing (PSTDDATA[7:0]). PSTCLK is at the same frequency as the internal
XLB and SDRAM bus frequency. The frequency is one-half the core frequency.
2.2.15.2Processor Status Debug Data (PSTDDATA[7:0])
Processor status data outputs indicate both processor status and captured address/data values. They operate
at half the processor’s frequency, using PSTCLK. Given that real-time trace information appears as a
sequence of 4-bit data values, there are no alignment restrictions; that is, PST values and operands may
appear on either PSTDDATA[7:0] nibble. The upper nibble, PSTDDATA[7:4], is most significant.
2.2.15.3Development Serial Clock/Test Reset (DSCLK/TRST)
If MTMOD0 is low, DSCLK is selected. DSCLK is the development serial clock for the serial interface to
the debug module. The maximum DSCLK frequency is 1/5 CLKIN.
If MTMOD0 is high, TRST is selected. TRST asynchronously resets the internal JTAG controller to the
test logic reset state, causing the JTAG instruction register to choose the bypass instruction. When this
occurs, JTAG logic is benign and does not interfere with normal MCF548x functionality.
Although TRST is asynchronous, Freescale recommends that it makes an asserted-to-negated transition
only while TMS is held high. TRST has an internal pull-up resistor so if it is not driven low, it defaults to
a logic level of 1. If TRST is not used, it can be tied to ground or, if TCK is clocked, to EVDD. Tying TRST
to ground places the JTAG controller in test logic reset state immediately. Tying it to EVDD causes the
JTAG controller (if TMS is a logic level of 1) to eventually enter test logic reset state after 5 TCK clocks.
MCF548x Reference Manual, Rev. 3
Freescale Semiconductor2-29
2.2.15.4Breakpoint/Test Mode Select (BKPT/TMS)
If MTMOD0 is low, BKPT is selected. BKPT signals a hardware breakpoint to the processor in debug
mode.
If MTMOD0 is high, TMS is selected. The TMS input provides information to determine the JTAG test
operation mode. The state of TMS and the internal 16-state JTAG controller state machine at the rising
edge of TCK determine whether the JTAG controller holds its current state or advances to the next state.
This directly controls whether JTAG data or instruction operations occur. TMS has an internal pull-up
resistor so that if it is not driven low, it defaults to a logic level of 1. But if TMS is not used, it should be
tied to VDD.
2.2.15.5Development Serial Input/Test Data Input (DSI/TDI)
If MTMOD0 is low, DSI is selected. DSI provides the single-bit communication for debug module
commands.
If MTMOD0 is high, TDI is selected. TDI provides the serial data port for loading the various JTAG
boundary scan, bypass, and instruction registers. Shifting in data depends on the state of the JTAG
controller state machine and the instruction in the instruction register. Shifts occur on the TCK rising edge.
TDI has an internal pull-up resistor, so when not driven low it defaults to high. But if TDI is not used, it
should be tied to EVDD.
2.2.15.6Development Serial Output/Test Data Output (DSO/TDO)
If MTMOD0 is low, DSO is selected. DSO provides single-bit communication for debug module
responses.
If MTMOD0 is high, TDO is selected. The TDO output provides the serial data port for outputting data
from JTAG logic. Shifting out data depends on the JTAG controller state machine and the instruction in
the instruction register. Data shifting occurs on the falling edge of TCK. When TDO is not outputting test
data, it is three-stated. TDO can be three-stated to allow bused or parallel connections to other devices
having a JTAG port.
2.2.15.7Test Clock (TCK)
TCK is the dedicated JTAG test logic clock independent of the MCF548x processor clock. Various JTAG
operations occur on the rising or falling edge of TCK. Holding TCK high or low for an indefinite period
does not cause JTAG test logic to lose state information. If TCK is not used, it must be tied to ground.
2.2.16Test Signals
2.2.16.1Test Mode (MTMOD[3:0])
The test mode signals choose between multiplexed debug module and JTAG signals. If MTMOD0 is low,
the part is in normal and background debug mode (BDM); if it is high, it is in normal and JTAG mode. All
other MTMOD values are reserved; MTMOD[3:1] should be tied to ground and MTMOD[3:0] should not
be changed while RSTI is negated
MCF548x Reference Manual, Rev. 3
2-30Freescale Semiconductor
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.