PEmicro | Experts in Embedded tools for Flash Programming and Development
PEmicro logo
Cart New Account Login

Logo image
HomeAbout usProductsSupportForumsBlogCustomer Service


by Steve McGrath


PEmicro has added support for its Multilink and Cyclone tools to 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 blog demonstrates the procedures needed to install and then configure PEMicro Multilink and Cyclone debug support in Renesas e2Studio.

Installation Procedure

 

Step

Frequency

1. Install the PEmicro GDB server for ARM device Plugin

Only Once

2. Create a Launch Configuration

Once Per Project

1. Install the PEmicro GDB server for ARM device Plugin

After e² studio is launched, the following steps will install the PEMicro GDB server for ARM devices plug-in.

a. Locate the “Help” tab

b. Select the “Install New Software” option as shown in the screenshot below

c. In the “Work With” input box, enter the following address:  https://www.pemicro.com/eclipse/updates and hit the keyboard Enter key.

d. In the following dialog click ‘Next’, accept the License, and click Finish.

e. This will install support for PEMicro 's Multilink and Cyclone hardware into e² studio. You will also be allowed to connect all corresponding target devices that are supported by PEMicro hardware. A dialog will pop up prompting you to restart e² studio. Click Yes.

PEMicro debug support has now been added into e² studio.

2. Create a Launch Configuration

The following steps will help you to create a Launch configuration:

a. Open or create the project of your choice.

     i. For example, select the “File” tab in the top left corner and then select New->Renesas C/C++. From here, navigate to the applicable Renesas project depending on your target processor (RA, Synergy, etc) as show in the screenshot below.

     ii. The following screen will appear to create a new Renesas project. Name the project and select the type of project that will be created and click "Next".

     iii. Then select the corresponding ‘FSP Version’, ‘Board’ and “Device’ you wish to work with under the "Device Selection" option, as well as the specific part of the target board categorized by MCU family. Once these are selected, click “Next” and then continue on specifying the type of project you would like to create. The next page will show “Bare Metal – Minimal” example or whichever example(s) is present to get started, then select “Finish”. 

b. Build the project by right-clicking on the project and searching for the “Build Project” option. Alternately, you may click on the project in the Project Explorer popup menu and click the icon with the picture of a hammer on the main button bar.

c. Once you are ready to debug the project for the first time, open the Debug Configurations dialog. This can be done from the main button bar (as highlighted in the figure below) or the Project Explorer popup menu. The Project Explorer popup menu is shown here:

d. This brings up the dialog where launch settings are configured. Normally, you would select the configuration of your choice to edit it. In this case, we have never configured a launch before and need to create a launch configuration. Select Debug As -> Debug Configurations...

e. You should now see “GDB PEMicro Interface Debugging” presented as an option in the Debug Configurations window. Double click this option.

 

 This will create a GDB PEMicro debug configuration with default settings which need to be adjusted.

f.) Next select the “Debugger” Tab of the Debug Configurations dialog. This brings up launch settings for the currently selected configuration.

g.) Select the PEMicro hardware you are using to interface with the target device (for this web example we will be using the Multilink FX hardware via USB connection).

h.) Next, we need to select the specific microcontroller type to be debugged. This is done by clicking the “Select Device” button which pops up the “Select Target Device” dialog. This dialog shows a tree structure of all supported devices. In this case we want to navigate to “Renesas” -> ”RA2x” -> whichever Renesas RA2 device is being used.

Select the device to be programmed and click the “Select” button. 

k.) The GDB Debug Client also needs to be specified to launch a debug session. There is a panel titled “GDB Client Settings” on the Debugger Tab which has a path to the GDB client executable (provided by Silicon Labs). Click the “Browse...” button and navigate to the proper GDB client executable (usually arm-none-eabi-gdb.exe). In this example, the path is “C:\Renesas\e2_studio\eclipse\plugins\com.pemicro.debug.gdbjtag.pne.expansion_5.1.0.202109011413\win32\gdb\arm-none-eabi-gdb.exe”. Once selected, the path is shown in the “Executable” input box.

There are many settings in this dialog. Refer to the plug-in documentation for these details.

You are now ready to debug. Click the Apply button to save the settings and then the Debug button to launch a debug session.

 





search in blog posts

Tags

Product pages
Cyclone (91)
Cyclone FX (94)
Multilink (56)
Multilink FX (51)
GDB Server (26)
Prog ACMP (22)
Interface Library Routines (5)


Manufacturer
ARM (73)
NXP (81)
Microchip (7)
Cypress (7)
Infineon (7)
Maxim (3)
Nordic Semiconductor (3)
Silicon Labs (6)
Silergy Teridian (1)
STMicroelectronics (10)
Texas Instruments (2)
Toshiba (3)
Renesas (11)


Categories
Production Programming (94)
Debug (58)
Automated Control (24)
Miscellaneous (39)



© 2021 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement