assembly program + avrdude gui + duemilanove

bperrybap:
The beauty of using the commandline is that there is nothing hidden.
You get exactly what you type, which means that as long as the
underlying commandline tool works, you can always make it work.
This is not always the case when using a GUI wrapper.

Another benefit is that the commandline works across multiple
OS's whereas most GUIs are limited to running on Windows.

--- bill

Understood, but the command line options available for AVRDUDE can be very overwhelming for many typical arduino users (such as me anyway, typical or not) to understand what they do and why one might want or need to use them or not use them. Trust me a GUI 'wrapper' for running AVRDUDE does target some users perfectly.

Not all arduino users come to the table with the same skill and experience levels of other users and they may indeed never try to enter the world of AVRDUDE command line level statements if they can find a tool that works for them that would avoid that. I'm just saying that the specific GUI that the OP is using works very well, for me anyway. It even allows one to add command line arguments if one wants and knows how. I don't plan on ever learning to make my own make files to run the arduino gcc tool chain manually either.

Now only if the Arduino IDE would park a copy of a sketch's hex file into the user's sketch directory directly like it once did so many moons ago, I would be a happier camper. :wink:

Lefty