eclipse-embed-cdt/eclipse-plugins

The Eclipse Embedded CDT plug-ins for Arm & RISC-V C/C++ developers (formerly known as the GNU MCU Eclipse plug-ins). Includes the archive of previous plug-ins versions, as Releases.

The Eclipse Embedded CDT plug-ins

These are the Eclipse projects used to build the Eclipse Embedded CDT plug-ins, formerly the GNU MCU/ARM Eclipse plug-ins.

The project is now part of the Eclipse Foundation and is hosted on GitHub.

How to install

Eclipse Packages

For new installs, the preferred method is via Eclipse IDE for Embedded C/C++ Developers which packs the official Eclipse IDE for C/C++ Developers release with all Eclipse Embedded CDT plug-ins already installed.

Older packages are available from GitHub Releases.

Eclipse Marketplace

For existing Eclipse instances, the recommended install method is via Eclipse Marketplace; search for Embedded CDT.

Eclipse Update Sites

• Stable: https://download.eclipse.org/embed-cdt/updates/v6/ This is the official release; it is also referred by the Eclipse Marketplace and the same content is packed as Eclipse IDE for Embedded C/C++ Developers.
• Pre-release versions: https://download.eclipse.org/embed-cdt/updates/v6-test/ Usually this site should be safe, but use it with caution.
• Development versions: https://download.eclipse.org/embed-cdt/builds/develop/p2 Sometimes you can use this site to test features that are not completely implemented, or that might change before a final version is released. Note: This site is not always functional; use it carefully, back up your workspace, and do not use it for production projects.

Run-time dependencies

Starting with v6.x, the minimum requirements for running the Eclipse Embedded CDT plug-ins are:

• JavaSE-11 or later
• CDT 9.2.1 (Neon.3)

The recommended:

• JavaSE-11 or later
• Eclipse 2020-09 or later

Support

For support, please check the web support page.

Maintainer info

Please read the separate README-MAINTAINER page.

License

Copyright (c) 2012, 2023 Liviu Ionescu and others.

This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0 which is available at https://www.eclipse.org/legal/epl-2.0/.

SPDX-License-Identifier: EPL-2.0

eclipse-plugins's Issues

After Keil server upgrade, Packs Update is extremely slow

Every time I click the update button, it processes several packs at reasonable speed (several seconds at most) and then grinds to a complete halt for a random pack.
This happens with the current release and the beta of the plugin for both cached files and freshly downloaded ones.
Even canceling the update can take over 10 minutes:

[...]
Copy 79kB
 from "http://www.keil.com/pack/Keil.LPC1700_DFP.pdsc"
 to   "/home/eric/Packages/.cache/Keil.LPC1700_DFP.2.1.0.pdsc"
Processing "/home/eric/Packages/.cache/Keil.LPC1700_DFP.2.1.0.pdsc" for content.xml ...
Schema version "1.2".
Completed in 5538ms.
Copy 65kB
 from "http://www.keil.com/pack/Keil.LPC1800_DFP.pdsc"
 to   "/home/eric/Packages/.cache/Keil.LPC1800_DFP.2.5.0.pdsc"
Processing "/home/eric/Packages/.cache/Keil.LPC1800_DFP.2.5.0.pdsc" for content.xml ...
Schema version "1.3".
Completed in 16024ms.
Copy 25kB
 from "http://www.keil.com/pack/Keil.LPC4000_DFP.pdsc"
 to   "/home/eric/Packages/.cache/Keil.LPC4000_DFP.1.1.0.pdsc"
Processing "/home/eric/Packages/.cache/Keil.LPC4000_DFP.1.1.0.pdsc" for content.xml ...
Schema version "1.2".
Completed in 1744ms.
Copy 70kB
 from "http://www.keil.com/pack/Keil.LPC4300_DFP.pdsc"
 to   "/home/eric/Packages/.cache/Keil.LPC4300_DFP.2.5.0.pdsc"
Processing "/home/eric/Packages/.cache/Keil.LPC4300_DFP.2.5.0.pdsc" for content.xml ...
Schema version "1.3".
Completed in 979908ms.
Job cancelled

I left it running for several hours without any visible progress. It stops on every try, but the affected pack seems to be completely random.

System:
Eclipse 4.5.1
Linux 4.2.2
openjdk 1.8.0_65

Setting watchpoints?

Sorry if I missed this somewhere but it appears watchpoints are not supported by the plugin? I highlight a variable, go to Run->Toggle Watchpoint but it's grayed out. Has this feature just not been implemented in the plugin yet? For completeness, here's my setup:

Eclipse: Luna 4.4.1
GNU ARM C/C++ J-Link Debugging: 3.1.1.201412191510
JLink V4.96
JLink Pro debugger
Windows 7 Pro 64 bit

Tool Settings Tab not available for Makefile projects

