Keil ULINKpro, Инструкция по использованию, Страница: 3 / 14

P a g e 2 | 13
Overview
The purpose of this paper is to discuss and demonstrate how to use the ARM Keil MDK toolkit with μVision® IDE
with the Avnet-AT&T Cellular IoT Kit at http://cloudconnectkits.org/product/att-cellular-iot-starter-kit.
The paper uses the Avnet-AT&T Cellular IoT Kit software which is located at
https://developer.mbed.org/users/JMF/code/Avnet_ATT_Cellular_IOT/ and focuses on how to connect the
ULINK
pro JTAG debugger to the hardware, what to modify in the software, and how to configure the μVision IDE.
Additional information on the ULINK tools & Keil Environment can be found in the following App Notes from Keil,
NXP K64 Freedom:
www.keil.com/appnotes/docs/apnt_287.asp and NXP K64 Tower:
www.keil.com/appnotes/docs/apnt_288.asp .
Why Use Keil MDK?
Development on the NXP/FRDM-K64F is simplified for users by having OpenSDA tools pre-installed when it is
delivered. While this environment is suitable for many development activities, it lacks the hardware and
performance specific capabilities that a
USB-JTAG/SW Debug and Trace Unit provide. Using the Keil μVision IDE
and ULINK pro environment, users enjoy the following:

A μVision IDE with Integrated Debugger and Flash programmer

The ARM® Compiler tool chain

USB-JTAG Debugging (and/or Serial Wire Debug) with CoreSight™ Serial Wire Viewer and ETM trace
capability
Other Keil tools such as ULINK2 and ULINK-ME and the Segger J-Link can be used in place of the ULINK pro but
these units do not support the ETM, Performance Analysis, and Code Coverage features.
Finally, being able to switch between the online development at mbed.org and the ARM/Keil environment is the
goal of this paper. While integrating the Avnet WNC-Shield board, more extensive hardware debug capabilities
were needed which drove the need for this capability.
ULINK pro features
The specific features of the ULINK pro that were needed are as follows:
1. Serial Wire Viewer (SWV) data trace including exceptions and ETM instruction trace
2. Real-time read and write to memory locations for watch, and memory windows
3. Hardware breakpoints and watchpoints (also called access breaks)
Introduction to the MDK
This paper uses MDK 5.20 and Software Pack 1.4.0. Install MDK 5 Core first and then download the required
Software Packs. Software Packs are an ARM CMSIS standard
1
.
1
See www.keil.com/CMSIS or www.keil.com/dd2/pack for the complete list of software packs.