Eclipse Versions:
2023-09 (4.29), 2023-06 (4.28), 2023-03 (4.27), 2022-12 (4.26), 2022-09 (4.25), 2022-06 (4.24), 2022-03 (4.23), 2021-12 (4.22), 2021-09 (4.21), 2021-06 (4.20), 2021-03 (4.19), 2020-12 (4.18), 2020-09 (4.17), 2020-06 (4.16), 2020-03 (4.15), 2019-12 (4.14), 2019-09 (4.13), 2019-06 (4.12), 2019-03 (4.11), 2018-12 (4.10), 2018-09 (4.9), Photon (4.8), Oxygen (4.7), Neon (4.6)
Reviews Sign in to post reviews
GNU MCU eclipse 4.7.2 problems
Submitted by Ferenc Keresztúri on Thu, 2020-04-16 09:06
If I install "GNU MCU eclipse 4.7.2" it did not install the GNU ARM C/C++ cross compliler. Is it part of the package?
Thanks,
Re: GNU MCU eclipse 4.7.2 problems
Submitted by Ferenc Keresztúri on Fri, 2020-04-17 12:18
It installs the "ilg.gnumcueclipse.managedbuild.cross.arm_2.7.1.202001271244.jar" package, but in the preferences/C/C++/Build/ "Workspace tool path" did not appear (missing).
Re: GNU MCU eclipse 4.7.2 problems
Submitted by Liviu Ionescu on Fri, 2020-04-17 09:26
https://gnu-mcu-eclipse.github.io/support/
Profiling the code- RISC V
Submitted by Prashant Joshi on Sat, 2019-08-17 00:20
hI,
I am using gnu mcu eclipse. Trying the run the code targeted to RISC V tool chain. I wish to perform the software debugging and profile the code to analyze - cpu cycles, DMA access, cache related issues. Please suggest the proper steps.
Thank you,
Dr. PVJ
Re: Profiling the code- RISC V
Submitted by Liviu Ionescu on Mon, 2019-08-19 11:55
https://gnu-mcu-eclipse.github.io/support/
error installing plugin in ubuntu 18.04
Submitted by Mehdi Molu on Tue, 2018-08-07 18:26
I am getting following error "unable to read repository at (gnu-mcu-eclipse url)''
Broken entry
Submitted by Carsten Reckord on Wed, 2018-01-10 15:44
The installation data for this entry is broken at the moment. All listed installable units are missing a ".feature" at the end, meaning they can't be found on the update site and therefore installation through the Marketplace Client fails with "The following solutions are not available: GNU MCU Eclipse 4.2.1".
Re: Broken entry
Submitted by Liviu Ionescu on Wed, 2018-01-10 16:54
I edited the marketplace page and added .feature at the end of each feature id, and now it seems ok.
Thank you for the hint,
Liviu
Re: Broken entry
Submitted by Liviu Ionescu on Wed, 2018-01-10 16:46
Thank you Carsten, I nticed that from a certain moment installing from the marketplace failed, but I don't remember doing anything special with my builds. I even registered a bug in bugzilla, but received no answer. Installing directly from the update site works as expected.
Can you be more specific on the missing `.feature` at the end?
The feature projects do have a .feature at the end. And also the feature name, as defined in feature.xml, has a .feature at the end. (https://github.com/gnu-mcu-eclipse/eclipse-plugins/tree/develop/features).
Can you suggest a fix?
Re: Broken entry
Submitted by Liviu Ionescu on Wed, 2018-01-10 16:46
Thank you Carsten, I nticed that from a certain moment installing from the marketplace failed, but I don't remember doing anything special with my builds. I even registered a bug in bugzilla, but received no answer. Installing directly from the update site works as expected.
Can you be more specific on the missing `.feature` at the end?
The feature projects do have a .feature at the end. And also the feature name, as defined in feature.xml, has a .feature at the end. (https://github.com/gnu-mcu-eclipse/eclipse-plugins/tree/develop/features).
Can you suggest a fix?