I've followed all the installation steps and I'm able to run both tutorials (Blinky ARM test & Hello ARM test) without problems. However, when I import a project into Eclipse via Import > "Existing Code as Makefile Project", then the Properties - Setting dialog is missing the "Tool Settings" tab and others tabs (see attachments). To reproduce, just reimport the Hello ARM test project.

Eclipse IDE for C/C++ Version: Mars Release (4.5.0) Build id: 20150621-1200
gnuarmeclipse-qemu-osx-2.3.50-201508041609-dev
gcc-arm-none-eabi-4_9-2015q3
OSX 10.10.4

Remove the Packages folder when the Package Manager is unable to find Packs

I followed the instruction as precisely as i could. I have tried refreshing the Packs several times, but no success. This is the warning in the console. Also I checked the whole console, there was no error related to downloads or anything. Also there are many .pdsc files in the cache folder. I'm using Kubuntu 15.10 with Eclipse neon M2. Please help. Thanks in advance :)

Update packs completed in 196s.
2015-10-25 19:35:17
Loading repos summaries...
Parsing cached content file "/home/katph/c_workspace/packages/.cache/.content_www_keil_com_pack.xml"...
File does not exist, ignored.
Parsing cached content file "/home/katph/c_workspace/packages/.cache/.content_gnuarmeclipse_sourceforge_net_packages.xml"...
File parsed in 1ms.
Identifying installed packages...
Found no installed packages.
Completed in 2ms.

2015-10-25 19:35:17
Collecting devices...
Found none.
Completed in 1ms.

2015-10-25 19:35:17
Collecting packs...
Found none.
Completed in 1ms.

The contents of the xml file:

<?xml version="1.0" encoding="UTF-8"?>

<root version="1.1">
    <repository name="GNUARM">
        <description>GNU ARM Eclipse packs repository</description>
        <properties>
            <property name="type">xcdl.repo</property>
            <property name="repo.url">http://gnuarmeclipse.sourceforge.net/content.xml</property>
            <property name="generator">GNU ARM Eclipse Plug-ins</property>
            <property name="date">20140716090015</property>
        </properties>
    </repository>
</root>

How is the /system/ directory excluded from Eclipse's indexer/analyzer?

Hello,

I have been using the gnuarmeclipse plug-ins for some time, developing on the STM32F107 using c. The tools are excellent. Thank you.

Using the default STM32F10x template, it appears that everything in the /system folder (including CMSIS, the standard peripheral libraries, etc) is being excluded from Eclipse's Code Analyzer.

Sometimes Eclipse will have a problem and I'll get a bunch of warnings from one or more of the files in /system. I can get rid of these errors by rebuilding the Eclipse index and then restarting Eclipse.

Now, however, I have warnings that I cannot make go away. Please see the screenshot. These are spawned by Eclipse's CODAN, not by the gcc toolchain. These just started showing up. I have a different project built with the same template that doesn't show these errors.

Do you have any ideas for me? I do not want to disable the code analyzer entirely.

Thank you.

Versions:

• Plug-in: Core 2.7.1;
• Eclipse: Luna SP2 (4.4.2)
• Java: 1.8.0_65
• OS: Win7 Pro, XP1, 64-bit
• Toolchain: 4.9.3

Packs (2.2.2.201511061603) not returning any packs on refresh

plug-in version: GNU ARM C/C++ Packs (Experimental) 2.2.2.201511061603
eclipse version: 4.4.2
java version: 1.7.0_85
os: Ubuntu 14.04
toolchain version: gcc-arm-none-eabi-4_9-2015q3

I was following to tutorial on http://gnuarmeclipse.github.io/plugins/packs-manager/ . When I hit the refresh button to retrieve the available packs, no available packs were returned.

Attached is the eclipse console log.
log.txt

I had an internet connection present throughout the tutorial, tried restarting eclipse and re-installing the plug-in. However I was unable to retrieve any packs.

May I know what I have done wrong?

Thank you for your attention.

reimplement system() for semihosting usage

in the current newlib, the system() call seems not functional, probably due to the missing HAVE_SYSTEM definition.

in the semihosting section of syscalls, reimplement system() to call _system().

Trace Control for GDB

it would be great to be able to control the trace peripheral from within Eclipse.

There might be some button to start program counter sampling.
https://github.com/PetteriAimonen/STM32_Trace_Example/blob/master/configure-trace.openocd
I have no idea how to add this to eclipse :(
a second tool could then parse the PC samples to a statistical report about the time the processor spends where.

Wrong toolchain selection triggers #error "<dirent.h> not supported"

I downloaded all the components required by the GNU ARM Eclipse documentation. However, when I try to build my project on OSX Yosemite (10.10.4); I get this #error "<dirent.h> not supported". Do I need to install something else. Thank you in advance!

---

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 227977]

