For some reason I am suddenly unable to program the chip.
All connections have been verified and the serial port works fine with the sketch already programmed.
The IDE seems unable to reset the chip to initiate firmware upload. Manually pressing the reset button at this point doesn't work either while at all other times pressing the reset button successfully resets the chip.
Please also note that I am neither able to re-burn the bootloader because of wrong signature reporting.
I am now suspecting a faulty chip unless ....someone else can come up with another idea.
Thanks
Sketch uses 24462 bytes (85%) of program storage space. Maximum is 28672 bytes.
Global variables use 1084 bytes (42%) of dynamic memory, leaving 1476 bytes for local variables. Maximum is 2560 bytes.
Forcing reset using 1200bps open/close on port COM11
PORTS {COM11, COM17, COM18, COM19, } / {COM17, COM18, COM19, } => {}
PORTS {COM17, COM18, COM19, } / {COM17, COM18, COM19, } => {}
PORTS {COM17, COM18, COM19, } / {COM17, COM18, COM19, } => {}
Regarding the upload error, make sure you have the correct port selected from the Tools > Port menu. The ATmega32U4 based boards will occasionally change their port number.
Regarding the problem burning the bootloader, please do this:
File > Preferences > Show verbose output during: > compilation (uncheck) > upload (check) > OK
Tools > Burn Bootloader
After the process fails you'll see a button on the right side of the orange bar "Copy error messages". Click that button.
I used a Nano clone for over a year with the three Leds and a cable built from Gammon's site. It worked almost as well as a Usbasp . Then one day after sitting on an hourly build long enough to forget I had changed to it, my Nano went on the blink and it took me a long time to trouble shoot it. I am seeing people with experience running into the same thing. Worked last month on 50 chips and now you can't get one to program.
One more thing to consider is that i was able to program a 1284p chip with mightycore with the same arduino programmer and ide 1.8.7! In this case a different programmer setting is chosen in the ide (arduino as isp mightycore)
The above had me thinking that the 32u4 chips had some sort of an issue. .
I finally found the pull request where this change was made:
It has a lot of information on why this was considered necessary. It seems to come down to the problem where you couldn't use an ATmega32U4-based board as an Arduino As ISP programmer. I made a workaround for this problem years ago by simply creating a new "Arduino as ISP(ATmega32U4)" programmer definition, which uses the arduino protocol:
Works for Linux doesn't work for Win10.
Works for everything, works for nothing.
Works for Win10 sometimes.
Works for this Arduino doesn't work for the same Arduino at a different elevation.