During this time, I was designing keyboards using Atmel's series of microcontrollers at90usb128x/64x and atmega32u4. One of the at90 microcontrollers was locked due to an incorrect fuse bit setting, which caused Progisp to be unable to flash the program. I checked online and found several ways to unlock it:
Since the fuse bit of my microcontroller is set to the internal clock, the above three methods are invalid, and I can only resort to the last straw - high-voltage programming. Most of the solutions found on Baidu only support high-voltage programming of low-end chips such as atmega8/16. After searching on Google, I found a solution that can support unlocking of most avr microcontrollers https://www.instructables.com/id/How-to-fix-dead-atmega-and-attiny-avr-chips/This It was a plan given by a foreigner. My schematic is based on his basic design, mainly changed to support qfn64, qfn44 and qfp44 packages, which can be used for high-voltage programming of at90usb128x/64x and atmega32u4, and changed to use an external power supply. If you need to program dip28 or dip40 packaged chips, you can use his original design. For the pin connections of each chip, please refer to the instructions on this website and the chip manual. Notice:
This project has been shared to CSDN https://blog.csdn.net/weixin_43607069/article/details/105679284
All reference designs on this site are sourced from major semiconductor manufacturers or collected online for learning and research. The copyright belongs to the semiconductor manufacturer or the original author. If you believe that the reference design of this site infringes upon your relevant rights and interests, please send us a rights notice. As a neutral platform service provider, we will take measures to delete the relevant content in accordance with relevant laws after receiving the relevant notice from the rights holder. Please send relevant notifications to email: bbs_service@eeworld.com.cn.
It is your responsibility to test the circuit yourself and determine its suitability for you. EEWorld will not be liable for direct, indirect, special, incidental, consequential or punitive damages arising from any cause or anything connected to any reference design used.
Supported by EEWorld Datasheet