Building file: ../psp/fsw/shared/cfe_psp_eeprom.c
Invoking: Cross ARM C Compiler
arm-none-eabi-gcc -mcpu=cortex-a7 -mthumb -O2 -g -I../include -I/Users/abencomo/Downloads/cFE-6.4.2b/psp/fsw/inc -I/Users/abencomo/Downloads/cFE-6.4.2b/osal/src/os/inc -I/Users/abencomo/Downloads/cFE-6.4.2b/osal/build/inc -std=gnu11 -MMD -MP -MF"psp/fsw/shared/cfe_psp_eeprom.d" -MT"psp/fsw/shared/cfe_psp_eeprom.o" -c -o "psp/fsw/shared/cfe_psp_eeprom.o" "../psp/fsw/shared/cfe_psp_eeprom.c"
In file included from /usr/local/gcc-arm-none-eabi-4_9-2015q3/arm-none-eabi/include/dirent.h:6:0,
from ../psp/fsw/shared/cfe_psp_eeprom.c:28:
/usr/local/gcc-arm-none-eabi-4_9-2015q3/arm-none-eabi/include/sys/dirent.h:10:2: error: #error "<dirent.h> not supported"

error "<dirent.h> not supported"

^

Add a project importer for CubeMX aC6 projects

Since recent versions of CubeMX can generate Eclipse projects, but the simplistic plug-ins available by default in aC6 (System Workbench), not the extended format used by GNU ARM Eclipse.

it should be possible to write an importer plug-in, to convert the projects to the current format.

in practical terms, the .cproject xml must be processed and the project constructed using the new definitions.

Restart button not working in Eclipse Mars

After switching to Eclipse Mars i noticed that the restart button in the Debug perspective stopped working. I can see in the log-window that "something" is happening (see log below). But the processor doesn't start over. It seems, that the processor just starts running where it was stopped.

The failing system is:
Eclipse: Version: Mars.1 Release (4.5.1) Build id: 20150924-1200
CDT: 8.8.0.201509131935
Gnu Arm Eclipse: 3.2.1.201511061603
Win 7 Pro 64 bit, but same behaviour in Linux Mint 17.1 64 bit under Virtual Box
ToolChain: GNU Tools ARM Embedded\4.9 2015q1 and also GNU Tools ARM Embedded\4.9 2015q2

The working system is:
Eclipse: Version: Luna Service Release 2 (4.4.2) Build id: 20150219-0600
CDT: 8.6.0.201502131403
Gnu Arm Eclipse: 3.2.1.201504061754
Win 7 Pro 64 bit
ToolChain: GNU Tools ARM Embedded\4.9 2015q1 and also GNU Tools ARM Embedded\4.9 2015q2

I tried it with Segger-Jlink Software V4.98e and V5.02g. Both behave the same under Luna and Mars, So this doesn't seem to be the culprit.

This is the log of the failing setup (Mars) after the processor was already halted:
Read 2 bytes @ address 0x08006A2A (Data = 0xF7FF)
Read 2 bytes @ address 0x08006A2A (Data = 0xF7FF)
Read 2 bytes @ address 0x08006A2A (Data = 0xF7FF)
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 20000BA0
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000, R13= 20000B98, MSP= 20003FA8, PSP= 20000B98
R14(LR) = 080030B5, R15(PC) = 08006CEA
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 02000000, CONTROL 2000000, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x08006CEA (Data = 0x46BDAF00)
Setting breakpoint @ address 0x08006A2A, Size = 2, BPHandle = 0x0006
Starting target CPU...

And this is the log of the working setup (Luna) after the processor was already halted:
Resetting target
Halting target CPU...
...Target halted (PC = 0x080001DC)
Read 2 bytes @ address 0x0800189A (Data = 0xF7FF)
Read 2 bytes @ address 0x0800189A (Data = 0xF7FF)
Read 2 bytes @ address 0x08001898 (Data = 0xB508)
R0 = FFFFFFFF, R1 = FFFFFFFF, R2 = FFFFFFFF, R3 = FFFFFFFF
R4 = FFFFFFFF, R5 = FFFFFFFF, R6 = FFFFFFFF, R7 = FFFFFFFF
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= FFFFFFFF, R13= 20002000, MSP= 20002000, PSP= FFFFFFFC
R14(LR) = FFFFFFFF, R15(PC) = 080001DC
XPSR C1000000, APSR C0000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x080001DC (Data = 0xF7FFB508)
Setting breakpoint @ address 0x08001898, Size = 2, BPHandle = 0x0002
Starting target CPU...
...Breakpoint reached @ address 0x08001898
Reading all registers
Read 4 bytes @ address 0x08001898 (Data = 0xF7FFB508)
Removing breakpoint @ address 0x08001898, Size = 2

I don't have any clue how to search further. Any hint?

Regards,
Martin

How to re-enable files excluded from build?

hello, ilg-ul.

