NXP JN5189-DK006 Development Kit User Guide

Document Identifier: UM11368

Revision: 2, 11/2020

Chapter 1 Introduction

The JN5189 DK is designed for JN5189 IC evaluation and development. It is very convenient to evaluate JN5189's functions and performance. It also includes useful peripherals like GPIOs and an Arduino interface. J-Link and J-Trace functions are supported for debugging JN5189. The ISP download function is also included and is very easy to use.

1.1 Purpose

This document introduces all functions of the JN5189 DK and describes all parts of the JN5189 DK boards in detail.

1.2 Kit contents

Figure 1. Board overview: This image displays the JN5189 Development Kit, showing the Carrier Main Board (labeled 'Carrier Main Board (DK6 V3)'), a Generic expansion board, and a QN9090 Module (labeled 'QN9090 Module NTAG').

Chapter 2 Carrier Main Board

The OM15076, also known as the DK6 JN5189 carrier board, provides a flexible development system for NXP's JN5189 ultra-low power, high performance wireless microcontroller. It can be used with a wide range of development tools, including NXP's MCUXpresso IDE. It has been developed by NXP to enable evaluation and prototyping with the JN5189_30_T Bluetooth Low Energy wireless microcontroller. The carrier boards (part number: OM15076) supplied in the development kit are physically identical. They are all pre-fitted with an Arduino-compatible expansion board and a JN5189-based module with an integrated antenna.

Figure 2. Carrier Main Board: This image shows the NXP OM15076 Carrier Main Board, highlighting its various connectors, components, and the integrated JN5189 module with an antenna.

2.1 Feature summary

Chapter 2.2 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 JN5189 Carrier board is shown in Figure 3.

Figure 3. Carrier board layout: This image shows a detailed top-down view of the JN5189 Carrier board, highlighting the placement of various components, connectors (e.g., CN1-CN4, J1-J15), jumpers (JP1-JP7), buttons (SW1-SW4, BP1), and LEDs (DS1-DS8).

Table 1. Board Interface Components

Circuit ref Description
D1Link2 LPC4322 BOOT0_LED indicator. Reflects the state of LPC43xx Link2 MCU P1_1. When the boot process fails, D1 will toggle at a 1 Hz rate for 60 seconds. After 60 seconds, the LPC4322 is reset.
DS1JN5189 Power LED
DS2, DS32x Red debug LEDs connected respectively to JN5189 PIO_0 (DS2) and PIO_3 (DS3). LEDs are on anytime the PIO is low.
DS4JN5189 Reset LED – LED is on anytime the Target RESET is pulled low.
DS5, DS6Green LEDs connected respectively to UART0_Tx (DS5) and UART0_Rx (DS6).
DS8In System Programming (ISP) LED indicator. LED is ON when SW2 button is pressed.
IC2Link2 MCU
J2FTDI serial header. In addition to providing a serial output from JN5189, the Target side of the board can be powered from the FTDI header. The JN5189 supports serial ISP boot from the FTDI header.
J332 pins Expansion header connector for debug. All the JN5189 IOs from modules and more are available here.
J14JN5189 VBAT current monitor V sense measurement. The V sense can be measured with a volt meter. Pin 1 (square pad) is positive and pin 2 is negative. JN5189 current is calculated by dividing the measured voltage at J14 by the V sense resistance value of 3.3Ω.
J15Link2 mini USB B-type connector. Powers both the Link2 side of the board and, depending on the JP3, JP5 configuration, the JN5189 Target side of the board. Power the board from this connector when using the on-board debug probe to debug the JN5189 Target MCU.
JP1JN5189 Target SWD disable – 2-position jumper pins. 1. Jumper "ON" (default) enables the JN5189 Target SWD interface. Normal operating mode where the Target SWD is connected to either the on-board Link2 debug probe or an external debug probe. 2. Jumper "OFF" disables the JN5189 Target SWD interface. Use this setting only when the on-board Link2 debug probe is used to debug an off-board Target JN5189.
JP2SWD interface buffer power selection
JP3JN5189 power source selection. 1. Jumper fitted in position pin 1 - 2 (default -5V REG). Power source is either 5V from mini USB connector or FTDI connector, or 4.5V from 3xAAA batteries or 5V from a 7-12V DC power supply connected on J4. 2. Jumper fitted in position pin 2 - 3 (BAT 6V). Power source is 4xAAA batteries. See details on Board power diagram Figure 5.
JP4Jumper to route LPC or FTDI to UART RX0 JN5189 (to change in pair with JP7)
JP5Link2 (LPC4322) force DFU boot – 2 position jumper pins. 1. Jumper open (default) or shunted to boot mode for Link2 to follow the normal boot sequence. The Link2 will boot from internal flash if an image is found there. With the internal flash erased, the Link2 normal boot sequence will fall through to DFU boot. 2. 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 MCUXpresso IDE with CMSIS-DAP protocol.
JP6JP6 is used to isolate the Link2 debug probe (SPI bridge function) from the JN5189 target to prevent leakage current in power critical applications / current consumption analysis. JP6 needs to be fitted in position 1 - 2 to use the SPI bridging function between the JN5189 and Link2. This jumper is not fitted by default.
JP7Jumper to shunt LPC to JN5189 or FTDI to UART TX0 JN5189 (to change in pair with JP4)
CN1, CN2, CN3, CN4Expansion connectors, including Arduino Uno rev3 compatible connectivity.
JM1, JM2JN5189 module headers
P110-pin SWD connector – The SWD connector is used to debug the JN5189 Target 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 be shunted).
BP1User Interface button connected to IO1. Used in some Applications Notes.
SW2In System Programming (ISP) button. JN5189 will enter ISP mode when SW2 is pressed during hardware reset.
SW4JN5189 Reset pushbutton.

To ease board usage and debugging, connector serigraphy is also copied on the PCB bottom. J7, J13, J12 & J11 battery slots are also located here.

Figure 4. OM15076 DK6 PCB bottom view: This image shows the bottom side of the OM15076 DK6 PCB, illustrating component markings and connector locations.

2.3 LED indicators

The DK6 board LED locations are shown in Figure 3. A description of each on-board LED indicator is shown in the next table.

Table 2. LED indicator functions

LED reference Description
D1Link2 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 JP5).
DS1JN5189 Power LED. This LED is on any time power is applied to the JN5189 wireless MCU.
DS2, DS32x Red debug LEDs connected respectively to JN5189 PIO_0 (DS2) and PIO_3 (DS3). LEDs are on anytime the respective PIOs from the JN5189 are pulled low.
DS4JN5189 Reset LED – LED is on anytime the Target RESET is pulled low.
DS5, DS62x Green LEDs connected respectively to UART0_Tx (DS5) and UART0_Rx (DS6). LEDs will flash any time there is activity on the UART0.
DS8In System Programming (ISP) LED indicator. LED is ON when IO5_ISP is pulled low and when SW2 button is pressed.

2.4 ARDUINO connectors

ARDUINO compatible connectors are based on Arduino R3. References on the DK6 board are CN1, CN2, CN3, CN4. The Generic expansion board OM15082 can be plugged into these connectors.

2.5 Buttons

2.5.1 Reset button

This button (SW4) is used to reset the JN5189 (note that the Link2 is NOT reset by this button).

2.5.2 ISP button

This button connects the JN5189_PIO5 (ISP_Entry) pin to ground. This should be used to set the JN5189 in ISP mode to program a binary file into the chip memory. To force entry into this ISP mode, hold down the ISP button (SW2), press and release the Reset button (SW4), then release the ISP button (SW2). This is done automatically when using the DK6 Production Flash programmer with J2 (FTDI USB interface).

2.6 User Interface button

This button (BP1) is connected to JN5189_PIO_1 and should be used as an input.

2.7 JN5189 Serial port

The JN5189 UART0 can also be connected through a virtual communication port (VCOM) UART bridge Link2 function either to a host computer connected to the J2 USB FTDI or to J15 USB Link2. By default, the DK 6 is configured to use the FTDI USB. For Link2 USB: The factory default CMSIS-DAP Link2 image includes UART bridge functionality (VCOM support), and this firmware is also available with the LPCScrypt utility, available at https://www.nxp.com/design/microcontrollers-developer-resources/lpc-microcontroller-utilities:LPC-UTILITIES power connections and measurements. For the USB FTDI, the PC driver is available on FTDI website (the FTDI chip is already configured before the carrier board release).

2.8 Board power connections

A block diagram of the board power tree is shown in Figure 5. When the JN5189 Target is to be debugged from the on-board Link2 probe, the USB mini B-type connector (J15) must be connected to a Host computer. When the JN5189 Target is to be debugged from an external debug probe, instead of the on-board debug probe, the Link USB connector (J15) must be disconnected.

Figure 5. Board power diagram: This diagram illustrates the power distribution pathways for the DK6 board, showing various power sources (USB, batteries, external supply) and their connections to different components via regulators and jumpers.

2.9 Debug Configurations

The DK6 board has a built-in debug probe referred to as "Link2". The JN5189 target wireless MCU can be debugged by the Link2 debugging probe, or from an external debug probe installed at P1. On-board jumpers JP1 and JP2 must be correctly positioned for each mode. The on-board Link2 debug probe is capable of debugging target MCU's with a VDDIO range of 1.6V to 3.6V. Check the sections below for the appropriate jumper settings and how to properly power the board.

2.9.1 Debug using on-board debug probe

To use the on-board Link debug probe:

2.9.2 Debug using external debug probe

To use an external debug probe:

2.9.3 On-Board Link2 flash programming

