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 Semiconduc tor product could
create a situation where personal injury or death may occur. Should Buyer
purchase or use Freescale Semicon ductor 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.
1. This product as shipped from the factory with associated power supplies and cables, has been tested and
meets with requirements of EN5022 and EN 50082-1: 1998 as a CLASS A product.
2. This product is designed and intended for use as a development platform for hardware or software in an
educational or professional laboratory.
3. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
4. Anti-static precautions must be adhered to when using this product.
5. Attaching additional cables or wiring to this product or modifying the products operation from the factory
default as shipped may effect its performance and also cause interference with other apparatus in the
immediate vicinity. If such interference is detected, suitable mitigating measures should be taken.
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductoriii
WARNING
This board generates, uses, and can radiate radio frequency energy and, if not
installed properly, may cause interference to radio communications. As
temporarily permitted by regulation, it has not been tested for compliance with the
limits for class a computing devices pursuant to Subpart J of Part 15 of FCC rules,
which are designed to provide reasonable protection against such interference.
Operation of this product in a residential area is likely to cause interference, in
which case the user, at his/her own expense, will be required to correct the
interference.
C-1M523xEVB Bill of Materials ...................................................................................................6-2
Title
Page
Number
M523xEVB User’s Manual, Rev. 1.2
Freescale SemiconductorFreescale Semiconductor Internal Use Onlyix
Tables
Table
Number
Title
Page
Number
M523xEVB User’s Manual, Rev. 1.2
xFreescale Semiconductor Internal Use OnlyFreescale Semiconductor
Chapter 1
M523xEVB
This document details the setup and configuration of the ColdFire M523xEVB evaluation board (hereafter
referred to as the EVB). The EVB is intended to provide a mechanism for easy customer evaluation of the
MCF523x family of ColdFire microprocessors and to facilitate hardware and software development. The
EVB can be used by software and hardware developers to test programs, tools, or circuits without having
to develop a complete microprocessor system themselves. All special features of the MCF523x family are
supported.
The heart of the evaluation board is the MCF5235, all the other M523x family members have a subset of
the MCF5235 specification and can therefore be fully emulated using the MCF5235 device. Table 1-1
below details the full product family.
Table 1 - 1 . M5 2 3x Product Family
Part NumberPackageeTPUFECCRYPTOCAN
MCF5232CAB80160 QFP16-channelNoNo1
MCF5232CVM100196 MAPBGA16-channelNoNo1
MCF5232CVM150196 MAPBGA16-channelNoNo1
MCF5233CVM100256 MAPBGA32-channelNoNo2
MCF5233CVM150256 MAPBGA32-channelNoNo2
MCF5234CVM100256 MAPBGA16-channelYesNo1
MCF5234CVM150256 MAPBGA16-channelYesNo1
MCF5235CVM100256 MAPBGA16-channelYesYes2
MCF5235CVM150256 MAPBGA16-channelYesYes2
All of the devices in the same package are pin compatible.
The EVB provides for low cost software testing with the use of a ROM resident debug monitor, dBUG,
programmed into the external Flash device. Operation allows the user to load code in the on-board RAM,
execute applications, set breakpoints, and display or modify registers or memory. No additional hardware
or software is required for basic operation.
Specifications:
•Motorola MCF5235 Microprocessor (150 MHz max core frequency)
•External Clock source: 25 MHz
•Operating temperature: 0°C to +70°C
•Power requirement: 7–14V DC @ 300 ma Typical
•Power output: 5V, 3.3V and 1.5V regulated supplies
•Ethernet port 10/100Mb/s (Dual-Speed Fast Ethernet Transceiver, with MII)
•UART0 (RS-232 serial port for dBUG firmware)
•UART1 (auxiliary RS-232 serial port)
•UART2 (auxiliary1 RS-232 serial port jumper selectable with FlexCAN1)
•Enhanced Time Processor Unit (eTPU)
2
•I
C interface
•QSPI interface to ADC
•FlexCan0 interface
•USB Host and Device Interface
•BDM/JTAG interface
User Interface:
•Reset logic switch (debounced)
•Boot logic selectable (dip switch)
•Abort/IRQ7 logic switch (debounced)
•PLL Clocking options - Oscillator, Crystal or SMA for external clocking signals
•LEDs for power-up indication, general purpose I/O, and timer output signals
•Expansion connectors for daughter card
•UNI-3 connector for motor control cards
Software:
•Resident firmware package that provides a self-contained programming and operating
environment (dBUG)
M523xEVB User’s Manual, Rev. 1.2
1-2Freescale Semiconductor
MCF5235 Microprocessor
r
DB-9 (2)
connector
RJ-45
connector
DB-9
connector
DB-9
connector
RS-232
transceivers (2)
Ethernet
Transceiver*
25 MHz
Osc.
CAN Transceiver
RS-232 / CAN
Transceiver
ColdFire MCF523X
Peripheral signals
Data [31:0]
Address [23:0]
Control Signals
26-pin Debug Heade
Clocking
circuitry
25 MHz
Osc.
USB 2.0 Host & Device
ADC
ETPU Headers*
SDRAM
16 Mbytes
Flash
2-4 Mbytes
ASRAM
1 Mbyte
(4) 60 pin Daughter Card
expansion connectors
*There is a jumper that allows the option of choosing between 16 eTPU channels and
Ethernet or 32 eTPU channels and no Ethernet
Figure 1-1. M523xEVB Block Diagram
1.1MCF5235 Microprocessor
The microprocessor used on the EVB is the highly integrated Motorola MCF5235 32-bit ColdFire
variable-length RISC processor. The MCF5235 implements a ColdFire Version 2 core with a maximum
core frequency of 150 MHz and external bus speed of 75 MHz. Features of the MCF5235 include:
•V2 ColdFire core with enhanced multiply-accumulate unit (EMAC) providing 144 (Dhrystone 2.1)
MIPS @ 150 MHz
•eTPU with 16 or 32 channels, 6 Kbytes of code memory and 1.5 Kbytes of data memory with
debug support
•64 Kbytes of internal SRAM
•External bus speed of one half the CPU operating frequency (75 MHz bus @ 150 MHz core)
•10/100 Mbps bus-mastering Ethernet controller
•8 Kbytes of configurable instruction/data cache
•Three universal asynchronous receiver/transmitters (UARTs) with DMA support
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-3
M523xEVB
•Controller area network 2.0B (FlexCAN module)
— Optional second FlexCAN module multiplexed with the third UART
•Inter-integrated circuit (I
2
C) bus controller
•Queued serial peripheral interface (QSPI) module
•Hardware cryptography accelerator (optional)
— Random number generator
•Interrupt controller capable of handling up to 126 interrupt sources
•Clock module with Phase Locked Loop (PLL)
•External bus interface module including a 2-bank synchronous DRAM controller
•32-bit non-multiplexed bus with up to 8 chip select signals that support page-mode FLASH
memories
The MCF5235 communicates with external devices over a 32-bit wide data bus, D[31:0]. The MCF5235
can address a 32 bit address range. However, only 24 bits are available on the external bus A[23:0]. There
are internally generated chip selects to allow the full 32 bit address range to be selected. There are regions
that can be decoded to allow supervisor, user, instruction, and data each to have the 32-bit address range.
All the processor's signals are available via daughter card expansion connectors. Refer to the schematic
(Appendix B) for their pin assignments.
The MCF5235 processor has the capability to support both BDM and JTAG. These ports are multiplexed
and can be used with third party tools to allow the user to download code to the board. The board is
configured to boot up in the normal/BDM mode of operation. The BDM signals are available at the port
labeled BDM.
Figure 1-2 shows the MCF5235 processor block diagram.
M523xEVB User’s Manual, Rev. 1.2
1-4Freescale Semiconductor
(To/From PADI)
(To/From PADI)
(To/From
PAD I)
MUX
DREQ[2:0]
JTAG_EN
FAST
ETHERNET
CONTROLLER
(FEC)
4 CH DMA
DACK[2:0]
(To/From SRAM backdoor)
Arbiter
UART
UART
0
1
DTIM
DTIM
0
V2 ColdFire CPU
BDM
UART
2
1
DIV
INTC0
DTIM
2
2
I
INTC1
C
EMAC
QSPI
DTIM
3
EIM
CHIP
SELECTS
EBI
SDRAMC
MCF5235 Microprocessor
SDRAMC
QSPI
SDA
SCL
UnTXD
UnRXD
UnRTS
UnCTS
TnOUT
TnIN
FEC
PAD I
D[31:0]
A[23:0]
R/
W
CS[3:0]
TA
TSIZ[1:0]
TEA
BS[3:0]
JTAG
TAP
Watchdog
Timer
SKHA
RNGA
MDHA
Cryptography
Modules
64 Kbytes
SRAM
(8Kx16)x4
8 Kbytes
CACHE
(1Kx32)x2
(To/From Arbiter)
PLL
PIT0
CLKGEN
(To/From INTC)
Edge
Port
Figure 1-2. MCF5235 Block Diagram
PORTS
(GPIO)
CIM
PIT1PIT2PIT3
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-5
M523xEVB
1.2System Memory
The following diagram shows the external memory implementation on the EVB.
MPU
Data
Address
Control
Buffers
SDRAM
(16 Mbytes)
Expansion
Connectors
Figure 1-3. External Memory Scheme
NOTE:
ASRAM
(1 Mbyte)
Flash
(512K × 16
or
512K × 32)
The external bus interface signals to the external ASRAM and FLASH (and
USB) are buffered. This is in order not to exceed the maximum output load
capacitance of the microprocessor on the EVB. The signals to the expansion
connectors remain unbuffered to provide a “true” interface to the user.
1.2.1External Flash
The EVB is fitted with a single 512K × 16 page-mode FLASH memory (U19) giving a total memory space
of 2Mbytes. Alternatively a footprint is available for the EVB user to upgrade this device to a 512K × 32
page-mode FLASH memory (U35), doubling the memory size to 4Mbytes. Either U19 OR U35 should be
fitted on the board - both devices cannot be populated at the same time. Refer to the specific device data
sheet and sample software provided for configuring the FLASH memory.
Users should note that the debug monitor firmware is installed in this flash device. Development tools or
user application programs may erase or corrupt the debug monitor. If the debug monitor becomes
corrupted and it’s operation is desired, the firmware must be programmed into the flash by applying a
development port tool such as BDM. Users should use caution to avoid this situation. The M523xEVB
dBUG debugger/monitor firmware is programmed into the lower sectors of Flash (0xFFE0_0000 to
0xFFE2_FFFF for 2Mbytes of FLASH or 0xFFC0_0000 to 0xFFC2_FFFF for 4 Mbytes of FLASH).
By default with U19 fitted on the EVB, jumper 64 (JP64) provides an alternative hardware mechanism for
write protection.
M523xEVB User’s Manual, Rev. 1.2
1-6Freescale Semiconductor
System Memory
If the user has replaced U19 with the 32-bit FLASH device (U35), jumper 31 (JP31) has the same
functionality as JP64. U35 also has it’s own hardware write protect pin (C5) which protects the bottom
boot sector when pulled to ground.
1.2.2SDRAM
The EVB is populated with 16 Mbytes of SDRAM. This is done with two devices (Micron
MT48LC4M16A2TG) each with a 16 bit data bus. Each device is organized as 1 Meg × 16 × 4 banks with
a 16 bit data bus. One device stores the upper 16-bit word and the other the lower 16 bit word of the
MCF523x 32 bit data bus.
1.2.3ASRAM
The EVB has a footprint for two 512K × 16 Asynchronous SRAM devices (Cypress Semiconductor -
CY7C1041CV3310ZC). These memory devices (U1 and U2) may be populated by the user for
benchmarking purposes.
Also see Section 1.2.5, “M523xEVB Memory Map”.
1.2.4Internal SRAM
The MCF5235 processor has 64-Kbytes of internal SRAM memory which may be used as data or
instruction memory. This memory is mapped to 0x2000_0000 and configured as data space but is not used
by the dBUG monitor except during system initialization. After system initialization is complete, the
internal memory is available to the user. The memory is relocatable to any 32-Kbyte boundary within the
processor’s four gigabyte address space.
1.2.5M523xEVB Memory Map
Interface signals to support the interface to external memory and peripheral devices are generated by the
memory controller. The MCF5235 supports 8 external chip selects, CS[1:0] are used with external
memories, CS2 is used for the USB controller and CS[7:3] are easily accessible to users via the daughter
card expansion connectors. CS0 also functions as the global (boot) chip-select for booting out of external
flash.
Since the MCF5235 chip selects are fully programmable, the memory banks may be located at any
64-Kbyte boundary within the processor’s four gigabyte address space.
The default memory map for this board as configured by the Debug Monitor located in the external
FLASH bank can be found in table 1-2. The internal memory space of the MCF5235 is detailed further in
the MCF5235 Reference Manual. Chip Selects 0 and 1 can be changed by user software to map the external
memory in different locations but the chip select configuration such as wait states and transfer
acknowledge for each memory type should be maintained.
0xFFE0_0000–0xFFFF_FFFF
or
0xFFC0_0000–0xFFFF_FFFF
2 Mbytes External Flash
or
4 Mbytes External Flash
1.2.5.1Reset Vector Mapping
Asserting the reset input signal to the processor causes a reset exception. The reset exception has the
highest priority of any exception; it provides for system initialization and recovery from catastrophic
failure. Reset also aborts any processing in progress when the reset input is recognized. Processing cannot
be recovered.
The reset exception places the processor in the supervisor mode by setting the S-bit and disables tracing
by clearing the T bit in the SR. This exception also clears the M-bit and sets the processor’s interrupt
priority mask in the SR to the highest level (level 7). Next, the VBR is initialized to zero (0x00000000).
The control registers specifying the operation of any memories (e.g., cache and/or RAM modules)
connected directly to the processor are disabled.
Once the processor is granted the bus, it then performs two longword read bus cycles. The first longword
at address 0 is loaded into the stack pointer and the second longword at address 4 is loaded into the program
counter. After the initial instruction is fetched from memory, program execution begins at the address in
the PC. If an access error or address error occurs before the first instruction is executed, the processor
enters the fault-on-fault halted state.
The Memory that the MCF5235 accesses at address 0 is determined at reset by sampling D[20:19].
The reset logic provides system initialization. Reset occurs during power-on or via assertion of the signal
RESET which causes the MCF5235 to reset. RESET is triggered by the reset switch (SW6) which resets
the entire processor/system.
dBUG configures the MCF5235 microprocessor internal resources during initialization. The contents of
the exception table are copied to address 0x0000_0000 in the SDRAM. The Software Watchdog Timer is
M523xEVB User’s Manual, Rev. 1.2
1-8Freescale Semiconductor
Support Logic
disabled, the Bus Monitor is enabled, and the internal timers are placed in a stop condition. A memory map
for the entire board can be seen in Table 1-2.
If the external RCON
pin is asserted (SW7-1 ON) during reset, then various chip functions, including the
reset configuration pin functions after reset, are configured according to the levels driven onto the external
data pins. See tables below on settings for reset configurations.
If the RCON
pin is not asserted (SW7-1 OFF) during reset, the chip configuration and the reset
configuration pin functions after reset are determined by the RCON register or fixed defaults, regardless
of the states of the external data pins.
SW7-1Reset Configuration
OFFRCON
ONRCON is asserted, Chip functions, including the reset configuration after reset,
SW1-2JTAG Enable
OFFJTAG interface enabled
ONBDM interface enabled
not asserted, Default Chip configuration or RCON register settings
are configured according to the levels driven onto the external data pins.
Table 1-6. SW7-[4:3] Encoded Clock Mode
SW7-3SW7-4Clock Mode
Table 1-4. SW7-1 RCON
Table 1-5. SW7-2 JTAG_EN
OFFOFFExternal clock mode- (PLL disabled)
OFFON1:1 PLL
ONOFFNormal PLL mode with external clock reference
The are three options to provide the clock to the CPU. These options can be configured by setting
JP[35:37]. See Table 1-11 below.
Table 1-11. M523xEVB Clock Source Selection
JP35JP36JP37Clock Selection
1-21-2ON25 MHz Oscillator (default setting)
2-31-2ON25 MHz External Clock
X2-3OFF25 MHz Crystal (not populated)
The 25-MHz oscillator (U23) also feeds the Ethernet chip (U11).
There is also a 12-MHz crystal feeding the USB controller (U33).
1.3.3Watchdog Timer
The dBUG Firmware does NOT enable the watchdog timer on the MCF5235.
M523xEVB User’s Manual, Rev. 1.2
1-10Freescale Semiconductor
Support Logic
1.3.4Exception Sources
The ColdFire® family of processors can receive seven levels of interrupt priorities. When the processor
receives an interrupt which has a higher priority than the current interrupt mask (in the status register), it
will perform an interrupt acknowledge cycle at the end of the current instruction cycle. This interrupt
acknowledge cycle indicates to the source of the interrupt that the request is being acknowledged and the
device should provide the proper vector number to indicate where the service routine for this interrupt level
is located. If the source of interrupt is not capable of providing a vector, its interrupt should be set up as an
autovector interrupt which directs the processor to a predefined entry in the exception table (refer to the
MCF5235 Reference Manual).
The processor goes to an exception routine via the exception table. This table is stored in the Flash
EEPROM. The address of the table location is stored in the VBR. The dBUG ROM monitor writes a copy
of the exception table into the RAM starting at $00000000. To set an exception vector, the user places the
address of the exception handler in the appropriate vector in the vector table located at $00000000 and then
points the VBR to $00000000.
The MCF5235 microprocessor has seven external interrupt request lines IRQ
[7:1]. The interrupt controller
is capable of providing up to 63 interrupt sources. These sources are:-
•External interrupt signals IRQ
[7:1] (EPORT)
•Software watchdog timer module
•Timer modules
•UART modules 0, 1 and 2
2
•I
C module
•DMA module
•QSPI module
•FEC module
•PIT
•Security module
•FlexCAN0 and FlexCAN1
•eTPU
All external interrupt inputs are edge sensitive. The active level is programmable. An interrupt request
must be held valid until an IACK cycle starts to guarantee correct processing. Each interrupt input can have
it’s priority programmed by setting the xIPL[2:0] bits in the Interrupt Control Registers apart from
interrupts 1-7 which have fixed priority already allocated to them.
No interrupt sources should have the same level and priority as another. Programming two interrupt
sources with the same level and priority can result in undefined operation.
The M523xEVB hardware uses IRQ7
to support the ABORT function using the ABORT switch (SW5).
This switch is used to force an interrupt (level 7, priority 3) if the user's program execution should be
aborted without issuing a RESET (refer to Chapter 2 for more information on ABORT). Since the ABORT
switch is not capable of generating a vector in response to a level seven interrupt acknowledge from the
processor, the dBUG programs this interrupt request for autovector mode.
Refer to MCF5235 Reference Manual for more information about the interrupt controller.
1.3.5TA Generation
The processor starts a bus cycle by asserting CSx with the other control signals. The processor then waits
for a transfer acknowledgment (TA) either from within (Auto acknowledge - AA mode) or from the
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-11
M523xEVB
externally addressed device before it can complete the bus cycle. TA is used to indicate the completion of
the bus cycle. It also allows devices with different access times to communicate with the processor
properly asynchronously. The MCF5235 processor, as part of the chip-select logic, has a built-in
mechanism to generate TA for all external devices which do not have the capability to generate this signal.
For example the Flash ROM cannot generate a TA signal. The chip-select logic is programmed by the
dBUG ROM Monitor to generate TA internally after a pre-programmed number of wait states. In order to
support future expansion of the M523xEVB, the TA input of the processor is also connected to the
Processor Expansion Bus (J9, pin 44). This allows any expansion boards to assert this line to provide a TA
signal to the processor. On the expansion boards this signal should be generated through an open collector
buffer with no pull-up resistor; a pull-up resistor is included on this board. All TA signals from expansion
boards should be connected to this line.
1.3.6User’s Program
JP64 on the 16Mbit FLASH (U19) or JP31 if using 32Mbit FLASH (U35) allows users to test code from
boot/POR without having to overwrite the ROM Monitor.
When the jumper is set between pins 1 and 2, the behavior of the system is normal, dBUG boots and then
runs from 0xFFE00000 (0xFFC00000). When the jumper is set between pins 2 and 3, the board boots from
the top half of the FLASH (0xFFF00000).
Procedure:
1. Compile and link as though the code was to be placed at the base of the flash.
2. Set up the jumper JP64 (JP31) for Normal operation, pin1 connected to pin 2.
3. Download to SDRAM (If using serial or ethernet, start the ROM Monitor first. If using BDM via
a wiggler cable, download first, then start ROM Monitor by pointing the program counter (PC) to
0xFFE00400(0xFFC00400) and run.)
4. In the ROM Monitor, execute the 'FL write <dest> <src> <bytes>' command.
5. Move jumper JP64 (JP31) to pin 2 connected to pin 3 and push the reset button (SW6). User code
should now be running from reset/POR.
1.4Communication Ports
The EVB provides external communication interfaces for two UART serial ports, a UART/FlexCAN1
port, FlexCan0 port, QSPI, I2C port, 10/100T ethernet port, eTPU port (including UNI3 and HS/ENCO
connectors for auxiliary motor control cards), USB Host port, USB Device port, and BDM/JTAG port.
1.4.1UART0 and UART1 Ports
The MCF5235 device has three built in UARTs, each with its own software programmable baud rate
generator. Two of these UART interfaces are brought out to RS232 transceivers. One channel is the ROM
Monitor to Terminal output and the other is available to the user. The ROM Monitor programs the interrupt
level for UART0 to Level 3, priority 2 and autovector mode of operation. The interrupt level for UART1
is programmed to Level 3, priority 1 and autovector mode of operation. The signals from these channels
are available on expansion connectors J7 and J8. The signals of UART0 and UART1 are passed through
the RS-232 transceivers (U30) & (U31) and are available on DB-9 connectors (P4) and (P5).
Refer to the MCF5235 Reference Manual for programming the UART’s and their register maps.
M523xEVB User’s Manual, Rev. 1.2
1-12Freescale Semiconductor
Communication Ports
1.4.2UART2/FlexCAN1 Port
The third UART on the MCF5235 is multiplexed with the second FlexCAN (FlexCAN1) module. As these
two modules are multiplexed such that the user has access to one or the other, the functionality on the EVB
is jumper selectable. Table 1-12 shows the jumper configuration to activate UART2 or FlexCAN1.
Table 1-12. UART2/FlexCAN1 Jumper Configuration
JumperUART2 Setting FlexCAN1 Setting
JP71-22-3
JP121-22-3
JP252-3X
JP262-3X
JP502-31-2
JP512-31-2
JP522-31-2
The signals of UART2 are passed through RS-232 transceiver U32 and are jumper selectable (for settings
see Table 1-12) on DB-9 connector P6.
The CAN1TX and CAN1RX signals from FlexCAN1 are brought out to a 3.3-V CAN transceiver (Texas
Instruments - SN65HVD230D) and are jumper selectable (for settings see Table 1-12) on DB-9 connector
P6. Jumpers JP3 and JP4 control the CAN hardware configuration.
Table 1-13. FlexCAN1 Jumper Configuration
JumperFunctionONOFF
JP3Transceiver modeStandbyHigh Speed (No Slope
Control)
JP4CAN TerminationTerminating resistor
between CANL and CANH
No terminating resistor
1.4.3FlexCAN0 Port
The EVB provides 1 dedicated CAN transceiver. The CAN0TX and CAN0RX signals are brought out to
a 3.3V CAN transceiver (Texas Instruments - SN65HVD230D). Jumper JP1 and JP2 control the CAN
hardware configuration.
Table 1-14. FlexCAN0 Jumper Configuration
JumperFunctionONOFF
JP1Transceiver modeStandbyHigh Speed (No Slope
Control)
JP2CAN TerminationTerminating resistor
between CANL and CANH
No terminating resistor
The CANL and CANH signals are brought out from the CAN transceiver to a female DB-9 connector (P1)
in the configuration below.
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-13
M523xEVB
Table 1-15. CAN Bus Connector Pinout
DB-9 pinSignal
1,4-6,7-9Not Connected
2CANL
3Ground
7CANH
1.4.410/100T Ethernet Port
The MCF5235 microprocessor populated on the EVB is a superset device of the MCF523x family. The
upper 16 eTPU channels are multiplexed with the ethernet port giving the EVB user the choice of utilizing
either the full 32-channels of eTPU or 16-channels of eTPU with the Fast Ethernet Controller (FEC)
activated. Pin M4 on the MCF5235 configures the internal functionality of these 16 pins. If the user is
using the FEC, pin M4 must be pulled low by setting SW7-11 to the ON position.
These 16 pins are also jumper selectable between the eTPU and the FEC in order to isolate the external
circuitry required to implement the functionality of these modules. Table 1-16 lists the appropriate jumper
settings to enable eTPU or FEC functionality on these pins.
The MCF5235 device performs the full set of IEEE 802.3/Ethernet CSMA/CD media access control and
channel interface functions. The MCF5235 Ethernet Controller requires an external interface adaptor and
transceiver function to complete the interface to the ethernet media. The MCF5235 Ethernet module also
features an integrated fast (100baseT) Ethernet media access controller (MAC).
The Fast Ethernet controller (FEC) incorporates the following features:
•Support for three different Ethernet physical interfaces:
— 100-Mbps IEEE 802.3 MII
— 10-Mbps IEEE 802.3 MII
— 10-Mbps 7-wire interface (industry standard)
•IEEE 802.3 full duplex flow control
•Programmable max frame length supports IEEE 802.1 VLAN tags and priority
•Support for full-duplex operation (200Mbps throughput) with a minimum system clock rate of
50 MHz
•Support for half-duplex operation (100Mbps throughput) with a minimum system clock rate of
25 MHz
•Retransmission from transmit FIFO following a collision (no processor bus utilization)
•Automatic internal flushing of the receive FIFO for runts (collision fragments) and address
recognition rejects (no processor bus utilization)
•Address recognition
— Frames with broadcast address may be always accepted or always rejected
— Exact match for single 48-bit individual (unicast) address
— Hash (64-bit hash) check of individual (unicast) addresses
— Hash (64-bit hash) check of group (multicast) addresses
— Promiscuous mode
M523xEVB User’s Manual, Rev. 1.2
1-14Freescale Semiconductor
Communication Ports
For more details see the MCF523x Reference Manual. The on board ROM MONITOR is programmed to
allow a user to download files from a network to memory in different formats. The current compiler
formats supported are S-Record, COFF, ELF or Image.
Table 1-16. Ethernet/eTPU Jumper Configuration
JumperPin
JP5D52-3ERXER1-223
JP9C52-3ETXCLK1-222
JP10B52-3ETXD21-218
JP11A52-3ETXD11-217
JP13D62-3ETXEN1-221
JP14C62-3ETXER1-220
JP15B62-3ETXD31-219
JP16C42-3ERXD01-224
JP17B72-3ETXD01-216
JP18C32-3ERXD11-225
JP19D42-3ERXD21-226
JP20D32-3ERXD31-227
JP21E32-3ERXCLK1-229
JP22E42-3ERXDV1-228
JP23F32-3ECOL1-231
JP24F42-3ECRS1-230
Ethernet
Setting
Ethernet
Signal
eTPU
Setting
eTPU
Channel
1.4.5eTPU
The eTPU is an intelligent programmable I/O controller with its own core and memory system, allowing
it to perform complex timing and I/O management independently of the CPU. The eTPU is essentially a
co-processor designed for timing control, I/O handling, serial communications, motor control. and engine
control applications and accesses data without the host CPU’s intervention. Consequently, the host CPU
setup and service times for each timer event are minimized or eliminated.
The eTPU is an enhanced version of the TPU module implemented on the MC68332 and MPC500
products. Enhancements of the eTPU include a more powerful processor which handles high-level C code
efficiently and allows for more functionality and increased performance. Although there is no
compatibility at microcode level, the eTPU maintains several features of older TPU versions and is
conceptually almost identical. The eTPU library is a superset of the standard TPU library functions
modified to take advantage of enhancements in the eTPU. These, along with a C compiler, make it
relatively easy to port older applications. By providing source code for the Motorola library, it is possible
for the eTPU to support the users own function development.
The eTPU has up to 32 timer channels in addition to having 6 Kbytes of code memory and 1.5 Kbytes of
data memory that stores software modules downloaded at boot time and that can be mixed and matched as
required for any specific application.
As mentioned in Section 1.4.4, “10/100T Ethernet Port,” the upper 16-channels of the eTPU are
multiplexed with the Fast Ethernet Controller.
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-15
M523xEVB
Refer to Table 1-16 to set the appropriate jumpers to enable 16 or 32-channels.
To configure the device to operate with the top 16-channels of the eTPU activated, pin M4 must be pulled
high by setting SW7-11 to the OFF position.
All 32 eTPU channels are available on a 0.1” 2x20 Molex connector providing easy access to the eTPU
for the EVB user.
Table 1-17. eTPU Header Pin Assignment
PineTPU SignalPineTPU Signal
1+3.3V2+5V
3TPUCH164UTPUODIS
5TPUCH176LTPUODIS
7TPUCH188TPUCH0
9TPUCH1910TPUCH1
11TPUCH2012TPUCH2
13TPUCH2114TPUCH3
15TPUCH2216TPUCH4
17TPUCH2318TPUCH5
19TPUCH2420TPUCH6
21TPUCH2522TPUCH7
23TPUCH2624TPUCH8
25TPUCH2726TPUCH9
27TPUCH2828TPUCH10
29TPUCH2930TPUCH11
31TPUCH3032TPUCH12
33TPUCH3134TPUCH13
35GND36TPUCH14
37TCRCLK38TPUCH15
39GND40GND
There is a UNI3 connector and HS/ENCO connector on the EVB for connection to an auxiliary card.
The auxiliary card is intended for evaluation of the eTPU functionality.
1.4.6BDM/JTAG Port
The MCF5235 processor has a Background Debug Mode (BDM) port, which supports Real-Time Trace
and Real-Time Debug. The signals which are necessary for debug are available at connector (J1).
Figure 1-4 shows the (J1) Connector pin assignment.
M523xEVB User’s Manual, Rev. 1.2
1-16Freescale Semiconductor
Communication Ports
DEVELOPER RESERVED
GND
GND
RESET
I/O or Pad Voltage
GND
PST2
PST0
DDATA2
DDATA0
MOTOROLA RESERVED
GND
Core Voltage
11
13
15
17
19
21
23
25
1
3
5
7
9
2
4
6
8
10
12
14
16
18
20
22
24
26
BKPT
DSCLK
DEVELOPER RESERVED
DSI
DSO
PST3
PST1
DDATA3
DDATA1
GND
MOTOROLA RESERVED
PSTCLK
TA
Figure 1-4. J1- BDM Connector Pin Assignment
The BDM connector can also be used to interface to JTAG signals. On reset, the JTAG_EN signal selects
between multiplexed debug module and JTAG signals. See Table 1-5.
1.4.7I2C
The MCF5235’s I2C module includes the following features:
2
•Compatibility with the I
•Multi master operation
•Software programmable for one of 50 different clock frequencies
•Software selectable acknowledge bit
•Interrupt driven byte by byte data transfer
•Arbitration-lost interrupt with automatic mode switching from master to slave
•Calling address identification interrupt
•Start and stop signal generation and detection
•Repeated start signal generation
•Acknowledge bit generation and detection
•Bus busy detection
Please see the MCF523x Reference Manual for more detail. The I
are brought out to expansion connector (J13).
2
The I
C functionality of the MCF5235 is multiplexed on the same pins as the QSPI. Jumpers JP6 and JP8
are used to connect/disconnect the I2C signals, SDA and SCL. To enable I2C JP6 and JP8 should be set
between pins 2 and 3.
C bus standard version 2.1
2
C signals from the MCF5235 device
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-17
M523xEVB
1.4.8QSPI
The QSPI (Queued Serial Peripheral Interface) module provides a serial peripheral interface with queued
transfer capability. It will support up to 16 stacked transfers at one time, minimizing CPU intervention
between transfers. Transfer RAMs in the QSPI are indirectly accessible using address and data registers.
Functionality is very similar, but not identical, to the QSPI portion of the QSM (Queued Serial Module)
implemented in the MC68332 processor.
•Programmable queue to support up to 16 transfers without user intervention
•Supports transfer sizes of 8 to 16 bits in 1-bit increments
•Four peripheral chip-select lines for control of up to 15 devices
•Baud rates from 147.1-Kbps to 18.75-Mbps at 75 MHz.
•Programmable delays before and after transfers
•Programmable QSPI clock phase and polarity
•Supports wrap-around mode for continuous transfers
Please see the MCF523x Reference Manual for more detail. The QSPI signals from the MCF5235 device
are brought out to expansion connector (J12).
Some of the QSPI signals are multiplexed with the I
and 2 to enable the QSPI module.
The EVB features an A to D converter (ADC) interfaced to the CPU via the QSPI. The ADC uses QSPI
chip select 0. This chip select has a jumper that can be removed if the EVB user is not using the ADC and
wishes to connect QSPI_CS0 to an alternative device.
2
C module. JP6 and JP8 should be set between pins 1
1.4.9USB Host and Device
The EVB features a USB controller interfaced externally to the MCF5235 via the DMA and external bus
modules. The USB controller can be configured to run in Host or Device mode.
There is a series “A” connector (Host) and a series “B” connector (Device) populated on the EVB. Either
one or the other can be used depending on whether the USB controller is configured to run in Host or
Device mode. JP56 must be set between pins 2 and 3 if the controller is configured in Host mode and
between pin 1 and 2 if the controller is configured in Device mode.
The USB controller also has On-The-Go (OTG) functionality. There is a footprint on the EVB for an OTG
Mini-AB connector if the user wants to utilize USB OTG. If using OTG JP55 must be fitted.
For more details see the Philips Semiconductor datasheet for the ISP1362 USB OTG controller.
There are a series of jumpers connected to the USB controller that allow the user to disconnect the DMA
and interrupt signals between the CPU and the USB controller if the USB controller is not in use. This
gives the user access to the DMA timer module channels 1 and 2 and an extra interrupt signal if they do
not require USB functionality. Table 1-18 details these jumper settings.
Table 1-18. USB DMA Enable and Disable Settings
JumperFunctionality when Jumper is FittedFunctionality when Jumper is NOT Fitted
JP61DACK1 not in use - pulled highDMA acknowledge 1 enabled
JP62Interrupt 4 enabled for USBInterrupt 4 disabled from USB
JP63DACK2 not in use - pulled highDMA acknowledge 2 enabled
1.5Connectors and User Components
1.5.1Daughter Card Expansion Connectors
Four, 60-way SMT connectors (J7, J8, J9 and J10) provide access to all MCF5235 signals. These
connectors are ideal for interfacing to a custom daughter card or for simple probing of processor signals.
Below is a pinout description of these connectors.
Table 1 - 1 9 . J 7
PinSignalPinSignal
1+5V2+5V
3+3.3V4+3.3V
5+3.3V6+3.3V
7GND8GND
9TPUCH2410TPUCH6
11TPUCH1712TPUCH4
13TPUCH1814TPUCH5
15TPUCH2216TPUCH2
17TPUCH2318TPUCH3
19TPUCH1920TPUCH1
21TPUCH2022TPUCH0
23TPUCH2124GND
25TPUCH1626EMDIO
27U2CTS
29I2C_SCL30I2C_SDA
31QSPI_SCK32QSPI_DIN
33BS334QSPI_DOUT
28EMDC
35BS236QSPI_PCS0
37BS1
39BS040CAN1RX
M523xEVB User’s Manual, Rev. 1.2
Freescale Semiconductor1-19
38SD_SCKE
M523xEVB
Table 1-19. J7 (continued)
PinSignalPinSignal
41U2RTS
43QSPI_PCS144U1CTS
45U1RTS46CAN1TX
47U1RXD48U2TXD
49U1TXD50CS2
51CS352CS7
53CS654CS5
55CS156CS0
57CS458A23
59GND60GND
42U2RXD
Table 1 - 2 0 . J 8
PinSignalPinSignal
1+5V2+1.5V
3+3.3V4+3.3V
5TPUCH86TPUCH7
7TPUCH108TPUCH9
9TPUCH2510TPUCH12
11TPUCH2712TPUCH11
13TPUCH2614TPUCH14
15TPUCH2916TPUCH13
17TPUCH2818TCRCLK
19TPUCH3120TPUCH15
21TPUCH3022GND
23GND24U0CTS
25U0RXD26DTOUT0
27DTIN028U0TXD
29U0RTS30GND
31CLKMOD032+3.3V
33CLKMOD134GND
35GND36D28
37D3038D29
39D3140D24
M523xEVB User’s Manual, Rev. 1.2
1-20Freescale Semiconductor
Loading...
+ 82 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.