Is a hvsp fuse resetter needed to turn off Brown Out Detect for ATtiny85?

I want to utilize the attiny core that is available at: 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( and a ATtiny85 breadboard breakout board(

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( 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.

You shouldn't need High Voltage Parallel Programming unless you set the flags to disable serial programing or the Reset pin.

I couldn't find any AVR chip with the 1E 05 02 signature. Perhaps the data or clock line had a bad connection?

How do I find out if the chip has a stable external clock connection? Also, I noticed the device signature always reads a different value every time I send any avrdude command. I am seriously thinking about headind over to radioshack to buy a 12mhz ceramic crystal and the appropriate caps to redo the breadboard Breakout. I'm not sure if that would work because I still get the error msg that was explained above when I try to program off the Breakout. Sometimes the programmer can't sync.

I noticed the device signature always reads a different value every time I send any avrdude command.

Sounds like a bad connection. Re-do the wiring.