The Fm+ Development Kit (OM13320) is intended for several different tasks: from a
hands-on introduction, understanding, and use of the I
bus), to I
shows and sales pitches).
The kit has a core Printed-Circuit Board (PCB) assembly, and three add-on PCBs. Other
PCBs are available for advanced use or to support newly-released I
as they are introduced to the market.
The Fm+ Development Kit (OM13320) is supported by a Graphics User Interface (GUI)
software program that runs on a Pe rsonal Com pute r ( PC) u nder the Microso ft Windows 7
Operation System. In some uses the GUI is not required, and the Fm+ Development Kit
(OM13320) can be run as a standalone demonstration, requiring only an external power
adapter (not included).
2. Key features
I2C-bus masters
2
2
C device evaluation, and as a simple product demonstration platfo rm (for trade
Self-contained PCB with two independent I
2
Bus 1: On-card I
C MCU master (NXP LPC1343)
2
C buses
C-bus (Inter-Integrated Circuit
2
C-bus components
Bus 2: NXP LPC Xpresso MCU module (not included), and NXP PCA9665 bus
controller
USB interface to on-card MCU (for connection to a PC running the GUI software)
2
C-bus slaves
I
General Purpose Input/Output (GPIO): PCA9672 (one each on Bus1 and Bus2)
LED driver, with 16 constant current outputs: PCA9955 (with four RGB and four White
LEDs on Bus1)
Accessory sockets
Connectors for up to four daughter cards, each providing power, Bus1 and Bus2 I
2
signals
Connector for the Bus Buffer Board OM13398 (supplied) containing two PCA9617A bus
buffers
2
Connector for a third-party I
C-bus logger or I2C-bus controller (Beagle and Aardvark,
from Total Phase)
2
C buses
I
2
C-bus voltage: jumper select 5 V (external) or 3.3 V (on-card 3.3 V regulator)
I
2
C-bus pull-up resistors: jumper select of ‘high’, ‘med’ or ‘low’ loading
SPI ports: One for on-card MCU, two more for LPC Xpresso
Serial Com Port: EIA232 with voltage level shifter and con nection to the LPC Xpresso
LED blinker: NXP PCA9901 one-wire with on-card LED
INT (Interrupt) and RST (Reset) Bus signal monitor LEDs (buffered)
Logic probe: Utility LEDs (buffered) to monitor signals by user jumper wire connection
External DC input (6 V DC maximum)
Prototype area: Uncommitted 8 × 8 100 mil pitch tie points for end user component
attachment
Test points and ground: for probe attachment to major signals
2
Connection of both I
C buses together (supplied 2-wire jumper)
3. Fm+ development kit quick tour
3.1 Kit contents
UM10741
Fm+ development kit OM13320
Before using the kit for the first time, please familiarize yourself with the various
components listed in Table 1
. See Figure 1.
Remark: Each PCB assembly is shipped in an anti-static bag. After the first use, these
may be discarded to simplify future storage.
Fm+ development board (OM13260)
GPIO target board (OM13303)
PCA9617A bus buffer demo board (OM13398)
Bridge board (OM13399)
Cable, USB Type A to Type B
Ribbon cable, 10 position (bag of two)
Jumper wires with female terminals (bag of ten)
Shorting jumpers (bag of twenty)
Hardware (bag of M3 screws and standoffs)
3.1.1 Box contents
The Fm+ Development Kit (OM13320) contains four PCB assemblies, cables, and loose
hardware. These should be retained in the box for future access. Depending upon the
desired use, some of the PCB assemblies may be attached to each other, either by plug
connection or by ‘stacking’ the GPIO PCB assemblies above the Fm+ Development
Board (OM13260), using the supplied ribbon cables and hardware.
There are four PCB assemblies in the kit. Each has a spe cific function an d n ot all of th em
are used at the same time.
3.2.1 Fm+ Development Board (OM13260)
The large PCB, Figure 2, contains two separate I2C-bus structures, together with
supporting circuitry . Each bus has a bus master, one or more bus slaves, and user options
to change the bus voltage and bus pull-up resistors. Adjusting these changes the
operation of the buses to suit various goals. In addition, the two buses may be linked
together to operate a one I
(supplied) or the Bus Buffer Board OM133998 (supplied). See figure 3.5. Four identical
ports provide access for add-on boards that cont ain additional I
UM10741
Fm+ development kit OM13320
2
C-bus structure. This can be done with a two-wire jumper
Outputs from the GPIO devices on the Fm+ Development Board (OM13260), and those
when using GPIO daughter cards (not supplied in the kit), require the GPIO Target Board
(OM13303). Each one has eight channels of LED indicator and push-button switches for
user input. See Figure 3
Fig 3.OM13303 GPIO target board PCB assembly
3.2.3 PCA9617A bus buffer demo board (OM13398)
Bus buffers bridge two I2C-bus segments, which are provided on the Fm+ Development
Board (OM13260) by Bus1 and Bus2. Bus buffer daughter ca rd s, such as th e PCA9 617 A
Bus Buffer Demo Board (OM13398) (supplied in the kit) can be installed directly on Port E
(CN12). See Figure 4
Some existing Demo Boards used a single row connector with nine pins. To use these
with the Fm+ Development Kit requires the Bridge Board (OM13399, supplied in the kit).
See Figure 5
UM10741
Fm+ development kit OM13320
.
Fig 5.OM13399 bridge board PCB assembly
3.2.5 Daughter cards (not supplied in the kit)
These are not in the OM13230 kit, and should be obtained separately. Daughter cards
hedge against obsolescence so that the Fm+ Development Kit (OM13320) can be used
with future devices by adding newly released daughter cards as they become available.
An example daughter card is shown in Figure 6
4. First time setup: Fm+ development board kit (OM13320)
4.1 Before you begin
To use the Fm+ Development Kit (OM13320) for the first time requires some hardware
setup and installation of both firmware (on the Fm+ Developmen t Board OM13260) and
software on the attached computer.
The following three steps must be completed:
UM10741
1. Install Jumpers on the Fm+ Development Board (OM13260) (see Section 4.3
2. Install Firmware on the Fm+ Development Board (OM13260) (see Section 4 .6
3. Install the NXP GUI Software on the computer to be used with the kit
(see Section 4.7
).
4.2 First time setup of the Fm+ development board (OM13260)
Several jumpers must be installed before using the Fm+ Develop ment Board (OM13260)
PCB. The on-board microcontroller (MCU) must contain the appropriate firmware.
To install the firmware requires the connection to a Personal Computer (PC) running
Microsoft Windows 7/64 Operating System and a USB port.
4.3 OM132680 jumpers
The jumpers and their function are shown in Table 2. Using Figure 7 and the table data,
install the jumpers.
Depending up the intended operation of the Fm+ Development Board (OM1326 0),
Port E (CN12) should be left open, or linked with a jumper wire, or for the attachm ent of a
Bus Buffer Board. The PCA9617A Bus Buf fer Demo Board (OM13398) is supplied in the
kit.
For the purpose of this quick setup section, install the two-wire jumper (supplied) as
shown in Figure 8
Remark: The two-wire jumper requires a twist, as shown. The diagonally opposite pins
are linked.
To prevent damage to the table surface, it is recommended that met a l hardware (supplied
in the kit) is installed in the four mounting holes. This raises the PCB assembly about
6mm. See Figure 9
UM10741
Fm+ development kit OM13320
.
Fig 9.OM13260 mounting hardware
Remark: Save the completed Fm+ Development Board, now install the NXP USB Driver.
The micro on the Fm+ Development Board needs firmware running on it to interface with
the GUI running on a Windows 7 PC over USB. The board is shipped with a blank
microprocessor, so user action is necessary for proper operation.
UM10741
Fm+ development kit OM13320
An installation user manual UM10785 (Ref. 1
the process. A quick overview is presented here.
1. Download NXP_Fm+_Eval_Board_V1_0_firmware.zip from
www.nxp.com/demoboard/OM13320.html#documentation
2. Connect a USB cable from the PC USB port to CN5.
3. Install the Connect (JP3) jumper to connect the USB communications.
4. Install the ISP (JP6) jumper to put the MCU into In-System Programming mode.
5. Install and then remove RST (JP4) jumper to reset the MCU.
6. The MCU will enumerate on the PC as a disk drive called CRP_DISABLD.
7. Delete the file on the MCU (size may vary — up to 32 kB).
8. Copy the new firmware file NXP_Fm_Eval_Board_V1_0.bin, extracted from the
zip file to the MCU.
9. Remove the ISP (JP6) jumper.
10. Install and then remove RST (JP4) jumper to reset the MCU.
) is available at for a complete explanation of
4.7 NXP GUI installat ion
A Graphical User Interface (GUI) is provided which allows easy manipulation of the
devices included on the Fm+ Development Board and ma ny others that can be connected
to the board via daughter cards.
An installation user manual UM10785 (Ref. 1
the process. A quick overview is presented here.
1. Download NXP_Fm_Board_V1_0_Installation.zip from
www.nxp.com/demoboard/OM13320.html#documentation
2. Extract NXP Fm+ Board V1.0 Installation.exe and run.
3. Follow the instruction prompts. Select the default answers.
This GUI uses a USB Human Interface Driver (HID), so no driver installation is required.
If the firmware and GUI installs are successful, an Fm+ Development Board block
diagram is displayed when the GUI executes (Figure 10
The Fm+ Development Board (OM13260) PCB assembly is self- contained, requiring only
DC power to operate. Depending upon the firmware installed on the Fm+ Development
Board (OM13260), it can also operate with a connected Personal Computer (PC) via a
USB cable.
The modular design of the kit and this board in par ticular allows accessory boards to be
easily connected.
5.1 Theory of operation
UM10741
Fm+ development kit OM13320
Fig 10. Fm+ development board bus structure
An I2C-bus requires a Master and one or more Slaves. The two bus signals, clock SCL
and data SDA, are wired-OR and require pull-ups to a DC power supply. Two similar but
separate I
2
C buses each support one Master and at least one Slave device on the bo ard .
The two buses may be linked by either a Bus Buffer Board (OM13398 supplied in the kit)
or a wire jumper, at the Port E connector (CN12).
The signals from both buses are available simultaneously at each of four connectors,
Port A through Port D (CN1 through CN4, respectively). These are intended for
2
attachment of accessory daughter cards, which will be made available as future I
C-bus
devices are released.
The size of the pull-up resistors can be changed by moving shorting jumpers (JP1, JP2,
JP1 1, and JP12), providing selection of ‘Low’ ‘Med’ and ‘High’ resistor values scaled to the
2
C-bus drive strength. When both buses are joine d by a jump er wire, the pull- ups
Fm+ I
are effectively in parallel, and have one-half the stated resistance values.
Operating voltage of the I
that select either 3.3 V or 5 V connected to the pull-up resistors. Compliant I
devices can tolerate 5.5 V (maximum), regardless of the device operating voltage.
2
C-bus depends upon the shorting jumpers (JP13 and JP23)
2
C-bus
NXP Semiconductors
Each bus has a GPIO 8-bit Slave device (PCA9672, IC10 an d IC2 0), an d Bus 1 also has
an LED Driver 16-channel device (PCA9955, IC6). All sixteen outputs are connected to
LEDs, for visual indication. The 8-bit GPIOs require connection of GPIO Target Boards
(OM13303, supplied in the kit) to both indicate the output using eight LEDs and a llow user
input from eight push switches.
An NXP LPC1343 Microcontroller (MCU) serves as both the Bus 1 Master, and the USB
link. The firmware on the MCU can be replaced by the In-System Programming (ISP)
mode, with data sent over the USB link (CN5).
Bus 2 has a Parallel to I
an optional NXP LPC Xpresso module (not supplied). That module is also an I
and connected to Bus 2.
Remark: Although Bus 2 has more than one I
The remaining circuitry is to support the I
PC over a USB link.
UM10741
Fm+ development kit OM13320
2
C-bus Controller device (PCA9665, IC6), which is to be driven by
2
C Master, only one is active at any time.
2
C devices, and provide communications with the
2
C Master
The main operating voltage on th e Fm+ Development Boa rd (OM13260) is 3.3 V supplied
2
from a linear regulator (IC1). Some circuits and the op tional I
C-bus pull-ups may run from
5 V derived either from the USB host (typically a PC) or an AC-DC power supply (not
supplied in the kit). The actual voltage is seldom 5 V, due to cable losses, plus an
additional drop in a series connected diode used to OR the two input s. Wh ichever has th e
highest voltage has priority.
A shunt Zener diode (6.2 V) protects the board from reverse polarity and overvoltage at
the DC Power connector (CN6).
To aid in understanding digital signal levels on the board, two ‘logic probe’ circuits are
provided. These are buffered LEDs (Green, D6 and Red, D7), which light if their
respective inputs (CN11) are grounded.
2
Two global digital signal nets, called INT (interrupt) and RST (reset) connect all I
C-bus
devices on the board and also the Port A – Port E Daughter Card connectors. These are
also connected to the Master (MCU, IC5) on Bus 1, the Master (Bus Controller, IC4), and
the LPC Xpresso module.
2
Remark: The I
only reset the I
The test points provide monitoring of interrup ts (usually generated by I
software reset of Fm+ class I
C global Reset is not the same as the MCU Reset. Resetting the MCU will
2
C-bus if the MCU firmware is intended to create a global reset.
2
2
C-bus devices that have that feature.
C-bus Slaves) and
Additional buffered LEDs are provided (D19, RST and D20, Interrupt) on the Fm+
Development Board (OM13260) for visual indication.
V arious MCU and LPC Xpresso signals are made a vailable through additional connectors.
These include a serial Port (CN7) with EIA232 volta ge level translation (I C2) and SPI Bus
signals (SP0, CN9 and SP1, CN8) from the LPC Xpresso module, together with SPI Bus
(SP2, CN16) from the MCU (IC5).
A prototyping area is provided for solder connection of components that may be required
by an application circuit beyond this board’s design. Power supplies and other sign als are
readily available.
On the Fm+ Development Board (OM13260) V3.0 there is an LED Blinker device
(PCA9901, IC3) and LED indicator (D10), while not strictly an I
one-wire protocol, it belongs to the NXP I
Remark: The PCA9901 will be made obsolete, and will not be present on future versions
of the Fm+ Development Board (OM13260).
The operation of the Fm+ Development Board (OM13260) is greatly enhanced by
third-party tools (not supplied in the kit) that may be attached to either I
dedicated connectors (Bus1, CN17 and Bus2, CN18), labeled ‘TESTER’.
5.2 Circuit description
The schematic diagram has multiple sheets. For clarification, only fragments of the
schematic are shown here. The full schematic should be downloaded if required. The
following pages are divided in to several sections covering the powe r supply, USB
interface, Bus1, Bus2, and support circuits.
5.2.1 Power supply
The Fm+ Development Board (OM13260) operates from DC, either from the USB Host
connector (CN5) or an optional external AC-DC power adapter (not supplied in the kit) via
connector (CN6). See Figure 11
automatic, using ORing diodes (D1 and D2). The main power on the Fm+ Development
Board (OM13260) is 3.3 V from a linear regulator (IC1), but some of the circuits are
powered directly from the incoming supply, which is a nominal 5 V. Linear regulator (IC1)
uses the PCB bottom layer copper as a heat sink. The Fm+ Development Board
(OM13260) external DC input is protected against reverse polarity or overvoltage by
Zener diode (D3). Both input sources are scaled by resistor dividers (R1, R2 and R39,
R40) and fed to the MCU (IC5) Port1 ADC inputs for voltage leve l monitoring. The VBUS
from the USB Host is fed to the MCU Port 0 so that the MCU can detect that a USB
connection is available. Green LED (D4) confirms 5 V, and Green LED (D5) confirms
The USB Host connector (CN5) provides DC power and USB connectivity using the MCU
(IC5) hardware interface, see Figure 12
resistors (R27 and R28) and protected by an ESD network (IC7). To signal to the host that
the USB connection is required, the USB signal DP is pulled to 3.3 V via a resistor (R18)
and a transistor (Q1). USB Connection is contro lled by the MCU (IC5) via signal CON_EN
and can be disabled by removing a jumper (JP3) ‘CONNECT’. Whe n the MCU requests a
USB connection, and the jumper (JP3) is installed, the green LED (D9) is ON. MCU
activity is displayed by the Heart Beat green LED (D8), which is set to blink at about
one per second.
UM10741
Fm+ development kit OM13320
and Figure 13. USB data lines are terminated by
+3V3
IC5G$8
USB_DP
USB_Dm
LPC134X_HVQFN32
14
13
Fig 13. USB interface
5.3 Bus one (Bus1)
R17
820 Ω
D9
10 kΩ
2.2 kΩ
SOFTCONNECT
VBUS
Q1
PDTA123YT
R18
1.5 kΩ
GND
DP
DM
VBUS
GND
GND
5
GND
6
CN5-3
CN5-2
CN5-1
CN5-4
LTST-C170KGKT GRN
R27
R28
33 Ω
33 Ω
GND
D8
CONFIG
USB_LED
CON_EN
IC7
2
IO1
1
GND
PRTR5V0U2X
R20
820 Ω
LTST-C170KGKT GRN
JP3-1
USB_CONNECT
3
IO2
4
VCC
CONNECT
JP3-2
USB PORTUSB INTERFACE
aaa-011873
There are two almost identical I2C buses on the Fm+ Development Board (OM13260),
called Bus1 and Bus2. These share a ground and power connection but may be operated
independently.
2
Remark: The bus voltage for each I
2
I
C-bus, 5 V for the other I2C-bus).
C may be different (for example 3.3 V for one
5.3.1 Bus1 master (MCU LPC1343)
Microcontroller (MCU) (LPC1343, IC5) serves as the Bus1 Master and the USB Bridge.
Firmware installed on the Fm+ Development Board (OM13260) is stored in non-volatile
memory, which has a limit of 32 kB. The MCU may be programmed through the USB por t
or the JTAG connector (CN 19), using Single Wire Debug (SWD), see Figure 14
The HVQN32 package has a thermal pad grou nd connection, and ope rates from the main
3.3 V supply. The MCU operates with a 12.00 MHz crystal controlled oscillator. The
frequency value and accuracy is necessary for correct USB timing (see Figure 18
).
NXP Semiconductors
LPC134X_HVQFN32
GND9
GND8
GND7
GND6
GND5
GND4
GND3
GND2
GND1
IC5G$7
UM10741
Fm+ development kit OM13320
LPC134X_HVQFN32
4
XTALIN
XTALOUT
41
40
39
38
37
36
35
34
33
GND
LPC134X_HVQFN32
VDDIO_EXT_1
VDDMAIN_EXT
IC5G$6
5
IC5G$5
15 pF
6
29
C8
GND
C9
100 nF
12 MHz
GND
XE1
NX5032GA
GND
+3V3
GND
aaa-011877
C7
15 pF
C6
100 nF
Fig 18. IC5 MCU Port1, oscillator and power supply
5.3.2 Bus1 pull-up resistors
The Bus1 is pulled up to either the 3.3 V or 5 V supplies via JP13. Three different value
pull-up resistors are provided by jumper selection, JP11 and JP12. The values of the
pull-up resistors are shown in Table 3
SDA signal lines. Bus2 has a similar arrangement. See Figure 19
Bus1 is also used to control the LED Driver (PCA9955, IC6). Th e LED Driver has constant
current outputs and is directly connected to the LEDs, without customary series resistors.
The LEDs are powered directly from the 5 V supply, thus avoiding further power
dissipation in the 3.3 V linear regulator, IC1. The sixteen channels drive eight LED
clusters consisting of four White LEDs (LED12 – LED15) and four RGB LED clusters
(LED0 – LED11). The maximum current available for each channel is set by R35 and the
variable resistor R36. The LEDs use the PCB top metal for heat dissipation, the LED
driver is in the HTSSOP28 package has a thermal pad ground connection, and operates
from the main 3.3 V supply. See Figure 21
Operation of all sixteen LEDs at maximum current will overheat the LED driver, which is
protected by an internal thermal limiter. The device will shut down and recover when the
temperature has fallen.
When powered from the USB port (CN5) the USB Host is typically limited to 500 mA, and
it will shut down before the LEDs reach maximum current. Operation from an external DC
power supply connection (CN6) is required to drive the LEDs to the maximum current per
channel of 57 mA, for a total of approximately 1 A.
User manualRev. 1 — 1 April 2014 22 of 61
Fig 22. Bus1 LED driv er 16-channel section
NXP Semiconductors
The recommended AC-DC adapter is Digikey PN: 62-1132-ND (not supplied).
See Figure 23
UM10741
Fm+ development kit OM13320
.
Fig 23. AC-DC adapter, 6 V, 2 A
The Slave address is set by JP5, summarized in Table 4. Remark: The PCB is marked with hexadecimal (8-bit) address data, but data sheets and
the NXP GUI use the 7-bit address values. See Table 4
The GPIO (PCA9672, IC10) is connected to Bus1, and provides eight input/output
channels at CN10. Jumper JP10 sets the device address to one of four options,
depending on whether the A0 pin is connected to GND, V
similar arrangement for a second GPIO (PCA9672, IC20). See Figure 24
Remark: The PCB is marked with hexadecimal (8-bit) address data, but data sheets and
the NXP GUI use the 7-bit address values. This is summarized in Table 5
The second I2C bus on the Fm+ Development Board (OM13260) requires the addition of
an NXP LPC Xpresso Module (not included in the kit) to either be the Master, or drive the
bus controller (PCA9665, IC4).
There are two almost identical I
called Bus1 and Bus2. These share a ground and power connection, but may be o perated
independently.
Remark: The bus voltage for each I
5 V for the other I
5.4.1 Bus2 master (LPC Xpresso — MCU LPC1343)
The LPC Xpresso Module contains an NXP LPC1343 MCU (similar to the one on Bus 1)
and support circuits called LPC-Link. See Figure 26
that is loaded through either the LPC-Link and USB Bridge, or JTAG Single Wire Debug
(SWD) connector.
Remark: The LPC Xpresso is not compatible with the NXP GUI, and requires the
installation of an IDE for code development.
2
C bus).
UM10741
Fm+ development kit OM13320
2
C buses on the Fm+ Development Board (OM13260),
2
C maybe different (for example 3.3 V for one I2C bus,
. The LPC Xpresso requires firmware
Fig 26. Fm+ development board with LPC Xpresso installed
The LPC-Link may be powered from the Fm+ Development Board (OM13260), or from a
USB Host (connected to the LPC-Link port). There is a possible conflict that the LC P-Link
3.3 V supply will compete with the Fm+ Development Board (OM13260) 3.3 V supply.
To avoid this issue the LPC Xpresso Module can provide its own 3.3 V power by removing
jumper JP1 on the Fm+ Development Board (OM13260). See Figure 27
2
C Bus2 is connected to the MCU Port0 via RC edge rate control networks that provide
I
bus fall time control (SCL2: R45 and C23; SDA1: R44 and C19). See Figure 28
A second Bus Master is connected to Bus2 using a dedicated Bus Controller device
(PCA9665 Fm+ parallel bus to I
connected to the LPC Xpresso module (LPC1343 PIO2 and PIO3). The I
2
C-bus controller) (IC4). The parallel port side is
2
C side is
connected via RC edge rate control networks that provide bus fall time control (SCL2: R47
and C21; SDA2: R46 and C22). See Figure 29
The Bus2 is pulled up to either the 3.3 V or 5 V supplies, via JP23. Three different value
pull-up resistors are provided by jumper selection, JP21 and JP22. The values of the
pull-up resistors are shown in Table 6
SDA signal lines. See Figure 31
Section 5.3.2
UM10741
Fm+ development kit OM13320
. Separate pull-ups are provided for the SCL and
and Figure 32. Bus1 has a similar arrangement (see
Accessory circuit cards called Daughter Cards may be att ached to any ports (P ort A – Port
D), connectors CN1 – CN4 respectively, see Figure 34
signals, regardless of physical location. Daughter Cards have jumpers to select whether
connection to Bus1 or Bus2 is required. Port A is shown in Figure 33
identical, and effectively in parallel.
UM10741
Fm+ development kit OM13320
. Each port carries the same
; Port B – Port D are
Fig 33. Port A
SCL1
SDA2
INT
RESET
+5V
+3V3
GND
GND
+3V3
+5V
RESET
INT
SDA1
SCL2
CN1-14
CN1-13
CN1-12
CN1-11
CN1-10
CN1-9
CN1-8
CN1-7
CN1-6
CN1-5
CN1-4
CN1-3
CN1-2
CN1-1
SCL BUS1
SDA BUS2
INT
RESET
+5V
+3V3
GND
GND
+3V3
+5V
RESET
INT
SDA BUS1
SCL BUS2
aaa-012042
Fig 34. Daughter ca rd connectors (Port A and Port B shown)
The two independent I2C Buses (Bus1 and Bus2) can be joined electrically to create a
single I
2
C-bus. The link may be made by wire jumper or by an add-on board with an I2C
Bus Buffer device installed. The PCA9617A Bus Buffer Demo Board (OM13398) (supplied
in the kit) is an example. The Fm+ Development Board (OM13260) may also be operated
with nothing connected to Port E (CN12).
The Port E signal pins are arranged to be symmetrical, permitting the card to be rotated
180°, effectively changing the direction of the signals th rough the ca rd. See Figure 35
Figure 36
.
Remark: When linked together by wire jumper, the pull-up resistors on each bus are
effectively in parallel. The resulting value is therefore one-half of the original value. Pull-up
The LCP Xpresso module has a serial comms (communications) port, EIA232 standards
compliant using IC2, a voltage level translator. See Figure 40
connection to I
2
C Bridge devices that require Serial Communications.
To save space on the PCB, a small mini-DIN connector (CN7) replaces the standar d 9-pin
DE shell connector . For connection to standard serial comms cables an adapter is
required, see Figure 41
PN: AE1393-ND (not supplied) See Figure 42
. The recommended Mini-DIN to DE-9 Adapter is Digikey
Both the Bus1 Master MCU and the Bus2 Master LPC Xpress o Mo d ule suppo rt SPI
communications. The Bus1 MCU has one SPI port (SPI2) (CN16) and the LPC Xpresso
has two SPI ports (SPI0 and SPI1) (CN9 and CN8, respectively). See Figure 43
Figure 44
the tester connector (for third-party tools) with the SPI ports.
UM10741
Fm+ development kit OM13320
,
and Figure 45. Also refer to Section 9 of this user manual for details on using
Most of the I2C-bus slaves produce logic signals on their input/output ports. It is necessa ry
to know a logic state. To facilitate this test there are two LEDs with buffers that may be
used as a simple ‘logic probe’.
UM10741
Fm+ development kit OM13320
To prevent circuit loading the LEDs are buffered by FETs as shown in Figure 46
. Green
LED (D6) is driven by FET (Q2) when CN11-1 is at or near ground. When CN11-1 is open
(or logic 1) the FET is non-conducting, and the LED is off. Red LED (D7) is driven by FET
(Q3) when CN11-4 is at or near ground. When CN11-4 is open (or logic 1) the FET is
non-conducting, and the LED is off. See Figure 47
Note that the threshold voltage (V
) of the FET is 2.5 V to 4.5 V to ensure it operates
th
.
correctly on both 3.3 V and 5 V logic levels. The FET source is tied to 5 V, and the gate
must therefore be at 2.5 V or lower relative to ground, to turn on the FET and light the
LED.
Fig 47. Logic probe section (shown monitoring two GPIO channels from Bus1)
5.11 INT and RST indicators
Two global digital signal nets, called INT (interrupt) and RST (reset), connect all I2C-bus
devices on the board and also the Port A – Port E daughter card connectors. These are
also connected to the Master (MCU, IC5) on Bus1, the Master (Bus Controller, IC4), and
the LPC Xpresso module. See Figure 48
Additional buffered LEDs are provided (D19, RST and D20, Interrupt) on the Fm+
Development Board (OM13260) for visual indication. These buffered LEDs operate in the
same fashion as the logic probe (see Section 5.10 “
Additional circuits may be required to for an application beyond the intended scope of the
Fm+ Development Board (OM13260). For e xample, using dif f erent value p ull-up resistors
than those supplied, or other circuit experiments.
The prototype area is available, and consists of pads and holes on a 100 mil (2.54 mm)
grid. Power for these components is made available at several connector points (CN15 is
ground, CN21 is +3.3 V, and CN22 is +5 V). See Figure 50
On the Fm+ Development Board (OM13260) V3.0 there is an LED Blinker device
(PCA9901, IC3) and LED indicator (D10). While not strictly an I
one-wire protocol, it belongs to the NXP I
2
C-bus product portfolio.
2
C-bus device, as it uses a
Remark: The PCA9901 will be made obsolete, and will not be present on future versions
of the Fm+ Development Board (OM13260).
Refer to the PCA9901 data sheet for det ails of th is device. Note that it is not connected to
2
either I
C Bus on the Fm+ Development Board (OM13260). It is connected to the LPC
Xpresso module (PIO_0.7), and that module must be present (and programmed) to drive
the PCA9901 device. See Figure 52
The GPIO Target Board (OM13303) is used to monitor the Input/Output (I/O) signals from
a GPIO. The board has eight channels, each with a push switch and an LED indicator.
See Figure 54
Each of the eight channels operates independently and in the same way. The voltage
applied to the input pin is compared in a Windows comparator, which in tur n drives a d ua l
color LED. The thresholds for the comparators are set to one-third (logic zero) and
two-thirds (logic one) of the supply voltage. These values correspond to the I
threshold voltages for the I
2
C-bus specification.
2
C-bus logic
When a push button is pressed, a logic zero is applied the channel, which can be r ead by
the GPIO device to which the GPIO Target Board is attached. A 2 × 5 header is used to
connect to the Fm+ Development Board (OM13260) or a GPIO daughter card with a flat
ribbon cable (supplied in the kit).
Two connectors are installed, one on each end of the board, and on opposite sides of the
PCB to aid in connection without the cables blocking the buttons or LEDs.
There are no option jumpers and no adjustments on the GPIO Target Board (OM13303).
Unlike other PCB assemblies in the Fm+ Development Kit (OM13320), the GPIO Target
Board (OM13303) has components on both sides of the PCB. See Figure 55
The schematic diagram has multiple sheets. For clarification, only fragments of the
schematic are shown here. The full schematic should be downloaded if required. The
following pages are divided in to several sections covering the win dow comparator, push
switches, bias circuit, and connectors.
6.2.1 Window comparator
Channel 0 is shown; channels 1 through 7 are identical. The input signal is applied to two
comparators, (IC01A and IC01B).
UM10741
Fm+ development kit OM13320
If the input (IO0) is higher than the threshold set by V
and resistor divider (R03 and
IH
R04), the output of the comparator (IC01A) switches to near ground. This turns on the
green LED (D01). Resistor (R04) applies positive feedback hysteresis (about 150 mV) to
the comparator, shifting the trip point to a slightly lower voltage, to stop the circuit from
oscillation around the switch point.
The input (IO0) is attenuated slightly by a resistor divider (R07 and R08), if the resulting
voltage is lower than the threshold set by V
, the output of the comparator (IC1B)
IL
switches to near ground. This turns on the red LED (D01). Resistor (R08) applies positive
feedback hysteresis (about 125 mV) to the comparator, shifting the trip point to a slightly
higher voltage, to stop the circuit from oscillation around the switch point.
LED current is limited by resistors R05 and R09, which are selected to give approximately
equal brightness to the green and red LED elements. See Figure 56
.
The operation of the window circuit is shown by applying a ramp waveform, see Figure 57
and Figure 58
Each channel has a push switch (S01 through S71) that connects the appropriate IO pin
to ground when pressed. Series resistors (R01 th rough R71) lim it the current, in the event
that the IO pin is being driven HIGH (by the connected GPIO device) when the push
switch is closed. Each input is biased to VC (one-half the supply volt age), in the event that
the IO pin is left open. This extinguishes both the green and red LEDs of that channel,
preventing false readings. See Figure 59
UM10741
Fm+ development kit OM13320
.
VC
R102
IO0
R01
1
2
3
4
S01
GND
Fig 59. Push switches
6.2.3 Bias circuit
Each channel requires three reference voltag es (VL, VC, and VH), from the bias circuit.
A resistor divider chain (R01, R02, R0 3, and R04) divides the supply voltage to produce
one-third (VL), one half (VC) and two-thirds (VH). Each value is buffered by an op amp
(sections of IC80). Test points are provided as PCB pads for VH (high), VC (center), and
VL (low). The fourth section of the quad op amp (IC80) is not used. Noise spikes on each
bias supply are removed by capacitors (C89, C90, and C91), powe r supply variations are
removed by capacitors (C86 and C87). See Figure 60
The GPIO Target Board (OM13303) is intended to be connected to the Fm+ Development
Board (OM13260) (or other GPIO daughter cards) via a 10-pin ribbon cable. There are
two identical connectors, one on each end of the GPIO Target Board to allow connection
without blocking the push switches or the LEDs. See Figure 61
Two identical bus buffer devices are connected in series between the Bus1 and Bus2
segments on the Fm+ Development Board (OM13260). Ea ch Bus Buf fer has two identica l
channels, one for I
will be described in detail.
UM10741
Fm+ development kit OM13320
2
C clock (SCL) and the second for I2C data (SDA). Only one channel
Each PCA9617A bus buffer device has two p ower supply conn ections, V
to allow voltage level shifting between one I
2
C-bus segment and another I2C-bus
CC(A)
segment. Jumpers on the Bus Buffer Boar d ( OM133 98 ) select th e voltage source of each
of the two device power supplies. To demonstrate the voltage level translator ability the
link between the two bus buffers is supplied from a variable voltage regulator, which in
turn can be set by the user anywhere between 1.0 V and 3.2 V.
The pull-up resistor on the Low Voltage Bus section is selected by jumpers.
7.2 Circuit description
The schematic diagram has multiple sheets. For clarification, only fragments of the
schematic are shown here. The full schematic should be downloaded if required. The
following pages are divided in to several sections covering the Bu s1 Bus Buf fer, Bus2 Bus
Buffer, Supply select jumpers, Adjustable Voltage Regulator , and Connectors. A block
diagram will assist understanding. See Figure 66
5 V
ADJUSTABLE
VOLTAGE
REGULATOR
1.0 V to 3.2 V
V
CC(B)
V
V
CC(A)
JP2
CC(A)
3.3 V
PULL-UP
RESISTORS
V
CC(A)
.
5 V
JP1
3.3 V
V
CC(B)
V
CC(A)
V
CC(B)
and V
CC(B)
,
BUS1
BA
PCA9617A
low
voltage
bus
AB
PCA9617A
BUS2
aaa-012142
Fig 66. Block diagram for the bus buffer board (OM13398)
I2C-bus signals from the Fm+ Development Board (OM13260), called SCL1 an d SDA1,
are applied to the high voltage or ‘B’ Side of IC1 (PCA9617A). The required pull-up
resistors on this section of Bus1 are on the Fm+ Development Board (OM13260).
Signals on the low voltage or ‘A’ Side of IC1 are connected to a selection of pull-up
resistors selected by either JP5 (for SCL) or JP3 (for SDA), and the low voltage or ‘A’ Side
of the second PCA9617A, IC3.
Loading capacitors, C31 for SCL and C51 SDA, can be place d on the low voltage section
of the bus. To accommodate two different footprints IC1 (TSSOP8) and IC2 (HWSON8)
are connected in parallel, but only one part is installed. Installing JP4 disables the Bus
Buffer. See Figure 67
I2C-bus signals on the low voltage bus are also connected to the A side of the second
PCA9617A Bus Buffer device, IC3. To accommodate two different footprints, IC3
(TSSOP8) and IC4 (HWSON8) are connected in parallel, but only one device is installed.
Installing JP6 disables the bus buffer. See Figure 68
2
C-bus signals from the high voltage or ‘B’ side of IC3 (PCA9617A) are passed back to
I
the Fm+ Development Board (OM13260). The required pull-up resistors on this section of
Bus1 are on the Fm+ Development Board (OM13260).
The ‘B Side’ (high voltage side of the voltage level translator) of each PCA9617A can be
either 3.3 V or 5 V as selected by JP1. The ‘A Side’ (low voltage side of the voltage level
translator) of each PCA9617A can be either 3.3 V or a var iable voltage between 1.0 V and
The low voltage bus bias is generated by an LDO (Low Drop Out) voltage regulator, IC5.
The output voltage is set by resistor divider R3, R4, and R5, and provides a range of 1.0 V
to 3.2 V. The LDO provides a ‘Power Good’ signal, which is pulled HIGH by R6, and
buffered by Q1. When the LDO is working correctly, the blue LED (D2) is turned ON.
See Figure 69
NXP Semiconductors
aaa-012146
CN1-14
SCL1
CN1-13
CN1-12
INT
CN1-11
RESET
CN1-10
+5V
CN1-9
+3V3
CN1-8
CN1-7
GND
CN1-6
+3V3
CN1-5
+5V
SDA2
GND
CN1-4
CN1-3
INT
CN1-2
SDA1
CN1-1
SCL2
RESET
Fm+ BOARD PORT E
aaa-012147
135791113
2468101214
SCL2
INT
5V
GND
3V3
RESET
SDA2
SDA1
RESET
3V3
GND
5V
INT
SCL1
7.2.5 Connector
The connector on the Bus Buffer Board (OM13398) matches the Port E connector on the
Fm+ Development Board (OM13260). See Figure 70
The signals are arranged to be symmetrical so that the Bus Buffer Board (OM13398) can
be rotated 180°, causing the signals from the Fm+ Development Board (OM13260) to flow
in the opposite direction. For example, from Bu s1 to Bus2, or from Bus2 to Bus1 when the
Bus Buffer Board (OM13398) is rotated in th e Port E connector . See Figure 71
to reverse the signal flow is necessary when examining differ ent I
one NXP device to a non-NXP device.
The Bridge Board is mostly a mechanical platform for the old style with a 9-pin, in-line,
non-polarized connector of NXP designed I
position connector. Previous NXP I
2
C demo boards were released with both vertical and
2
C demo boards that use a non-polarized nine
horizontal mounting, and both male pins and female sockets. The Bridge Board
(OM13399) therefore has both styles. There is also a ‘Tester’ connector that allows direct
connection of the third-party tools (see Section 9
non-polarized nine-circuit connector had only one I
). The old style with a 9-pin, in-line,
2
C-bus, with SCL and SDA signals.
The Fm+ Development Board Daughter Card ports have two I
signals. One or other I
2
C Bus can be selected by jumpers. The power source may also be
selected by jumper.
8.2 Circuit description
The schematic diagram has a single sheet. For clarification, only fragments of the
schematic are shown here. The full schematic should be downloaded if required. The
circuit is simple.
8.2.1 Fm+ development board (OM13260) connector (CN3)
CN3-14
CN3-13
CN3-12
CN3-11
CN3-10
CN3-9
CN3-8
CN3-7
CN3-6
CN3-5
CN3-4
CN3-3
CN3-2
CN3-1
Fm+ BOARD
SCL1
SDA2
INT
RESET
+5V
+3V3
GND
GND
+3V3
+5V
RESET
INT
SDA1
SCL2
SCL
SDA
2
C Buses (Bus1 and Bus2)
JP2-3
JP2-2
JP2-1
JP3-3
JP3-2
JP3-1
SEL Fm+ BUS
1
2
1
2
aaa-012148
Fig 74. Fm+ development board (OM13260) connector (CN3)
The connector on the Bridge Board (OM13399) matches the Port connectors on the
Fm+ Development Board (OM13260) See Figure 74
. A Bridge Board (OM13399) can be
attached to any Port A – Port D inclusive. It cannot be connected to Port E due to
mechanical arrangement of the Port E connector.
2
The Fm+ Development Board has two separate I
C buses (Bus1 and Bus2) and one of
these is selected by two jumpers, JP2 for SCL and JP3 for SDA.
There are two power sources available to the Bridge Board (OM13399) depending upon
whether it is connected to the Fm+ Development Board (OM13260) or powered by a
third-party tool (see Section 9
UM10741
Fm+ development kit OM13320
).
The Tester socket provides 5 V and the Fm+ Development Board (OM13260) provides
both 3.3 V or 5 V. Jumper JP1 selects the source of the 5 V power. JP4 selects either
3.3 V or 5 V as needed.
Remark: When the Bridge Board (OM13399) is not attached to the Fm+ Development
Board and powered by the Tester, the only option is 5 V.
Two 9-position connectors are provided; both carry exactly the same signals. CN1 is
female, CN2 is male.
Remark: These connectors are not polarized or keyed. Take care to make connection
correctly.
NXP Semiconductors
aaa-012151
CN4-10
GND
CN4-9
CN4-8
CN4-7
CN4-6
5V_TSTR
CN4-5
CN4-4
CN4-3
SDA
CN4-2
GND
CN4-1
SCL
I2C TESTER
PWR
aaa-012152
RESET
INT
R5
10 kΩ
GND
D2
R2
820 Ω
VDD
INT
LTST-C150KRKT(RED)
D1
R1
820 Ω
VDD
LTST-C150KGKT(GRN)
VDD1
SDA
SCL
R3
10 kΩ
VDD
R4
10 kΩ
VDD
8.2.4 Tester connector (CN4)
Fig 77. Tester connection (CN4)
The 10-position (2 × 5) shrouded header connector (CN4) mates with third-party tools
(see Section 9
UM10741
Fm+ development kit OM13320
). Only I2C-bus signals and available 5 V power ar e co nn ec te d.
Remark: The Tester’s bus signals are connected to the two 9-position connectors and,
depending upon the position of JP2 and JP3, to the Fm+ Development Board Bus1 or
2
Bus2. Take care to avoid double termination of the I
Two LEDs provide indication of power (D1, Green) and INT (interrupt) status (D2, Red). To
prevent malfunction of the I
does not have pull-up on either SCL or SDA, there are weak pull-ups (R3, R4). These may
2
C-bus if the Bridge Board (OM13399) is used in manner that
be replaced with lower value resistors (or removed), as needed.
NXP Semiconductors
8.3 Example using PCA9632 (OM13269)
UM10741
Fm+ development kit OM13320
Fig 79. Bridge boar d (OM13399) used to attach a PCA9632 (OM13269)
The Bridge Board (OM13399) (supplied in the kit) provides attachment of old style with a
9-pin, in-line, non-polarized connector NXP designed I
Generation, inspection and logging of I2C-bus data is easily achieved with third-party
development tools from a number of suppliers: SB Solutions, Inc. (www.i2ctools.com
Total Phase (www.totalphase.com
SB Solutions supplies a range of tools driven from USB and outputs to I
user interface is very similar to the Fm+ Development Board GUI, and a DLL is provided
for custom development. These tools are not supplied in the kit, and must be purchased
directly from the vendor.
Total Phase supplies two tools called Aardvark (host adapter) and Beagle (bus logger)
that connect directly to the Fm+ Development Board (OM13260). These tools are not
supplied in the kit, and must be purchased directly from the vendor.
UM10741
Fm+ development kit OM13320
) and
).
2
C and SPI. The
Fig 80. SB Solutions USB-to-I2C Pro connected to an Fm+ Develop ment Board
daughter card
Fig 81. Aardvark Host Adapter connected to the Fm+ development board (OM13260)
DLLDynamic Link Library
EVMEvaluation Module
FETField-Effect Transistor
Fm+Fast-mode Plus
GPIOGeneral Purpose Input/Output
GUIGraphical User Interface
HIDHuman Interface Driver
2
C-busInter-Integrated Circuit-bus
I
I/OInput/Output
ISPIn-System Programmable
JTAGJoint Test Action Group
LDOLow Drop-Out
LEDLight-Emitting Diode
MCUMicroController Unit
OSOperating System
PCPersonal Computer
PCBPrinted-Circuit Board
RCResistor-Capacitor network
RGBRed/Green/Blue
SPISerial Peripheral Interface
SWDSingle Wire Debug
USBUniversal Serial Port
Draft — The document is a draft version only. The content is still under
internal review and subject to formal approval, which may result in
modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included herein and shall have no liability for the consequences of
use of such information.
12.2 Disclaimers
Limited warranty and liability — Information in this document is believed to
be accurate and reliable. However, NXP Semiconductors does not give any
representations or warranties, expressed or implied, as to the accuracy or
completeness of such information and shall have no liability for the
consequences of use of such information. NXP Semiconductors takes no
responsibility for the content in this document if provided by an information
source outside of NXP Semiconductors.
In no event shall NXP Semiconductors be liable for any indirect, incidental,
punitive, special or consequential damages (including - without limitation - lost
profits, lost savings, business interruption, costs related to the removal or
replacement of any products or rework charges) whether or not such
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory.
Notwithstanding any damages that customer might incur for any reason
whatsoever, NXP Semi conductors’ aggregat e and cumulative liabil ity towards
customer for the products described herein shall be limited in accordance
with the Terms and conditions of commercial sale of NXP Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to make
changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
to the publication hereof.
Suitability for use — NXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-critical or
safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonably be expected
to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors and its suppliers accept no liability for
inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the cu stomer’s own
risk.
Applications — Applications that are described herein for any of these
products are for illustrative purposes only. NXP Semiconduct ors makes no
representation or warranty that such applications will be suitable for the
specified use without further testing or modification.
Customers are responsible for the design and operation of their applications
and products using NXP Semiconductors product s, and NXP Semiconductors
accepts no liability for any assistance with applications or customer product
design. It is customer’s sole responsibility to determine whether the NXP
Semiconductors product is suitable and fit for the customer’s applications and
products planned, as well as for the planned application and use of
customer’s third party customer(s). Customers should provide appropriate
design and operating safeguards to minimize the risks associated with their
applications and products.
NXP Semiconductors does not accept any liability related to any default ,
damage, costs or problem which is based on any weakness or default in the
customer’s applications or products, or the application or use by customer’s
third party customer(s). Customer is responsible for doing all necessary
testing for the customer’s applications and products using NXP
Semiconductors products in order to avoid a default of the applications and
the products or of the application or use by customer’s third part y
customer(s). NXP does not accept any liability in this respect.
Export control — This document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
authorization from competent authorities.
Evaluation products — This product is provided on an “as is” and “with all
faults” basis for evaluation purposes only. NXP Semiconductors, its affiliates
and their suppliers expressly disclaim all warranties, whet her express, implied
or statutory, including but not limited to the implied warranties of
non-infringement, merchantability and fitness for a particular purpose. The
entire risk as to the quality, or arising out of the use or performance, of this
product remains with customer.
In no event shall NXP Semiconductors, its affiliates or their su ppliers be liable
to customer for any special, indirect, consequential, punitive or incidental
damages (including without limitation damages for l oss of bu siness, busi ness
interruption, loss of use, loss of data or information, and the like) arising out
the use of or inability to use the product, whether or not based on tort
(including negligence), strict liability, breach of contract, breach of warranty or
any other theory , even if advised of the possibility of such damages.
Notwithstanding any damages that customer might incur for any reason
whatsoever (including without limitation, all damages referenced above and
all direct or general damages), the entire liability of NXP Semiconductors, its
affiliates and their suppliers and customer’s exclusive remedy for all of the
foregoing shall be limited to actual damages incurred by customer based on
reasonable reliance up to the greater of the amount actually paid by customer
for the product or five dollars (US$5.00). The foregoin g limita tions, exclusions
and disclaimers shall apply to the maximum extent permitted by applicable
law, even if any remedy fails of its essential purpose.
Translations — A non-English (translated) version of a document is for
reference only. The English version shall prevail in case of any discrepancy
between the translated and English versions.
12.3 Trademarks
Notice: All referenced brands, prod uct names, service names and trademarks
are the property of their respective owners.
2
I
C-bus — logo is a trademark of NXP Semiconductors N.V.
Please be aware that important notices concerning th is document and the product(s)
described herein, have been included in section ‘Legal information’.