-
-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"efuse" memory type not defined for part "atmega8" #3446
Comments
Try this #2541 |
Yes!! I deleted the line with efuse. It worked thank you, but now will not work the others wich need efuse. Ofcourse i made a copy of original platform, and when i will need it for others microcontrolers i will replace it, but you must solve this problem for arduino.. You know it's wery unprofetional like this. Trimis din Yahoo Mail pe Android De la:"rigelinorion" notifications@github.com Try this #2541 — |
I do not think you understand this way of working. The solution is not removing EFUS of the line only, but for the creation of additional tools that you use for the mC that this EFUS do not use. You do not need to swap any files. |
@cmaglie this is a duplicate of #2075 in which is described IMO the best way to solve this issue at #2075 (comment). |
i have solved this problem check this link below @andrei777777777 @rigelinorion @per1234 @cmaglie @JackDanger you will get the solution here |
Closed by: |
"Efuse" memory type not defined for part "atmega8"
Error while burning bootloader.
In arduino/hardware/arduino/avr/boards for atmega8 is good declared low fuses and high fuses, and is not present declaration for extended fuses like example atmega168, so is good, but the function who realy do the fuses try to fuse and extended fuses for atmega8, and atmega8 has no extended fuses, so gives that error.
I know that atmega8 is old" but i want to use it with bootloader ...
Please correct the function who realy make the fuses for atmega8 for not try to fuse extended fuses.
Or tell me where is it , to try to correct myself
The text was updated successfully, but these errors were encountered: