Features
- USB interface from PC to Multilink allows for fast, easy programming and debugging -- with the ease and compatibility of the USB interface.
- Draws power from USB interface-- no separate power supply required (draws less than 1mA from the target).
- Target Voltage: 1.8V-5.25V
- Supports JTAG daisy chaining of multiple ARM MCUs
- Pipelined programming algorithms for some Power Architecture families that dramatically increase programming speed.
- ARM device support includes both the JTAG and SWD protocols
- Includes USB cable, Type A Male to Type B Male, 6-ft.
- Auto-frequency detection + trimming capabilities for HCS08 devices.
- Auto-frequency detection for HC(S)12(X) devices.
- Generates programming voltage on RESET line for RS08 devices.
Highlights
PEmicro's no-cost GDB Server for ARM devices (Eclipse plug-in) includes the following powerful features:
Real-Time Expression View
This view gives the user the ability to view variables and memory while a target ARM device is running. Sometimes the process of halting the target masks a bug. Sometimes, in order to reproduce a particular bug, the program must be kept running while being fed a particular set of data. In those cases, having the ability to view variable values as they change without halting the target is a great asset.
OS-Aware Feature Supports FreeRTOS
The GDB server will automatically detect the presence, type, and configuration of an OS by querying the application’s symbol table for identifying characteristics. Using these discovered symbols, the debugger can traverse the kernel’s internal data structures to enumerate the available threads and their corresponding execution context. This information is then used to dynamically populate the Eclipse views as the user navigates between the threads. Additional OS support is expected to be added soon.
Single-Wire Output (SWO) Debug Tools
By using NXP's MCUXpresso or PEmicro's plug-in for ARM-based GDB IDEs, users can monitor multiple variables and expressions in real time, use printf calls to be notified when specific events occur during the debug session, and use trace capture to log user-specified events and triggers. This allows much more insight into the operation of the user's code.