I received a couple of SOIC-8 ATtiny85s recently and, as is my wont, I stuck one of them onto a DIL adapter for testing before I stored them away.
I created a basic 'Hello World' (LED blink) program and uploaded using AVRDude and an USBASP.
This was (is) just a simple 'toggle-pin-after-interval' type program and there was no attempt to modify any fuse settings.
But something went awry and the device would not respond to the USBASP after the upload.
I dug out a Digispark ATtiny85 device, and this also failed after trying to upload the program.
Neither would respond to the Microchip SNAP using MPLABX but I am not going to detail the extensive sequences I went through with that platform.
I then used an Arduino UNO to create an HV programmer and was able to read the new ATtiny85 device fuses, which were reported as L: 52, H: 5E and E: FE.
Although none of these fuse values are the defaults, the High fuse RSTDISBL bit being programmed would be expected to be the problem.
But the *Arduino based High Voltage programmer could not write new fuse values to the device, although it went through the motions.
I swapped in the Digispark and the Arduino HV programmer reported the fuses on this device to be L: E1, H: 9D and E: FE
These settings create a number of issues, the most significant probably being a 'reserved' clock select and debugWire enabled.
The Arduino HV programmer failed to reprogram the Digispark ATtiny85 fuses initially (many attempts) but eventually managed to write these to their default values.
This Digispark ATtiny85 now responds to the USBASP (e.g. avrdude -p t85 -c usbasp -v -B 3)
I have two questions that those here with their extensive knowledge and experience might be able to answer
1) Has the new ATtiny85 been subject to a stroke? Is its mind still functional, but unable to respond properly to the outside world?
2) Is there any way to recover from this? Is there any other programmer and/or technique that might be used to restore the 'normal' functionality of the RESET pin?
*The 'Arduino HV Programmer' used is based on http://www.electronics-lab.com/r...
I am sorry if this matter has been addressed elsewhere on this forum. I have searched for this issue and read quite a bit about related matters but have not yet come across a post that really matches what I have experienced.