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
).
Loading...
+ 42 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.