Renesas: Debugging with Renesas' e² studio IDE and RDPM
PEmicro's Multilink and Cyclone tools are supported in Renesas' e² studio IDE. e² studio is an Eclipse-based IDE created by Renesas which supports development and debugging of code on Renesas' Synergy and RA devices. This article demonstrates the procedures needed to install and then configure PEMicro Multilink and Cyclone debug support in Renesas e2Studio.
SiliconLabs Simplicity Studio 4 and 5 : Installing PEmicro Multilink and Cyclone Support
Simplicity Studio 4 and 5 are Eclipse-based IDEs by Silicon Labs which support development and debugging of code on EFM32 devices. PEmicro provides hardware debug probes which provide sophisticated debug of these same EFM32 devices. This blog demonstrates the three steps needed to install and configure PEmicro Multilink and Cyclone debug support in Simplicity Studio. UPDATE: All following steps now apply to Simplicity Studio 5
Updated "GO" Command Enables Improved Control of MCU Reset Type
PEmicro has improved user reset capabilities after a flash programming sequence. With the updated implementation of the ‘GO’ command (available with most ARM Cortex processors) in both PEmicro's Cyclone and PROGACMP (v8.76 and up) software-based programming solutions, the user is able to specify the use of a software or hardware reset to reset the MCU.
PEmicro Announces Development Tool Support for NXP’s New S32K3 Automotive MCU Family
PEmicro, an NXP® Semiconductors Gold Partner, has announced a range of development tool support for the S32K3 Automotive MCU family for next generation body, zone, and domain control applications. Tightly integrated with NXP’s evaluation boards and S32 Design Studio IDE, PEmicro tools provide a powerful platform for the evaluation, development, and production programming stages of the product cycle.
NXP: Overview: OS-Aware Debug Support for Azure RTOS ThreadX in GDB Server, MCUXpresso, etc.
Version 5.1.4 of PEmicro's GDB Server for ARM devices, is required to support for Azure RTOS ThreadX. The user does not have to do anything to set it up; the GDB server will automatically detect the presence, type, and configuration of an OS by the 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.
PEmicro Legacy Hardware Support Notice (In Effect As of 1 Oct. 2021)
Beginning October 1, 2021 the latest versions of PEmicro software will only be tested against and designed to work with the following PEmicro hardware interfaces: MULTILINK DEBUG PROBES (2015+) CYCLONE PROGRAMMERS (2016+)
Read more...
NXP: Multilink/Cyclone Debug with NXP's S32 Design Studio for ARM IDE
NXP''s S32 Design Studio for ARM provides a comprehensive enablement platform for ARM development with full integration of PEmicro’s GDB Server for ARM devices. This provides advanced debug capabilities via PEmicro’s Multilink, Cyclone, and embedded OpenSDA debug interfaces.
STMicroelectronics: Multilink/Cyclone Debug with STM32CubeIDE from STMicroelectronics
STM32CubeIDE from STMicroelectronics is an Eclipse-based enablement platform which supports development and debugging of code on STM32 ARM microprocessors. PEmicro's Multilink debug probes and Cyclone programmers can be leveraged for advanced debug capabilities via an Eclipse GDB plugin installed into any Eclipse IDE. This blog demonstrates the steps needed to install and configure PEmicro Multilink and Cyclone debug support in STM32CubeIDE to the point of launching a debug session.
Infineon: DAVE IDE: Installing PEmicro Multilink and Cyclone Support
DAVE™ is an Eclipse-based IDE by Infineon which supports development and debugging of code on XMC1000 and XMC4000 devices. PEmicro's Multilink debug probes and Cyclone programmers can provide sophisticated debug for these Infineon devices via the DAVE™ IDE. To use PEmicro's debug probes the user can simply install PEmicro's GDB Server Plug-In for ARM devices and then create a launch configuration.
Exception Catching Support in NXP's MCUXpresso IDE
ARMv7-M devices have the ability to halt when specified exceptions occur. If exception catching is enabled, the processor will halt when a user's code hits the corresponding fault handler. Exception catching serves as an aid to development by alerting users in real-time about exceptions that occur in their code. When installed in NXP's MCUXpresso IDE, PEmicro's GDB Server plug-ins from v3.96 onward include options for exception catching, and return information about the exceptions that have occurred.
JTAG Daisy Chaining MCUs With PEmicro Multilink & Cyclone
Dec. 2018 - We've updated this blog post with more info about Multilink and Cyclone implementation... The JTAG specification introduced daisy chaining of MCUs in order to reduce the number of headers required to debug and program multiple MCUs. JTAG daisy chaining allows multiple MCU’s (and other JTAG compatible hardware, such as FPGAs) to share a single debug header. PEmicro currently supports daisy chaining of ARM-Cortex MCUs via our Cyclone programmers and Multilink debug probes. The same is true for most PEmicro software, including our Eclipse plugin GDB Server, and our Cyclone automation and control packages.
NXP: NXP's MCUXpresso IDE Debug With Fully Integrated PEmicro GDB Server
NXP's MCUXpresso Integrated Development Environment for LPC and Kinetis microcontrollers features full integration with PEmicro’s GDB Server. This provides advanced debug capabilities via PEmicro’s Multilink, Cyclone, and embedded OpenSDA debug interfaces including: hardware breakpoints, watchpoints, real-time variables, semihosting, FreeRTOS awareness, the ability to attach to a running target, the ability to provide target power, remote debug, and more.
FreeRTOS: PEmicro Introduces OS-Aware Debugging in GDB Server for ARM devices
There comes a time when an embedded application becomes complex enough that it requires an operating system. This may be because of a need for rich driver libraries, or a sophisticated task scheduling engine. In either case, a developer needs an equally sophisticated debugger to provide invaluable context information of their application. To that end, PEmicro introduced OS-aware debugging in its GDB Server for ARM devices. Initial support is available now for FreeRTOS, with further OS modules to be developed. PEmicro's GDB Server for ARM devices is available for download at no cost and works with PEmicro Multilink, Cyclone, and OpenSDA hardware interfaces.
View Variables While Code is Running in PEmicro's GDB Eclipse Plug-In
PEmicro’s GDB Server Plug-in for ARM devices features the ability to view variables and memory while a target ARM device is running. This Eclipse plugin can be installed in any Eclipse-based IDE and supports the debug of ARM microcontrollers via PEmicro’s Multilink, Cyclone, and OpenSDA debug hardware. The “Real Time Expressions” view, which is part of the plugin, is similar to the normal expressions view, except that it works while the part is running.
How to Install and Update PEmicro’s GDB Server in Eclipse-Based IDEs
PEmicro’s GDB Server can be installed directly into an Eclipse based IDE from an update site on PEmicro’s website. This adds the ability to debug via PEmicro’s Multilink, Cyclone, and OpenSDA hardware interfaces via the standard GDB debugger. Features include flash programming, breakpoints, watchpoints, trim, memory preservation, real-time variables, semi-hosting, and more. PEmicro periodically updates the plugins on its website with new device support, new features, and bug fixes.
Save Data From Erase Module Using Preserve Range
The Erase Module function of PEmicro programming algorithms generally erases all data in a flash module. Sometimes a user may not wish to fully erase the flash. On algorithms which support selective erase functions (like Erase Object Ranges or Erase Range), those mechanisms can be used instead to only erase the regions desired. On algorithms which only support Erase Module, the algorithm itself can be modified to preserve certain ranges of flash memory. Before erasing the flash, the programmer looks at the ranges to be preserved, saves it, and reprograms it automatically after the Flash/EEPROM has been erased. Some settings in some flashes (like timing TRIM parameters) are automatically preserved.