The MPC8313E reference design board (RDB) is a system
featuring the PowerQUICC™ II Pro processor, which
includes a built-in security accelerator. This low-cost,
high-performance system solution consists of a printed
circuit board (PCB) assembly plus a s oft ware board support
package (BSP) distributed in a CD image. This BSP enables
the fastest possible time-to-market for development or
integration of applications including printer engines,
broadband gateways, no-new-wires home adapters/access
points, and home automation boxes.
This document describes the hardware features of the board
including specifications, block diagram, connectors,
interfaces, and hardware straps. It also describes the board
settings and physical connections needed to boot the
MPC8313E RDB. Finally, it considers the software shipped
with the platform.
When you finish reading this document, you should:
•Be familiar with the board layout
•Understand the default board configuration and your
board configuration options
This is a class A product. In a domestic
environment this product may cause radio
interference, in which case the user may
be required to take adequate measures.
•Know about the software and further documentation
that supports the board
Use this manual in conjunction with the following documents:
•MPC8313E PowerQUICC™ II Pro Integrated Communications Processor Family Reference Manual (MPC8313ERM)
•MPC8313E PowerQUICC II Pro Processor Hardw are Specifications (MPC8313EEC)
•“Hardware and Layout Design Considerations for DDR Memory Interfaces” (AN2582)
NOTE
The normal function of the product may be disturbed by strong
electromagnetic interference. If so, simply reset the product to resume
normal operation by following the instructions in the manual. If normal
function does not resume, use the product in another location.
This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy. If it is
not installed and used in accordance with the instruction manual, it may
cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in
which case the user will be require d to co rr ect the interference at his or her
own expense.
1MPC8313E RDB Hardware
This section covers the features, block diagram, specifications, and mechanical data of the MPC8313E
RDB.
1.1Features
The board features are as follows:
•CPU: Freescale MPC8313E running at 333/166 MHz; CPU/coherent system bus (CSB)
•Memory subsystem:
— 128 Mbyte unbuffered DDR2 SDRAM discrete devices
— 8 Mbyte flash single-chip memory
— 32 Mbyte NAND flash memory
— 256 Kbit M24256 serial EEPROM
— SD connector to interface with the SD memory card in SPI mode
•Interfaces:
— 10/100/1000 BaseT Ethernet ports:
™
– eTSEC1, RGMII: five 10/100/1000 BaseT RJ-45 interfaces using Vitesse
switch, or selectable one 10/100/1000 BaseT RJ-45 interface using Marvell
in REVC board
The MPC8313E RDB reset module generates a single reset to the MPC8313E and other peripherals on the
board. The reset unit provides power-on reset, hard reset, and soft reset signals in compliance with the
MPC8313E hardware specification.
Figure 4 shows the reset circuitry. Note the following:
•Hard reset is generated either by the COP/JTAG port or the MPC8313E.
•Power-on reset is generated by the Maxim MAX811 device. When MR is deasserted and 3.3 V is
ready , the MAX81 1 internal timeout guarantees a minimum reset active time of 150 ms before
PORESET is deasserted. This circuitry guarantees a 150 ms PORESET pulse width after 3.3 V
reaches the right voltage level, which meets the specification of the PORESET input of
MPC8313E.
•COP/JTAG port reset provides convenient hard-reset capability for a COP/JT AG controller. The
RESET line is available at the COP/JT AG port connector. The COP/JTAG controller can directly
generate the hard-reset signal by asserting this line low.
•Push button reset interfaces using the MR signal with debounce capability to produce a manual
master reset of the RDB.
•Soft reset is generated by the COP/JT AG port. Assertion of SRESET causes the MPC8313E to
abort all current internal and external transactions and set most registers to their default values.
66.666 MHzMPC8313E CLKIN66.666 MHz oscillatorThe MPC8313E uses CLKIN to generate the
PCI_SYNC_OUT clock signal, which is fed back
on the board through the PCI_SYNC_IN signal
to the internal system PLL. From the power-on
reset configuration, the CSB clock is generated
by the internal PLL and is fed to the e300 core
PLL for generating the e300 core clock. The
CFG_CLKIN_DIV
whether CLKIN or CLKIN/2 is driven on the
PCI_SYNC_OUT signal. The CFG_CLKIN_DIV
is tied to the M66EN input pin.
133 MHzDDR2 SDRAMMPC8313EThe DDR memory controller is configured to use
the 2:1 mode CSB to DDR for the DDR interface
(DDR266). The local bus clock uses 1:1 local to
CSB clock, which is configured by hard reset
configuration or SPMR register.
configuration input selects
33/66 MHzPCI 32-bit slot and MiniPCI
slot
25 MHzL2 Switch and GBE PHY25 MHz oscillatorThe 25 MHz oscillator provides the clock for the
125 MHzeTSEC clockGBE PHY with PLL
48 MHzUSB clock48 MHz oscillator48 MHz is provided for on-chip USB PHY of
24 MHzULPI external USB PHY24 MHz crystal24 MHz crystal is used by the ULPI external
32.768 KHzReal-time clock32.768 KHz crystal32.768 KHz crystal is used by the real-time clock
MPC8313EThe PCI module uses the PCI_SYNC_IN as its
clock source. The trace length of the
PCI_SYNC_IN to PCI_SYNC_OUT signal is
matched with all PCI clocks on the RDB.
L2 switch and the GBE PHY
The GTX_CLK125 and SERDES (SGMII) clocks
(REVC), or
125 MHz oscillators
(REVB), or
GBE PHY (REVAx)
MHz VCXO
are provided by external oscillators (or by GBE
PHY in REVAx and REVC boards).
MPC8313E
50 MHz is used by the IEEE 1588 module. It can
be an ordinary oscillator or VCXO controlled by
SPI DAC.
USB PHY
2.4DDR2 SDRAM Controller
The MPC8313E processor uses DDR2 SDRAM as the system memory. The DDR2 interface uses the
SSTL2 driver/receiver and 1.8 V power. A Vref 1.8 V/2 is needed for all SSTL2 receivers in the DDR2
interface. For details on DDR2 timing design and termination, refer to the Freescale application note
entitled “Hardware and Layout Design Considerations for DDR Memory Interfaces” (AN2582). Signal
integrity test results show this design does not require terminating resistors (series resistor (R
termination resistor (R
)) for the discrete DDR2 devices used. DDR2 supports on-die termination; the
T
DDR2 chips and MPC8313E are connected directly. The interface is 1.8 V provided by an on-board
voltage regulator. VREF, which is half the interface voltage, or 0.9 V, is provided by a voltage divider of
1.8 V for voltage tracking and low cost. The MPC8313E provides a pair of clock pins, which are connected
and shared by the two DDR2 devices.
Figure 7 shows the DDR2 SDRAM controller connection.
2.5Local Bus Controller
The MPC8313E local bus controller has a 26-bit LAD[0–15] and LA[16–25] address that consists of
16-bit data multiplex bus and control signals. The local bus speed is up to 133 MHz. T o interface with the
standard memory device, an address latch must provide the address signals. The LALE is used as the
latching signal. To reduce loading of the high speed local bus interface, a data buffer for all low-speed
devices is attached to the memory controller. The followings modules are connected to the local bus:
2.5.1NOR Flash Memory
Through the general-purpose chip-select machine (GPCM), the MPC8313E RDB provides 8 Mbyte of
flash memory using a chip-select signal. The flash memory is used with the 16-bit port size. Figure 8
shows the hardware connections for the flash memory . The starting address for the 8 M byte flash memory
is 0xFE00_0000 to 0xFE7F_FFFF.
2.5.2NAND Flash Memory
The MPC8313E has native support for NAND Flash memory through its NAND Flash control machine
(FCM). The MPC8313E RDB implements an 8-bit NAND Flash with 32 Mbyte in size. Figure 9 shows
the NAND Flash connection.
The MPC8313E RDB has an 8-bit read/write buffer . The read buffer returns information on M66EN, board
revision, boot device (NOR or NAND), and SD card status. The write buffer controls eight LEDs on the
board for status or debug indication. Figure 10 shows the hardware connection of the buffers.
2.6I2C Interfaces
The MPC8313E has two I2C interfaces. On the MPC8313E RDB, I2C1 is used as master mode. It is
connected to the following three devices as shown in Figure 11.
It may also be connected to the DAC AD5301 at addres s 0x0C, whose optional nature is represented in
Figure 11 by the dashed line.
The connection of the I
the reset configuration word of the MPC8313E, as well as to store the configuration registers’ values and
user program if the MPC8313E boot sequencer is enabled. By default, the EEPROM is not used and the
hard reset configuration words are loaded from local bus flash memory. For details about how to program
Figure 10. LED/Status Buffers
•Serial EEPROM M24256 at address 0x50.
•Real-time clock DS1339U at address 0x68.
•Thermal sensor LM75 at address 0x48.
2
C bus is shown in Figure 11. The M24256 serial EEPROM can be used to store
the reset configuration word value i n I2C EEPROM and the boot se quencer mode, refer to the MPC8313E
reference manual.
Figure 11. I2C Connection
2.7SD Memory Card Interface
An SD memory card interface connects directly to the SPI bus of the MPC8313E. SD data mode and SDIO
mode are not supported. The SPI mode is the only SD operating mode supported by this connection. Hot
insertion and removal is not supported. See Figure 12 for the hardware connection.
For REVB boards, the SD card chip select signal is changed from GPIO31(SPISEL) to GPIO13(LA8)
because when using SPI as master mode, SPISEL
device select signal). In this case, another GPIO pin should be used. GPIO13 is implemented on this board
as an example.
cannot be set as GPIO (which is supposed to be used for
**NOTE: Because ULPI is multiplexed with eTSEC1 RGMII, by default
on-chip PHY is used. A change of resistor option is needed to use
the external USB PHY interface.
OR
Power down before inserting or removing the SD memory card.
2.8USB Interface
CAUTION
Figure 12. SD Memory Card Connection
MPC8313E supports a USB 2.0 high speed host/device i nterface through its on-chip USB PHY or external
ULPI USB PHY. The MPC8313E R DB s upports both options. By default, the on- chip USB PHY is used.
Dual RS-232 ports are supported on the RDB. Figure 16 illustrates the serial port connection using a
MAX3232 3.3 V RS-232 driver to interface with a 9-pin D type female connector . Thi s serial connection
runs at up to 115.2 Kbps.
Figure 16. RS-232 Debug Ports Connection
2.12PCI Bus
The 32-bit PCI interface connects to a 32-bit 3.3 V PCI slot and a miniPCI slot (see Figure 17).
The common on-chip processor (COP) is part of the MPC8313E JTAG module and is implemented as a
set of additional ins tructions and logi c. This por t can connect to a dedicated emulator for extensive system
debugging. Several third-party emulators in the market can connect to the host computer through the
Ethernet port, USB port, parallel port, RS-232, and so on. A typical setup using a USB port emulator is
shown in Figure 18.
Figure 18. Connecting MPC8313E-RDB to a USB Emulator
The 16-pin generic header connector carries the COP/JTAG signals and the additional signals for system
debugging. The pinout of this connector is shown in Figure 19.
Figure 19. MPC8313E RDB COP Connector
3Connectors, Jumpers, Switches, and LEDs
Table 3 summarizes the connectors, jumpers, switches, and LEDs on the MPC8313E RDB and provides
the number of the section/page on which each is discussed. The rest of this section discusses each of these
in the order of its appearance in the table.
Table 3. Connectors, Jumpers, Switches, and LEDs (continued)
ReferenceDescription Section/Page
D11On-chip USB PHY CTL1—
D1612-V Indicator—
D155-V Indicator—
D143.3-V Indicator—
D172.5-V Indicator—
D135-V standby indicator—
D3Programmable LED0 (Red)3.12/Page 27
D5Programmable LED1 (Yellow)
D2Programmable LED2 (Green)
D1Programmable LED3 (Green)
D22Programmable LED4 (Green)
D21Programmable LED5 (Green)
D20Programmable LED6 (Green)
D4Programmable LED7/LCD_EN (Green)
3.1COP Connector (P1)
The COP connector allows the user to connect a COP/JTAG-based debugger to the MPC8313E RDB for
debugging. Table 4 lists the pin assignments of the COP connector.
Table 4. COP Connector Pin Assignments
PinSignalPinSignal
1TDO2GND
3TDI4TRST
5QREQ 6VDD_SENSE
7TCK8CKSTP_IN
9TMS 10 NC
11SRESET
13HRESET
15CKSTP_OUT16GND
12NC
14NC
3.2PCI Slot (P2)
The MPC8313E RDB has one 32-bit 3.3-V PCI expansion slot (P2) for an expansion card. The slot
connects AD15 for its device select signal. Only the 3.3-V PCI card is supported. Turn OFF power during
insertion and removal of the PCI card. As Figure 20 shows, 3.3-V PCI cards can be identified by the key
position on the PCI card.
Figure 20. 3.3 V Key on a Typical 3.3 V PCI Card
3.3MiniPCI Connector (P3)
There is a MiniPCI connector (P3) on the RDB. The slot connects to AD14 for its device select signal.
Figure 21 shows how to install a MiniPCI card.
3.4USB Connectors (P4, P8)
There are two USB connectors on the MPC8313E RDB . One connects to the on-chip PHY of the
MPC8313E, and the other connects to the external ULPI USB PHY. Either can be enabled at a time. The
selection between the two requires modification of micro-jumpers/resistor options as discussed later. By
default, the on-chip PHY USB is used. Figure 22 shows the USB connectors in front panel.
Figure 22. USB Connectors
3.5Ethernet Connectors (P5, P6, P7)
The MPC8313E RDB has six Ethernet ports (RJ-45). The first five ports (G0–G4) are supported by
eTSEC1 (L2 switch), and the last port (G5) is supported by eTSEC2 (GBE PHY). Figure 23 shows the
G0–G5 mapping viewing from the front panel.
Serial interfaces are available at connector P11. It is a double deck RS-232 female connector. The upper
port is UART1 and the lower port is UART2. By default, UAR T 1 is used. Figure 24 shows the RS-232
UART connector front view.
.
Figure 24. RS-232 UART Connectors
3.7SD Memory Card Socket (U44)
An SD card socket (U44) for SD memory card installation is located next to the UART connector of the
board. Figure 25 shows how to install a compact flash card.
3.8LCD Connectors (J21, J22)
T wo headers (J21, J22) are provided for LCD connections. They use the MPC8313E GPIO interface. Both
headers carry the same set of GPIO signal pins, but they are different physically. J21 is single row of
1 × 14, and J22 is double row of 2 × 7. Table 5 shows the mapping.
A header (P10) is provided for IEEE 1588 signals connection. It is double r ow of 2 × 8 header connector.
The pinout of this connector is shown in Figure 26.
DIP switch S3 selects the reset configuration source (RST_CFG_SRC) for the MPC8313E. Figure 27
shows the factory default configuration of S3.
Figure 27. DIP Switch S3
Check the MPC8313E reference manual for the meaning of the CFG_RST_SRC combination. By default,
the DIP switch is set to all ON, meaning CFG_RST_SRC[0..3] = 0000. In this case, the hardware reset
configuration is loaded from local bus NOR flash memory.
3.11DIP Switch S4
DIP switch S4 on the RDB is shown in Figure 28, with the factory default configuration.
RSVD is reserved. When software options are implemented, their values can be read from a buffer on the
board. CFG_BOOT_ECC_DIS switch is OFF by default to disable booting with ECC by driving HIGH to
the signal LB_POR_CFG_BOOT_ECC_DIS (TSEC1_MDC) during power on reset (REVB and REVC
only . REVAx is a reserved switch (RSVD0)). REV1 represents bit 1 of the revision number. T ogether with
REV0 (implemented by resistor option; the default is 0), REV[0..1] shows the revision number, which is
01 by default. The values can be read from a buffer on the RDB. BOOT1 selects the boot device on the
RDB. By default, BOOT1 is set, so chip-select 0 (CS0) is connected to the NOR Flash. CS1 is connected
to the NAND Flash memory. If BOOT1 is cleared, CS0 is connected to NAND Flash memory, and CS1 is
connected to NOR Flash memory.
3.12RDB Programmable LEDs
Eight programmable LEDs give status indication and debug information. Figure 29 shows the diagram.
Figure 29. Programmable LEDs
An 8-bit write register on the RDB turns the LEDs on and off. The LEDs are arranged so that the most
significant bit represents LED0 and least significant bit represents LED7; that is, LED[0..7]. A write of
0x00 turns on all LEDs, and 0xFF turns off all LEDs.
4Micro-Jumper/Resistor Options for eTSEC1
The eTSEC1 RGMII, ULPI USB, and IEEE 1588 signals are multiplexed on the MPC8313E. The
MPC8313E RDB supports switching among the three interfaces using micro-jumpers (REVA boards) or
resistor options (REVA1 or later boards).
NOTE
For IEEE 1588 support, use the same setting as for the eTS EC1 RGMII. In
this case, a 50 MHz clock would be provided for the IEEE 1588 TMR_CLK
pin.
Because the eTSEC1 Ethernet switch PHY on the RDB supports only RGMII, the eTSEC1 SGMII is not
supported. The micro-jumper settings listed only matter for the eTSEC1 pin connections. They have
nothing to do with switching between eTSEC2 RGMII and SGMII. The settings of eTSEC2 SGMII are
provided as a reference.
Figure 35 shows the graphical representation for Setup 4.
Figure 35. Setup 4 Resistor Options for REVA1
Because the eTSEC1 Ethernet switch PHY on the RDB supports only RGMII, the eTSEC1 SGMII is not
supported on the RDB. The resistor options listed only matter for the eTSEC1 pin connections. They have
nothing to do with switching between eTSEC2 RGMII and SGMII. They are listed for reference. The
switch between eTSEC2 RGMII and SGMII does not require hardware modification on the RDB.
4.3REVB Boards
For REVB boards, three more resistor options (R311–R313) are added to route three IEEE 1588 signals
to the IEEE 1588 connector.
All other resistor options are the same as on the REVA1 to REVA4 boards.
Table 14 shows how to populate the resistors if these three optional signals are used.
Table 14. Resistor Options for REVB Using Three Optional IEEE 1588 Signals
For REVC boards, 22 more resistor options (R31 1–R313) are added to route eTSEC2 RGMII signals either
to L2 Switch or Marvell 88E1111 PHY. All other resistor options are the same as on the REVB boards.
Figure 38 shows the graphical representation for Setup 3.
Figure 38. Setup 2 Resistor Options for REVC
5MPC8313E RDB Board Configuration
This section describes the operational frequency and configuration options of the MPC8313E RDB.
5.1PCI Operating Frequency
An M66EN input pin determines the frequency of the PCI interface. On the MPC8313E RDB, the M66EN
signal level is determined by the PCI agent card connected to the miniPCI or PCI slot. If a 33 MHz-only
card is inserted, the M66EN signal is driven to 0 by the PCI agent card according to the PCI specification.
However, it is pulled to 1 if it can perform at 66 MHz. By default, the MPC8313E RDB runs its PCI
interfaces at 66 MHz unless a 33-MHz PCI card is inserted.
5.2Reset Configuration Word
The reset configuration word (RCW) controls the clock ratios and other basic device functions such as PCI
host or agent mode, boot location, and endian mode. The reset configuration word is divided into reset
configuration word lower (RCWL) and reset configuration word higher (RCWH) and is loaded from the
local bus during the power-on or hard reset flow. The default RCW low bit setting is 0x6204_0000. The
default RCW high bit setting is 0xA060_7800. The RCW is located at the lowest 64 bytes of the boot flash
memory, which is 0xFE00_0000 if the default memory map is used.
Table 18 shows the default RCW in the flash memory.
Table 18. Default RCW in Flash Memory
Address
FE000000:62626262626262620404040404040404
FE000010:00000000000000000000000000000000
FE000020:A0A0A0A0A0A0A0A06060606060606060
FE000030:78787878787878780000000000000000
The RCW definitions are shown in Figure 39 and Figure 40.
0123456789101112131415
FieldLBCM DDRCM—SPMF—COREPLL
16171819202122232425262728293031
Field—
Figure 39. Reset Configuration Word Low (RCWL) Bit Settings
012345678910 11 12131415
Field PCIHOST—PCIABR—COREDIS BMS BOOTSEQ SWEN ROMLOCRLEXT—
16171819202122232425 26 2728293031
FieldTSEC1MTSEC2M—TLE LALE—
Figure 40. Reset Configuration Word High (RCWH) Bit Settings
Table 19. RCWL Bit Descriptions
BitsNameMeaningDescription
0LBCMLocal bus clock mode Local Bus Controller Clock: CSB_CLK
Table 20. Reset Configuration Word High (RCWH) Bit Descriptions (continued)
BitsNameMeaning Description
19-21TSEC2MTSEC2 Mode000MII mode
001RMII mode
011:DefaultRGMII mode
101RTBI mode
110SGMII mode
010,100,111Reserved
22-27Reserved—Must be cleared
28TLETrue little endian0: DefaultBig-endian mode
1True little endian mode
29LALELocal Bus ALE
signal timing
30-31Reserved—Must be cleared
0: DefaultNormal LALE timing
1LALE is negated 1/2 lbc_controller_clk earlier.
5.3Power Supply
The MPC8313E RDB requires a power supply from the A TX power connector. The ATX supply connector
directly provides 12-V, 5-V, and 3.3-V voltages. Core voltage, DDR2 voltage, RGMII voltage, and
PHY-specific voltages are provided by either switching or linear regulated depending on the voltage drop
and current consumption requirement. MPC8313E power-down mode is supported. A regulator that can
be shut down is implemented for this purpose.
The MPC8313E does not require the core supply voltage and IO supply voltages to be applied in any
particular order. However, during the power ramp up, before the power supplies are stable, there may be
an interval when the IO pins are actively driven. After the power is stable, as long as PORESET is asserted,
most IO pins are three-stated. To minimize the time that IO pins are actively driven, apply core voltage
before IO voltage and assert PORESET before the power supplies fully ramp up.
Table 21 shows the power supply table.
Table 21. Power Supply Usage Summary
VoltageUsageBudgetSolution
1 V shutdownableVDD, AVDD1<1 AMIC1510ETB+ regulator (3 A) with tracking
1 VVDDC<10 AMIC1953EUB+ switching
1.2 VVSC7385, 88E11111.75 A + 0.4 AMIC37302 LDO (3 A)
1.8 VDDR20.5 A + DDR chip x2pcsMIC37302 LDO (3 A)
2.5 VRGMII0.2 A + 0.2 A + 0.2 AMIC39100-2.5WS (1 A)
This section describes how to boot the MPC8313E RDB. The on-board flash memory is preloaded with a
flash image from the factory. Before powering up the board, verify that all the on-board DIP switches and
jumpers are set to the factory defaults according to the settings listed in Section 6.1, “Board Jumper
Settings,” and make all external connections as described in Section 6.2, “Externa l Cable Connections.”
CAUTION
A void touching areas of integrated circuitry and connectors; static discharge
can damage circuits.
Only the 3.3-V PCI Card is supported. T urn OFF power during insertion and
removal of a PCI card.
CAT-5 cable to
one of the ports (lowerright-most is eTSEC2, other
five are eTSEC1)
Straight-through 9-conductor
serial cable, M-F (upper
port for UART1 default;
lower por t for UART2)
6.2External Cable Connections
Do not turn on power until all cables are connected and the serial port is configured as described in
Section 6.3, “Serial Port Configuration (PC).” C onnect the serial port of the MPC8313E RDB system and
the personal computer using an RS-232 cable as shown in Figure 42.
Figure 42. External Connections
6.3Serial Port Configuration (PC)
Before powering up the MPC8313E RDB, configure the serial port of the attached computer with the
following values:
•Data rate: 115200 bps
•Number of data bits: 8
•Parity: None
•Number of Stop bits: 1
•Flow Control: Ha rd wa re /N on e
6.4Power Up
An ATX-type power connector (P9) should be used to supply necessary DC power to the MPC8313E
RDB. It can be provided by an ATX-type power supply or from a mini-ITX case.
WARNING
Turn off the main power for the ATX power supply/mini-ITX case before
the power connector is attached.
Coherent System Bus: xxx MHz
Core: yyy MHz
Local Bus Controller: xxx MHz
Local Bus: yy MHz
DDR: xxx MHz
…
Hit any key to stop autoboot: 0
=>
NOTE
The normal function of the product may be disturbed by strong
electromagnetic interference. If so, simply reset the product to resume
normal operation by following the instructions in the manual. If normal
function does not resume, use the product in another location.
7MPC8313E RDB Software
A board support package (BSP) is pre-installed on the MPC8313E RDB. This BSP consists of a bootloader
(U-Boot), a generic PowerPC Linux-based system, and an associated file system. U-Boot, the Linux
kernel, and the file system reside in the on-board flash memory. At power up, the Linux system runs on
the MPC8313E RDB.
The MPC8313E RDB BSP generation takes advantage of a tool called the Linux Target Image Builder
(LTIB). LTIB is a suite of tools that leverages existing open source configuration scripts and source code
packages and bundles them into a single BSP-generation package. The source code packages include boot
loaders and Linux kernel sources as well as many user-space source code packages to build a complete
BSP. L TI B also provides compiler packages required to build the BSP. Freescale developers use LTIB to
create BSPs for a multitude of Freescale development targets. LTIB leverages as many BSP elements as
possible for all Freescale-supported targets, and it offers the flexibility to customize components that
require platform-specific modifications.
The MPC8313E RDB BSP release package contains a file named
MPC8313E RDB-<yyyymmdd>.iso. This file
is an ISO image that can be burned to a CD-ROM or mounted directly from your hard disk. Note that
<yyyymmdd> is the release creation date. The LTIB installation script that installs all necessary packages on
a host Linux PC and allows you to modify the BSP and packages within the BSP is in the
/ltib-MPC8313E-RDB
subdirectory within the ISO image.
This ISO image contains a file called Readme.txt that describes how to generate and install the BSP on the
MPC8313E RDB hardware platform.
ISO image also contains
Release Notes.txt, which describes changes to the current BSP version versus
Readme.txt contains the latest information for each BSP release. The
earlier releases. To rebuild the BSP package or to add application software, carefully follow th e
instructions in Readme.txt. Th is file contains details on how to build, run, and install the BSP. It guides the
user to achieve a successful re-installation of the BSP on the MPC8313E RDB. This ISO image contains
the following documents as well:
•MPC8313ERDBUG.pdf. This user's guide document in PDF format.
MPC8313E-RDB_schematic.pdf. The platform schematic in PDF format.
•
•
SEC2SWUG.pdf. User's guide for the driver software of the security engine. This document details the
driver software interface to boost the throughput performance of security applications such as
IPSec.
•LtibFaq.pdf. Frequently asked questions for LTIB, which is a us eful document desc ribing how to
use LTIB to build the ISO image.
For more information on the MPC8313E RDB, visit the Freescale website listed on the back cover of this
document. To run demonstrations or to acquire details of Freescale third-party applications for this
MPC8313E RDB, contact your local Freescale sales office.
8Frequently Asked Questions (FAQs)
Here are some commonly asked questions and their respective answers.
8.1What are the differences among RDB revisions?
There are five revisions of the RDB, which are REVA, REVA1, REVA2, REVA3, REVA4, REVB and
REVC. Table 24 lists and describes these revisions.
Table 24. MPC8313E-RBD Revisions
RevisionDescription
REVAThere are two major issues on the REVA board:
• On-chip PHY USB signals (DP, DM) are swapped. To use the USB, use a USB cable that swaps the signals
(the cable is attached in the REVA package).
• NAND flash memory cannot be used as a boot device.
REVA1Fixes both major issues on the REVA board. The boot-from-NAND on the REVA1 RDB has been verified.
However, on the current BSP preloaded on REVA1 RDB, NAND flash memory is empty, so it is also not
bootable. Booting from NAND flash memory will be supported in a future release of the BSP.
Software for REVA and REVA1 differs only in the OR1[BCTLD] register setting for NAND flash memory. That
is, REVA OR1[BCTLD] is 1; while REVA1 OR1[BCTLD] is 0.
REVA2A minor update from REVA1 for mass production. It updates the silkscreen and adds a 12-V fan connector
(J25) and resistor loading for ATX power.
Software can be shared without modification between REVA1 and REVA2.
REVA3Fixes the PMC register issue mentioned in Section 8.5, “Power management control (PMC) registers cannot
be accessed?”
Because of a processor erratum, a 166 MHz CSB frequency should be used. For this reason, some REVA3
and all later boards have 33 MHz instead of 66 MHz as the clock input (check your board U15 oscillator
marking). The CORE/CSB/DDR frequency setting is 333/166/333 MHz. However, there are two drawbacks:
• PCI bus can run at up to only 33 MHz
• PCI/mini-PCI card can run at 66 MHz (has its M66EN pulled up) and should be used. Even the PCI bus on
the RDB runs at only 33 MHz. Otherwise, the PCI frequency is further divided and it becomes 16.6 MHz.
• Changed default TSEC1_GTX_CLK125 clock source to PLL CY23EP05SX-1 instead of external 125 MHZ
oscillator.
• Changed U36 1A linear regulator MIC39100-2.5WS to 3A MIC37302WR for higher 2.5V power consumption
by additional PHY.
• Changed default DAC to 16-bit SPI controlled MAX5203BEUB+ (U47).
(GPIO31) to GPIO13.
8.2What should I do if the flash (NOR flash) image on the RDB is
accidentally erased?
You should set the RDB to use a hardcoded reset configuration and reprogram the flash memory by
debugger (for example, CodeWarrior debugger + USBTAP). T o use a hardcoded reset configuration, set
DIP switch S3 as OFF-ON-OFF-OFF (1011). On the other hand, if there is a reset configuration in NAND
Flash or the I2C EEPROM, you may want to use either one as a hard reset configuration source.
Alte rnat iv ely, some RE VA3 and all later boards have the I2C EEPROM bootloader programmed. It can be
used to reprogram the NOR Flash memory without a debugger. The procedure is as follows:
1. Power off the board and set DIP switch S3 as ON-OFF-ON-ON (0100).
2. Connect the board to Kermit (a UART terminal program; the other terminal program does not
work at this mode). Kermit can be downloaded from http://kermit.wwarthen.com/Download.htm.
3. Set the baud rate in Kermit as 38400 bps (for a 66 MHz clock-in RDB) or 19200 bps (for a 33
MHz clock-in RDB).
4. Power on the board and you should see the following in Kermit:
Hello and welcome to I2C BOOTLOADER
## Ready for binary (kermit) download
5. Go to Kermit → Send and select the u-boot image binary to be written into flash memory .
6. Wait for the file transfer and flash programming until you see
7. Power off the board and set DIP switch S3 back to ON-ON-ON-ON (0000).
8. Power on the board and you should see a running u-boot.
8.3What is the hardware setting for boot from NAND Flash?
Set DIP switch S4 as OFF-OF F-OFF-ON (1 1 10) and set DIP swit ch S3 as ON-ON-ON-OFF (0001). Note
that there is no boot image on NAND flash memory with the default shipment.
8.4Some ATX power supplies do not work with the RDB?
Some ATX power supplies may need a large 5-V loading to stabilize the 3.3-V output; otherwise, you may
observe the 3.3 V lowered to around 2.9 V–3 V. The consequence can be a periodic reset by the on-board
voltage monitoring circuit. For a workaround, you may take one of the following actions:
•Add a 5-V loading to the power supply, for example, attach a hard disk drive.
•Change to another ATX power supply that does not require a large 5-V loading.
•Use the power supply provided with the RDB package.
Starting from revision REVA2, a resistor loading for 5 V is added. It should work better with the ATX
power supply that requires large 5-V loading. If there is still a problem, simply apply one of the
workarounds presented here.
8.5Power management control (PMC) registers cannot be
accessed?
The PMC registers range from IMMR + 0x0B00 to IMMR + 0x0BFF . When this area is accessed in u-boot,
the RDB hangs up. It appears that the PMC block is related to the JT AG interface; TRST must not be pulled
down for normal operation of the PMC block. Possible workarounds are as follows:
•Attach a debugger to drive TRST high during normal operation.
•Remove the pull-down resistor (R37) for TRST. Although this tested on some RDBs without any
problem, it violates the hardware specification. If it does not work on your RDB, use another
workaround.
•This problem is fixed in REVA3
9Revision History
Table 25 provides a revision history for this document.
Table 25. Document Revision History
Rev.
Number
02/2007Initial public release.
14/2007Replaced a faulty table of contents and restructured sections of the document for clarity.
24/2007Added information to Section 8, Frequently Asked Questions (FAQs)
Freescale Semiconductor, Inc.
Technical Information Center, EL516
2100 East Elliot Road
Tempe, Arizona 85284
+1-800-521-6274 or
+1-480-768-2130
www.freescale.com/support
Japan:
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 2666 8080
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
+1-303-675-2140
Fax: +1-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 m ake 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 which 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 whi ch the failure o f the Freescale Semiconductor product
could create a situation where personal injury or deat h may occur. Should Buyer
purchase or use Freescale Semiconductor products for any such unintended or
unauthorized application, Buyer shall indemnify and hold Freescale Semiconductor
and its officers, employees, subsidiaries, affiliates, and distributors har mless against all
claims, costs, damages, and expenses, and reasonable attor ney 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 d esign or manufacture of the part.
Freescale™ and the Freescale logo are trademarks of Freescale Semiconductor, Inc.
The Power Architecture and Power.org word marks and the Power and Power.org logos
and related marks are trademarks and service marks licensed by Power.org. The
PowerPC name is a trademark of IBM Corp. and is used under license. IEEE 1588 are
registered trademarks of the Institute of Electrical and Electronics Engineers, Inc.
(IEEE). This product is not endorsed or approved by the IEEE. All other product or
service names are the property of their respective owners.