Why the default state system/src/stm32f1-stdperiph/ some xxx.c is Not enabled? How to enable them?
I system/src/stm32f1-stdperiph/*.c copy to system/include/stm32f1-stdperiph/ directory. This problem can be solved!

• plug-in version : 2.9.3
• Eclipse version : Eclipse IDE for C/C++ Developers Version: Mars.1 Release (4.5.1) Build id: 20150924-1200
• Java version: 1.8.0_51
• operating system: Gentoo/Linux 64-bit
• toolchain version: gcc-arm-none-eabi-4_9-2015q3

Memory map content messed for duplicate definitions

If definitions of different devices use common families, and the memory map is not defined at device level but at family member, the two trees cannot simply be merged together, definitions should be kept separately.

For this it might be better to propagate definitions from family to device before creating the device tree.

(copied from SF bugs#140).

Linker flags not shown for C++ projects

For C++ projects, the 'Linker flags' box is not shown at:
Project properties > C/C++ Build > Settings > Cross ARM C++ Linker > Miscellaneous

For C projects it is shown.

• v2.6.1-201502281154
• Eclipse 4.5.1
• Java 1.7.0_60
• Windows 8.1

Disconnecting J-Link after the run session is successfully initiated

Hello there,
I am happy to see the project migrated to github, the new site is great as well :)!

I would like to bring up front the case with automatic disconnect feature after successful run again. I am working heavilly with you plugin now and I notice that this feature would be really usefull and would improve work a lot (at least in my opinion). I was wondering either it would be possible for you to add a checkbox in the debug configuration maybe so that after checking it, after a run configuration is used, JLINK would automatically disconnect from target?

The plugin is great at this point, so thank you anyways :).

How to use C style directives in assembler ?

I'm reading u-boot sourc code recently. I found u-boot uses C style directives such as "#define" "#ifdef" and etc in assemble files. But the assembler only recognize directives like ".ifdef" ".define" by default. I guess there is some command line options of the assembler to make it recognize C style directives instead of the default ones. It will be appreciate if some one could tell me how to deal with this issue.

Question: Peripheral view is empty, why?

Short: Nothing appears in Peripheral tab on debug with ATSAMD10/OpenOCD/CMSIS-DAP; why?

Longer:
I have installed the tools on Windows (10).

Installed:
GDB Hardware 8.8.0
Eclipse 4.5.1
Packs 2.2.2.201511061603
(not in use but QEMU 2.2.2.201511061603)
OpenOCD 0.9.0-201505190955
Build Tools 2.6-201507152002
GNU ARM Tools 4.9 2015q3

Procedure:
Create new C project -> Hello World ARM Cortex M
M0+
1 MHz
16 kB Flash
4 kB RAM
Freestanding
Trace: None
Check some warnings
-Og on debug
newlib nano
Vendor CMSIS name samd10

I only have 1 complier so next to Finish

Using Packs view I have installed the packs for SAND10_DFP (1.1.0)

Project->Properties-> C/C+ Build-> settings-> Devices tab

I select Atmel-> SAM D Series -> SAM D10-> ATSAMD10D14A
I click apply then okay

The RAM amount is correct so there must a file for this microcontroller somewhere.

I cut and paste a simple blink the LED with pointers to the PORTA device program and a NOP delay function.

Build-> Yes it complies.

Setup debugger:
GDB openOCD Debugging:
elf is correct on Main tab
Debug tab, config option:
-f board/atmel_samd10_xplained_mini.cfg (this file I created as a modification from the D20 board file)

GDB client setup:
set mem inaccessible-by-default off

Run with debug configuration:
Result light blinks fine, registers report fine, memory dumps fine if you put it in by hand where to watch.

Peripherals tab is empty. Right clicking provides no options.
View reset does not help.

Suggestions?

nRF51 SVD is not being loaded from Nordic DeviceFamilyPack

Hi,

I have successfully installed packages for STM32F030 devices and noted that the SVD files were processed. Producing the following in the log.

Parsing SVD file ".../Packages/Keil/STM32F0xx_DFP/1.4.0/SVD/STM32F030.svd"...

When I install the NordicSemiconductor.nRF_DeviceFamilyPack.8.2.0.pack it does not load the nrf51.svd file and the result is that the devices are not available for selection in the Project Properties Device Selection.

I looked through the working pdsc files for STM devices and I noted that STM SVDs are under "subfamily" nodes while the Nordic SVDs are under a "family" XML node.

Are the Nordic files broken in some way?

OS X 10.11.1
Eclipse 4.5.1
GNU ARM Eclipse plug-ins 201511061603

Regards
Derek

Implement an extension point to add custom toolchains

Add support for developer users to add new GNU ARM toolchains using an extension point. For example, this could be used to add more versions of an already supported toolchain. See
#33
when a toolchain's prefix was changed in a later version.

Do not use Synaptics to install Eclipse on Linux, it does not work

I get the following when trying to install Cross Compiler and OpenOCD plugins:

Cannot complete the install because one or more required items could not be found.
Software being installed: GNU ARM C/C++ Cross Compiler 1.15.2.201511061603 (ilg.gnuarmeclipse.managedbuild.cross.feature.group 1.15.2.201511061603)
Missing requirement: GNU ARM C/C++ Core 2.10.2.201511061603 (ilg.gnuarmeclipse.core 2.10.2.201511061603) requires 'bundle org.eclipse.debug.core 3.8.0' but it could not be found
Cannot satisfy dependency:
From: GNU ARM C/C++ Cross Compiler 1.15.2.201511061603 (ilg.gnuarmeclipse.managedbuild.cross 1.15.2.201511061603)
To: bundle ilg.gnuarmeclipse.core 0.0.0
Cannot satisfy dependency:
From: GNU ARM C/C++ Cross Compiler 1.15.2.201511061603 (ilg.gnuarmeclipse.managedbuild.cross.feature.group 1.15.2.201511061603)
To: ilg.gnuarmeclipse.managedbuild.cross [1.15.2.201511061603]

Global Tools Paths not visible... without installing the plug-ins...

I'm attempting to configure Eclipse to create applications for ARM-based microcontrollers, such as the Nordic nrf51822. According to the instructions at http://embeddedsoftdev.blogspot.com/p/ehal-nrf51.html, I can use Eclipse to do this.

On my Windows 7 Pro laptop, I've installed Eclipse, Java 8, GCC for ARM embedded, ARM Eclipse plugins, and ARM Toolchain, so far. When I get to the build tools (make & rm v2.6), I run into problems.

After running the setup wizard and successfully checking its version with "make --version" command, I went to check the global tools path as instructed in the directions (http://gnuarmeclipse.github.io/windows-build-tools/install/), but found the "Global Tools Paths" area in Eclipse Preferences windows is not there. The instructions to check if the paths definitions are effective, point to C/C++ Build/Environment - here again, my list of environment variables is blank.

Tried installing an older version of the build tools (2.4) and tried again - same result.

Attached are screen shots of the instructions and my Eclipse installation screens for both the Global Tools Paths issue as well as the environment variables issue.
Eclipse issues.docx

Create template plugin or use pack?

I'd like to create something like the templates for STMxxxxx, but for the Nordic chips instead.

What is the correct method of doing this? Templates? Or use the new packs? I'd rather not go through a lot of useless details for templates only to have it all obviated by packs in the next couple of months. I would rather learn the new thing and deal with some instability rather than learn a bunch of details that are a dead end.

I have managed to pull and compile everything with maven. I even created a project to encompass what I need for the Nordic chips, but then I run into having no idea how to integrate this into the Maven build. There is lots of Maven magic in the .parent project and it is not clear how to extend that.

Sorry for creating an issue on this, but it's not clear where else I should make this query. If there is a better place/forum, please give me a pointer and I will go there.

Thanks.

Which code makes semihosting work when not running under debugger?

The FAQ say:

Update: M3/M4 projects generated with version 2.2.1-201404120702 or later check when not running under debugger and skip the trace call, so it is possible to run the application standalone.

But how should it set? I have 2 projects using the trace_printf with semihosting, one is working fine without debugger and the other stuck but I can't find the different, where is this issue being taking care of?

Thanks

What does "Not yet used during build" mean?

"Not yet used during build!" how to handle it?

OpenSTM32 interoperability

Hello there,
I have been using Arm Gnu Eclipse plugin together with a OpenSTM32 plugin for a while and it worked ok. I generated project in CubeMx and imported it to eclipse using OpenSTM32 plugin. Then built it with the same plugin compiller. I then used Arm Gnu Eclipse only for jlink configuration and debugging.
And today i discovered a huge problem- I cannot see registers view... Both plugins got it covered but it wont work together. I cannot use Packs from Arm Gnu Eclipse, because there is no Device section in the project, as the project is made by OpenSTM32 plugin. Also I cannot see registers from OpenSTM32 plugin, as I am using Jlink not ST-Link... I am stuck.

I was wondering, do you know any workaround for this situation maybe, so I could use Packs with OpenSTM32 project? I would really rather use the Arm Gnu Eclipse project structure but I cannot import project from CubeMX to it... :(
Is there a solution? I would apreciate all help!

JLinkGDBServerCL.exe Windows tray icons do not disappear

Hello there,
I have posted a topic on segger forums about the windows icon not dissapearing after succesfull programing in Eclipse:

http://forum.segger.com/index.php?page=Thread&postID=9013#post9013

But they seem to be blaming the plugin- that it doesnt close properly. Could you relate please? I would apreciate all help!

QEMU command line arguments

Hi, I successfully compiled ELF file in Eclipse and when I click Debug in GDB QEMU Debugging configuration I get this error:

Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".

Running Eclipse Kepler with 32bit QEMU on Winx64
I tried to run QEMU manually with command line but I don't know which command line arguments I have to pass. I ended up with :

qemu-system-gnuarmeclipse.exe -board NUCLEO-F103RB -mcu STM32F103RB --image ..\images\NUCLEO-F103RB.jpg

Eclipse plugin version:
GNU ARM C/C++ QEMU Debugging 2.1.3.201512141335

Eclipse QEMU console:
GNU ARM Eclipse 32-bits QEMU v2.4.50 (qemu-system-gnuarmeclipse.exe).
Board: 'STM32-H103' (Olimex Header Board for STM32F103RBT6).
Device: 'STM32F103RB' (Cortex-M3 r0p1, MPU), Flash: 128 kB, RAM: 20 kB.
Command line: 'qemu_test 3 2 1' (15 bytes).
Cortex-M3 r0p1 core initialised.
LED: Green active low 14*12 @(97,243) /machine/mcu/stm32/gpio[c],12
GDB Server listening on: 'tcp::1234'...
QEMU 2.4.50 monitor - type 'help' for more information
(qemu) QEMU 2.4.50 monitor - type 'help' for more information
(qemu) Cortex-M3 r0p1 core reset.

I have bit older GCC but I managed to compile blink example to the ELF file.
GDB version:
C:\Program Files (x86)\GNU ARM Eclipse\QEMU\2.4.50-201510290935-dev\bin>arm-none
-eabi-gdb.exe --version
GNU gdb (GDB) 7.2.50.20100908-cvs
Copyright (C) 2010 Free Software Foundation, Inc.
This GDB was configured as "--host=i686-mingw32 --target=arm-none-eabi".

Thank you for any suggestions

Use quotes around openOCD echo command (-c 'echo "Started by GNU ARM Eclipse"')

When I use "StartOpenOCD locally", debugging doesn't work because openOCD crashes because the plugin attatches "-c echo "Started by GNU ARM Eclipse"" to the arguments. Launching OOCD w/o this argument, it works flawlessly

Non-related to plug-ins (OpenOCD silent installations on windows 7)

I am trying to install https://github.com/gnuarmeclipse/openocd/releases/download/gae-0.9.0-20150519/gnuarmeclipse-openocd-win64-0.9.0-201505190955-setup.exe from command line. I am successfully able to install silently with /S option but failed to install to different folder than default. The silent installations always installing openocd at "C:\Program Files\GNU ARM Eclipse\OpenOCD". Kindly let me know how install to different folder than default one.

Following are the commands i used to install openocd at "L:\openocd":

C:>"C:\Users\rkandur\Downloads\gnuarmeclipse-openocd-win64-0.9.0-201505190955-setup.exe" /S /D=l:\openocd

Where can i configure and manage a gdbinit script for DGB SEGGER J-Link Debugging

Hello ilg-ul,

my development environment ist eclipse mars latest cdt and gnuarmeclipse plugin and all things are working pretty. Now i would like to add a gdbinit file like old settings from pure gdb sessions. In my old environment i add a .gdbinit with following settings:

define hook-step
mon cortex_m3 maskisr on
end
define hookpost-step
mon cortex_m3 maskisr off
end

In the source file ilg.gnuarmeclipse.debug.gdbjtag.jlink/src/ilg/gnuarmeclipse/debug/gdbjtag/jlink/Configuration.java at line 276 is a comment that these settings are set in the LaunchSequence. Now i thing that the arm-none-eabi-gdb --interpreter=mi2 --nx process on linux is a client process, so i look in the main documentation from JLinkGdbServer for information to handle the maskisr on and of function.

My question: can you tell me some examples how i can enable maskisr?

Another cool topic:
Now i have test some settings to flash a binary into the LPC1768 chip with J-Link, here are my results:

You can set up a External Tools RUN configuration in eclipse to start the JLinkExe program directly with parameter to flash a bin file directly in ROM. So you don't need to start a debug session for the same result and it is very fast.

On Location: /opt/SEGGER/JLink/JLinkExe
On Working Directory: ${workspace_loc:/LPC17xx_Blinky}
On Arguments: -device LPC1768 -speed 1000khz -CommanderScript ${workspace_loc:/LPC17xx_Blinky}/openocd/lpc17xx_flash.jlink

File lpc17xx_flash.jlink:
si
speed 4000
r
h
loadbin /projekte/eclipse/workspace450/LPC17xx_Blinky/Debug/LPC17xx_Blinky.bin,0x0
verifybin /projekte/eclipse/workspace450/LPC17xx_Blinky/Debug/LPC17xx_Blinky.bin,0x0
q

The same in a bash script jlink_lpc17xx_flash.sh:
#!/bin/bash -
#===============================================================================
#
#          FILE: jlink_lpc17xx_flash.sh
#
#         USAGE: ./jlink_lpc17xx_flash.sh
#
#   DESCRIPTION: Start JlinkExe with jlink CommanderScript to flash the program in ROM
#
#       OPTIONS: $1 is the workspace project
#  REQUIREMENTS: ---
#          BUGS: ---
#         NOTES: ---
#        AUTHOR: Michael Kruschinsky (), [email protected]
#  ORGANIZATION: mySMK
#       CREATED: 19.09.2015 00:23:24 CEST
#      REVISION:  ---
#===============================================================================

set -o nounset                              # Treat unset variables as an error

#/opt/SEGGER/JLink/JLinkExe -device LPC1768 -speed 1000khz -CommanderScript /projekte/eclipse/workspace450/LPC17xx_Blinky/openocd/lpc17xx_flash.jlink
/opt/SEGGER/JLink/JLinkExe -device LPC1768 -speed 1000khz -CommanderScript $1/openocd/lpc17xx_flash.jlink

regard
Michael

Help Wanted

I installed the plug-in using the http address in eclipse but I cannot see any of the gnu arm toolchain when I create a new projet. Any help or guidance will be appreciated

Here are some system spec:
-Window 10 x64
-GNU ARM C/C++ Cross Compiler 1.15.2.201511061603 and
all of the other packages of 7th november 2015.
-Eclipse : Mars.1 Release (4.5.1)
-java version "1.8.0_66" and "1.7.0_79"
-MinGW : gcc (GCC) 4.8.1
-GNU Tools ARM Embedded 4.9 2015q3
-GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.10.0-dev-00141-g09aeb96-dirty

After removing Packs, other views are not updated

After removing packages, the icons in the Board view do not turn grey.
Probably other views must be also updated.

(copied from SF bugs#115).

SourceTree EHAL clarification needed

Continuing to work through Eclipse/ARM installation steps, and got to the point where EHAL for nRF51 needs to be added.
Instructions (http://embeddedsoftdev.blogspot.com/p/ehal-nrf51.html) say "Clone the EHAL source tree. This can be done using git command line tools or use SourceTree from this site http://www.sourcetreeapp.com. github : https://github.com/I-SYST/EHAL."
As a newbie to SourceTree and Eclipse (and using Windows 7 platform) I downloaded both the SourceTree app and the EHAL zip file, but I'm unsure where to place the EHAL stuff. Instructions say to mimic a source tree, which is expressed as relative to "/your_root" - where is this "/your_root" folder (by default) on a Win7 Eclipse install? I'm not seeing anything obvious in my folder structure.

toolchain path for J-Link with LPCXpresso (Eclipse-based IDE from NXP)

I'm using LPCXpresso 7.9.2_493 (that is an Eclipse-based IDE released from NXP, I think it is based on Eclipse 4.4.2). I'd like to use J-Link debugger/probe in LPCXpresso.

Segger suggests to use GNU ARM Eclipse plug-ins as I did just now.

First problem: I can't see Devices tab in the Settings window of project Properties. It seems this is not mandatory, so I didn't care about it.

I created a new Debug Configuration and set the cross_prefix substring (as indicated by Segger in this link).

Second problem: when I launch the debug session, the error Error while launching command: arm-none-eabi-gdb --version appears. I think gdb client can't be found, so I changed the executable from ${cross_prefix}gdb${cross_suffix} to C:\nxp\LPCXpresso_7.9.2_493\lpcxpresso\tools\bin\arm-none-eabi-gdb.exe.

Now it seems to work.

Make the Devices tab available for projects created with other plug-ins

Check if it is possible to enable the Devices tab for any projects, not only projects created by GNU ARM Eclipse plug-ins.

This will will allow LPCXpresso, aC6, etc, to assign devices to projects.

READ ME FIRST!

Please use this tracker to record only issues related to the GNU ARM Eclipse plug-ins. DO NOT record here any other issues related to the tools (QEMU, OpenOCD, Build tools, etc), which should be addressed to their corresponding trackers). Web content issues should be addressed to the Web Issues tracker. J-Link specific questions should be addresses to SEGGER support.

For general questions and requests for help that cannot be classified as bug reports or requests for enhancements, please use the GNU ARM Eclipse forum.

Before posting here, please check the list of Known Issues and the FAQ.

When entering a new issue, please be sure you provide:

• plug-in version (sorry, no support for 0.5.x)
• Eclipse version
• Java version
• operating system (sorry, no requests for Win XP 64)
• toolchain version
• the detailed and complete list of steps to reproduce the bug (mandatory)

Please understand that without being able to reproduce the bug we cannot identify your problem.

To enter new issues, you need to first login to GitHub.

Note: the text should respect the markdown syntax; preview the message before posting and correct if it does not look as you expected, especially inline code or other quoted text.

Set arm family from device selection

When a device is assigned to the project, set the arm family automatically in project settings.

(Migrated from SF feature-requests#80).

Create a user discussion forum

In the past I had several requests to open a discussion forum for GNU ARM Eclipse users.

I think such a request makes sense, and will allow users to exchange ideas and help each other (hopefully also reducing the number of tickets registered here).

Since my experience with forums is relatively small, I would like to suggest a solution, and you to comment on it.

Up to now I evaluated three solutions, and the one that has the best profi look is:

• http://www.element14.com/community/groups/gnu-arm-eclipse

It is based on jive, and looks identical to the one used by the ARM Community site. GNU ARM Eclipse is a complex group, with Blog, Discussions, Documents and many more.

Access is currently open to everyone and non-members can view content.

Previous experiments include:

• http://gnuarmeclipse.forumotion.net, a phpBB forum, with a common look, not particularly attractive to my opinion;
• https://groups.google.com/forum/#!forum/gnu-arm-eclipse-users, a Google discussion group, too simple for my taste.

If there are no better ideas, I suggest to make the Element14 group the public discussion forum for GNU ARM Eclipse.

What do you think?

Packs outlook is not refreshed after pack install

After installing a new pack version, the outlook continues to display the summary outlook, not the full outlook, requiring a click on the pack version to refresh.

(migrated from SF bugs#142).

Add Cortex-M7 hard FP specifics (fpv5-d16 & fpv5-sp-d16)

The Cortex-M7 has a new version of FP (v5).

In the managedbuild.cross plug-in, add new entries in the toolchain definition, to accept the two new hard FP settings fpv5-d16 & fpv5-sp-d16.

GDB problem error when debugging u-boot with JLink

I'm debugging u-boot-2015 with GDB and JLink.
All the processes on assembler code are OK.
But when jumping to C code GDB can't display the source code correctly. It will displays some codes in other places. But I'm sure the binary code is still executing correctly.
I've tried two different versions of u-boot(2015.10 and 2015.07), but it appeared the same problem.

Fix duplicate Docs

In certain conditions, the documents displayed in the Docs view appear twice.

(migrated from SF bugs#143).

Add support for arm-none-eabi-gdb 7.10

Hi,

I'm using the Eclipse plugin for debugging with a SEGGER JLink Debugger.
Up until now everything worked fine.

I'm using several STM32F4 microcontrollers.

However, a few weeks ago the arm-none-eabi-gdb was updated to version 7.10-2. Now the Eclipse plugin can't debug anymore.

I get this error:

Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".

Changing back to the older GDB version 7.9 helps. However, this version is compiled with old dependencies and cannot longer be used on my system.

The output of the JLinkGDBServer shows, that it waits for a connection. This means that GDB isn't even connecting to the server.

Using GDB manually everything works fine. Therefore I think it's a problem with the plugin.

How can I solve this issue?

Best regards

arm-none-eabi-gdb 7.10 not yet supported

gnuarmeclipse openocd plugin stops with
"Error in final launch sequence
Failed to execute MI command:
-exec-run"
This used to work correctly and now after standard installation of eclipse (4.4 or 4.5) and gnuarmeclipse plugins it seems to start openocd debug session as a local one instead of remote.

Do not use macros in debug configurations for non GNU ARM Eclipse projects

For projects not created with GNU ARM Eclipse, when creating debug configurations, do not use ${cross...} because these macros are not available.

Special care for makefile projects.

Add Segger Real Time Terminal (RTT) support to J-Link plug-in

As a faster alternative to semihosting, RTT provides a bidirectional channel between the target and the host, that can be used to send trace messages.

Keil packs server down, returns 404 for .pdsc files

Hi, I have a problem with update pack. You can not execute refresh package. In the error window is writen : "http://www.keil.com/pack/.......pdsc." Failed to open connection, response code 404. I re-install Eclipse and OFF antivirus. I do not know where I find fault. Please help. Thank you beforhand for your time.

Manually create managed projects without templates

This might be a bit of a silly question, but is it at all possible to build a STM32F4 project without the Newlib and µOS++ III libraries?

I've seen some minimalistic STM32F4 examples that just contain a main.c, and ldscript and some of the HAL libraries, but not sure how to compile them with GNU ARM Eclipse. I'd like an approach where instead of going through __initialize_hardware(), I can have main() be my entry point instead of having µOS++ III initialize the hardware before main is executed.

I'd like to, for example import the STM32F4 Cube examples and compile them with GNU ARM Eclipse, but not entirely sure how.

Update aarch64-elf-g++ prefix for Linaro AArch64 bare-metal toolchain version 4.9.

Please note that new Linaro tool provided for Baremetal 64bit has been renamed from aarch64-none-elf-g++ into aarch64-elf-g++, thus an update is required.

Question: is there a way to configure the prefix for each toolchain similar with what we have for toolchain's path/name, explained here: http://gnuarmeclipse.github.io/developer/preferences/ilg.gnuarmeclipse.managedbuild.cross?

Usability problems with the debugging Tabs on OS X

On small screens, the content of some debugger configuration windows is too long, and require scrolling the window, which, on OS X, sometimes is difficult.

Ideally the tabs should be redesigned to fit a normal laptop screen without having to use the scroll bars.

(Migrated from SF support-requests#78).