NXP Semiconductors
UM11079
IoT Module base board
UM11079_OM40006.docm
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2017, 2018. All rights reserved.
User manual
Rev. 1.0
— March 20, 2018
12 of 23
3.3 Starting a debug session using an external debug probe
Code running on the installed IoT Module may be debugged using an external debug
probe that conforms to the standard ARM debug connector. To use an external debug
probe connect the probe to the SWD connector on the Module, and connect power via
the micro USB connector J1. Note that the Debug link connector J7 must be left
unconnected so that the Link2 debug probe is left unpowered and does not contend with
the SWD interface signals from the external debug probe.
4. Link2 debug features
This section describes the features provided by the on-board Link2 debug probe. See the
Getting Started section for more information on how to program the device.
The Link2 debug probe is implemented using an LPC432x MCU (circuit reference U18),
which provides a high-speed USB port interface to the host computer which is running
the development tools. This device is not intended for developer use, and should only be
used with approved firmware images from NXP. The Link2 on-chip flash memory is
factory programmed with a firmware image that support CMSIS-DAP debug protocol, but
also includes other USB end point functions:
•
Virtual COM (VCOM) port: a serial device that can be used with any host
computer application design for serial port communication (e.g. Teraterm,
puTTY, etc.)
•
SWO trace end point: this virtual device is used by MCUXpresso to retrieve
SWO trace data. See the MCUXpresso IDE documentation for more information.
All of these devices are independent of each other and of the CMSIS-DAP debug device
that is enumerated when the board is connected to a host computer; for example the
VCOM port can be used if the board is running an application when no debugger is
running.
In order to correctly install and use the Link2 device on the OM40006 (as will be required
for any debugging) for host computers running Window 7 or 8, drivers must first be
installed. These drivers will automatically be installed when MCUXpresso IDE has
already been installed. If these IDEs are not being used, it is recommended LPCScrypt
be installed as this also includes the required drivers. All these tools and utilities are
available for free download at
www.nxp.com
.
The CMSIS-DAP firmware image installed at the factory (and by LPCScrypt) will uniquely
identify itself to the host computer so that more than one board can be connected to that
host computer at any time. Some toolchains cannot discern between multiple debug
devices; refer to your toolchain documentation for more information (note the
MCUXpresso does support multiple LPCXpresso board targets.)
Note that the Link2 only boots when the board is power cycled; the reset button on the
board does not reset the Link2.
When using MCUXpresso IDE, the Link2 can be automatically booted with the latest /
most appropriate firmware for that IDE version by installing JP6 before powering up the
board. This is the recommended approach for the MCUXpresso IDE. Note that if JP6 is
installed the VCOM port (and other devices mentioned above) device will not appear until
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from
Downloaded from