top of page

Debugging NXP ARM Microcontrollers Using PEMicro with S32 Design Studio

Updated: Apr 7

Embedded firmware development requires efficient debugging tools to identify issues quickly and ensure reliable system behaviour. For developers working with NXP ARM microcontrollers, integrating PEMicro debug tools with S32 Design Studio provides a powerful and flexible debugging environment.

In this blog, we explore how PEMicro debugging tools work with S32 Design Studio and how developers can configure and start a debugging session effectively.


Overview of S32 Design Studio


S32 Design Studio is an Eclipse-based Integrated Development Environment (IDE) developed by NXP Semiconductors for programming and debugging NXP microcontrollers and processors.

It supports various automotive and industrial MCU families and integrates seamlessly with debugging tools from PEMicro.


 By using PEMicro ‘S GDB Server integration, developers can perform:


  • Real-time firmware debugging

  • Flash programming

  • Breakpoint and watchpoint monitoring

  • Memory inspection

  • Multi-core debugging

  • Remote debugging through network interfaces


These features significantly improve development efficiency during embedded system design.



Supported Debug Hardware


PEmicro supports multiple hardware debug interfaces that can be used with S32 Design Studio.

Commonly used interfaces include:

  • Multilink Universal debug probe

  • Cyclone programming and debug tools

  • On-board debugging interfaces such as OpenSDA or OSBDM

These interfaces communicate with the target microcontroller through JTAG or Serial Wire Debug (SWD) protocols.


Once connected, the IDE typically detects the debugger automatically.


Starting a Debug Session in S32 Design Studio


Launching a debug session is straightforward.



Step-by-Step Procedure


  1. Build the project to generate the executable firmware file.

  2. In the toolbar, click the Debug icon dropdown.

  3. Select Debug Configurations.

  4. Choose GDB PEMicro Interface Debugging.

  5. Configure the target device and debugger settings.

  6. Click Debug to start the session.


After launching, the IDE switches to Debug Perspective, allowing developers to step through the code and analyze execution.


Key Debug Configuration Settings


To ensure proper debugging, several parameters must be configured correctly.

1. Hardware Debugger Selection

Choose the connected debug probe such as:

  • Multilink

  • Cyclone

  • OpenSDA interface

The IDE usually detects available hardware automatically through USB or Ethernet.




2. Target MCU Selection

Developers must select the correct microcontroller device used in the project.

For example, commonly supported families include:

  • S32K1 Series

  • S32K3 Series

  • S32V Series

  • KEA Automotive MCUs

Selecting the correct MCU ensures that the appropriate flash programming algorithm is used.




3. Application Binary File

The debugger needs the compiled firmware file to load into the target MCU.

Typical formats include:

  • .elf

  • .bin

  • .srec

For single-core devices, only one application file is required.

For multi-core devices, multiple binaries may be configured for different CPU cores.



Multi-Core Debugging Support


Some modern NXP processors feature multiple CPU cores.

In these cases:

  • The primary core handles flash programming.

  • Secondary cores are attached using Attach to Running Target mode.

This approach avoids reprogramming the device unnecessarily and allows independent debugging of each core.




Advanced Debug Features


Serial Wire Output (SWO)

SWO allows real-time data tracing from the microcontroller without requiring additional UART hardware.

Developers can use SWO for:

  • Runtime logging

  • Debug messages

  • Variable monitoring

  • Event tracing

This makes debugging faster and less intrusive.



Power Consumption Monitoring


Some advanced PEmicro probes support power measurement features.

This enables developers to:

  • Monitor real-time current consumption

  • Optimize firmware for low-power applications

  • Identify power spikes during operation

This feature is especially valuable for battery-powered IoT and automotive systems.




Benefits of Using PEMicro with S32 Design Studio


Combining PEMicro debug tools with S32 Design Studio offers several advantages:

  • Reliable debugging for NXP ARM microcontrollers

  • Support for both single-core and multi-core architectures

  • Real-time trace and monitoring features

  • Integrated flash programming and debugging

  • Easy hardware integration through USB or Ethernet

These capabilities make it easier for developers to build stable and high-performance embedded systems.


Conclusion


Debugging is a critical stage in embedded firmware development. Using PEMicro debug probes together with S32 Design Studio enables developers to quickly identify issues, monitor system behaviour, and optimize firmware performance.

With its powerful debugging capabilities and seamless integration with NXP devices, this setup is widely used in automotive, industrial, and IoT embedded development.

Comments

bottom of page