This article will walk the user through the following installation steps:

Install the PEmicro GDB server Plugin for ARM devices

The following steps will help the user install the PEmicro GDB Server Plug-In for ARM devices.

1. The first step is to start DAVE™:

Figure 1. Splash Screen

2. Hit Ctrl-3 on the keyboard to bring up the Quick Access dialog.
3. Type 'install' and select the 'Install New Software' option from the selections that appear.

Figure 2. Select "Install New Software"

This will pop up the following Install dialog:

Figure 3. Specify "Work With" Path

4. Near the top, in the 'Work With' input box, enter the following web address and then hit the Add button.  http://www.pemicro.com/eclipse/updates/Infineon
5. In the 'embsysregview' category, select both the 'Embedded Systems Register View (SFR)' and the 'EmbSysRegView Data' option.
6. Further down, in the 'PEmicro Software' category, select the 'GNU ARM PEmicro Interface Debugging Support' option.
7. At the bottom click the Next button, accept the License, and click Finish.
8. This will install support for PEmicro's Multilink and Cyclone hardware into DAVE™. All corresponding target devices that are supported by PEmicro hardware can be connected. A dialog will pop up prompting the user to restart DAVE™. Click Yes.

Figure 4. Restart DAVE to Implement Changes

PEmicro debug support has now been added into DAVE™.

Create a Launch Configuration

The following steps will help the user create a Launch configuration:

1. Create a new project (or open an existing project).
   1. Select the “File” tab in the top left corner and then select New->Dave Project as shown in the figure below. 

Figure 5. Select New -> DAVE Project

2. The following screen will appear to create a new DAVE project, name the project and select the type of project that will be created.

Figure 6. Specify Project Name & Type

c) Then, under the 'Microcontrollers' option, select the desired target board as well as the specific part of the target board, categorized by MCU family. Once these are selected, click Finish.

Figure 7. Select Target Board

2. Build the project by right-clicking on the project and then selecting the 'Build Project' option. Alternately, select the project in the Project Explorer popup menu and click the icon with the picture of a hammer on the main button bar to build it:

Figure 8. Build Project

3. Once the project is ready to be debugged 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:

Figure 9. Project Explorer Popup Menu

This brings up the dialog where launch settings are configured. Normally, the user would select the configuration of their choice to edit it. In this case a launch has never been configured before, so that will be the next step. 

4. Create a launch configuration (new project)
   1. First remove any filter text by clicking on the icon that shows three arrows pointing to the right. This will make sure that the GDB PEMicro settings will appear

Figure 10. Remove Any Filter Text

2. This will bring up the Launch Configurations window. Locate the 'GDB PEMicro Interface Debugging' option in the drop down menu and uncheck the option. Then click Apply and OK to remove the filter.

Figure 11. Click Apply and OK

3. The 'GDB PEMicro Interface Debugging' option should now be visible  in the Debug Configurations window. Double click this option.

Figure 12. Double-click GDB PEMicro Interface Debugging' Option

This will create a GDB PEmicro debug configuration with default settings which need to be adjusted as the next step.

5. Adjust the default launch config settings.

1. Select the 'Debugger' Tab of the Debug Configurations dialog. This brings up launch settings for the currently selected configuration.
2. Select the PEmicro hardware being used to interface with the target device. In this case, the Multilink FX hardware via USB connection will be selected
3. Next 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. There is a box where a string may be entered to filter the devices shown (blank = everything). In this example, the XMC4800-1024 device is being set up.  Enter '4800' in the filter box to make the selection easier. 

Figure 13. Enter Part Number Digits to Filter

4. Select the device to be programmed and click the 'Select' button.

Figure 14. Select Device

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 Infineon). 

5. 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:\DAVE_IDE\DAVE_4-4-2_64bit_2018-02-23\DAVE-IDE-4.4.2-64Bit\eclipse\ARM-GCC-49\bin\arm-none-eabi-gdb.exe'. Once selected, the path is shown in the 'Executable' input box.

Figure 14. Path Shown in "Executable" Input Box

There are many settings in this dialog such as selecting semihosting, using retarget or updating linker scripts and startup code,. Refer to the plug-in documentation for these details which in this example is located in the C:\DAVE_IDE\DAVE_4-4-2_64bit_2018-02-23\DAVE-IDE-4.4.2-64Bit\eclipse\ARM-GCC-49\share\doc\gcc-arm-none-eabi\readme.txt.

6. Click the Apply button to save the settings and then the Debug button to launch a debug session. The Infineon's DAVE IDE is now ready to debug via PEmicro's Multilink or Cyclone.