To program the Link2 Flash, the Link2 MCU must be in DFU mode. If the Link2 already has a valid image in the flash, you will need to force it into DFU mode by placing a jumper shunt on JP5 across pin 1 - 2, then power the board by connecting the mini USB J15 to a host computer. Link2 MCU programming is performed using the LPCScrypt utility (see https://www.nxp.com/design/microcontrollers-developer-resources/lpc-microcontroller-utilities:LPC-UTILITIES). Instructions for using the tool are located at the same web page.

2.9.4 Using the DK6 to debug an off-board target

The DK6 board's Link2 debug probe may be used to debug an off-board target MCU. The on-board Link2 debug probe is capable of debugging target MCU's with a VDDIO range of 1.6V to 3.6V. To keep the on-board target JN5189 MCU from interfering with the SWD interface:

Chapter 3 JN5189 Modules

The JN5189 Module board is the JN5189 minimum system board. The module should be mounted to a carrier board as the target. There is an RF connector on this board, which can be used for RF signal testing.

Figure 6. JN5189 module board: This image shows the JN5189 Module board, a compact PCB featuring the JN5189 chip and an RF connector.

Chapter 4 Generic expansion board

This expansion board is available in the development kit and is compatible with Arduino shields. They are supplied pre-fitted with Arduino-compatible headers for Carrier Boards in the development kit.

The Generic Expansion Board has the following features:

Figure 7. Generic expansion board: This image shows the Generic Expansion Board, featuring a USB port, potentiometer, buttons (SW1-SW4), and expansion headers (CN1-CN4).

Chapter 5 Light expansion board

This expansion board is available in the development kit and is compatible with Arduino shields. They are supplied pre-fitted with Arduino-compatible headers for Carrier Boards in the development kit.

The Generic Expansion Board has the following features:

Figure 8. Lighting expansion board: This image shows the Lighting Expansion Board, featuring multiple sensors and LEDs, connected via Arduino-compatible headers.

Chapter 6 JN5189 USB Dongle

The OM15080-JN5189 can be used as a node in a Zigbee network as a Zigbee Control Bridge, Zigbee Coordinator, or packet sniffer. It can also be used in a Thread wireless network, typically as a dongle for Border Router, Network/Radio Co-Processor (NCP/RCP).

Figure 9. JN5189 USB Dongle: This image shows the JN5189 USB Dongle, a compact USB device designed for Zigbee and Thread networking.

Chapter 7 JN5189 current measurement

The JN5189 current can be measured:

  1. Using the on-board current measurement circuit with MCUXpresso.
  2. Measuring the voltage across a sense resistor (R51) in series with the supply.
  3. Using a current meter on a modified DK6 board or a stand-alone module.

Each of these methods will be described in subsections below. When a board is attached, attempting to measure the lowest possible power requires the JN5189 IO pins to be configured by software to avoid any extra current from the JN5189 IO ports that have external pull-up or pull-down resistors enabled. JP6 should be opened to avoid leakage to the Link2 via the I2C and SPI connections between it and the JN5189.

7.1 Current measurement with MCUXpresso

The DK6 board has an on-board current measurement circuit consisting of a MAX9634T (IC21) current monitor chip and a 12-bit ADC (ADC122S021, IC19) with a 12-bit sample at 50k to 200ksps. The on-board MAX9634T current monitor measures the voltage across the JN5189 VBAT Vsense resistor of 3.3Ω. The MAX9634 multiplies the sense voltage by 25 to provide a voltage range suitable for the ADC to measure. The current measurement circuit is controlled by the debug processor and is not user programmable. Power measurement utilities to use this feature are available in the MCUXpresso IDE installation. Due to input offset voltage variations in the MAX9634, the current measurement circuit is not recommended for measuring current below 150uA.

7.2 Vsense resistor measurement

The voltage across a series 3.3Ω resistor with the target JN5189 VBAT can be manually measured at J14 on the PCB. The voltmeter positive probe is applied to J14 pin 1 (square pad) and the negative probe to J14 pin 2. Use Ohm's law to calculate the current (JN5189 current = measured voltage / 3.3Ω). For example, if the measured voltage is 10mV, then 10e-3 / 3.3 = 3.03mA. Note that the input current to the MAX9634 used in the on-board current measurement will be included in the voltage measured across this resistor.

7.3 Current measurement with a multimeter

Figure 10 shows the circuit for the power supply to the module. The signal VBAT is used to power the JN5189 module.

Figure 10. Power Sensing Circuit: This schematic illustrates the power sensing circuit, including the VBAT connection, a sense resistor (R51), and the power LED (DS1).

This signal goes to the module (JM1.17) and the expansion connector (J3.31).

Figure 11. VBAT Connections: This diagram shows the module connections (JM1, JM2) and the expansion header (J3) pinouts related to VBAT and other signals.

To measure the current using a multimeter, remove R51 and place the multimeter across J14 pins 1 and 2.

Figure 12. R51 Location: This image highlights the location of resistor R51 on the PCB, which is part of the current sensing circuit.

The multimeter will also measure the current taken by the VSENSE line. This signal is used to measure the voltage drop across the 3R3 resistor so that the current consumption results can be shown with MCUXpresso. The current taken from this signal is negligible but can be removed by cutting JS6.

Figure 13. Voltage Sense Circuit: This schematic shows the voltage sense circuit, featuring the MAX9634 current monitor (IC21) and the ADC (IC19).

7.4 IO Considerations

If an expansion board is not fitted, then the following IO lines are connected on the DK6 board. Setting IOs incorrectly in the software will cause current to be consumed, and this should be taken into consideration when measuring current. The following IOs are connected.

Table 3. Connected IOs

Function PIOs Affected Schematic Page number Comment
NTAG10, 114Not connected by default. R45 and R59 are not fitted by default.
User Interface Button14Leave signal high and do not press switch.
DS2 LED04Leave signal high.
DS3 LED34Leave signal high.
QSPI16, 17, 18, 19, 20, 214Negligible affect if QSPI is not used. To completely remove any current consumption, either remove IC3 or remove RX1, 3, 4, 7, 9 and RX11 to disconnect all PIOs.
Bridge SPI0, 1, 2, 3, 77Negligible effect. Remove IC18 and IC24.
UART8,9 (UART 0)
0,1 (UART 1)
7Remove jumpers on JP4 and JP7.
IC2 interface to LPC10, 115Disabled by default. No current draw if DIOS 10 and 11 are high. Cut JS2 and JS11 to remove completely.
Debug Interface12, 13, 146Negligible effect. Cut CH4 to disconnect.
RESET and ISP buttons5, RST7Negligible current drawn if not pressed. See Table for Sleep current measurement.

For sleep current measurements, the following additional changes are required to achieve the datasheet value; otherwise, the result is typically 600nA high.

Table 4. Additional changes

Component Action Schematic Page Comment
R51Remove2Allow connection of a Multimeter across J14.
IC22Remove 3V3OUT7See Section 5.5 below.
D5Remove7Disconnect ISPEN from FTDI device.
C33Remove7Remove capacitor from Reset Line.
R64Remove7Remove Pullup Resistor from ISPEN.
IC21 or cut JS5-6Remove6Disconnect current sense amplifier.
IC11Remove6Disconnect control lines from LPC debug interface.

7.5 Running the DK6 board at different voltages

In order to run the DK6 at different voltages, it is necessary to disconnect the FTDI 3V3OUT signal; otherwise, this will continue to supply 3.3V to the board. The circuit is shown below in Figure 14.

Figure 14. FTDI Interface: This schematic shows the FTDI interface circuit, including the FT230XS chip and its connections for UART and USB.

It is important to leave C49 connected to Pin10 of the FT230A. To achieve this, modify the boards as shown in Figure 15.

Figure 15. 3V3OUT modification: This image shows a modification on the board to disconnect the 3V3OUT signal from the FTDI chip, illustrating the placement of C49 and the FTDI FT230X chip.

Chapter 8 Revision history

Table 5. Revision history

Rev Date Description
020200115Initial release
120200428Added Lighting Expansion and USB Dongle
220201102Update

PDF preview unavailable. Download the PDF instead.

UM11368 Antenna House PDF Output Library 7.0.1600

Related Documents

Preview NXP JN5189(T)/JN5188(T) User Manual: Arm Cortex-M4 Wireless Microcontroller Guide
Comprehensive user manual for NXP's JN5189(T) and JN5188(T) wireless microcontrollers. Covers Arm Cortex-M4 features, Zigbee, Thread, low-power operation, pin configurations, memory maps, and system architecture for IoT and embedded applications.
Preview NXP Kinetis KW41Z Wireless Solutions: BLE and Thread for IoT
Explore NXP's Kinetis KW41Z wireless microcontroller, featuring Bluetooth Low Energy (BLE) and Thread connectivity for the Internet of Things (IoT). Learn about its low-power, secure, and multi-protocol capabilities, supported by comprehensive development tools and hardware.
Preview NXP LPC845 Breakout Board User Manual
User manual for the NXP LPC845 Breakout board, detailing its features, setup, usage with MCUXpresso IDE and third-party tools, debug probe functionality, and board layout for prototyping with LPC84x MCUs.
Preview MCUXpresso IDE User Guide - NXP Semiconductors
A comprehensive user guide for the MCUXpresso Integrated Development Environment (IDE) from NXP Semiconductors. This guide covers features, setup, debugging, and project creation for NXP's ARM-based microcontrollers.
Preview NXP FRDM-MCXA156 Development Board: Quick Start Guide for MCUXpresso
Get started quickly with the NXP FRDM-MCXA156 development board. This guide covers setup, software, expansion boards, and support for the MCUXpresso Developer Experience.
Preview FRDM-MCXC444 Development Board Quick Start Guide | NXP MCUXpresso
Get started quickly with the NXP FRDM-MCXC444 development board. This guide covers setup, accessing software tools, and understanding board features for MCU development with MCUXpresso.
Preview S32K118EVB-Q064 Evaluation Board Schematic and Technical Overview
This document provides a detailed schematic and technical overview of the NXP S32K118EVB-Q064 Evaluation Board, featuring the S32K118 microcontroller, OpenSDA debugging interface, power supply circuits, and various I/O headers for development and testing.
Preview Get Started with the NXP FRDM-MCXN947 Development Board
A comprehensive guide to developing projects on the NXP FRDM-MCXN947 Development Board, covering connectivity, graphics, machine learning, motor control, and sensors.