IDE for Firmware development


#1

Hi all,
what IDE are you using for firmware development? I'm working on Windows...


#2

Eclipse for Firmware, NetBeans for the GUI.


#3

Ok for Netbeans...but Eclipse compiler? Particular toolchain?


#4

There is the GNU Arm toolchain plugin


#5

Are there any guidelines to import axoloti firmware in eclipse with http://gnuarmeclipse.github.io/ ?


#6

Import Makefile project should do the trick.


#7

Maybe my setup is not correct... i imported Makefile project :sob:
`Description Resource Path Location Type
Field 'fattrib' could not be resolved ui.c /axoloti-firmware line 323 Semantic Error
Field 'fname' could not be resolved ui.c /axoloti-firmware line 318 Semantic Error
Field 'fname' could not be resolved ui.c /axoloti-firmware line 320 Semantic Error
Field 'fname' could not be resolved ui.c /axoloti-firmware line 322 Semantic Error
Program "" not found in PATH axoloti-firmware C/C++ Problem
Program "echo" not found in PATH axoloti-firmware Project Properties, C++ Preprocessor Include.../Providers, [CDT GCC Built-in Compiler Settings Cross ARM] options C/C++ Scanner Discovery Problem
Symbol 'AM_DIR' could not be resolved ui.c /axoloti-firmware line 323 Semantic Error
Symbol 'FR_OK' could not be resolved ui.c /axoloti-firmware line 315 Semantic Error
Symbol 'FR_OK' could not be resolved ui.c /axoloti-firmware line 318 Semantic Error
Symbol 'FR_OK' could not be resolved ui.c /axoloti-firmware line 348 Semantic Error
Symbol 'NORMALPRIO' could not be resolved ui.c /axoloti-firmware line 471 Semantic Error


#8

I partially solved my Eclipse setup, but now i've to add all include paths :anguished:


#9

this is i think to be expected, as far as I could tell, eclipse will only import the files, things like include directories, and also things like chibios will not be setup, nor with the compiler flags/defines etc.

what this means, is you need to use the make and the makefile to compile, you don't compile directly from eclipse...

UNLESS you plan to do all the above manually, and then you will have to be very careful that you see aLL the defines and flags correctly, otherwise it will compile not but run as expected, frankly i didn't think it worth it, as you can still debug without this.

(or of course, if you can find a way to get eclipse to be more intelligent about parsing the makefile, to bring in all settings/includes/defines/compiler & linker flags. which I couldn't ... but I'm not a big eclipse user)

another point, last time I tried, patches could not be debugged, as the symbol references were not aligned correctly. it was a while ago and I didn't look too deeply, but it did not 'just work'... id be interested if you have more success in this.


#10

Eclipse can launch make with a makefile project, and parse gcc errors.
More work is needed for c/c++ reference discovery to make it find chibios etc, not sure about the right steps. Ah, here is a eclipse/chibios setup guide!


#11

Ok, so i can try my old friend http://www.coocox.org/ :slight_smile: