Add a sound effect for success and failure.
QuoteAdd a sound effect for success and failure. You're talking about optiLoader rather than bootloader itself, right?Interesting idea. An LED is more likely (I supposed I could do either.)Actually, there are all sorts of possibilities if I want the loader to become a featureful stand-alone AVR programmer
single avrdude command vs 2 commands
do I have something wrong or this bootloader used on Arduino 2009 doesn't auto reset after uploading a new sketch?
It turns out that avrdude resets the USB device when it closes the connectionon all operating system other than FreeBSDso the USB device (the dragon in this case) must re-enumerate.This enumeration takes time, if a second avrdude command comes in beforethe device is fully enumerated with the OS, the usb device will not be seen.This causes the second avrdude command to fail.
putyn@koala:~/optiboot$ make atmega8avr-gcc -g -Wall -Os -fno-inline-small-functions -fno-split-wide-types -mshort-calls -mmcu=atmega8 -DF_CPU=8000000L '-DLED_START_FLASHES=3' '-DBAUD_RATE=9600' -c -o optiboot.o optiboot.coptiboot.c: In function 'main':optiboot.c:318: error: 'UART_DDR' undeclared (first use in this function)optiboot.c:318: error: (Each undeclared identifier is reported only onceoptiboot.c:318: error: for each function it appears in.)optiboot.c:318: error: 'UART_TX_BIT' undeclared (first use in this function)optiboot.c: In function 'putch':optiboot.c:525: error: 'UART_PORT' undeclared (first use in this function)optiboot.c:526: error: 'UART_TX_BIT' undeclared (first use in this function)optiboot.c: In function 'getch':optiboot.c:563: error: 'UART_PIN' undeclared (first use in this function)optiboot.c:564: error: 'UART_RX_BIT' undeclared (first use in this function)make: *** [optiboot.o] Error 1putyn@koala:~/optiboot$