This phyCORE-ARM9/LPC3250 Hardware Manual describes the single board computer's design and
functions. Precise specifications for the NXP Semiconductors LPC3250 processor can be found in the
enclosed processor Data Sheet/User's Manual. If software is included please also refer to additional
documentation for this software.
In this hardware manual and in the attached schematics, low active signals are denoted by a "/" preceding
the signal name (i.e.: /RD). A "0" indicates a logic-zero or low-level signal, while a "1" represents a logicone or high-level signal.
Declaration of Electro Magnetic Conformity of the PHYTEC
phyCORE-LPC3250
PHYTEC System on Modules (SOMs) are designed for installation in electrical appliances or, combined
with the PHYTEC Carrier Board, can be used as dedicated Evaluation Boards (i.e.: for use as a test and
prototype platform for hardware/software development) in laboratory environments.
CAUTION:
PHYTEC products lacking protective enclosures are subject to damage by ESD and, hence, may only be
unpacked, handled or operated in environments in which sufficient precautionary measures have been
taken in respect to ESD-dangers. It is also necessary that only appropriately trained personnel (such as
electricians, technicians and engineers) handle and/or operate these products. Moreover, PHYTEC
products should not be operated without protection circuitry if connections to the product's pin header
rows are longer than 3 m.
PHYTEC products fulfill the norms of the European Union's Directive for Electro Magnetic Conformity only
in accordance to the descriptions and rules of usage indicated in this hardware manual (particularly in
respect to the pin header row connectors, power connector and serial interface to a host-PC).
Implementation of PHYTEC products into target devices, as well as user modifications and extensions of
PHYTEC products, is subject to renewed establishment of conformity to, and certification of, Electro
Magnetic Directives. Users should ensure conformance following any modifications to the products as
well as implementation of the products into target systems.
The phyCORE-LPC3250 is one of a series of PHYTEC System on Modules that can be populated with
different controllers and, hence, offers various functions and configurations. PHYTEC supports a variety of
8-/16- and 32-bit controllers in two ways:
1. As the basis for Rapid Development Kits which serve as a reference and evaluation platform.
2. As insert-ready, fully functional phyCORE OEM modules, which can be embedded directly into the
user's peripheral hardware, design.
Implementation of an OEM-able SOM subassembly as the "core" of your embedded design allows you to
focus on hardware peripherals and firmware without expending resources to "re-invent" microcontroller
circuitry. Furthermore, much of the value of the phyCORE module lies in its layout and test.
Production-ready Board Support Packages (BSPs) and Design Services for our hardware further reduce
development time and expenses. Take advantage of PHYTEC products to shorten time-to-market, reduce
development costs, and avoid substantial design issues and risks. For more information go to:
Part 1 of this 3 part manual provides detailed information on the phyCORE-ARM9/LPC3250 System on
Module (SOM) designed for custom integration into customer applications.
The information in the following chapters is applicable to the 1304.1 PCB revision of the phyCORELPC3250 SOM.
The phyCORE-LPC3250 belongs to PHYTEC’s phyCORE System on Module (SOM) family. The
phyCORE SOMs represent the continuous development of PHYTEC SOM technology. Like its mini-,
micro- and nanoMODUL predecessors, the phyCORE boards integrate all core elements of a
microcontroller system on a subminiature board and are designed in a manner that ensures their easy
expansion and embedding in peripheral hardware developments.
As independent research indicates that approximately 70% of all EMI (Electro Magnetic Interference)
problems stem from insufficient supply voltage grounding of electronic components in high frequency
environments, the phyCORE board design features an increased pin package. The increased pin package
allows dedication of approximately 20% of all connector pins on the phyCORE boards to ground. This
improves EMI and EMC characteristics and makes it easier to design complex applications meeting EMI
and EMC guidelines using phyCORE boards even in high noise environments.
phyCORE boards achieve their small size through modern SMD technology and multi-layer design. In
accordance with the complexity of the module, 0402-packaged SMD components and laser-drilled
Microvias are used on the boards, providing phyCORE users with access to this cutting edge
miniaturization technology for integration into their own design.
The phyCORE-LPC3250 is a sub-miniature (70 x 58 mm) insert-ready SOM populated with the NXP
LPC3250 ARM926EJ-S core processor. Its universal design enables its insertion in a wide range of
embedded applications. All processor signals and ports extend from the processor to high-density pitch
(0.635 mm) connectors aligning two sides of the board, allowing it to be plugged like a "big chip" into a
target application.
Precise specifications for the processor populating the board can be found in the applicable processor
User’s Manual or datasheet. The descriptions in this manual are based on the NXP Semiconductors
ARM9/LPC3250 processor. No description of compatible processor derivative functions is included, as
such functions are not relevant for the basic functioning of the phyCORE-LPC3250.
The phyCORE-LPC3250 offers the following features:
•Insert-ready, sub-miniature (70 x 58 mm) System on Module (SOM) subassembly in low EMI
design, achieved through advanced SMD technology
•Populated with the NXP LPC3250 processor (296-ball BGA packaging)
•Improved interference safety achieved through multi-layer PCB technology and dedicated ground
pins
•Controller signals and ports extend to two 160-pin high-density (0.635 mm) Molex connectors
aligning two sides of the board, enabling it to be plugged like a "big chip" into target application
•Max. 208 MHz core clock frequency
•Vector Floating Point coprocessor supporting single-precision and double-precision add, subtract,
multiply, divide, and multiply-accumulate at CPU clock speeds.
•Memory Management Unit (MMU), Memory and DMA controllers
•64 MB of external address space, with bus buffers to condition and protect signal load of
peripherals on the LPC3250 external memory bus
•1 to 8 MB of on-board NOR Flash operating at 1.8V or 3.15V
•16 to 128 MB of on-board NAND flash at 1.8V
•16 to 128MB of on-board 1.8V mobile SDRAM at 104 MHz
•32 KByte SPI bootable EEPROM
•USB OTG transceiver for embedded USB host/peripheral functionality
•6 rail voltage supervision with deep sleep supervision support
•On-board high efficiency switching regulators generating 1.8, 1.2, and an adjustable 0.9-1.2
voltage supplies
•Processor independent watchdog with disable, normal, and extended modes
Please note that all module connections are not to exceed their expressed maximum voltage or current.
Maximum signal input values are indicated in the corresponding controller manuals/data sheets. As
damage from improper connections varies according to use and application, it is the user's responsibility to
take appropriate safety measures to ensure that the module connections are protected from overloading
through connected peripherals.
All controller signals extend to surface mount technology (SMT) connectors (0.635 mm) lining two sides of
the module (referred to as the phyCORE-Connector). This allows the phyCORE-LPC3250 to be plugged
into any target application like a "big chip".
The numbering scheme for the phyCORE-Connector is based on a two dimensional matrix in which
column positions are identified by a letter and row position by a number. Pin 1A, for example, is always
located in the upper left hand corner of the matrix. The pin numbering values increase moving down on the
board. Lettering of the pin connector rows progresses alphabetically from left to right (refer to Figure 2-1).
The numbered matrix can be aligned with the phyCORE-LPC3250 (viewed from above; phyCOREConnector pointing down) or with the socket of the corresponding phyCORE Carrier Board/user target
circuitry. The upper left-hand corner of the numbered matrix (pin 1A) is thus covered with the corner of the
phyCORE-LPC3250 marked with a white triangle. The numbering scheme is always in relation to the PCB
as viewed from above, even if all connector contacts extend to the bottom of the module.
The numbering scheme is thus consistent for both the module’s phyCORE-Connector as well as mating
connectors on the phyCORE Carrier Board or target hardware, thereby considerably reducing the risk of
pin identification errors.
Since the pins are exactly defined according to the numbered matrix previously described, the phyCOREConnector is usually assigned a single designator for its position (X1 for example). In this manner the
phyCORE-Connector comprises a single, logical unit regardless of the fact that it could consist of more
than one physical socketed connector. The location of row 1 on the board is marked by a white triangle on
the PCB to allow easy identification.
Figure 2-1 illustrates the numbered matrix system. It shows a phyCORE-LPC3250 with SMT phyCORE-
Connectors on its underside (defined as dotted lines) mounted on a Carrier Board. In order to facilitate
understanding of the pin assignment scheme, the diagram presents a cross-view of the phyCORE module
showing these phyCORE-Connectors mounted on the underside of the module’s PCB.
Table 2-3. Pin Descriptions, phyCORE-Connector X2, Row C (Continued)
Pin # SignalI/OSLDescription
6CVBATI3.0V3.0V battery backup input for sleep conditions. This
supply must be present for deep sleep.
7CGND--Ground
8CN/C--Not connected
9C/SERVICEI3.15VµC signal /SERVICE/GPI_01. This signal has an inter-
nal 100k pull-up.
10C/RESET_SYSO3.15VOpen-drain system reset output with internal 10k pull-
up. Connect this to external 3.15V devices requiring a
power-up, power-fail, or power-down reset.
11C/RESOUTO1.8VµC generated reset output. Connect this to external
1.8V devices required a power-up, power-fail, or
power-down reset.
12CGND-0Ground
13C/RESET_BATO3.0VOpen-drain RTC and SDRAM power supply supervisor
reset output with internal 10k pull-up. Connect this to
external 3.0V devices requiring a power-up, power-fail,
or power-down reset. This signal is typically used with
external deep sleep control logic.
14CN/C--Not connected
15CN/C--Not connected
16CN/C--Not connected
17CGND--Ground
18C/FLASH_WPIVCC_EMBNOR flash write protect input with internal 10k pull-up.
Drive this signal low to prevent write access to the NOR
flash.
19CU5_RXI3.15VµC signal U5_RX
20CU5_TXO3.15VµC signal U5_TX
21CU5_RX_RS232I
6.4V
c
U5_RX converted to RS-232 levels
22CGND--Ground
23CU5_TX_RS232O
6.4V
c
U5_TX converted to RS-232 levels
24CU3_TXO3.15VµC signal U3_TX
25CU3_RX3.15VµC signal U3_RX
26CU3_CTSI3.15VµC signal U3_CTS/U2_HCTS
27CGND--Ground
28CU3_DCDI3.15VµC signal U3_DCD/GPI_05
29CU6_IRTXO3.15VµC signal U6_IRTX
30CI2C2_SCLO1.8VµC signal I2C2_SCL. This signal has an internal 2.2k
pull-up.
31CI2C1_SCLO3.15VµC signal I2C1_SCL. This signal has an internal 2.2k
Table 2-3. Pin Descriptions, phyCORE-Connector X2, Row C (Continued)
Pin # SignalI/OSLDescription
33CENET_LINKO3.15VEthernet link status output. Typically this is connected
to a link LED to indicate Ethernet link status.
34CENET_ACTIVITYO3.15VEthernet activity status output. Typically this is con-
nected to an activity LED to indicated Ethernet activity
status.
35CENET_RXNI
36CENET_RXPI
Note
Note
d
d
Ethernet negative differential receive input
Ethernet positive differential receive input
37CGND--Ground
38CGPIO_0I/O3.15VµC signal GPIO_00
39CGPI_3I1.8VµC signal GPI_03
40CGPI_19I3.15VµC signal GPI_19
41CGPO_0O1.8VµC signal GPO_00/TST_CLK1
42CGND--Ground
43CGPO_5O1.8VµC signal GPO_05
44CGPO_14O1.8VµC signal GPO_14
45CGPO_19O1.8VµC signal GPO_19. This signal defaults to NAND Flash
write protection control via jumper J5 with an internal
100k pull-up. See section 9.2 for details.
46CUSB_ADR/PSWI/O1.8VUSB OTG address select input/power supply control
output. On power-up this signal is latched as the lower
USB transceiver address bit and can be reconfigured
as a power supply control output to control an external
5.0V power supply in HOST mode. This signal has an
internal 100k pull-down.
47CGND--Ground
48CUSB_VBUSI/O5.0VUSB OTG VBUS input and output. This signal supplies
up to 8mA when operating as an embedded OTG Host.
49CSCK0I/O3.15VµC signal SCK0/SPI1_CLK. This signal is connected to
the on-board SPI bootable EEPROM.
50CMISO0I/O3.15VµC signal MISO0/SPI1_DATIN. This signal is con-
nected to the on-board SPI bootable EEPROM and has
an internal 10k pull-up.
51CSSEL0I/O3.15VµC signal SSEL0/GPIO_05. This signal is connected to
the on-board SPI bootable EEPROM and has an internal 10k pull-up.
73CSDIO_D1I/OVCC_SDIOSDIO controller data 1 input/output
74CSDIO_D2I/OVCC_SDIOSDIO controller data 2 input/output
75CSDIO_D4I/OVCC_SDIOSDIO controller data 4 input/output
76CSDIO_D7I/OVCC_SDIOSDIO controller data 7 input/output
77CAGND--Analog ground
78CTS_XOUTI/O3.15VµC signal TS_XOUT
79CADIN1I3.15VµC signal ADIN1
80CADIN0I3.15VµC signal ADIN0
a. See the NXP SDIO101 datasheet for details.
b. See the NXP SDIO101 datasheet for details.
c. Typical -- See ADM3307 datasheet for details.
d. See LAN8700I datasheet for details.
Table 2-4. Pin Descriptions, phyCORE-Connector X2, Row D
Pin # SignalI/OSLDescription
1DVCCI3.15V3.15V primary voltage supply input
2DVCCI3.15V3.15V primary voltage supply input
3DGND--Ground
4DVCC_AD_EXTI3.15VµC ADC power supply input
5DVCC_AD_EXTI3.15VµC ADC power supply input
6DN/C--Not connected
7DN/C--Not connected
8DWDII3.15VWatchdog input. Connect this pin to an applicable sig-
Table 2-4. Pin Descriptions, phyCORE-Connector X2, Row D (Continued)
Pin # SignalI/OSLDescription
9DGND--Ground
10D/RESINI
3.0V
a
or 3.15V
System reset input. Connect this pin to an open-drain
output and momentarily pull LOW to initiate a system
reset. Do not connect this pin to a push-pull output or
any other pull-up/pull-down circuitry.
11DN/C--Not connected
12DN/C--Not connected
13DN/C--Not connected
14DGND--Ground
15DN/C--Not connected
16DU1_RXI3.15VµC signal U1_RX/CAP1.0
17DU1_TXO3.15VµC signal U1_TX
18DGPO_20O1.8VµC signal GPO_20
19DGND--Ground
20D/RS232_ENI3.15VUART 5/UART 1 RS-232 transceiver enable input. This
signal has an internal 100k pull-down.
21DRS232_SDI3.15VUART 5/UART 1 RS-232 transceiver shut down input.
This signal has an internal 100k pull-down.
22DU1_RX_RS232I
23DU1_TX_RS232O
6.4V
6.4V
b
b
U1_RX converted to RS-232 levels
U1_TX converted to RS-232 levels
24DGND--Ground
25DU3_DSRI/O3.15VµC signal U3_DSR/U2_RX
26DU3_DTRO3.15VµC signal U3_DTR/U2_TX
27DU3_RTSO3.15VµC signal U3_RTS/U2_HRTS/GPO_23
28DU3_RII3.15VµC signal U3_RI/GPI_11
29DGND--Ground
30DU6_IRRXI3.15VµC signal U6_IRRX
31DI2C2_SDAI/O1.8VµC signal I2C2_SDA. This signal has an internal 2.2k
pull-up.
32DI2C1_SDAI/O3.15VµC signal I2C1_SDA. This signal has an internal 2.2k
pull-up.
33D/RTC_INTO3.0VOff-chip Real Time Clock interrupt alarm open-drain
output. This pin has an optional 100k internal pull-up.[3]
34DGND--Ground
35DENET_TXNO
36DENET_TXPO
37DENET_CLKENI3.15VEthernet clock enable. This pin has an internal 100k
Table 2-4. Pin Descriptions, phyCORE-Connector X2, Row D (Continued)
Pin # SignalI/OSLDescription
71DSDIO_POW0OVCC_SDIOSDIO controller power control signal 1 output
72DSDIO_CLKOVCC_SDIOSDIO controller clock output
73DSDIO_D0I/OVCC_SDIOSDIO controller data 0 input/output
74DGND--Ground
75DSDIO_D3I/OVCC_SDIOSDIO controller data 3 input/output
76DSDIO_D5I/OVCC_SDIOSDIO controller data 5 input/output
77DSDIO_D6I/OVCC_SDIOSDIO controller data 6 input/output
78DTS_YOUTI/O-µC signal TS_YOUT
79DAGND--Analog ground
80DADIN2I3.15VµC signal ADIN2
a. 3.0V is the standard phyCORE-LPC3250 SOM configuration.
b. Typical -- see ADM3307 datasheet for details.
c. See the LAN8700I datasheet for details.
d. See the ISP1301 datasheet for details.
For configuration purposes, the phyCORE-LPC3250 has 24 solder jumpers, some of which have been
installed prior to delivery. Figure 3-1 and Figure 3-2 indicate the location of the solder jumpers on the
board. There are 11 solder jumpers located on the top side of the module (opposite side of connectors)
and 13 solder jumpers on the bottom side.
If manual jumper modification is required be sure to pay special attention to the "TYPE" column to ensure
you are using the correct type of jumper (0 Ohms, 10k Ohms, etc…). All jumpers are 0805 package with a
1/8W or better power rating.
Three and four position jumpers have pin 1 marked with a GREEN pad.
NAND Flash write protected during power-up, power-fail, and
power-down events by the controller /RESOUT signal.
NAND Flash permanently write protected.
NAND Flash write protection controlled via GPO_19.
NAND Flash permanently write enabled.
Activating /RESIN produces a system /RESET_SYS event.
Activating /RESIN produces a system /RESET_SYS and a /
RESET_BAT event.
Ethernet PHY operation MODE0 bit = 1.
Ethernet PHY operation MODE0 bit = 0.
Ethernet PHY operation MODE1 bit = 1.
Ethernet PHY operation MODE1 bit = 0.
Ethernet PHY operation MODE2 bit = 1.
Ethernet PHY operation MODE2 bit = 0.
µC signal SSEL0 disconnected from on-board SPI EEPROM /CS0
input.
µC signal SSEL0 connected to on-board SPI EEPROM /CS0
input.
Watchdog extended mode selected. Timeout period ~6s.
Watchdog normal mode selected. Timeout period ~12ms.
External watchdog reset forces a system wide reset and sleep
reset.
External watchdog reset forces a system wide reset.
External memory bus voltage set to 1.8V.
External memory bus voltage set to 3.15V.
Voltage regulator U22 disconnected from VCC_RTC.
Voltage regulator U22 supplies VCC_RTC power.
Voltage regulator U22 disconnected from VCC_SDRAM.
Voltage regulator U22 supplies VCC_SDRAM power.
Voltage regulator U23 disconnected from VCC_SDRAM.
The phyCORE-LPC3250 operates off of four separate power supply input domains. For systems that do
not required maximum flexibility it is possible to operate the phyCORE-LPC3250 off of a single power
supply voltage.
The following sections of this chapter discuss the primary power pins on the phyCORE-Connector X2 in
detail.
4.1 Primary System Power (VCC)
The phyCORE-LPC3250 operates off of a primary voltage supply with a nominal value of 3.15V. On-board
switching regulators generate the 1.8V, and 1.2V, and adjustable 0.9-1.2V voltage supplies required by the
LPC3250 MCU and on-board components from the primary 3.15V supplied to the SOM.
For proper operation the phyCORE-LPC3250 must be supplied with a voltage source of 3.15V ± 0.1V at
the VCC pins on the phyCORE-Connector X2. See Table 2-1 for VCC pin locations. See Chapter 14 for
current requirements.
Connect all +3.15V VCC input pins to your power supply and at least the matching number of GND pins
neighboring the +3.15V pins.
CAUTION:
As a general design rule we recommend connecting all GND pins neighboring signals which are being
used in the application circuitry. For maximum EMI performance all GND pins should be connected to a
solid ground plane.
4.2 Secondary Battery Power (VBAT)
For applications requiring a low power deep sleep mode a secondary battery sleep supply with a nominal
value of 3.0V is required. The battery supply powers the SDRAM and RTCs during a sleep condition,
allowing primary system power (VCC) to be removed.
For deep sleep operation the phyCORE-LPC3250 must be supplied with a secondary voltage source of
3.0V ± 0.1V at the VBAT pin on the phyCORE-Connector X2. See Table 2-1 for the VBAT pin location. See
Chapter 14 for current requirements.
Applications not requiring a sleep mode can connect the VBAT pin to the primary system power supply
(VCC = 3.15V).
4.3 Analog-to-Digital Converter Power (VCC_AD_EXT)
The LPC3250 Analog-to-Digital converter power domain pins are brought out to the phyCORE-Connector
X2 for an optional external filtered power supply. See Table 2-1 for the VCC_AD_EXT pin location. See the
NXP LPC3250 datasheet for permissible input voltage ranges (2.7V to 3.3V as of the printing of this
manual).
In general the VCC_AD_EXT pins will be connected to the primary VCC = 3.15V supply, requiring no
special circuitry. The phyCORE-LPC3250 Carrier Board connects the VCC_AD_EXT pins through a 1R/
4.7uF filter network from the primary VCC = 3.15V supply. Refer to the phyCORE-LPC3250 Carrier Board
schematics for details.
The on-board SDIO controller is capable of a configurable interface voltage to meet the demands of the
variety of SDIO devices with varying power requirements. In addition the SDIO controller is capable of
switching between a high power and low power mode on-the-fly to optimize dynamic power consumption.
The SDIO controller interface voltage is powered and set via the VCC_SDIO pins on the phyCOREConnector X2. The high/low power switching is controlled via the SDIO_POW0 and SDIO_POW1 pins on
the phyCORE-Connector X2. See the NXP SDIO101 datasheet for details on these power mode control
pins. See Table 2-1 for the locations of the applicable SDIO power and control pins.
For applications requiring an adjustable SDIO supply voltage the VCC_SDIO pins must be supplied with a
voltage of 2.25-3.6V
1
. See Chapter 14 for current requirements. See the phyCORE-LPC3250 Carrier
Board schematics for example adjustable supply circuitry. For SDIO applications which can operate off of
3.15V the VCC_SDIO pins can be connected directly to the VCC power supply and the SDIO_POW0/1
pins can be left unconnected.
4.5 On-board Voltage Regulators
The phyCORE-LPC3250 provides three on-board switching regulators to source the 1.2V, 1.8V, and
adjustable 0.9-1.2V voltages required by the processor and on-board components. Figure 4-1 presents a
graphical depiction of the powering scheme. The jumpers in blue are by default populated, while the
jumpers in white are unpopulated. By default U27 powers the VCC_CORE rail with an adjustable supply,
U22 powers the VCC_RTC and VCC_SDRAM rails, and U23 powers the VCC_1V2 and VCC_1V8 rails.
Notice that U22 generates 1.2V and 1.8V just as does U23. The reason for this is that U22 continues to
power the RTC and SDRAM subsystems via backup battery during a sleep mode. See Chapter 5 for
details.
To reduce system costs U27 and U22 can be removed. To supply the power lost by the removal of these
two regulators J26, J27, and J24 must be closed. Figure 4-1 depicts the standard default configuration, but
custom configurations can also be ordered. If your system does not require an adjustable core voltage to
periodically lower core power consumption while keeping the system powered then U27 can be removed
and J27 can be closed (note that the core is fixed at 1.2V in this case). If your system is not power
conscious and does not need to enter a sleep mode during moments of processor inactivity to conserve
power then U23 can be removed and J26 and J24 can be closed. This multi regulator + jumper approach
provide cost and system requirement flexibility.
The following sections go into detail about each switching regulator and any associated configuration
jumpers.
The dual output switching regulator located at U23 generates the 1.2V and 1.8V core and peripheral
supplies required by system components from the primary VCC = 3.15V board supply. Various jumpers
have been provided as current measurement access points on the outputs of both of these supplies. Table
4-1 provides a summary of the jumpers and their operation. See Chapter 4.5.4 for current measurement
techniques with a precision shunt resistor.
Table 4-1. U23 1.2V/1.8V Primary Voltage Regulator Jumper Settings
JType Setting Description
J24 0ROpen
J25 0ROpen
J26 0ROpen
J27 0ROpen
J28 0ROpen
Closed
Closed
Closed
Closed
Closed
Voltage regulator U23 disconnected from VCC_SDRAM.
Voltage regulator U23 supplies VCC_SDRAM power. Do not close this unless
U22 is unpopulated.
Voltage regulator U23 disconnected from VCC_1V8.
Voltage regulator U23 disconnected from VCC_1V8.
Voltage regulator U23 disconnected from VCC_RTC.
Voltage regulator U23 supplies VCC_RTC power. Do not close this unless U22
is unpopulated.
Voltage regulator U23 disconnected from VCC_CORE.
Voltage regulator U23 supplies VCC_CORE power. Do not close this unless
U22 is unpopulated.
The single output switching regulator located at U27 generates the adjustable 0.9V to 1.2V core supply to
the processor from the primary VCC = 3.15V board supply. The regulator's output voltage is controlled by
the processor's HIGHCORE signal (labeled as net LCD17). To set the core voltage to 0.9V set the
HIGHCORE signal HIGH. To set the core voltage to 1.2V set the HIGHCORE signal LOW. The
HIGHCORE signal can be automatically managed or manually controlled via the LPC3250 power
management registers. See the LPC3250 User Manual for details.
Because the HIGHCORE signal is multiplexed with other peripherals, jumper J30 has been provided to
allow disconnection of the HIGHCORE signal from controlling the core regulator output voltage. When J30
is disconnected the core regulator is fixed at 1.2V. This jumper is provided as a prototyping convenience.
In practice an unneeded additional cost would be added by simply ordering a SOM configuration in which
J30 is removed. If J30 is removed then the regulator is fixed at 1.2V and therefore an adjustable supply is
no longer needed and instead can be satisfied by the dual 1.2V/1.8V regulator U23 through additional
jumper configurations. A SOM without the need for an adjustable core would have U27 removed and J27
closed.
Output jumper J29 has been provided as current measurement access points for this supply. See Chapter
4.5.4 for current measurement techniques with a precision shunt resistor.
4.5.3 SDRAM and RTC Supplies (U22)
The dual output switching regulator located at U23 generates the 1.2V and 1.8V RTC and SDRAM
supplies required by the RTC and SDRAM. U23 gets its input power from the output of the battery switch
located at U19. The battery switch is responsible for connecting VCC to the input of U23 during normal
operating conditions (VCC is present) and VBAT to the input of U23 during sleep operations (VCC is shut
down). This switchover between VCC and VBAT is automatic. Output jumpers have been provided as
current measurement access points for both of these supplies. Table 4-2 provides a summary of the
jumpers and their operation. See Chapter 4.5.4 for current measurement techniques with a precision shunt
resistor.
Table 4-2. U22 RTC/SDRAM Voltage Regulator Jumper Settings
JType Setting Description
J22 0ROpen
Closed
J23 0ROpen
Closed
Voltage regulator U22 disconnected from VCC_SDRAM.
Voltage regulator U22 supplies VCC_SDRAM power.
Voltage regulator U22 disconnected from VCC_RTC.
Voltage regulator U22 supplies VCC_RTC power.
4.5.4 Selecting Shunt Resistors for Current Measurements
To make current measurements the 0 Ohm resistors populating the regulator output jumpers should be
replaced by precision shunt resistors allowing the current draw to be calculated from the voltage
measurement taken across the shunt resistor. When selecting a shunt resistor it is desirable to select a
resistor large enough to give a voltage measurement that is not overtaken by noise. However, a larger
shunt resistor means a larger voltage drop across the shunt resulting in a smaller output voltage. The
output voltage after the shunt should be kept above the reset threshold. If the shunt resistor is too large the
voltage at the output could be below the supervisor reset threshold and force the system into reset. A good
starting place is a 0.025 Ohm precision shunt in a 0805 package.
The phyCORE-LPC3250 comes equipped with two triple voltage supervisor IC's located at U16 and U17.
These voltage supervisors are responsible for monitoring all on-board supply voltages (with the exception
of the adjustable core supply voltage which is not monitored) and issuing a system reset during a powerup, power-fail, or power-down event.
U16 is the primary system supervisor which is responsible for monitoring the primary system supply
voltage VCC = 3.15V, the fixed VCC_1V8 = 1.8V peripheral supply voltage, and the fixed VCC_1V2 = 1.2V
core supply voltage. When any of the three supplies dip below their nominal reset threshold voltages for a
predetermined amount of time the /RESET_SYS signal is asserted LOW for the duration of the power fail
event and is held low for an additional 200ms
thresholds for U16 are set at:
Table 4-3. Primary System Supervisor Reset Thresholds
Supply Voltage Nominal Reset Threshold
VCC (3.15V)3.0V
VCC_1V8 (1.8V)1.7V
VCC_1V2 (1.2V)1.1V
1
after the power fail event has cleared. The nominal reset
U17 is the sleep mode supervisor and is responsible for monitoring the VBAT = 3.0V input voltage, the
VCC_SDRAM = 1.8V SDRAM supply voltage, and the VCC_RTC = 1.2V supply voltage. When any of the
three supplies dip below their nominal reset threshold voltages for a predetermined amount of time the /
RESET_BAT and /RESET_SYS signals are asserted LOW for the duration of the power fail event and are
held low for an additional 200ms
1
after the power fail event has cleared. The nominal reset thresholds for
U17 are set at:
Table 4-4. Sleep System Supervisor Reset Thresholds
Supply VoltageNominal Reset Threshold
VBAT (3.0V)2.8V
VCC_SDRAM (1.8V) 1.7V
VCC_RTC (1.2V)1.1V
The dual supervisor approach allows the creation of two separate reset signals: the system reset signal /
RESET_SYS, and the sleep reset signal /RESET_BAT. The primary system supervisor U16 is capable of
issuing a system reset via the /RESET_SYS signal while the sleep supervisor U17 is capable of issuing a
sleep reset via the /RESET_BAT signal in addition to a system reset via the /RESET_SYS signal. This
method allows: (1) the processor to always be held in reset (via /RESET_SYS) when main system power is
removed and (2) the detection of a power fail event during a sleep condition via the /RESET_BAT signal.
Condition (1) is required any time power is reapplied to the processor to ensure proper system startup after
the reapplication of power. Condition (2) allows for additional external deep sleep/power control logic to be
reset during a power fail event on the battery supplies (VBAT, VCC_RTC, or VCC_SDRAM). Since the
LPC3250 does not provide sleep registers (however the on-chip RTC SRAM could potentially double for
this) that are powered during a sleep condition the LPC3250 must rely on another method of determining it
was in a sleep state upon a wake event. This could be done via writing a special code in the RTC scratch
pad SRAM before entering sleep (a key value that indicates you were in sleep), however, a momentary fail
on the supply could potentially corrupt SRAM in an area that did not affect the key or corrupt sections of
SDRAM which are undetectable. In this instance the system would resume from a sleep condition where
1. Typical reset period. See Maxim IC MAX6710 datasheet for details.
data was corrupted, but have no method of determining so, resulting in a possible processor lockup. To
prevent this from happening external sleep circuitry should be used which remembers the sleep state and
is reset via the /RESET_BAT signal should a sleep supply (VBAT, VCC_RTC, VCC_SDRAM) fail.
The phyCORE-LPC3250 was designed to support a "deep sleep" mode where all primary system power is
removed, leaving only a battery backup supply powering essential sleep functions. This mode was
designed for ultra low power to extend primary system battery life in power critical applications. Note that
this mode assumes the use of a battery as the primary system power source, but is not required. A wall
adapter, or other power source can also be used but it is more typical that low power consumption is
required when operating the system from a battery supply to maximize battery life.
Figure 5-1 depicts a typical sleep enabled powering system where the entire system is powered from a
battery. The battery is then regulated to 3.15V, 3.3V, and 3.0V to satisfy the necessary power inputs to the
phyCORE-LPC3250. Control logic is responsible for enabling and disabling primary system power (VCC
and VCC_SDIO), while the secondary battery voltage VDS remains continuously.
Under normal operating conditions S1 will be closed and the system will be powered up. The user will
initiate a sleep event by pressing the Power Button. The phyCORE-LPC3250 will detect the press of the
power button and begin a sleep sequence in software preparing the system for the removal of primary
power. The last step in the sleep sequence will be the phyCORE-LPC3250 signaling the Control Logic to
shut down the external power supplies by opening switch S1. The only parts of the system that remain
powered during a deep sleep condition are the on-board SDRAM, on-chip RTC, off-chip RTC, and sleep
Control Logic. All four subsystems are powered by the 3.0V supply during a sleep event, drawing minimal
power.
Once in sleep there are three different methods to wake the system and resume normal operation. These
methods are: (1) an on-chip RTC alarm event via the ONSW signal or (2) an off-chip RTC alarm event via
the /RTC_INT signal or (3) a user initiated wake event via the Power Button. Any three of these signals can
trigger the Control Logic to reapply power to the system via closing S1. In addition to power control, the
Control Logic also remembers the sleep state. Upon system reboot during a wake event the processor can
check the sleep state to determine if the system should have a fresh boot or take the necessary steps to
resume from a sleep condition. The Control Logic sleep state can only be cleared by either the processor,
or a power fail event during sleep via the /RESET_BAT signal. In this manor should the power fail during a
sleep event the processor can begin a normal boot sequence on reapplication of power due to the possibly
corrupted memory data caused by the power fail condition.
The on-board battery switch U19 is responsible for automatically powering the SDRAM and RTC
subsystems from the VBAT input when VCC is lost. Under normal operating conditions (when VCC is
present) the RTC and SDRAM domains are powered by the VCC supply. See the Texas Instruments
TPS2115 battery switch datasheet for more details.
For a detailed explanation of the sleep control circuitry on the phyCORE-LPC3250 Carrier Board see
An external RTC (RTC-8564JE) located at U26 has been provided in addition to the LPC3250 on-chip
RTC. This RTC provides a secondary time keeping source, along with a secondary alarm mechanism to
the processor via the /RTC_INT signal. By default the /RTC_INT signal is used on the phyCORE-LPC3250
Carrier Board to wake-up the power system during a deep sleep.
The RTC is interfaced to the processor via the I²C1 port. The default I²C address of the device is binary
1010 001x, where the 'x' bit is the read/write operation bit.
The RTC is automatically powered via the VBAT power input during a sleep condition. Jumper J32 is
provided to configure the power source when the phyCORE-LPC3250 is ordered with a custom power
configuration. In this configuration the on-chip RTC and SDRAM do not need to be powered during sleep,
and only the external RTC is powered. This allows a reduced cost configuration with the removal of the
dual switching regulator U22 and battery switch IC U19. This is also the most power efficient method of
putting the system to sleep while allowing the external RTC to reawake the system at a later time. By
default J32 is set to the 1+2 position, connecting the RTC power to the VCC_BATT signal, used during the
more complex sleep mode that keeps the on-chip RTC and SDRAM alive. Alternatively this jumper can be
set to the 2+3 position for the ultra low power sleep mode where U22 and U19 are removed.
An external Maxim MAX6301 watchdog located at U18 has been provided as a processor independent
means of system recovery in the event of a lockup. By default the watchdog is disabled. To enable the
watchdog circuit the WDI input at the phyCORE-Connector (see Table 2-1) must be taken out of Hi-Z.
When the phyCORE-LPC3250 SOM is mounted on the phyCORE-LPC3250 Carrier Board the watchdog
can be taken out of Hi-Z by closing an applicable jumper. See the phyCORE-LPC3250 Carrier Board
Chapter 38 for details on the jumper and associated settings. When closed processor signal GPO_20 is
connected to the WDI input of the watchdog circuit. Since GPO_20 is a push-pull output of the processor,
this connection effectively takes the WDI input out of Hi-Z and enables the watchdog. After the watchdog's
internal timer expires the open collector /RES output of the IC is pulled LOW. Jumper J19 connects the
watchdog IC's /RES output to either the /RESET_SYS signal, or the /RESET_BAT signal. By default J19 is
set to the 2+3 position, connecting the /RES output to the /RESET_SYS signal. Alternatively this jumper
can be set to the 1+2 position, connecting the /RES output to the /RESET_BAT signal.
Once enabled the watchdog WDI input must be toggled before the internal timeout period expires to
prevent the /RES output from going active. The nominal watchdog timeout period is set to 6 seconds and
can be adjusted down to 12 milliseconds by closing jumper J17. Leave J17 open to keep the watchdog
timeout period at 6 seconds.
The WDI input does not need to be pulsed with a HIGH or LOW going pulse, but instead the WDI input just
needs to change states before the timeout period expires.
Typically the processor will use an available timer interrupt to change the state of the WDI input (via
GPO_20 when used on the phyCORE-LPC3250 Carrier Board) before the watchdog timeout period
expires. In this manor should the processor lock up, the WDI input will no longer be toggled, the watchdog
timeout period will expire, and the watchdog will assert the /RES output causing a system reset restoring
processor operation.
Part I, Chapter 8: System Configuration and Booting
L-714e_1
8 System Configuration and Booting
For operation of the phyCORE-LPC3250 several parts of the system should be initialized. Although very
little initialization needs to take place for the most basic operation, it is typical that the following interfaces
will be initialized:
1. Clocking and power
2. SDRAM
3. Boot map
Clocking and Power
After a reboot the processor is operating off of the main crystal at 13.0MHz. While sufficient for small
applications, it is most likely that at some point the need for full processor frequency will arise. To initialize
the primary clocking and power control the following registers must be set:
1. HCLKDIV_CTRL
2. HCLKPLL_CTRL
3. PWR_CTRL
Please refer to the "Clocking and Power Control" chapter of the NXP Semiconductors LPC3250 hardware
manual for details on setting these registers. Additionally you may refer to the example code provided on
the PHYTEC Spectrum CD.
SDRAM
After a reboot the SDRAM interface is reset and must be initialized. The initialization procedure involves
initializing two primary interfaces: 1) the LPC3250 SDRAM controller, and 2) the SDRAM itself.
Initialization of the LPC3250 SDRAM controller sets up the processor with the proper timing and size
configuration values required to interfaces the external SDRAM. The initialization of the SDRAM sets up
the "mode" and "extended mode" registers on the SDRAM with information such as burst length, burst
type, CAS latency, driver strength, etc... Example SDRAM initialization is code provided on the PHYTEC
Spectrum CD.
Boot Map
By default after a reboot the LPC3250 on-chip boot ROM is mapped to address 0x0000 0000 and internal
RAM (IRAM) is mapped to 0x0800 0000. The BOOT_MAP register controls remapping the IRAM to
address 0x0000 0000. Remapping of IRAM is required for interrupts to function correctly. The beginning of
IRAM is reserved for the interrupt vector table, and without proper remapping an interrupt will cause the
processor to jump to the on-chip boot ROM. Therefore one of the very first initialization steps should be to
set this register to 1 to remap IRAM to 0x0000 0000.
8.1 Boot Process and Boot Modes
The boot process for the LPC3250 is a multi-staged effort involving one or more boot loaders. At the very
least after a reset the LPC3250 on-chip boot ROM will execute either (1) the UART5 boot mode, or (2) the
normal boot mode. The boot mode is controlled by strapping the SERVICE_N signal of the processor
HIGH or LOW after a reset. On the phyCORE-LPC3250 this signal is labeled as /SERVICE. An on-board
pull-up resistor pulls this signal HIGH. However, when installed on the phyCORE-LPC3250 Carrier Board
the default boot configuration jumper connects the /SERVICE signal to GND.
In boot mode (1) the boot ROM attempts to boot code loaded over UART5 with a simple boot protocol. In
boot mode (2) the boot ROM first attempts to boot from the SPI port, followed by the external memory bus,
and finally from NAND Flash. Details of the boot protocol for each bootable source can be found in the
LPC3250 User's Manual.
Part I, Chapter 8: System Configuration and Booting
L-714e_1
The most typical boot configuration will boot from NAND Flash. In this boot mode the boot ROM attempts
to copy boot code from block 0 or block 1 (block 1 if block 0 is bad) into IRAM and executes it. Since the
boot ROM can only copy code from block 0 or block 1, this limits the size of the secondary boot loader to
be constricted to stay within a single block in NAND Flash. For the phyCORE-LPC3250 NAND Flash this
limit is 16kBytes. In practice this is limited to 15.5kBytes for reasons which will become apparent in the
sections that follow.
The secondary boot loader is responsible for loading and executing a third level boot loader or application
code, depending on the complexity of the software design. For bare-metal applications the secondary boot
loader will likely suffice to load and execute the application. For operating systems the secondary boot
loader will likely load a more robust, feature rich boot loader such as Das U-Boot, or E-Boot.
The job of a basic secondary boot loader can be summarized as the following:
1. Initialize the Clocking and Power (bump the core up to 208MHz)
2. Initialize the SDRAM
3. Copy the remaining code from NAND Flash into SDRAM
4. Transfer execution to SDRAM
Before covering the structure of the secondary boot loader and application code in NAND Flash, a short
description of the structure of the external SLC NAND Flash device used on the phyCORE-LPC3250 is
presented.
The external SLC NAND Flash used on the phyCORE-LPC3250 is a "small page" device consisting of
"blocks" and "pages" of data. The NAND Flash is divided into blocks which are 16kB in size. Each block
consists of 32 pages which are 512 bytes in size + 16 bytes of "spare" area. The spare area is used to (1)
store bad block information, and (2) store error correction data. Unlike NOR Flash, NAND Flash can
contain "bad blocks" within the Flash device. These are blocks which 1 or more bits within the block can no
longer be reliably written and read. Therefore the entire block is marked bad and should not be used.
NAND Flash devices are shipped with BLOCK 0 guaranteed to be a good block. Each individual NAND
device may contain 0 or more bad blocks from the manufacturer, and more bad blocks may develop over
time through write/erase operations. Bad blocks in new NAND devices are marked by the manufacturer by
writing a value other than 0xFF to the 6th byte of the spare area of the first page of each block. For
example, if the 6th byte of the spare area of block 12, page 0 did not contain 0xFF, this would indicate it is
a bad block. Figure 8-1 shows a graphical representation of the organization of the NAND Flash structure.
Part I, Chapter 8: System Configuration and Booting
Fig. 8-1. Small Page SLC NAND Flash Structure
L-714e_1
In addition to the spare area being used to mark bad blocks, it is also used by the LPC3250 NAND Flash
controllers to store error correction code (ECC) data. With this technique an integrity check between the
data within the page and the ECC can be made to determine if the data is good (given that bad blocks can
develop over time).
Now that a better understanding of the NAND structure has been presented a detailing of the code
structure which resides in NAND Flash can be presented.
The code in NAND Flash will have one of three structures: (1) application that is 15.5kB in size or less, (2)
boot loader + application that is 256kB in size or less, or (3) boot loader + application that exceeds 256kB
in size.
In (1) the code is small enough to fit and execute in IRAM and remains in block 0. It must fit in block 0
because the LPC3250 boot loader ROM will only load data from block 0.
In (2) the code exceeds block 0 in size and must occupy more NAND Flash. In this case a secondary boot
loader is needed to load the application code beyond block 0 into IRAM and execute it. The secondary
boot loader is placed in block 0. The application is placed in block 1 or beyond.
In (3) the code exceeds IRAM size and must be placed in SDRAM. In this case a secondary boot loader is
placed in block 0 and is responsible for initializing SDRAM, loading the application code beyond block 0
into SDRAM, and then transferring execution to SDRAM.
In all three instances above block 0 page 0 always contains special data. It is for this reason that the boot
loader is restricted to 15.5kB in size instead of 16kB. The block 0/page 0 data consists of the ICR, size
information, and block 0 bad block information. This information is needed by the LPC3250 boot ROM to
find out what type of NAND Flash the controller will be interfacing, how much code to copy from NAND
Part I, Chapter 8: System Configuration and Booting
Flash into IRAM, and if this block is a bad block and the boot information is contained in block 1 instead.
See the NXP Semiconductors LPC3250 hardware manual for a detailed explanation of the required data in
block 0 page 0 of the NAND Flash.
Typically applications will require (3) above. In this case the boot process becomes:
1. The controller is reset.
2. The LPC3250 boot loader ROM executes and loads the secondary boot loader code located in
block 0 of the NAND Flash into IRAM and transfers execution to it.
3. The secondary boot loader initializes the clocks and SDRAM.
4. The secondary boot loader copies the application code from NAND Flash starting at block 1 (or
beyond) into SDRAM and transfers execution to it.
At this point the primary application is running. For most applications not involving an operating system this
is all that is needed. It is possible that this application could be yet another boot loader that is responsible
for booting an operating system such as Linux or WinCE.
To simplify and enhance the boot process the phyCORE-LPC3250 comes pre-flashed with a special boot
loader written by NXP. This boot loader, called the "Stage 1 Loader" is discussed in more detail in the
follow section.
L-714e_1
8.1 Stage 1 Loader
The Stage 1 Loader (S1L) is a robust third level boot loader written by NXP Semiconductor to simplify and
enhance the LPC3250 booting procedure. The S1L is feature rich with the ability to configure clocking,
virtual memory mapping, data and instruction caches, the ability to access NAND flash, and the ability to
boot applications/images from the NAND flash, SD Card, or serial port to name a few of the features the
S1L provides.
In general the S1L is used to execute applications or, a 4th level boot loader such as Das U-Boot or EBoot. The PHYTEC Rapid Development Kit comes with a pre-loaded SD Card containing demo
applications, a Windows CE image, and a Linux image to easy facilitate the evaluation of each operating
system as well as stand alone "bare metal" applications without the need for a debugger/JTAG probe.
Kickstart Loader
As noted in the previous section the secondary boot loader residing in NAND flash must be 15.5kB in size
or less in order for the LPC3250 on-chip boot ROM to successfully load and execute the image. The robust
functionality that the S1L provides cannot be packed into such a small Flash footprint, and instead exceeds
the 15.5kB required for a secondary boot loader on the LPC3250. To get around this limitation the S1L is
loaded as 3rd level boot loader by a small, compact secondary boot loader called the Kickstart Loader. The
Kickstart Loader written by NXP fits within the 15.5kB constraints of the boot ROM and is executed
immediately after a processor reset (provided UART5 booting isn't enabled or successful, and SPI and
EMC booting fail).
Once the Kickstart Loader is executing it relocates itself to the top 16kB of IRAM, leaving 240KB of IRAM
space left (starting at address 0x0) for an application, or 3rd level boot loader. The Kickstart Loader then
loads code starting at Flash block 1 into IRAM and transfers execution to it.
On the phyCORE-LPC3250 this application/3rd level boot loader is the S1L. The S1L, once executed,
provides a menu/configuration interface via UART5 of the processor.
Part I, Chapter 8: System Configuration and Booting
L-714e_1
To access the Stage 1 Loader connect your PC to the bottom DB-9 female RS-232 connector on the
phyCORE-LPC3250 Carrier Board at connector P1. Configure a terminal communications application for
115200,8,n,1, no hardware flow control on your PC. Press the system reset button S1 on the Carrier board
to force a system reset. The terminal window should begin display S1L output. Press any key to stop the
auto boot procedure (if one is configured, otherwise the S1L will go to the phy3250> prompt by itself) and
come to the phy3250> prompt. Type help menu to get a list of commands. For further instructions on using
the S1L and executing demo applications, refer to the appropriate Quickstart guides provided on the
PHYTEC Spectrum CD.
Boot Sequence
1. The boot sequence with the Kickstart Loader and Stage 1 Loader is as follows:
2. Controller is reset
3. On-chip boot ROM executes and loads the Kickstart Loader from NAND block 0 into IRAM at
address 0 and executes it
4. Kickstart Loader relocates itself to the upper 16kB of IRAM
5. Kickstart Loader begins reading the NAND Flash at block 1 and loading code (in this case, the
Stage 1 Loader) starting at address 0x0 in IRAM. The first page of block 1 contains the size of the
code to be loaded.
6. The Kickstart transfers execution to the loaded application code (S1L) at address 0
7. The Stage 1 Loader executes and either stops at the S1L prompt, or continues to boot from the
terminal interface, SD card, or NAND flash depending on the auto boot configuration.
Where To Find More Information
In addition to the help menus NXP has published a document detailing the Kickstart Loader and the Stage
1 Loader. Please refer to this document, located on your PHYTEC Spectrum CD in PHYTEC\phyCORE-LPC3250\Documentation\Stage1 Loader, for more information regarding these boot loaders.
The phyCORE-LPC3250 provides four types of on-board memory:
1. SDR SDRAM (U10/U11):from 16MB to 128MB
2. NOR Flash (U12/U13):from 1MB to 8MB
3. NAND Flash (U8):from 16MB to 128MB
4. EEPROM (U9):from 1KB to 32KB
The following sections of this chapter detail each memory type used on the phyCORE-LPC3250 SOM.
9.1 SDRAM (U10, U11)
The phyCORE-LPC3250 comes pre-configured with 16, 32 or 64MB of 133MHz SDR SDRAM configured
for 32-bit access using two 16-bit wide RAM chips at U10 and U11.
The LPC3250 is capable of addressing a single RAM bank located at memory address 0x8000 0000 and
extending to 0x9FFF FFFF via the /DYCS0 signal. It should be noted that this is beyond what the
phyCORE-LPC3250 supplies for on-board memory. Refer to Table 9-1 for permissible SDRAM memory
access ranges.
The second SDRAM memory bank located on /DYSC1 is not used on the phyCORE-LPC3250. Accesses
to this region of memory should not be performed.
9.2 NAND Flash (U8)
The NAND memory is comprised of a single 16MB to 128MB chip located at U8 and is interfaced via the
LPC3250 NAND memory bus. Write protection control of the NAND device is configurable via jumper J5.
Table 9-2 lists the various NAND Flash write protection control options, including the default setting on the
kit version of the phyCORE-LPC3250 SOM.
Table 9-2. NAND Flash Write Protection via Jumper J5
JType Setting Description
J5 0R1+2
Open
NAND Flash write protected during power-up, power-fail, and power-down events
by the controller /RESOUT signal. Use this setting to protect your flash from accidental writes/erases during power interrupt events if software control over write
protect is not needed.
NAND Flash permanently write protected. Use this setting if your NAND flash is
2+3
pre-programmed and you wish to prevent write/erase access to the flash.
NAND Flash write protection controlled via GPO_19. Use this setting for
2+4
software controlled write protection.
NAND Flash permanently write enabled. Use this setting if you wish to permanently have write access to the device.
Refer to the NXP Common Driver Library (CDL) provided on the PHYTEC Spectrum CD for code
examples for accessing the NAND Flash.
It should be noted that the NAND Flash has a dedicated memory bus on the LPC3250 to the NAND
device. The NAND Flash signals are therefore not made available at the phyCORE-Connector X2.
L-714e_1
9.3 NOR Flash (U12, U13)
The phyCORE-LPC3250 comes pre-configured with 1 to 8MB of NOR Flash configured for 32-bit access
using two 16-bit wide Flash chips at U12 and U13. The NOR Flash chips occupy the first external memory
bank located on chip select 0 (/CS0), and are interfaced to the processor over the buffered external
memory bus. Table 9-3 provides a list of valid memory ranges for varying NOR Flash densities.
The NOR Flash is automatically write protected during power-up, power-fail, and power-down events with
the /RESET_EMB signal connected to the flash reset (/RP) input. In addition a /FLASH_WP signal is
extended out to the phyCORE-Connector X2-18C and connects to the flash write protect input (/WP). This
signal has an on-board 10k pull-up resistor. Pull this signal down to ground using an open-drain/opencollector output to write protect the device. This feature may be useful if software write protection is
desired.
The NOR Flash devices populating the default phyCORE-LPC3250 configuration operate at 3.15V. If
desired, low power 1.8V NOR Flash can also populate the board. In this configuration the buffered memory
bus voltage select must be set for 1.8V. All other devices connected to the external memory bus must also
support 1.8V. See Chapter 13 to configure the buffered memory bus voltage.
9.4 NOR vs. NAND
Typically both NOR and NAND Flash are not needed in the end system. The system designer will choose
between one or the other. NAND Flash provides high densities and low cost per bit, but suffers from bad
blocks and slower access times. NOR Flash provides fast access times, execute-in-place functionality, and
error free sectors, but suffers from a higher cost per bit. It is up to the system designer to decide which
characteristics are important for the system at hand. In addition the system designer should consider the
total flash size requirement. Although the cost per bit is more for NOR flash it could very well be that the
system requires only 2MB of flash, in which 2MB of NOR may be cheaper than the required minimum
16MB of NAND.
9.5 EEPROM (U9)
The phyCORE-LPC3250 comes pre-configured with a 32kByte SPI EEPROM located at U9 and is
connected to the LPC3250 SSP port 0. By default the EEPROM stores board configuration information
and the Ethernet MAC ID starting at 256 bytes from the end of the EEPROM (0x7f00). The data is stored in
the following configuration struct:
Table 9-4 and Table 9-5 detail the format of the dramcfg and syscfg fields in the configuration struct. The
MAC ID field uses the first 6 bytes in the 8 byte mac_id field for the Ethernet MAC ID. Lastly the fieldvval
must be set to 0x000a3250. This field provides a signature that the Stage 1 boot loader checks to
determine if the contents of the EEPROM configuration struct are intact.
Table 9-4. EEPROM Configuration Struct dramcfg Field Format
BitValue Description
1..000LowpowerSDRAM
1..001SDRAM
1..01xReserved
4..2000SDRAM16M,16bitsx2devices,0xa5
4..2001SDRAM32M,16bitsx2devices,0xa9
4..2010SDRAM64M,16bitsx2devices,0xad
4..2011SDRAM128M,16bitsx2devices,0xb1
31..5 0Reserved
.
Table 9-5. EEPROM Configuration Struct syscfg Field Format
BitValue Description
00SDIOControllerunpopulated
01SDIOControllerpopulated
31..1 0Reserved
The remaining space within the EEPROM is free for custom use or can be used to store a boot loader. See
Chapter 8 for details on booting from EEPROM.
In the event the SPI EEPROM is not needed and the SSP0 port is required for external use with some
other device, jumper J16 is provided to disconnect the SSP select signal SSEL0 from the EEPROM chip
select input. This jumper is provided as a convenience for prototyping. Custom SOM configurations can be
ordered which simply remove the EEPROM if not needed (instead of opening J16), reducing system costs.
Jumper J31 is provided to control the EEPROM write protect input. By default this jumper is set to the 1+2
position, allowing unrestricted write operations. Set this jumper to the 2+3 position to maintain control over
write protection. In addition to this jumper particular internal EEPROM status register bits must be
configured to enable full write protection. See the Atmel AT25256AN datasheet for details.
The phyCORE-LPC3250 memory map is summarized in Table 9-6 below. Make note of the memory
addresses assigned to functions on the phyCORE-LPC3250. Namely these are the SDIO controller, NOR
Flash, and SDRAM.
The phyCORE-LPC3250 provides on-board transceivers for three serial interfaces:
1. A high speed RS-232 transceiver supporting 920kbps on UART1 and 460kbps on UART5.
2. A full speed USB OTG transceiver supporting the LPC3250 USB OTG interface.
3. An Auto-MDIX enabled 10/100 Ethernet PHY supporting the LPC3250 Ethernet MAC.
The following sections of this chapter detail each of these serial interfaces and any applicable configuration
jumpers.
10.1 RS-232 Transceiver (U25)
An ADM3307E RS-232 transceiver supporting typical data rates of 920kbps populates the phyCORELPC3250 at U25. This device provides RS-232 level translation for UARTs U5 and U1. U1 is a high speed
UARTs supporting maximum data rates of 920kbps, while U5 is a standard speed UART supporting
maximum data rates of 460kbps. Table 10-1 details the TTL and RS-232 level signals for both UARTs. See
the pin description listing in Chapter 2, Table 2-1 for the signal locations on the phyCORE-Connector X2.
Table 10-1. UART 1/UART 5 TTL and RS-232 Level Signals
UARTTTL Level Signal RS-232 Level Signal
UART 1
UART 5
In addition to RS-232 level translation, two control signals are provided for increased transceiver control.
The /RS232_EN and RS232_SD signals provide enable and shutdown control. Both signals have internal
100k pull-down resistors. Drive the /RS232_EN signal HIGH (3.15V) to put the transmitter outputs into a
high impedance state. Drive the RS232_SD signal HIGH (3.15V) to shut down the device and reduce
power consumption to a mere 66nW. Refer to the Analog Devices ADM3307E datasheet for details on
these transceiver inputs (/EN and SD). See the pin description listing in Chapter 2, Table 2-1 for the signal
locations on the phyCORE-Connector X2.
For custom configurations which do not require RS-232 level translation, the RS-232 transceiver U25 can
be removed and 0 Ohm resistor network RN40 can be populated. In this configuration there is a direct
short between the TTL level signal name and RS-232 level signal name, leaving the RS-232 level signal
names operating at TTL levels.
U1_TXU1_TX_RS232
U1_RXU1_RX_RS232
U5_TXU5_TX_RS232
U5_RXU5_RX_RS232
10.2 Ethernet PHY (U6)
The phyCORE-LPC3250 comes populated with an SMSC LAN8700I Ethernet PHY at U6 supporting 10/
100 Mbps Ethernet connectivity. The PHY uses an RMII interface to the Ethernet MAC integrated on the
LPC3250.
The LAN8700I supports the HP Auto-MDIX function eliminating the need for consideration of a direct
connect LAN cable, or a cross-over patch cable. The LAN8700I detects the TX and RX pins of the
connected device and automatically configures the PHY TX and RX pins accordingly.
Interfacing the Ethernet port involves adding an RJ45 and appropriate magnetic devices in your design.
Please consult the phyCORE-LPC3250 Carrier Board schematics as a reference.
If your design does not require the Ethernet interface, but does require the keyboard interface, special
board alternations must be made to accommodate this. Due to pin multiplexing the Ethernet and keyboard
interfaces are not simultaneously operational. Instead, either Ethernet can be used, or Keyboard, but not
both.
To configure the SOM for keyboard use the following 0402 SMT resistors must be removed: R20, R21,
R22, R23, R24, R126. In addition the Ethernet clock oscillator must be disabled by driving the
ENET_CLKEN signal LOW. This can be accomplished by installing the applicable jumper on the
phyCORE-LPC3250 Carrier Board. See Chapter 25 for details on this jumper and its configuration. See
Figure 10-1 for the location of the resistors that must be removed for keyboard operation.
L-714e_1
10.2.1 Configuring the PHY Operating Mode (J7, J8, J9)
The LAN8700I operating mode is set via the 0R solder jumpers J7, J8, and J9. By default the PHY
operating mode is set to “All capable. Auto-negotiation enabled.” If a different operating mode is required
J7, J8, and J9 can be set according to Table 10-2 below. J7 sets MODE0, J8 sets MODE1, and J9 sets
MODE2. By default these signals are driven to "1" via weak internal pull-up resistors on the PHY. To set a
mode bit to "0" the corresponding jumper should be closed with a 10k-Ohm resistor. Refer to the SMSC
LAN8700I datasheet for a detailed presentation of the PHY operating modes.
The phyCORE-LPC3250 comes populated with an NXP Semiconductors ISP1301 USB On-The-Go
transceiver supporting both full speed and low speed data rates at U24. The ISP1301 functions as the
transceiver between the LPC3250 Host Controller, Device/Peripheral Controller, and On-The-Go
Controller. All three controllers interface the same set of USB port pins. The USB port can be configured as
a dedicated host, dedicated peripheral, or OTG interface.
When designing your USB interface you should pay special attention to current requirements when
operating as an embedded host. By default an embedded USB OTG host only needs to supply 8mA of
current to a connecting peripheral. The ISP1301 is capable of supplying at least 8mA to a connecting
peripheral, but unless the connecting peripheral is OTG compliant it will likely have a higher current
requirement. To meet this higher current requirement the USB_ADR/PSW pin can be made use of.
The USB_ADR/PSW pin both latches the lower I²C address bit of the ISP1301 and can be used to drive an
external power control switch capable of sourcing additional power. In this configuration the USB_ADR/
PSW signal is connected to the power supply enable input pin and the USB_VBUS signal is connected to
the 5V power supply output. See the phyCORE-LPC3250 Carrier Board schematics for reference circuitry
that makes use of the USB_ADR/PSW pin to provide additional host current. The USB_ADR/PSW pin is
pulled-down on the SOM by default. The resulting I2C address becomes: 0101 100x, where X is the R/W
bit in the I2C protocol specification.
Termination resistors and capacitors have already been populated on the phyCORE-LPC3250. A
USB_VBUS capacitor of 4.7µF in parallel with a 0.1µF capacitor has also been placed on the phyCORELPC3250. It should be noted that the maximum VBUS capacitance a USB OTG device can add to the bus
is 6.5µF. Therefore, adding anything more than 1.7µF external to the phyCORE-LPC3250 on USB_VBUS
is not recommended when operating in OTG mode. This maybe increased to the typical 120uF minimum
required by the USB specifications for dedicated host devices if OTG mode is not required.
In addition to optional power control circuitry via the USB_ADR/PSW signal, an external USB connector is
all that is needed to interface the phyCORE-LPC3250 USB functionality. Table 10-3 details applicable
connectors for various end application operating modes. The applicable interface signals (USB_D+/
USB_D-/USB_VBUS/USB_ID/USB_ADR/PSW) can be found in the phyCORE-connector pin-out Table 2-
1.
Table 10-3. Applicable USB Operating Mode Connectors
The phyCORE-LPC3250 comes populated with the NXP SDIO101 SD/SDIO/MMC/CE-ATA compliant host
controller at U14. The SDIO controller provides the hardware compliant layer to SD, SDIO, MMC, and CEATA enabled devices.
The SDIO controller is interfaced to the LPC3250 via the buffered external memory bus. Table 11-1
provides a detailed summary of the processor signals connected to the SDIO controller.
Table 11-1. SDIO Controller to LPC3250 Signal Mapping
SDIO Controller Signal LPC3250 Signal phyCORE-LPC3250 Signal
It should be noted that the GPI_7 interrupt signal has an internal 10k pull-up on-board.
The SDIO reset signal is connected through an inverter to the phyCORE-LPC3250 /RESET_EMB signal.
This will trigger a SDIO reset during power-up, power-fail, and power-down events.
The SDIO controller is clocked from the LPC3250 processor TST_CLK2 signal. This clock signal must be
configured on the LPC3250 (via the TEST_CLK register) to output a frequency compatible with the SDIO
controller. A good setting to use for the TEST_CLK register is either the main oscillator clock (13MHz) or
PERIPH_CLK (if configured for 13MHz).
The SD/SDIO/MMC/CE-ATA interface signals are listed in Tabl e 11 - 2 below.
Table 11-2. SDIO Controller Interface Signals
SDIO Controller Signal phyCORE-LPC3250 Signal Description
CLKSDIO_CLKClock output for read/write transactions
The SDIO controller provides a configurable voltage interface to the connecting SD/SDIO/MMC/CE-ATA
device via a set of power pins available at the phyCORE-Connector X2 as VCC_SDIO. In addition two
power control pins SDIO_POW0 and SDIO_POW1 are provided to control an external power supply to the
power pins and switch between off, low-power, and high-power modes. The flexibility of the power
interface allows a wide range of connecting devices to interface the on-board SDIO controller along with
management of dynamic power consumption.
Refer to the phyCORE-Connector X2 pinout Table 2-1 for signal locations. The phyCORE-LPC3250
Carrier Board schematics provide an excellent design reference for implementing a fully controllable SDIO
power interface. Refer to the NXP SDIO101 datasheet for SDIO controller details.
The phyCORE-LPC3250 is equipped with a JTAG interface for downloading program code into internal
controller RAM or for debugging programs currently executing. The JTAG interface extends out to 2.54 mm
pitch pin header at X1 on the edge of the module, in addition to being made available at the phyCOREConnector X2. Figure 12-1 shows the position of the debug interface (JTAG connector X1) on the
phyCORE-module. Even numbered pins are on the top of the module, starting with 2 on the right to 20 on
the left, while odd number pins are on the bottom, starting from (as viewed from the top) 1 on the right to 19
on the left. See Figure 12-1 below for details.
The JTAG edge card connector X1 provides an easy means of debugging the phyCORE-LPC3250 in your
target system via an external JTAG probe, such as the Abatron BDI2000.
NOTE:
The JTAG connector X1 only populates phyCORE-LPC3250 modules with order code PCM-040-xxxxxD.
This version of the phyCORE module must be special ordered. The JTAG connector X1 is not populated
on phyCORE modules included in the Rapid Development Kit. All JTAG signals are accessible from the
Carrier Board. The JTAG signals are also accessible at the phyCORE-Connector X2 (Molex connectors).
We recommend integration of a standard (2.54 mm pitch) pin header connector in the user target
circuitry to allow easy program updates via the JTAG interface. See Chapter 2 for details on the JTAG
signal pin assignment.
Part I, Chapter 13: Bus Buffers (U1, U2, U3, U4, U5)
L-714e_1
13 Bus Buffers (U1, U2, U3, U4, U5)
The phyCORE-LPC3250 provides a buffered version of the processor's external memory bus via bus
buffers U1, U2, U3, U4 and U5 for connection of external memory mapped peripherals. Data bus direction
is controlled by the processors output enable signal /OE. Table 13-1 provides a detailed list of the memory
bus signals available at the phyCORE-Connector X2. Refer to the phyCORE-Connector pin-out Table 2-1
for signal locations.
Table 13-1. Buffered Memory Bus Signal Mapping
LPC3250 Signal
EMC_D31…EMC_D0b_D31...b_D0Data bus
EMC_A23...EMC_A0b_A23...b_A0Address bus
/EMC_CS3.../EMC_ S0b_/CS3…b_/CS0Chip selects. Note b_/CS0 is connected to
EMC_BLS3…EMC_BLS0 b_BLS3…b_BLS0Byte lane selects
/EMC_OEb_/OEOutput enable
/EMC_WRb_/WRWrite enable
Configuration jumpers J1, J2, J3, and J4 are provided to control the bidirectional data bus buffer output
enable. By default all four jumpers are set to the 2+3 position, permanently enabling the data bus buffer
outputs. Depending on the memory bus operation of the connecting device it may be desirable to have the
data bus driven only during access times dictated by the byte lane select signals. This type of configuration
would be used for devices that may potentially drive the data bus on the bytes which are not being
currently written to. In this instance using J1-4 to drive enable the data bytes on the buffers for which the
byte lane select signals are active would prevent any contention between the buffers driving the bus and
the connecting device driving the bus on unaccessed bytes. This type of operation is very uncommon and
will likely not be needed, but configuration jumpers are provided nonetheless.
Table 13-2 provides a summary of the buffered memory map. Note that only chip select 2 and 3 are freely
available on the standard phyCORE-LPC3250 configuration.
Buffered phyCORELPC3250 Signal
Description
the on-board NOR flash and b_/CS1 is
connected to the on-board SDIO controller.
b_/CS2 and b_/CS3 are free for external
use.
Table 13-2. Buffered Memory Bus Map
AddressFunction
0xE300 0000 - 0xE3FF FFFF External memory busy chip select 3 (b_/CS3) - freely available for
0xE200 0000 - 0xE2FF FFFF External memory busy chip select 2 (b_/CS2) - freely available for
0xE100 0000 - 0xE1FF FFFF External memory busy chip select 1 (b_/CS1) - used by the on-board
0xE000 0000 - 0xE0FF FFFF External memory busy chip select 0 (b_/CS0) - used by the on-board
Part I, Chapter 13: Bus Buffers (U1, U2, U3, U4, U5)
L-714e_1
13.1 Buffered Memory Bus Voltage Select (J21)
The buffered memory bus operating voltage is configurable between 1.8V and 3.15V via jumper J21 to
allow connection of a variety of devices. By default this jumper is set to the 2+3 position, selecting 3.15V.
To interface 1.8V low power devices to the external memory bus J21 should be set to the 1+2 position.
WARNING:
The standard phyCORE-LPC3250 configuration does not allow a 1.8V external memory bus voltage. The
on-board NOR flash and SDIO controller are only operable at 3.15V. The 1.8V setting should not be used
unless you have specifically ordered a configuration that is compatible to 1.8V. Ordering options which
are compatible with 1.8V include: (1) 3.15V NOR Flash removed, SDIO controller removed, (2) 1.8V
NOR Flash populated, SDIO controller removed, or (3) NOR Flash and SDIO removed.
The physical dimensions of the phyCORE-LPC3250 are represented in Figure 14-1. The module's profile
is approximately 7.9mm thick, with a maximum component height of approximately 3.35mm on the bottom
(connector) side of the PCB and approximately 2.58mm on the top (microcontroller) side. The board itself
is approximately 1.26mm thick.
Battery operating currentDeep sleep; all SOM power
-255- uA
removed except RTC and
SDRAM; SDRAM in selfrefresh
LPC3250 A/D operating
current
Core @ 208MHz, 64MB
SDRAM @ 104MHz, 2MB
-TBD- mA
NOR, 64MB NAND
a. Tamb = -40C to +85C unless otherwise specified.
b. VBAT should always be less than VCC for proper operation.
c. Operating limits are per the NXP LPC3250 datasheet for the VCCA(3V0) pins.
These specifications describe the standard configuration of the phyCORE-LPC3250 as of the printing of
this manual.
Part I, Chapter 15: Hints for Handling the phyCORE-LPC3250
L-714e_1
15 Hints for Handling the phyCORE-LPC3250
Removal of various components, such as the microcontroller and the standard quartz, is not advisable
given the compact nature of the module. Should this nonetheless be necessary, please ensure that the
board as well as surrounding components and sockets remain undamaged while de-soldering.
Overheating the board can cause the solder pads to loosen, rendering the module inoperable. Carefully
heat neighboring connections in pairs. After a few alternations, components can be removed with the
solder-iron tip. Alternatively, a hot air gun can be used to heat and loosen the bonds.
Part 2 of this 3 part manual provides detailed information on the phyCORE-ARM9/LPC3250 Carrier Board
and its usage with the phyCORE-LPC3250 SOM.
The information in the following chapters is applicable to the 1305.3 PCB revision of the phyCORELPC3250 Carrier Board. The information is also applicable to the 1305.2 PCB revision, with the exception
of board images. All board images in this section of the manual refer to the 1305.3 PCB. Board images can
be used for the 1305.2 PCB revision, with the exception of jumper JP58. Jumper JP58 is moved a short
distance from the 1305.3 PCB. In all other respects the two board revisions are essentially identical.
The Carrier Board can also serves as a reference design for development of custom target hardware in
which the phyCORE SOM is deployed. Carrier Board schematics with BoM are available under a Non
Disclosure Agreement (NDA). Re-use of Carrier Board circuitry likewise enables users of PHYTEC SOMs
to shorten time-to-market, reduce development costs, and avoid substantial design issues and risks.
Fig. 17-1. phyCORE-LPC3250 Carrier Board Overview of Connectors and Interfaces
17 Introduction
L-714e_1
PHYTEC Carrier Boards are fully equipped with all mechanical and electrical components necessary for
the speedy and secure start-up and subsequent communication to and programming of the applicable
PHYTEC System on Module (SOM). Carrier Boards are designed for evaluation, testing and prototyping of
PHYTEC SOMs in laboratory environments prior to their use in customer designed applications.
The phyCORE-LPC3250 Carrier Board provides a flexible development platform enabling quick and easy
start-up and subsequent programming of the phyCORE-LPC3250 System on Module. The Carrier Board
design allows easy connection of additional expansion boards featuring various functions that support fast
and convenient prototyping and software evaluation.
The phyCORE-LPC3250 Carrier Board is depicted in Figure 17-1 and includes the following components
and peripherals listed in Table 18-1, Table 18-2, Table 18-3 and Table 18-4. For a more detailed description
of each peripheral refer to the appropriate chapter listed in the applicable table.
Table 18-1. Connectors and Headers
Ref. Des. DescriptionChapter
X1phyCORE-Connector for phyCORE-LPC3250 SOM connectivity20
X2GPIO expansion connector. Most phyCORE-LPC3250 signals are made avail-
able at this connector.
X3Audio MIC input jack for the UDA1380 audio codec24
X4Audio LINE input jack for the UDA1380 audio codec24
X5Audio LINE output jack for the UDA1380 audio codec24
X6Audio HEADPHONE output jack for the UDA1380 audio codec24
X7RJ-45 Ethernet jack for the phyCORE-LPC3250 Ethernet interface25
X8LCD signal configuration CPLD JTAG programming header for U427
X9Lithium-ion battery connector for powering the board via an external battery21.3
X10Wall adapter input power jack to supply main board power21.1
X11Easy access Ethernet/Keyboard signal header32
X12JTAG programming header22
X13Easy access UART3/UART2 signal header29
X14SD card connector for the phyCORE-LPC3250 on-board SD/SDIO/MMC/CE-
ATA controller
X15SD card connector for the LPC3250 SD/MMC port30
X16USB peripheral connector for the phyCORE-LPC3250 USB OTG interface26
X17USB OTG connector for the phyCORE-LPC3250 USB OTG interface26
X18USB host connector for the phyCORE-LPC3250 USB OTG interface26
X19Ground stud for easy ground connection of test equipment (e.g., oscilloscope
ground clip)
X20Ground stud for easy ground connection of test equipment (e.g., oscilloscope
ground clip)
X22USB and Ethernet shield ground connection access pointN/A
X23Easy access signal header for the phyCORE-LPC3250 on-board SD/SDIO/
MMC/CE-ATA controller
X24Easy access signal header for the LPC3250 SD/MMC port30
X25LCD signal configuration CPLD JTAG programming header for U627
X26LCD connector for connection of an external PHYTEC LCD board27
R175Potentiometer to test LPC3250 ADC channel 2 (ADIN2)35
Please note that all module connections are not to exceed their expressed maximum voltage or current.
Maximum signal input values are indicated in the corresponding controller User's Manual/Data Sheets. As
damage from improper connections varies according to use and application, it is the user's responsibility to
take appropriate safety measures to ensure that the module connections are protected from overloading
through connected peripherals.
The phyCORE-LPC3250 Carrier Board comes pre-configured with 51 removable jumpers (JP). The
jumpers allow the user flexibility of rerouting a limited amount of signals for development constraint
purposes. Table 19-1 below lists the 51 removable jumpers, their default positions, and their functions in
each position. Figure 19-2 depicts the jumper pad numbering scheme for reference when altering jumper
settings on the development board. Note that pin 1 is always marked by a square footprint in the jumper
location diagrams that follow. Figure 19-1 provides a detailed view of the phyCORE-LPC3250 Carrier
Board jumpers and their default settings.
Part II, Chapter 20: phyCORE-LPC3250 SOM Connectivity
Fig. 20-1. phyCORE-LPC3250 SOM Connectivity to the Carrier Board
20 phyCORE-LPC3250 SOM Connectivity
L-714e_1
Connector X1 on the Carrier Board provides the phyCORE-LPC3250 System on Module connectivity. The
connector is keyed for proper insertion of the SOM. Figure 20-1 above shows the location of connector X1,
along with the pin numbering scheme.
The phyCORE-LPC3250 Carrier Board powering scheme provides a flexible platform for a variety of
powering configurations. Board power sourcing includes a wall adapter, Power-over-Ethernet, or a battery
supply. A number of the on-board power supplies have configurable input sources along with shutdown
control during a sleep.
Figure 21-2 presents a block diagram of the Carrier Board powering scheme. Primary input power is
selected via jumper JP42 and comes from either the wall adapter jack X10, or the Power-over-Ethernet
circuit U2 (via the Ethernet jack X7) to generate the VIN signal. VIN is both an input into the battery
charging circuit U8 as well as an input into the power path control U22. The power path control U22
generates the output VCC_IN from one of the two inputs VIN, or V_LIBAT, and automatically selects which
one is routed to the output VCC_IN. When VIN is present VCC_IN is always sourced from VIN. When VIN
is absent (removal of wall power or Ethernet cable) VCC_IN is sourced from the lithium-ion battery output
V_LIBAT. All board power supplies ultimately generate power from VCC_IN.
The primary 5V regulator U21 is a buck-boost regulator sourced from VCC_IN and can be used as the
main board power source for the downstream regulators via the VCC_BB rail. Alternatively JP44 and JP45
can be configured to source the 3.15V, and 3.0V supplies directly from VCC_IN instead. These two
scenarios provide a method of testing maximal battery life configuration.
In one configuration U21, U9, and U11 are all sourced from VCC_IN. During deep sleep U9 and U21 are
shutdown, leaving only U11 operating and supplying the sleep power. In this configuration U11 is
essentially drawing its power directly from the lithium-ion battery (through the power path controller).
In the second configuration U21 is sourced from VCC_IN while U9 and U11 are sourced from VCC_BB,
which is the output of U21. During deep sleep only U9 is shut down. In this configuration U11 drawings its
power from a U21, which in turn is getting its power directly from the battery.
This multi-configuration approach allows you to test which scenario is more efficient with your battery. 4.2V
lithium-ion batteries tend to have very little power left when drained down to 3V. In the first configuration
this is ideal. If we expect the battery to have very little life left at 3V then there is no need to put the battery
through a buck-boost regulator and then regulate this down to 3.0V for the deep sleep power; this wastes
power through conversion losses in U21. On the other hand it may be unknown exactly how much power
remains in the battery when it is down around 3V. The second configuration allows the buck-boost
regulator U21 to operate in the boost region and continue to provide power from the battery all the way
down to 2.7V. The additional power gained from continuing to draw on the battery down to 2.7V instead of
3.0V may or may not be advantageous over the power losses in the buck-boost regulator; in essence it
could be more power efficient overall to not try and derive that little bit of power left at the end of battery life
and instead spare the power losses incurred in the buck-boost regulator by connecting the 3.0V deep
sleep supply directly to the battery output (VCC_IN essentially). The phyCORE-LPC3250 Carrier Board
allows you to test both configurations with the battery you decide to use in your end application.
A detailed list of the JP44 and JP45 configuration jumpers is presented below.
JP44Configures the VCC_3V15 supply U9 input power source. By default this jumper is in the
1+2 position, selecting VCC_IN as the power input source. Alternatively this jumper can be
set to the 2+3 position, selecting VCC_BB as the input power source.
JP45Configures the VCC_3V0 supply U11 input power source. By default this jumper is in the 1+2
position, selecting VCC_IN as the power input source. Alternatively this jumper can be set to
the 2+3 position, selecting VCC_BB as the input power source.
The following sections in this chapter describe each power block in detail.
CAUTION:
Do not use a laboratory adapter to supply power to the Carrier Board! Power spikes during power-on
could destroy the phyCORE module mounted on the Carrier Board! Do not change modules or jumper
settings while the Carrier Board is supplied with power!
21.1 Wall Adapter Input
Permissible input voltage: +5 VDC regulated.
The primary input power to the phyCORE-LPC3250 Carrier Board is located at connector X10 as shown in
Figure 21-2 above. The required load current capacity of the power supply depends on the specific
configuration of the phyCORE-LPC3250 mounted on the Carrier Board, in addition to the particular
interfaces enabled while executing software. An adapter with a minimum supply of 2600mA is
recommended.
A detailed list of applicable configuration jumpers is presented below.
JP42Configures primary input power source. By default this jumper is set to 4+6/5+3, sourcing
board power from the wall adapter input. Alternatively this jumper can be set to 4+2/1+3,
sourcing board power from the Power-over-Ethernet circuit.
D20Shows the status of the input power supply (wall power or PoE). When illuminated the
The Power-over-Ethernet (PoE) circuit provides a method of powering the board via the Ethernet interface.
In this configuration the phyCORE-LPC3250 Carrier Board acts as the Powered Device (PD) while the
connecting Ethernet interface acts as the Power Source Equipment (PSE). For applications that require
Ethernet connectivity this is an extremely convenient method to also simultaneously provide power.
To make use of the PoE circuit you must have a PSE for connectivity. Typically a PoE enabled router or
switch can be used. Table 21-1 provides a list of possible Power Sourcing Equipment you can purchase to
interface the phyCORE-LPC3250 PoE circuit if you do not already have a PSE.
Table 21-1. Possible Ethernet PSE Options
DeviceDescription
FS108PNetgear 8-port Ethernet switch with 4-port PoE support.
TPE-101I TRENDnet single port PoE injector
The IEEE PoE standard restricts the maximum amount of power a PSE must provide and therefore a PD
can consume. The phyCORE-LPC3250 PoE circuit was designed to provide up to 8.5W of power to the
board. Note that this is less than the wall adapter can supply and less than the board can potentially
consume. Be aware that this limitation could cause board operation to fail if peak power is exceeded due to
enabled peripherals.
The phyCORE-LPC3250 Carrier Board Ethernet connector X7 supports both PSE power sourcing
methods of power over the data wires, or power over the spare wires.
A detailed list of applicable configuration jumpers and LED indicators is presented below.
JP39Controls the PoE signature resistor internal to the Linear Tech LTC4267 PoE IC. By default
this jumper is set to the 2+3 position, enabling the 25k signature resistor. Alternatively this
jumper can be set to the 1+2 position, disabling the 25k signature resistor. For normal operation this jumper should be set to the 2+3 position, but in some applications it may be necessary to disable the signature resistor.
JP42Configures primary input power source. By default this jumper is set to 4+6/5+3, sourcing
board power from the wall adapter input. Alternatively this jumper can be set to 4+2/1+3,
sourcing board power from the Power-over-Ethernet circuit.
D14PoE 5V power indicator. When illuminated the PoE circuit is actively generating 5V.
D36Ethernet LINK status indicator. When illuminated the Ethernet interface has established a
link to the network.
D41Ethernet ACTIVITY status indicator. When illuminated the Ethernet interface is active on the
network.
21.3 Lithium-Ion Battery
The NXP LPC3250 processor is well suited for low power applications, and as such makes it an ideal
candidate for battery operation. The phyCORE-LPC3250 Carrier Board provides a lithium-ion battery input
and battery charging circuit at U8 to support this.
In general you should use the PHYTEC supplied battery with the phyCORE-LPC3250 Carrier Board.
Caution should be exercised when using your own battery. You should only use 4.2V lithium-ion batteries
capable of a 1.1A charging current. You should consult PHYTEC before using your own battery.
To use the battery option to power the board plug the PHYTEC supplied lithium-ion battery into connector
X9 on the Carrier Board. If the board is already powered via the PoE circuit, or the wall adapter input, the
battery will begin charging if the battery charging circuit detects an under voltage condition (see Chapter
21.3.1 for details) on the battery. The PoE supply or wall adapter input can be removed at any time to begin
powering the board from the battery. The transition is seamless between PoE/wall power, and battery
power. Likewise the connection of PoE or wall power after the board is running from the battery is
seamless. Removing and inserting the external supplies should not affect board operation.
21.3.1 Battery Charging Circuit
The battery charging circuit located at U8 is capable of recharging a 4.2V lithium-ion battery with a 1.1A
charging current when the board is powered from the PoE circuit or the wall adapter. Battery charging is
automatic when an alternate board power source is available. The battery charging will cease when the
battery becomes fully charged.
To charge the PHYTEC supplied lithium-ion battery plug the battery into connector X9 on the Carrier Board
while the board is powered via the wall adapter or PoE circuit. The red "Charging" LED D19 will illuminate
during a charging cycle.
A detailed list of applicable configuration jumpers is presented below.
JP2Configures the LTC4002 battery temperature monitoring function. By default this is set to the
2+3 position, disabling temperature monitor control. To enable this feature set the jumper to
the 1+2 position
a
.
D19Battery charging status indicator. When illuminated the connected lithium-ion battery is being
charged.
a. The battery must have an applicable thermistor integrated into the package for this function to operate properly
21.4 3.15V Supply (U9)
The Linear Technology LTC1622 switching regulator populated at U9 provides the primary VCC=3.15V
power to the phyCORE-LPC3250 System on Module. In addition many of the peripheral support
components are also powered via the 3.15V supply.
A detailed list of applicable configuration jumpers is presented below.
JP44Configures the VCC_3V15 supply U9 input power source. By default this jumper is in the
1+2 position, selecting VCC_IN as the power input source. Alternatively this jumper can be
set to the 2+3 position, selecting VCC_BB as the input power source
J3Current measurement access point jumper. By default this jumper is populated with a 1206
packaged 0 Ohm resistor. See Chapter 21.8 for techniques on measuring current at this
jumper.
The National Instruments LP2951 LDO regulator populated at U10 provides 1.8V for processor I/O
compatibility. Because of the multi voltage nature of the LPC3250 several of the I/O pins operate at 1.8V
instead of the primary VCC voltage of 3.15V. In general this 1.8V supply is used simply to power voltage
translation buffers like the 74AVC2T45.
A detailed list of applicable configuration jumpers is presented below.
J4Current measurement access point jumper. By default this jumper is populated with a 1206
packaged 0 Ohm resistor. See Chapter 21.8 for techniques on measuring current at this
jumper.
21.6 5.0V Buck-Boost Supply (U21)
The Linear Technology LTC3785 buck-boost switching regulator populated at U21 provides 5V required by
USB peripherals, the LCD interface, and can also be used as the input source to other downstream
regulators. U21 generates two voltage rails called VCC_BB and VCC_5V0. Both rails are at 5V. The
VCC_5V0_OFF signal provides on/off control over the VCC_5V0 rail while the VCC_BB rail remains active
as long as the board is powered. U21 derives its power from the active board powering source, which can
either be the wall adapter, PoE, or lithium-ion battery. As discussed in Chapter 21 it may be beneficial for
the downstream regulators to be powered via VCC_BB instead of the primary board input power source.
Refer to Chapter 21 for a detailed explanation of the pros/cons of using the VCC_BB rail for downstream
regulators.
A detailed list of applicable configuration jumpers is presented below.
J7Current measurement access point jumper. By default this jumper is populated with a 1206
packaged 0 Ohm resistor. See Chapter 21.8 for techniques on measuring current at this
jumper.
21.7 Power Path Controller
The Linear Technology LTC4412 power path controller populated at U22 is responsible for automatic
battery switching when primary board power is removed. Under normal operating conditions the wall
adapter or Power-over-Ethernet output will be powering the board. U22 automatically, and seamlessly
transitions from wall adapter/PoE power to battery power without interrupting board operation.
A detailed list of applicable configuration jumpers is presented below.
JP43Path configuration control. By default this jumper is set to the OPEN position, allowing the
circuit to operate as normal. Alternatively this jumper can be set to the CLOSED position,
forcing the power path controller to always source power from the wall adapter/PoE input.
This setting can be useful if you do not want the system to draw power from the battery when
unplugged, and instead be powered down.
21.8 Current Measurement
To facilitate current measurement jumpers J3 through J8 are provided as current access measurement
points. Replace these jumpers with 1206 packaged precision shunt resistors and measure the resulting
voltage drop across the shunt resistor to calculate current draw. A good value to start with for your shunt
resistor is 25milliOhms. The shunt resistor should be small enough to not affect the output voltage (it will be
reduced by the voltage drop across the shunt), but large enough to have a discernible measurement from
general noise.
Connector X12 provides a convenient JTAG probe connection interface for ARM compatible JTAG probes
to the LPC3250. Table 22-1 provides a detailed list of the signals at the JTAG connector. You should cross
reference this with your JTAG probe to ensure compatibility.
7TMSTest mode select input with internal 10k pull-up.
8GNDGround.
9TCKTest clock input with internal 10k pull-down.
10GNDGround.
11RTCKReturn test clock output with internal 10k pull-down.
12GNDGround.
13TDOTest data output.
14GNDGround.
15/SRSTSystem reset input with internal 10k pull-up.
16GNDGround.
17N/CNot connected.
18GNDGround.
19N/CNot connected.
20GNDGround.
L-714e_1
As of the printing of this manual Table 22-2 lists JTAG probes which are known to be compatible to the
phyCORE-LPC3250 Carrier Board JTAG interface.
Table 22-2. Compatible JTAG Probes for the phyCORE-LPC3250 Carrier Board
JTAG Probe Name
Keil U-Link and U-Link2
Segger J-Link
Abatron BDI2000
ARM Realview ICE
Two configuration jumpers allow control over board reset functionality. A detailed list of applicable
configuration jumpers is presented below.
JP30Controls enabling boundary scan mode for the processor. By default this jumper is opened,
configuring the LPC3250 for normal JTAG debug operation. Close this jumper to enable
boundary scan mode operation for the processor.
JP41Controls the power source to the JTAG /SRST circuit. By default this jumper is set to the 1+2
position, configuring the interface to drive the /RESET_SYS input to the phyCORELPC3250. Alternatively this jumper can be set to the 2+3 position, configuration the interface
to drive the /RESET_BAT input to the phyCORE-LPC3250. This jumper must be changed in
conjunction with jumper JP58. Both JP41 and JP58 must be in the 1+2 position, or both in
the 2+3 position.
JP58Controls which reset input the JTAG /SRST signal drives. By default this jumper is set to the
1+2 position, configuring the interface to drive the /RESET_SYS input to the phyCORELPC3250. Alternatively this jumper can be set to the 2+3 position, configuration the interface
to drive the /RESET_BAT input to the phyCORE-LPC3250. This jumper must be changed in
conjunction with jumper JP58. Both JP41 and JP58 must be in the 1+2 position, or both in
the 2+3 position.
The /RESET_SYS signal is the system reset input to the phyCORE-LPC3250. Driving this signal LOW will
cause a system reset. The /RESET_BAT signal is the system + sleep reset input to the phyCORELPC3250. Driving this signal LOW will cause a system reset just as the /RESET_SYS signal, and in
addition will reset the sleep circuitry. If it is required to be able to have reset control over the sleep circuitry
(which is normally only reset should a sleep voltage fail) via the JTAG probe during test/debug then
configure the JP41/JP58 jumper combo to drive the /RESET_BAT signal, otherwise leave the jumpers in
their default configuration to provide a system wide reset via /RESET_SYS.
The deep sleep circuit is responsible for power supply control and tracking deep sleep status. This circuit
coupled with sleep designed features on the phyCORE-LPC3250 allow the processor to shut down
primary system power supplies while maintaining SDRAM and RTC power. Figure 23-2 shows a block
diagram of the phyCORE-LPC3250 Carrier Board power system and deep sleep circuit, along with
connectivity to the phyCORE-LPC3250 System on Module.
In Figure 23-2 the deep sleep circuitry is represented by the Control Logic block. This block is composed of
two D flip-flops, some transistors, diodes, and resistors. Connectivity of the Control Logic to the phyCORELPC3250 consists of 6 different signals: GPO_11, GPO_17, GPI_19, /RESET_BAT, ONSW, and /
RTC_INT. In addition the power button is interfaced via the GPI_0 signal. A detailed description of signal
usage is presented below.
signal clears the deep sleep flip-flop DFF1 (see schematics), setting the Q_bar output
to HIGH. This is indicative of a wake state.
GPO_11This processor signal connects to the deep sleep clear input. When toggled HIGH this
GPO_17This processor signal connects to the deep sleep set input. When toggled HIGH this
signal sets the deep sleep flip-flop DFF1 (see schematics), setting the Q_bar output to
LOW and shutting down system power. This is indicative of a sleep state.
GPI_19This processor signal connects to the deep sleep state output. When read, a HIGH indi-
cates a wake state, and a LOW indicates a sleep state.
/RESET_BAT This signal is generated on the SBC and is the reset output of the sleep supervisor. If
the on-board RTC or SDRAM supplies fail or the sleep voltage VDS_3V0 fails (monitored as VBAT on the SBC) this signal will go LOW causing a reset to the deep sleep
state flip-flop DFF1 (set to wake state).
ONSWThis processor signal is the alarm output of the on-chip RTC block. When active (a
HIGH going pulse) this signal enables the system power supplies (5V and 3.15V) causing the system to begin booting.
/RTC_INTThis signal is the alarm output of the off-chip RTC on the SBC. When active (a LOW
going pulse) this signal enables the system power supplies (5V and 3.15V) causing the
system to begin booting.
GPI_0This processor signal is connected to the power switch output and senses a press of
the power switch button. When pressed the system should begin the sleep shutdown
process via software.
The Power Switch output is routed to both the deep sleep control circuitry and the phyCORE-LPC3250
SOM. The deep sleep circuitry only responds to the power switch when power has been removed.
Pressing the power switch will reapply system power. If system power is already applied then pressing the
power switch has no effect on the deep sleep circuitry. The phyCORE-LPC3250 only responds to the
power switch when the system is powered. The phyCORE-LPC3250 monitors the power switch (via an
edge triggered interrupt on GPI_0) and initiates a system sleep when the power switch has been pressed.
Figure 23-3 presents a state diagram of the entire sleep cycle from the system running, to the powered-
down stage, back to the system running again. The system starts in the System Off state where power is
either removed completely from the board (no wall adapter, battery, or PoE) or the on-board regulators are
shut down and the deep sleep supply VDS_3V0 is active. The system begins powering up through one of
four events:
1. The on-chip RTC generates an alarm signal via the ONSW output. The ONSW output signals the
deep sleep circuitry to enable the on-board regulators.
2. The off-chip RTC generates an alarm signal via the /RTC_INT output. The /RTC_INT output signals the deep sleep circuitry to enable the on-board regulators.
3. The power button is pressed, signaling to deep sleep circuitry to enable the on-board regulators.
4. The system is powered up for the very first time and the Carrier Board is configured via jumper
JP3 to apply system power after a /RESET_BAT event.
After power is applied and the voltage supervisors have taken the system out of reset (supplies have
stabilized) the system begins booting. In the first part of the boot process the user supplied bootloader
checks the status of GPI_19 to read the deep sleep state. If GPI_19 is set to HIGH then the system boots
normally. If GPI_19 is set to LOW the system boots knowing it was previously in deep sleep and the
contents of SDRAM and the RTC block are known and good. After booting has completed the system is in
the System Running state. From this point the system will operate until the next time it needs to enter deep
sleep. The system will enter deep sleep again via two methods:
1. The power button is pressed.
2. An internal event triggers a sleep request
In (1) the system detects the power button press via an edge triggered interrupt on GPI_0. In (2) an internal
event such as a count down timer expires. Both result in a request for the system to enter a sleep state. At
this point the software takes the appropriate measures to prepare for sleep. The last step to enter deep
sleep and shut down the system power supplies is to set GPO_17 high. This sets the deep sleep state flipflop to the sleeping state and triggers the removal of system power. The system has now come full circle
back to the System Off state.
Various configuration jumpers allow customizing the operation of the deep sleep circuit. A detailed list of
applicable configuration jumpers is presented below.
JP3Configures the power reset behavior after a /RESET_BAT event. By default this jumper
is in the 1+2 position, setting the board to the power off state after a /RESET_BAT
event. Alternatively this jumper can be set to the 2+3 position, setting the board to the
power up state after a /RESET_BAT event. /RESET_BAT event will occur at the very
first application of board power or during a fault on the battery supervisor rails (VBAT,
VCC_RTC, VCC_SDRAM).
JP15Connects processor input signal GPI_19 to the /DS_STATE output signal of the deep
sleep state flip-flop DFF1, allowing the processor to read the sleep state. By default this
jumper is set to the closed position, connecting GPI_19 to the /DS_STATE signal.
Remove this jumper to free GPI_19 for external use.
JP17Connects processor output signal GPO_17 to the DS_SET input signal of the deep
sleep state flip-flop DFF1, allowing the processor to set the sleep state. Remove this
jumper to free GPO_17 for external use.
JP18Connects the deep sleep circuitry VCC_OFF output signal to the 5V peripheral supply
OFF input. By default this jumper is closed, shutting off the 5V peripheral supply when
the system enters deep sleep. Remove this jumper to keep 5V peripheral circuitry alive
during a sleep. 5V peripheral circuitry will potentially include LCD and powered USB
peripherals. Reference the Carrier Board schematics for details.
JP19Connects the deep sleep circuitry VCC_OFF output signal to the primary 3.15V supply
OFF input. By default this jumper is closed, shutting off the 3.15V supply when the system enter deep sleep. Remove this jumper to keep 3.15V circuitry alive during a sleep.
3.15V circuitry includes the phyCORE-LPC3250 along with most of the supporting circuitry on the Carrier Board. Reference the Carrier Board schematics for details.
JP20Connects processor output signal GPO_11 to the DS_CLEAR input signal of the deep
sleep state flip-flop DFF1, allowing the processor to clear the sleep state. Remove this
jumper to free GPO_11 for external use.
JP22Reserved for future use. Keep this jumper set at the default 2+3 position.
JP24Connects the off-chip RTC output signal /RTC_INT to the deep sleep power control flip-
flop DFF2. By default this jumper is closed allowing the off-chip RTC to reapply power
during deep sleep. Remove this jumper to disable this function.
L-714e_1
JP46Connects the deep sleep circuitry VCC_OFF output signal to the 5V buck-boost periph-
eral supply OFF input. By default this jumper is closed, shutting off the 5V buck-boost
peripheral supply when the system enter deep sleep. Refer to Chapter 21 for a detailed
explanation on using this jumper. Remove this jumper when JP45 is set to 2+3 or JP44
is set to 2+3.
23.1 3.0V Deep Sleep Supply (U11)
The Linear Technology LTC1877 switching regulator populated at U11 provides the 3.0V deep sleep power
maintained during a sleep condition. This supply only provides power to the deep sleep circuit and the
VBAT input pin on the phyCORE-LPC3250.
A detailed list of applicable configuration jumpers is presented below.
JP45Configures the VCC_3V0 supply U11 input power source. By default this jumper is in
the 1+2 position, selecting VCC_IN as the power input source. Alternatively this jumper
can be set to the 2+3 position, selecting VCC_BB as the input power source.
J5Current measurement access point jumper. By default this jumper is populated with a
1206 packaged 0 Ohm resistor. See Chapter 21 for techniques on measuring current at
this jumper.
The audio interface provides a method of exploring the LPC3250's I²S capabilities. The phyCORELPC3250 Carrier Board comes populated with an NXP UDA1380 audio codec supporting a stereo line
input, a mono microphone input, a stereo line output, and a stereo headphone output. The UDA1380 is
interfaced to the phyCORE-LPC3250 via the I²S port 1 for audio data and the I²C port 1 for codec
configuration. The codec is clocked off of the processors I2STX_WS1 signal with the help of internal codec
PLLs. Alternatively the TST_CLK2 input can be used for clocking the codec, however, a lack of suitable
dividers limits the usable bit rates with the TST_CLK2 input. Eight configuration jumpers allow flexible
control over board audio connectivity. A detailed list of applicable configuration jumpers and connectors is
presented below.
X3Mono MIC jack input - Connect this to a compatible electret type microphone. The MIC is
biased via a 10k pull-up to 3.15V. Ensure that this does not exceed the biasing requirements
of your MIC.
X4Stereo Line Input jack - Connect this to an applicable stereo audio output source producing a
1V RMS output signal (such as the LINE OUT on a PC). Applications that require a 2V RMS
output signal must replace resistors R29 and R30 with 12k Ohm 0805 packaged resistors.
X5Stereo Line Output jack - Connect this to an applicable audio input source capable of receiv-
ing a ~0.945V RMS (typical) input signal (such as the LINE INPUT on a PC).
X6Stereo Headphone Output jack - Connect this to a set of headphones. This output is capable
of driving a 16 Ohm load.
JP1MIC bias configuration jumper. By default this jumper is set to the 1+2 position, biasing a
mono input microphone. This jumper may be useful for independently biasing and using
either channel of a stereo MIC. Set this jumper to the 2+3 position to use and bias the right
channel and 1+2 for the left channel.
JP7Connects the I2STX_SDA1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP8Connects the I2STX_WS1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP9Connects the I2STX_CLK1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP10Connects the I2SRX_SDA1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP11Connects the I2SRX_WS1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP12Connects the I2SRX_CLK1 processor signal to the audio codec. By default this jumper is set
to the closed position. Open this jumper to free this signal for external use.
JP13Connects the LCD0/GPO_02 processor signal to the audio codec reset input. By default this
jumper is closed. Open this jumper to free this signal for external use.
Fig. 25-1. Ethernet Interface Connectors and Jumpers
25 Ethernet Connectivity
L-714e_1
The Ethernet interface provides a method of connecting to the phyCORE-LPC3250 Ethernet functionality.
One RJ-45 connector is provided at X7. This connector provides both a connection to the Ethernet data
signals and the Power-over-Ethernet power signals. A LINK and ACTIVITY LED are provided on the
Carrier Board at D36 and D41. One configuration jumper is provided to disable the phyCORE-LPC3250
Ethernet clock oscillator.
A detailed list of applicable configuration jumpers is presented below.
JP14Enables/disables the phyCORE-LPC3250 Ethernet oscillator. By default this jumper is open,
enabling the phyCORE-LPC3250 Ethernet oscillator (required for Ethernet functionality). If
the Ethernet interface is not used, or the keyboard interface is required, close this jumper to
disable the on-board Ethernet clock oscillator. Disabling the Ethernet clock oscillator will
result in a noticeable decrease in power consumption.
JP39Disables the PoE signature resistor internal to the LTC4267. By default this jumper is set to
to the 2+3 position, enabling the PoE signature resistor. Close this jumper to disable the PoE
signature resistor.
For information on using the Power-over-Ethernet circuit refer to Chapter 21.2.
The USB interface provides connectivity to the phyCORE-LPC3250 USB OTG functionality. Three
connectors are provided for testing convenience: (1) a Standard-A Host connector X18, (2) a Standard-B
Peripheral connector X16, (3) and a Mini-AB OTG connector X17. All three connectors connect to the
same USB interface.
In addition to connectors an OTG configuration jumper is provided, along with additional 5V supply current
for non-OTG peripherals. A USB OTG compliant device is only required to source up to 8mA of current
when operating as a host. Because very few devices are OTG compliant and most USB peripherals
require more than 8mA to operate, a 5V power circuit and configuration jumper have been provided to
facilitate these devices.
A detailed list of applicable configuration jumpers and connectors is presented below.
X16USB Standard-B connection interface. Connect a USB Standard-B mating cable to this con-
nector when operating the USB interface in Peripheral mode.
X17USB Mini-AB connection interface. Connect a USB OTG cable to this connector when oper-
ating the USB interface in OTG mode.
X18USB Standard-A connection interface. Connect a USB Standard-A mating cable to this con-
nector when operating the USB interface in Host mode.
JP5Configures 5V power to connecting peripheral devices. By default this jumper is set to the
2+3 position, allowing the ISP1301 USB OTG transceiver to control the power supply during
over current conditions. Alternatively this jumper can be set to the 1+2 position providing 5V
power in excess of 500mA with no over current monitoring.
JP34Configures the OTG operating mode. By default this jumper is set to the open position, float-
ing the USB_ID pin, and configuring the OTG interface as a peripheral. Alternatively this
jumper can be set to the closed position, connecting USB_ID to GND, and configuring the
OTG interface as a host. Typically the configuration of a connecting device as host or peripheral is done automatically via a USB OTG cable. However, given the limited number of OTG
enabled devices in the embedded market this jumper is provided to either simulate an OTG
cable, or force the OTG interface into Host mode when OTG operation is not required.
JP52Controls the addition of 120uF of capacitance to the USB_VBUS net. By default this jumper
is in the open position, resulting in about 4.7uF of capacitance on USB_VBUS. This configuration is required when operating as an OTG device. When operating as a dedicated USB
host, close this jumper to add the required 120uF of capacitance on USB_VBUS required by
the USB specification.
The phyCORE-LPC3250 Carrier Board provides a flexible LCD connection interface to support various
PHYTEC provided LCD boards. The Universal LCD Connector X26 provides power, and buffered signals
to connecting LCDs.
The Universal LCD Interface consists of the following components:
1.CPLDs for buffered signals and color signal control
2.5.0V slew-rate limited power control + status LED
3.3.3V slew-rate limited power control + status LED
Fig. 27-3. LCD BLUE Signal Mapping in 16-bit Mode with an 18-Bit LCD
L-714e_1
The CPLDs come pre-programmed supporting the 24bpp, 16bpp (5:5:5), 16bpp (5:6:5), and 12bpp (4:4:4)
modes the LPC3250 LCD controller provides. The CPLDs provide two important features on the
phyCORE-LPC3250 Carrier Board:
1. Buffered signal and power interface
2. Color signal control
The buffered signal and power provide a means of completely shutting off power to the LCD on-the-fly.
This type of configuration allows dynamic control over system power consumption by turning off the LCD
when it is not needed.
Color signal control allows dynamic reconfiguration of the color signals to support various LCD bit widths.
As an example consider only the blue color signals from a 24-bit LCD and an 18-bit LCD. In the case of a
24-bit LCD Figure 29 shows the connection interface from the LPC3250 LCD port all the way to the LCD.
As can be seen LCD23...16 from the processor map directly to LCD_BLUE7...0 via the CPLD U4.
In the case of an 18-bit LCD Figure 30 shows the lower 3-bits of the BLUE signals to the connector X26 are
held to 0 (LOW) by the CPLD when operating the LPC3250 in 16-bit 5:6:5 mode. The result is the upper 5
bits of the LCD blue interface are driven with the blue color data provided by the LPC3250. The lower blue
LCD bit 0 is driven to 0 by the CPLD (since this data bit is not provided by the 16-bit operating mode of the
LPC3250). The lower 3 bits of the LPC3250 LCD interface, LCD18, LCD17, and LCD16 are freed for use
as their alternative functions when operating in this mode.
Table 28 shows a detailed mapping of the LPC3250 LCD port signals through the CPLD. In general the
CPLD is acting as a buffer, mapping LCD23...16 directly to LCD_BLUE7...0, LCD15...8 to
LCD_GREEN7...0, and LCD7...0 to LCD_RED7...0. The only time this is not true is for the lower LCD color
bits for 16-bit and 12-bit mode. In the 16-bit modes (5:6:5 and 5:5:5) and 12-bit mode (4:4:4) the unused
LCD bits on the LPC3250 LCD port are not buffered through the CPLD. Instead the CPLD holds these
signals LOW for these operating modes. The signal mapping is as follows for the four LCD bit modes:
A detailed list of applicable configuration jumpers and LED indicators is presented below.
JP40LCD interface enable control. By default this jumper is set to the 2+3 position, selecting pro-
cessor signal GPO_0 to control LCD interface enable. Set this jumper to the 1+2 position to
permanently disable the LCD interface. Remove this jumper to permanently enable the LCD
interface. When this jumper is removed or in the 1+2 position the processor signal GPO_0
becomes free for external use.
JP48..50 Configures the LCD operating mode. By default these jumpers are set to CLOSED, OPEN,
CLOSED resulting in the 16-bit 5:6:5 operating mode. See Table 29 for a detailed list of
jumper settings and corresponding operating modes.
JP51LCD backlight control jumper. By default this jumper is set to the 2+3 position, selecting pro-
cessor signal GPO_4 to control LCD backlight. Set this jumper to the 1+2 position to permanently turn off the LCD backlight. Remove this jumper to permanently turn on the LCD
backlight. When this jumper is removed or in the 1+2 position the processor signal GPO_4
becomes free for external use.
D17LCD 5.0V status indicator. When illuminated the 5.0V supply to the LCD connector X26 is
active.
D34LCD 3.3V status indicator. When illuminated the 3.3V supply to the LCD connector X26 is
The GPIO expansion port connector X2 provides a 1:1 mapping of most of the phyCORE-LPC3250 mating
connector X1 signals. Additional signals generated on the Carrier Board are also routed to the GPIO
expansion port connector X2. As an accessory a GPIO expansion board (part # PCM-988) is made
available through PHYTEC to mate with the X2 connector on the phyCORE-LPC3250 Carrier Board. This
expansion board provides a patch field for easy access to all signals, and additional board space for
testing and prototyping. A summary of the signal mappings between X1, X2, and the patch field on the
GPIO expansion board is provided in Part III.