The ODeV idea

Why only two MCU?
Why only manual managed Makefile?
Why long time-consuming debug sessions?
Why not application ad-hoc integrated tools?

The Eclipse revolution takes the power of hi-end software development tools into embedded world. The Eclipse open architecture allows to customize the IDE both, for general embedded multitasking development, and for end-application specific features.

For example I could image a Plug-in to trace the tasks context switch during a debug session, and plot the result in a graphical manner. I could have also a Plug-in displaying a GUI to configure a motor control application (SPEED, PID, etc.) and automatically generate the needed source files.

This is the ODeV idea (http://developers.stf12.net/odev)

I'm working on it. I'm analyzing it. I will update both this post and the web page.

Should you be interested on this idea, or if you would like to contribute to this idea, please don't hesitate to contact me.

Stefano