-
Notifications
You must be signed in to change notification settings - Fork 12
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
Corrupted firmware binaries in 1.11 pre Release assets #21
Comments
Hi, I assume that you not used the firmware from the 1.11 pre-release but the file from the URL I posted in another message.
The logs above shows that you connected probably a full speed USB device. AFAIK, the chinese USBasp clones ( if not all then the 98% ) are low speed devices . The speed identification of a USB device, being low speed or full speed, is indicated from the hardware not by the firmware. Can you post a photo of your device ? regards, |
Hi,
I just noticed that for the 1.10 release the firmware binaries are missing. I'll upload them over the next few days. Sorry for that. regards, |
Hi, confirmed that the binaries also in the 1.11 pre release are corrupted ! Re uploading them shortly ! regards, |
Hi, can you please test again with the new firmware binary ? regards, |
Yep, much better. Quick test under arduino IDE 1.88, cannot upload with programmer=USBASP |
Hi, thank you very much for your feedback !
Could you please open a new issue for the above ? regards, |
Hi
I flashed v1.11 USBasp_ATMega8_12MHz_TPI_HIDUART_SNWRITE.hex
succesfully, with fuses and the result is
Common causes says some clocking problem here.
The device is the common thing from aliexpress, based on atmega8.
Note:
it is an absolute waste of time to make the user 'build' the final binary to flash the atmega.
On the raspberry I used to flash , I did not go beyond apt-get install gcc-avc when compiler started complaining about fatal error: avr/io.h:
Just no point. Not the goal.
Simply try to put result of your compiler in 'bin/firmware', with explicit names for variants mega8 maga88.
Remove confusing crap (2007 ?? 2009 ??? 2011???)
keep fitsch.hex with the correct name (v1.5.hex= no; v1.05.hex = yes)
and try to find the USB problem ;)
Thank you
The text was updated successfully, but these errors were encountered: