I want to utilize the attiny core that is available at: http://code.google.com/p/arduino-tiny/ I originally uploaded ATtiny85 16MHz (external crystal; 4.3 v BOD) bootloader successfully using the Arduino IDE 1.0, ArduinoISP2 sketch with the Arduino Mega2560. Now, when I attempt to upload a new bootloader with the same setup AVRdude spits out this error message:
avrdude: Device signature = 0x1e0502 avrdude: Expected signature for ATtiny85 is 1E 93 0B Double check chip, or use -F to override this check.
avrdude done. Thank you.
My current ATtiny85 programming setup consists of a ATtiny85, USBtinyISP v2.0(http://www.ladyada.net/make/usbtinyisp/parts.html) and a ATtiny85 breadboard breakout board(http://allgaiershops.com/product_info.php?cPath=22&products_id=33)
ArduinoIDE 1.0 AVRdude command:
D:\electronics\ide\arduino-1.0-windows\arduino-1.0\hardware/tools/avr/bin/avrdude -CD:\electronics\ide\arduino-1.0-windows\arduino-1.0\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -pattiny85 -cusbtiny -e -Uefuse:w:0xFF:m -Uhfuse:w:0xD4:m -Ulfuse:w:0xFF:m
I bought an USBtinyISP v2.0 from adafruit thinking the ArduinoISP way of programming and burning bootloaders was buggy; however, I am still receiving the above AVRdude error message. I also noticed every time I would try to burn the bootloader the Device signature would change values. Is that normal?
After reading a bit more about fuses and using a fuse calculator(http://www.frank-zhao.com/fusecalc/fusecalc.php?chip=attiny85) I noticed the BOD setting is a hfuse. Since I enabled the BOD previously, am I going to need a hvsp fuse re-setter to reset the chip back to its default fuse settings?
I went into the boards.txt file supplied by the tiny core to look at the bootloader that I previously chose to burn(ATtiny85 16MHz (external crystal; 4.3 v BOD)). I do not think BOD was actually enabled because the attiny85at16e.bootloader.high_fuses equals 0xD4 when attiny85at16e.bootloader.high_fuses should equal 0xDC to enable 4.3 v BOD.