#21 Programmer as Run Configuration

[Manuel Stahl]

The Download Job for the Programmer (i.e. AVRdude) should be implemented as a Run Configuration not as a seperate button.

This would integrate more in the current Eclipse CDT concept.

Debugging In-System or with a simulator would then be a Debug Configuration.

[Thomas Holland]

Logged In: YES
user_id=1542541
Originator: NO

Hi Manuel,

I will look into this after I finish 2.3

Liebe Grüße,

Thomas

[Manuel Stahl]

Logged In: YES
user_id=91183
Originator: YES

Here is the Tutorial how to implement a LaunchConfigurationType.

http://www.eclipse.org/articles/Article-Launch-Framework/launch.html

[Nobody/Anonymous]

Maybe its also interesting to have a look at the Eclipse Target Management: http://www.eclipse.org/dsdp/tm/

I think this is now the official way how to support remote targets, like microcontrollers.

[Thomas Holland]

Thanks to the pointer to the DSDP-Target Management Project. I have been using it already for webDAV and SFTP purposes, but I did not follow the project itself.

I have browsed through the project pages and it looks interesting, although DSDP is currently a maze of intertwined technology sub-projects, some active -- some not. For the time being I will wait until the dust settles after the Galileo (Eclipse 3.5 / CDT 6.0 / TM 3.1) release (Mid 2009) and then check back to see how the AVR plugin can make use of DSDP.

One problem that I already see is that DSDP is complex stuff aimed at professional developers. However my impression is that quite a few AVR developers are hobbyists and embedded development beginners. All complexities of DSDP would need to be hidden by the plugin to not scare the beginners away.

For now I will continue my present roadmap which is:

• Implement target configurations similar to AVR32 Studio (thanks Manuel for the pointer)
• Target Configuration editor currently about 50% complete

• Target Configuration view about 30% complete.

• Add LaunchConfigurations for the Debugger and Uploads using the target configurations.

The problem I have are the many possible configurations users can have: avrdude, avarice, simulAVR, Bootloaders, JTAG, ISP etc. etc.
With the target configurations I think I now have a way to handle all the different settings in one place and they need to be done only once -- not over and over again for each project and each LauchConfiguration.

brgds,

Thomas