I'm trying to burn micronucleus bootloader from Arduino IDE and I get an error of avrdude.exe and it cannot burn the attiny85.
I'm using Arduino IDE 1.8.13 on windows 7 x64. To burn the bootloader from Arduino IDE I use Spencekonde's AttinyCore and I use a usbtiny isp as a programmer.
At the end of burning, when appears "avrdude done. Thank you" avrdude.exe crash (a window's window appear saying avrdude.exe has stopped working). In Arduino IDE console appears "error bootloader burn"
I have been doing several tests:
I used an Arduino Uno as ISP programmer. I was able to burn bootloader micronucleus in attiny85 successfully
I have used another USBTiny ISP but with no succes
I installed WinAvr and with USBTiny ISP and using console I could burn bootloader successfully
Finally I have replaced the micronucleus bootloader .hex from AttinyCore with wich I downloaded from micronucleus github and I managed to burn successfully bootloader using USBTiny ISP as a programmer and from Arduino IDE using AttinyCore menu.
Could it be that AttinyCore's .hex is corrupted? But if this is the case, how can it be that using an Arduino Uno as ISP I could burn the bootloader in attiny85?
So sorry of my english, I used goole translate to help me
So you can reproduce the error with avrdude 6.3.0 from the command line and my bootloader hex... but the winavr version of avrdude works with that hex?
And both work when you try to use a different hex file, but keep everything else the same?
What is the exact command that's causing the failure?
Avrdude 6.3.0 reproduce the error with usbtiny isp
Arduino IDE reproduce the error with usbtiny isp
With Arduino Uno as ISP burn succeffully from Arduino IDE, avrdude 6.3.0 and winavr
DrAzzy, I want to take the opportunity to ask you why if I select attiny85 micronucleus the B.O.D. level that I can select is onli 4.3v?
I would use attiny85 with two AA battery (3.6v more or less) and I would be interested in set B.O.D. level of 2.7v. I modify boards.txt and add this option, but I would like to know it is okay to select a B.O.D. level of 2.7v with a micronucleus bootloader.
At the end of burning, when appears "avrdude done. Thank you" avrdude.exe crash (a window's window appear saying avrdude.exe has stopped working). In Arduino IDE console appears "error bootloader burn"
If it says "avrdude done. Thank you", I suspect it is successfully uploading the bootloader. Check by "burn bootloader" with tiny85 no bootloader to clear everything out, then switch back to micronucleus, burn bootloader, and see if it works with micronucleus afterwards.
Will get back to you on the BOD voltage option, I know there was some reasoning for that, but I need to work on other priorities right now. I am way behind!
Back to BOD, I only know if there are any problem setting BOD level 2.7v with micronucleus bootloader.
I have already added the option in AttinyCore menu. It remains for me to thanks to excelent work in AttinyCore, I know is a lot of work and we appreciate the effort.
I have already do the test, clean attiny85 bootloader and burn micronucleus's bootloader. I got the same error and I couldn't upload any sketch from USB.
I attach two images. In the first one you can see the avrdude error and the text in arduino IDE (avrdude done. Thank you)
In the second image you can read the message "error burn bootloader".
Also I buy a Digispark clone and try to burn micronucleus bootloader without any success.
For now I will replace the AtttinyCore .hex with the micronucleus github .hex because that works well for me.
DrAzzy:
This is going from weird to even weirder. So:
My .hex file burned via other program = works
Micronucleus .hex file replacing the one in my core and bootload via IDE = works
My .hex file, bootload via ide = error, and doesn't work despite reporting success uploading before it dies?!
This is wacky if that's the behavior you're seeing. If my hex burned via other programs didn't work either, then at least everything would add up
There are plans to replace all the .hex files included with ATTinyCore in a future release anyway.
And your .hex file burned with Arduino Uno as ISP via Arduino IDE = works
Yes, is weird.
I would need to do the same tests from another computer and with another usbtiny isp programmer, but replacing the .hex file I resolve the problem.
Thank you very much for the support and for the great work with the AttinyCore
Where is the exact hex file that you can replace the one included with the core with, and have burn bootloader work? There are like a million forks of micronucleus repo with different contents
DrAzzy:
Where is the exact hex file that you can replace the one included with the core with, and have burn bootloader work? There are like a million forks of micronucleus repo with different contents
