USB Multilink Universal & USB Multilink Universal FX - Technical Summary
b. Activity appears on SWD_CLK and SWD_DIO (PC software instructs the processor to enable debug mode).
c. RESET is released by the interface and will go high.
d. Activity appears on SWD_CLK and SWD_DIO (Debug activity).
Port C – BDM
RS08, HCS08, S12Z, ColdFire V1
a. Debug activity is seen on BKGD (Pin-1).
HC(S)12(X)
a. BKGD (Pin-1) and RESET (Pin-4) are pulled low by the interface.
b. After 5 milliseconds, RESET (Pin-4) is released and goes high.
c. After 10 milliseconds, BKGD (Pin-1) is released and goes high.
d. After 20 more milliseconds, debug activity is seen on BKGD (Pin-1).
Port D – Coldfire V2/V3/V4
a. BKPT (Pin-2), DSI (Pin-8), and DSCLK (Pin-4) signals are driven low.
b. RESET (Pin-7) is driven low for 20+ milliseconds and released.
c. After RESET is released and if the processor has correctly entered background mode, the PST0 (Pin-15), PST1 (Pin-
14), PST2 (Pin-13) and PST3 (Pin-12) lines should all be driven high by the processor.
d. Activity (changing signals) is seen on the DSI, DSO, and DSCLK signals. The activity on the DSCLK and DSI lines is
generated by the PC and the activity on the DSO line is generated by the processor.
Port E – JTAG/COP (Not yet supported)
Port H
HC16/683XX (FX Only)
a. BKPT/DSCLK is pulled low (to processor).
b. Delay ~1ms.
c. RESET is pulled low (to processor).
d. Delay ~20ms.
e. RESET is released (tri state, should be pulled up on target).
f. Wait for FREEZE (out of processor).
g. Shifting activity appears on DSCLK, DSI and DSO.
MPC5xx/8xx (FX Only)
a. DSCK is driven high and DSI is driven low (to processor).
b. Delay ~1ms.
c. HRESET or SRESET is driven low (usually this will be HReset).
d. Delay ~20ms.
e. HRESET is released (tri-state, should be pulled up on target).
f. Shifting activity appears on DSCLK, DSI and DSO. (PC software communicating with target to determine if debug mode
was successfully entered).
6 Firmware Updates/Architecture Selection
The Multilink Universal and Universal FX use firmware updates to change between modes of operation to support different
families of NXP microcontrollers. Older versions of PEmicro's software and third-party software are not able to automatically
configure these Multilinks when the target is switched to a different family of microcontrollers. If you are not using the latest
version of PEmicro software, please contact us to determine if you are eligible for a discounted upgrade to the latest version of
your software. You may also download a manual configuration utility for the Multilink from the Support Center or corresponding
product page on our website: http://www.pemicro.com/support/downloads_find.cfm
7 Interface Libraries
PEmicro produces a set of interface libraries which allow the user to directly control the USB Multilink Universal or Universal FX
from any Windows Development environment which can interact with a DLL. The interface libraries come with examples for
controlling the Multilink interface from Microsoft Visual C as well as Borland Delphi. More details can be found on the Interface
Libraries page on the PEmicro website: http://www.pemicro.com/products/product_processor.cfm?category=9
8 Compatible Software
The USB Multilink Universal and Universal FX are supported by recent versions of NXP’s CodeWarrior, Kinetis Design Studio,
S32 Design Studio, and MCUXpresso, as well as third-party toolchains such as those from IAR, Keil, Cosmic, Mentor Graphics,
and Atollic. They also work with PEmicro software, including our no-cost, fully-featured GDB Server Eclipse plug-in. It is
recommended that you check with the vendor regarding support for your specific part. Information on compatible PEmicro
software can be found in the “Products” section of www.pemicro.com.
