|P&E’s USB Multilink Universal is an all-in-one development interface which allows a PC access to the Background Debug Mode (BDM) or JTAG interface on Freescale HCS08, HC(S)12(X), S12Z, RS08, ColdFire V1/+V1, ColdFire V2-4*, Qorivva 55xx/56xx, and Kinetis ARM microcontrollers. It connects between a USB port on a Windows machine and the standard debug connector on the target. The Freescale microcontrollers are supported via the multiple headers located on the USB Multilink Universal. The product photos to the left of this page show how the headers can be accessed by simply flipping open the plastic case. Ribbon cables suitable for a variety of architectures are included.
Supported Freescale Devices:
NOTE: For a much faster all-in-one development interface which can also supply power to the target, please see the USB Multilink Universal FX.
By using the USB Multilink Universal, the user can take advantage of the background debug mode to halt normal processor execution and use a PC to control the processor. The user can then directly control the target’s execution, read/write registers and memory values, debug code on the processor, and program internal or external FLASH memory devices.
The USB Multilink Universal works with P&E Microcomputer System's in-circuit debuggers and flash programmers to allow debug and flash programming of the target processor. For many of the supported processors, P&E has a set of interface libraries allowing the user to write their own Windows based application which interacts with P&E's debug interface. IAR, Codesourcery, Keil, and CodeWarrior software all support the use of P&E's USB Multilink Universal to develop and debug with Freescale's Kinetis ARM devices.
This interface is USB 2.0 compatible, and it is also backwards compatible with USB 1.1 ports.
The USB Multilink Universal includes a ribbon cable for connecting to ColdFire V2-4 targets, however the MCF5272 & MCF5206(E) devices will require a separate adapter cable (not included) to synchronize the communications signals (as these devices do not do this on-chip).
Which Hardware Interface Is The Best Fit?