AVR-Doper support is broken since version 6.4 #1626
Labels
bug
Something isn't working
Comments
|
Please provide more details of the issue as per the following Wiki FAQ entry. Please post the full debug log with Are you using Windows? If this is an USB HID device, please do not use libusb-win32 device driver and use Windows native HID driver to see if that works. |
|
Hello! |
|
I assume you are using the native Windows USB HID driver as the original CDC-ACM version will not work under Wndows 10. Looking at the debug log, latest git is complete broken for this old programmer. But then the support may already be broken a few years back since you mention that avrdude 6.4 already does not work. So I expect this may not be an easy issue to fix. |
mcuee
added
bug
|
If we compare the debug log of 7.2 release vs git main, there is a regression. But then 7.2 does not work either. So we may be able to live with it for the upcoming avrdude 7.3 release. |
Since he mentioned it's broken since 6.4, the most obvious change in the 6.4 NEWS file is: " * Major changes compared to the previous version: So I'd assume that eventually broke AVRdoper back then. |
|
Sorry, I don't have any avrdoper hardware either. |
I have ready-made firmware for the сhinese USBasp v2.0 board. I'll send it in the evening |
|
The archive contains the compiled main.hex and sources. The firmware is configured to use the HID interface. |
|
@Nibi-git avrdude 6.3 release works fine. git main does not work. It is quite broken for this avrdoper programmer. avrdude 7.2 does not work either, but not as broken as git main. Same for avrdude 6.4. BTW, forked version of avrdude 6.3 from Arduino does not work. @mariusgreuel's avrdude 6.3 Windows fork also does not work. |
Hmm, I can not even get that to work with avrdude 7.2 release. BTW, adding |
|
Major commits related to the changes.
Before 845abf1, avrdude uses libusb under non-Windows platform and libhid (native Windows HID API) under Windows. Example: |
|
Unfortunately I am not a programmer and the above is what I can do now. Hopefully @MCUdude or others can chime in to help to sort out the issue. |
|
I tend to think we cannot sort this out after avrdude 7.3 release, so we can probably target this with avrdude 7.4 release. I will carry out some tests using hidapitester when I finished my testing of hidapitester |
mcuee
changed the title
|
Remove this from avrdude 7.4 milestone since there is no active development on this topic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
I'm using an old USB HID programmer Avrdoper https://www.obdev.at/products/vusb/avrdoper.html
with VID_16C0&PID_05DF&REV_0100
Typically the command line to use it looks like this:
avrdude -c stk500v2 -F -P avrdoper -p m48p -B 20 ... and hex, fuses...For a long time I successfully used the version 6.3 of avrdude, but then I tried all newer versions and got an error.
In this case, the LEDs on the programmer board blink, but the operation ends with an error.
I added detailed logs of using different versions of Avrdude with minor modifications in the command line
Tried the old version 6.3 and new 7.2 and nightly
log file name contains command line options and avrdude version
avrdude_logs.zip
I'm using the native driver from Microsoft
OS: Windows 10 IoT Enterprise 10.0.19044 LTSC
PART: Atmmega48p
Connected via ISP
So for now I'm back to the old version 6.3 again.
Is it possible to fix this problem?
Best regards, Roman
The text was updated successfully, but these errors were encountered: