STM32CubeIDE from STMicroelectronics with Multilink/Cyclone

STM32CubeIDE from STMicroelectronics


STMicroelectronics' STM32CubeIDE is an Eclipse-based activation platform that supports code development and debugging on STM32 ARM microprocessors. PEmicro hardware interfaces: Multilink and Cyclone can be used for extended debugging functions via an Eclipse GDB plugin, which can be installed in any Eclipse IDE from the PEmicro update site (http://www.pemicro.com/ eclipse / updates) is freely available. This blog shows the steps required to install and configure PEmicro Multilink and Cyclone debug support in STM32CubeIDE before starting a debug session.

 

Installation progress​ Frequency
1. Install the PEmicro GDB-Server for the Arm-Geräte-Plugin One Time
2. Create a Start Configuration One Time per project


Install the PEmicro GDB server for the plug-in for ARM devices


a.) Start STM32CubeIDE and continue with Help -> Install new software to open the plugin installation and update wizard.

b.) Activate the checkboxes GNU ARM PEMicro Interface Debugging Support and PEmicro ARM Device Expansion Plugin and click on the Next button.

 

Installieren_des_PEmicro_GDB-Servers_fuer_das_Plugin_fuer_ARM-Geraete

 

c.) This installs support for the multilink and cyclone hardware from PEmicro in STM32CubeIDE. A dialog box appears asking you to restart STM32CubeIDE. Click yes.

 

 

Start a debug session


a.) It is incredibly easy to start a debugging session using PEmicro's debug tests with STM32CubeIDE. Open a project of your choice and call the debug configuration manager:

 

Start_einer_Debug_Sitzung_STmicro

 

b.) This opens the dialog in which the start settings are configured. PEmicro interfaces require a dedicated start debug configuration, which can first be created by double-clicking on the GDB PEMicro Interface Debugging category in the left pane.

 

zweiter_Schritt_oeffnen_einer_Debugsitzung_STmicro

 

After the debug configuration for the PEmicro start has been created, navigate on the Main tab to a current project and to a C / C ++ application file .elf that you want to debug.

c.) On the Debug tab, the user may want to change many startup settings to control the following functions:

  • ITM / Printf / Power measurements via SWO
  • Exceptional catch
  • Automatically powers / switches the target MCU
  • Memory area maintenance during programming
  • The application object files to be programmed and debugged
  • All additional object files to be programmed into the device (boot loader, etc.)
  • Indicates whether a target MCU should be reset / programmed or connected to a running device (hotsync)
  • Semihosting options that code can use to output debug messages
  • Temporary breakpoints
  • Selection of the MCU device
  • Debug probe selection via USB or Ethernet
  • Initialization scripts

A complete list of functions can be found in the documentation for the PEmicro plugin (http://www.pemicro.com/downloads/download_file.cfm?download_id=482).

The user should properly configure at least the following settings to start a debug session:

  • Debug the hardware interface
  • Part number of the MCU device
  • Project and application binary to start
  • A link to the executable file of the GDB client

 

PEmicro_STmicro

 

When creating a new start debug configuration, the user should first select the debug hardware interface to use. The PEmicro GDB server supports debug connections via the USB multilink debug probes from PEmicro as well as Cyclone programmers via USB and Ethernet.

 

PEmicro_STmicro_2

 

The USB and local Ethernet devices from PEmicro are automatically recognized. Remote networked Ethernet debug interfaces can be specified via their IP address.

Next, the user should select a particular STM32 MCU device to debug and program.

 

PEmicro_stmicro3

 

When creating a new debug configuration, the user should ensure that a path to a GDB client is specified under GDB client settings in the debug configuration. STM32CubeIDE is supplied with a pre-installed GNU plug-in for external tools: com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2- update.win32_1.0.0.201904181610. Therefore point to the text field GDB client setting with a direct path to the client arm-none-eabi-gdb.exe. Please note that the actual path may vary depending on the version of the plugin and the location of your STM32Cube installation directory (STM32CubeIDE \ plugins \ com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32). 7-2018-q2-update.win32_1.0.0.201904181610 \ tools \ bin \ arm-none-eabi-gdb.exe).

 

Pemicro_stmicro_4

 

Once these debug settings are complete, a debug session can be started by pressing the debug key.

With PEmicro's Eclipse-based GDB Server plug-in, developers can use PEmicro's Multicink and Cyclone interfaces to program and debug ARM and PowerPC processors in many different Eclipse-based IDEs. PEmicro Eclipse GDB plugins for ARM and PowerPC devices offer the possibility to quickly develop and debug code for STM32 ARM and SPC5 ST PowerPC devices.


Display per page
Sort by

PEmicro Universal Multilink Debug

Product no.: USB-ML-UNIVERSAL

PEmicro’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 wide range of ARM Cortex and NXP®/STmicroelectronics processor families.

299.00 *
In Stock, Delivery within 1-2 working days

PEmicro Cyclone FX Universal - ISP Programmer

Product no.: CYCLONE-FX-UNIV

Production in-system programmer for Cortex Flash and 8/16/32 bit components with 1 GB memory and 75 Mbits / s programming speed.

1,399.00 *
Product data sheet

can be shipped within 1-2 days

PEmicro Cyclone LC Universal - ISP Programmer

Product no.: CYCLONE-LC-UNIV

The Production In System programmer Cyclone LC Universal supports ARM Cortex Flash components and 8/16/32 bit components.

999.00 *
Product data sheet
In Stock, Delivery within 1-2 working days
*

Plus Vat for enduser and companies located in Germany