Find an error, fix it, download, all while keeping everything plugged in place.
When all done, pull the chip & plug it into the standalone project.
So why not just upload your final sketches to the standalone (non-bootloaded chip) project when its working (I'm sure that your method is good for some things but I'm wondering if people are spending time loading bootloaders when all they really need is to set the fuses to get their clock speeds right )
o why not just upload your final sketches to the standalone (non-bootloaded chip) project when its working
I wanted to program the boot loader into it so that I can develop the new software directly on the hardware it will run on.
but I prefer working in the Arduino IDE instead of in the gcc command line environment.
or via a £5 USB programmer.
Quoteor via a £5 USB programmer.The quick answer is that USB programmers are traditionally more expensive than that, and significantly more difficult to use. An Arduino is essentially a $10 microcontroller with a $10 USB interface that service double purpose: communications AND program loading. Adding a $10 programmer is a 33% cost increase... (those are sorta "wholesale" costs...)
What is somewhat ironic is that these days the USB to serial interface/cable costs more than a low cost USB ISP programmer.
There are some great low cost USB to Serial boards out there. I've actually lookedat that one. While usable, it is unfortunate that they didn't use the FTDI pinout -it would have made it a direct drop in for the Arduino crowd.