Visual GDB vs Crossworks

[asgard20032]

I need help to decide which IDE for arm programming. After checking many free IDE, like coocox, Embitz, and EmIDE, crossworks, and visual GDB, i cam to the conclusion i will either use crossworks or visual gdb, since they offer better device support (include header, LINKER SCRIPT, library...). I want to concentrate on programming, not the tool-chain.

So now I am down to two choice, either crossworks or visual gdb. What are the good and bad of each? How do they compare?

[nctnico]

You didn't look at Eclipse CDT?

[asgard20032]

Does CDT include linker script, header and every material needed? Do I have to write make file? Do I have to to know openocd debugger? Does it do debugging? Does it support all kinetis and stm32 and tiva and cc3200 and lpc?

[nctnico]

Does CDT include linker script, header and every material needed? Do I have to write make file? Do I have to to know openocd debugger? Does it do debugging? Does it support all kinetis and stm32 and tiva and cc3200 and lpc?

Eclipse CDT does all the building for you; no need to write makefiles. Eclipse is also extremely good at parsing header files and source files to be able to navigate through complex/large piece of source code, offers integration with various version control systems, etc. Ofcourse debugging is supported but I suggest to debug as much high level code as you can on a PC  (also using Eclipse) because that is infinitely easier than the best 'hardware' debugger.
For microcontroller support look here:
https://sourceforge.net/projects/gnuarmeclipse/

[legacy]

Eclipse is a dead big fat elephant
do we really need it ? 

[legacy]

Code: [Select]

Sonoku lib_mem_xstatic_v3 # nano project
current_folder
lib_queue_gp_v3
test_app


Code: [Select]

Sonoku lib_mem_xstatic_v3 # nano project.cflag
auto


Code: [Select]

Sonoku lib_mem_xstatic_v3 # ls *.c
app.c  lib_mem_kr_alloc_v1.c  lib_mem_xstatic_toy_v3.c  lib_mem_xstatic_v3.c
Sonoku lib_mem_xstatic_v3 #


Code: [Select]

Sonoku lib_mem_xstatic_v3 # myIDP-build-project-makefile-v4.2
analyzing inter modules dependencies … done
building Makefile … done


Code: [Select]

Sonoku lib_mem_xstatic_v3 # make
- compiling app ... done
- compiling lib_mem_kr_alloc_v1 ... done
- compiling lib_mem_xstatic_toy_v3 ... done
- compiling lib_mem_xstatic_v3 ... done
- linking to my
Sonoku lib_mem_xstatic_v3 #

Just as there are reasons why people write, there are reasons some people don't write. If you talk to enough people over the course of days, maybe even months: but why on the why people don't write a decent tool like the above?

• simple
• easy
• light

simple like a simple or uncompounded word, 'cause we do not like big fat dead elephants 


It's a tool I have created because asked by my boss, he has the Copyright.
I am not a pro-dude, so everyone skilled enough can replicate my work!

[legacy]

It could be integrated into Geany, which offers useful plugins!
check it out 

Code: [Select]

*  dev-util/geany
      Latest version available: 1.24.1
      Homepage:      http://www.geany.org
      Description:   GTK+ based fast and lightweight IDE
      License:       GPL-2+ HPND

*  dev-util/geany-plugins
      Latest version available: 1.24-r1
      Homepage:      http://plugins.geany.org/geany-plugins
      Description:   A collection of different plugins for Geany
      License:       GPL-2