NXP Semiconductors LPCXpresso4367 User manual

UM10946
LPCXpresso4367/43S67/18S37 Rev B Boards
Rev. 1.0 —18 November 2015
User manual
Document information
Info
Content
Keywords
LPCXpresso4337, LPCXpresso43S37, LPCXpresso43S67, LPC4300,
LPC43S00, LPC43xx, LPC43Sxx
Abstract
LPCXpresso4367/43S67 User Manual

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
2 of 19
Contact information
For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: salesad[email protected]
Revision history
Rev
Date
Description
1.0
20151118
Initial version

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
3 of 19
1. Introduction
The LPCXpresso™ family of boards provides a powerful and flexible development
system for NXP's Cortex®-M family of MCUs. They can be used with a wide range of
development tools, including the NXP’s LPCXpresso IDE. The LPCXpresso4367
(OM13088), LPCXpresso43S67 (OM13084) and Revision B LPCXpresso18S37
(OM13076) boards have been developed by NXP to enable evaluation of and prototyping
with the LPC4300, LPC43S00 and LPC18S00 MCUs respectively, and are based on the
100 pin BGA versions of these MCUs.
Fig 1. LPCXpresso43xx/18xx
This document describes the LPCXpresso4367, LPCXpresso43S67 and
LPCXpresso18S37 board hardware. These boards are functionally identical (using an
underlying Revision B circuit board) with the exception of target MCU and the
inclusion/exclusion of the A7001CM Secure Element device. The name
LPCXpresso4367 is used throughout this document to refer to all boards. The term
“Target MCU” is used to refer to the Target microcontroller (LPC4367, LPC43S67 or
LPC18S37). The following aspects of interfacing to the boards are covered by this guide:
Main board features
Setup for use with development tools
Supporting software drivers
Board interface connector pin out
Jumper settings
Powering the board
Mechanical drawing

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
4 of 19
Note that Revision A LPCXpresso18S37 boards have different circuit designators and
fewer functions. Please refer to User Manual UM10889 for that version of the board. The
board revision is printed on the silkscreen directly below the ISP button (see Fig 1.)
2. Feature summary
The LPCXpresso4367 board includes the following features:
On-board, high-speed USB based, Link2 debug probe with support for ARM’s
CMSIS-DAP and SEGGER J-Link protocol options
Link2 probe can be used with on-board Target MCU or external target
Built-in current measurement
Support for external debug probes
Tri-color LED
Target Reset, ISP and WAKE buttons
Expansion options based on Arduino UNO and PMod™, plus additional expansion
port pins
UART, I2C and SPI port bridging from Target MCU to USB via the on-board debug
probe
FTDI UART connector
8Mb Macronix Quad SPI flash (MX25L8035EM2I-10G)
Ethernet PHY (LAN8720A)
A7001CM Secure Element (LPCXpresso43S67/18S37 only)
2.1 Board layout and settings
This section provides a quick reference guide to the main board components,
configurable items, visual indicators and expansion connectors. The layout of the
components on the LPCXpresso4367 board is shown in Fig 2. Default jumper positions
are shown in red:

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
5 of 19
Fig 2
Fig 2. Board layout
The function of each identified component is listed in Table 1.
Table 1. Connectors, indicators and jumpers
Designator
Description
Reference section
D1
Tri-color LED –Driven by Target MCU. JP6 must be
shunted for +3.3V to be applied to D2 anode. The default
shunt for JP6 is a 0Ω resistor installed at JS17.
n/a
D4
Target MCU BOOT0_LED indicator. Reflects the state of
Target MCU P1_1. When the boot process fails, D1 will
toggle at a 1 Hz rate for 60 seconds. After 60 seconds,
the Target MCU is reset.
n/a
D5
Link2 MCU BOOT0_LED indicator. Reflects the state of
Link2 MCU P1_1. When the boot process fails, D1 will
toggle at a 1 Hz rate for 60 seconds. After 60 seconds,
the Link2 MCU is reset. It will be ON when the Link2
MCU is Booting using DFU (See description for JP6).
n/a
D8
Target MCU Power LED.
n/a
D9
Target MCU Reset LED –this LED is on anytime the
Target RESETn is pulled low.
n/a
D13
Ethernet link active indication (controlled via LAN8729A)
n/a
D11
Ethernet 100Mbps indication (controlled via LAN8729A)
n/a
J1, J2, J6,
J7
Expansion connectors, including Arduino UNO rev3
compatible connectivity.
7
J3
PMod™ (SPI / I2C) Bridge connector. An external
Application Processor (AP) or PMod™ peripheral may be
7

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
6 of 19
Designator
Description
Reference section
connected to the Target MCU SPI0 and I2C0 via this
connector.
J4
Target MCU Power / USB Device/Host connector.
Connect this micro USB A/B-type connector to a +5V
power source when it is desired to power only the Target
MCU, and leave the on-board Link2 debug probe
unpowered. This is useful when an external debug probe
is used to debug the Target MCU.
If this target USB port is being used in a USB Host
configuration (i.e. powering a USB device plugged into
the board), install JP4.
CAUTION: Do not install JP4 when applying external
power to J4.
5
J5
Link2 micro USB B-type connector. Powers both the
Link2 side of the board and Target MCU side of the
board. Power the board from this connector when using
the on-board debug probe to debug the Target MCU.
5
JP1
SWD VREF power selection –3 position jumper pins.
Jumper 1 –2 (default) when on-board Target MCU is
connected to either the on-board Link2 debug probe or
an external debug probe.
Jumper 2 –3 when on-board Link2 debug probe is used
to debug an off-board Target MCU.
5
JP2
Target MCU SWD disable –2-position jumper pins.
Jumper open (default) the Target MCU SWD interface
enabled. Normal operating mode where the Target SWD
is connected to either the on-board Link2 debug probe or
an external debug probe.
Jumper shunted, the Target MCU SWD interface is
disabled and the Target MCU is held in the reset state.
Use this setting only when the on-board Link2 debug
probe is used to debug an off-board Target MCU.
6
JP3, JP5
These jumpers are used to ISP boot select between
booting the Target MCU from the USART, USB or SPI
flash when the ISP button is pressed as the board is
released from Reset. See Section 8.2 for more
information
8.2
JP4
Provides 4.7V power to the Target MCU USB A/B
connector. Install JP4 only when the Target MCU is being
used as a Host USB controller.
CAUTION: Do not install JP4 when the Target MCU is
used as a USB Device or anytime external power is
applied at J4.
n/a
JP6
Link2 force DFU boot –2 position jumper pins.
Jumper open (default) for Link2 to follow the normal boot
sequence. The Link2 will boot from internal flash if image
is found there. With the internal flash erased the Link2
normal boot sequence will fall through to DFU boot.
n/a

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
7 of 19
Designator
Description
Reference section
Jumper shunted to force the Link2 to DFU boot mode.
Use this setting to reprogram the Link2 internal flash with
a new image or to use the LPCXpresso IDE with Redlink
protocol.
JP7, JP9
The on-board current measurement circuitry includes a
choice of two sense resistors for both the Target and I/O
supplies in order to enable more accurate current
measurement when the Target MCU is running in low
power modes. JP7 and JP9 are used to select short a
second sense resistor in the path of the current supplies
of the Target and I/O supplies respectively.
5.1.3
JP8, JP10
A current meter may be installed across JP8 terminals to
measure the Target MCU core current consumption. Pin
1 (square pad) is positive and pin 2 is negative. By
default JP5 is shunted by a 0Ω resistor installed at JS7.
Remove the resistor at JS7 to measure current at JP8.
A current meter may be installed across JP10 terminals
to measure the Target MCU I/O current consumption. Pin
1 (square pad) is positive and pin 2 is negative. By
default JP7 is shunted by a 0Ω resistor installed at JS15.
Remove the resistor at JS15 to measure current at JP7.
5.1.2
P1
10-pin SWD connector –The SWD connector is used to
debug the Target MCU from an external debug probe.
The same SWD connector can also be used to connect
the on-board Link2 debug probe to an off-board Target
MCU (for this JP1 must shunted 2–3, and JP2 must have
a shunt installed).
6
P2, P3
A voltmeter installed across P2 terminals may be used to
measure the voltage across a sense resistor (R66, 200
mohm) in order to determine current flow into the target
MCU. Pin 1 (square pad) is positive and pin 2 is negative.
Similarly, the current flow into the I/O supply of the Target
MCU may be determined by measuring the voltage drop
across a 3 ohm sense resistor (R77) via the P3 terminals.
5.1.1
P4
FTDI serial header. In addition to provide a serial output
from Target MCU, the Target side of the board can be
powered from the FTDI header.
CAUTION: Users must make sure the GND side of the
FTDI cable is connected to PIN1, connecting it in the
reverse might damage the MCU.
4.1
SW1
Target MCU WAKEUP pushbutton. When pressed the
WAKEUP switch will drive Target MCU WAKEUP0 to a
low level, and will wake the part from various
SLEEP/POWER_DOWN modes.
8.3
SW2
Target MCU ISP Bootload enable pushbutton. This
switch drives Target MCU P2_7 low. Holding SW2
pressed while powering up or reseting and the Target
MCU will skip the image in internal flash and proceed
with booting based on JP3 settings..
8.2

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
8 of 19
Designator
Description
Reference section
SW3
Target MCU Reset pushbutton.
8.1
TP1
Ground terminal test point.
n/a
U8
Link2 MCU
n/a
U11
Target MCU
n/a
3. Getting Started
By default, the LPCXpresso4367 is configured to use the on-board debug probe (Link2)
to debug the on-board target (Target MCU). The Link2 is unprogrammed at manufacture,
so will boot into DFU mode. The LPCXpresso IDE (available for free download at
http://www.lpcware.com/lpcxpresso/home) will automatically load the Redlink debug
protocol via DFU, so can be used in the default configuration, i.e. with the Link2 flash
unprogrammed. The Link2 On-board Debug Processor’s flash memory can also be
programmed with CMSIS-DAP or J-link OB protocols using the LPC-Link2 Configuration
Tool (LCT) or LPCScrypt (see http://www.lpcware.com/LPCUtilities for more information.)
To program the Link2 flash, a shunt must be installed at JP6. After programming the
flash, remove JP6 and power cycle the board to force the Link2 to boot with that protocol.
These alternate protocols enable the board to be used with tool chains from vendors
such as Keil, IAR, Atollic, Rowley and SEGGER. Note that the board can also be used
with LPCXpresso IDE when the CMSIS-DAP firmware has been programmed (note that
it may be necessary to manually select SWD instead of JTAG from the debug
configuration.)
Check with your toolchain vendor for availability of specific device support packs for the
LPC4300/43S00/18S00 family of devices.
Installation steps for use with LPCXpresso IDE:
1) Download and install the LPCXpresso IDE (version 7.6.2 or later) installer from
http://www.lpcware.com/lpcxpresso/download.
2) Connect the LPCXpresso4367 board to the USB port of your host computer,
connecting a micro USB cable to connector J5 (“Link”).
3) Download the LPCOpen examples & drivers from
http://www.lpcware.com/content/nxpfile/lpcopen-platform, selecting the version
for the toolchain you are using; project files for LPCXpresso IDE, Keil and IAR
tools are available.
4) Start the LPCXpresso IDE and import the LPCOpen zip file by clicking Import
project(s) in the “Start here panel.”
5) The simplest example is periph_blinky, which will blink the tricolor LED on the
LPCXpresso4367. Click on the periph_blinky in the “Project Explorer” panel, then
click Debug ‘periph_blinky’ in the “Start here” panel. This will build the project
and then launch the debug session.
Note that if the jumper setting of JP6 is changed with the board powered then the USB
connection must be removed and reconnected to J5 in order to force the Link2 to reset
and enter DFU boot mode and force drivers to enumerate on the host computer running
the tools. Redlink protocol is required for multicore debug using the LPCXpresso IDE.

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
9 of 19
Installation steps for use with Keil and IAR tool chains (using CMSIS-DAP or J-Link OB
protocols):
1) Program the firmware of the Link2 using the LCT tool or LPCScrypt, following the
instructions provided for those tools. Note that part of this process will involve
installing device drivers for the board on Windows platforms.
2) Ensuring JP6 is not installed, unplug then reconnect the board to board to the
USB port of your host computer, connecting a micro USB cable to connector J5
(“Link”).
3) Download the LPCOpen examples & drivers from
http://www.lpcware.com/content/nxpfile/lpcopen-platform, selecting the version
for the toolchain you are using; project files for LPCXpresso IDE, Keil and IAR
tools are available.
4) Import the project file.
4. Target MCU Serial ports
By default the Target MCU UART0 is connected to the FTDI header at P4. This can be
used for sending debug messages out to a host computer via a suitable cable. The
Target MCU UART0 can also be connected through a virtual communication port
(VCOM) UART bridge Link2 function to a host computer connected to the USB Link2
(J5).
The Redlink protocol firmware for the Link2 (downloaded by default by the LPCXpresso
IDE) includes UART bridge functionality (VCOM support). A version of the CMSIS-DAP
Link2 firmware is also available with this functionality (called “CMSIS-DAP with bridges”),
and can be programmed into the Link2 using the LPC-Link2 Configuration Tool (LCT),
available at http://www.lpcware.com/LPCUtilities. When running this firmware the default
source of data to the Target MCU RXD is the FTDI header. Once the Link2 receives any
data via the VCOM port of a host computer it will set P2_2 low to select the Link2 UART0
data to the Target MCU. Once the VCOM port has been used it is necessary to power
cycle the board before FTDI connection can be used.
4.1 P4 FTDI header
The FTDI header P4 mates with FTDI cable TTL-232R-3V3. P4 interfaces the Target
MCU UART0 to a Host PC virtual serial port. The P4 location is shown in Fig 2. The pin
out and a description of the signals at P4 are listed in Fig 3. By default there may be no
header installed at P4.
.

NXP Semiconductors
UM10946
LPCXpresso board for LPC4367/43S67/18S37 family of MCUs
UM10946
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 1.0 —18 November 2015
10 of 19
1
2
3
4
5
6
Fig 3. FTDI (P4) Target MCU serial port
Table 2. P4 FTDI interface
Target MCU Signal
FTDI
Signal
Pin #
Direction
GND
GND
1
No connect
CTS
2
Board +5V
5V
3
UART0_RXD
TXD
4
From host
UART0_TXD
RXD
5
To host
No connect
RTS
6