Skip to content
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

avrdude7.2 unable to detect atmelice - works with avrdude6.3 #1579

Closed
feroze-mohamed opened this issue Nov 24, 2023 · 11 comments
Closed

avrdude7.2 unable to detect atmelice - works with avrdude6.3 #1579

feroze-mohamed opened this issue Nov 24, 2023 · 11 comments
Labels
unconfirmed Maybe a bug, needs to be reproduced by someone else

Comments

@feroze-mohamed
Copy link

I have been using avrdude6.3 on windows 10 and 11 without issues.

But lately we needed support for ATTINY1626, so upgraded to v7.2

While 6.3 works (detects atmelice) , v7.2 says unable to detect the atmelice

used ZADIG to change the driver to libusb

v7.2 :
image

v6.3:
image

@MCUdude
Copy link
Collaborator

MCUdude commented Nov 24, 2023

Using Zadig, can you try to change your driver to WinUSB and see if this helps?

@feroze-mohamed
Copy link
Author

Thank you for the response.

libusb works for 6.3

however as you mentioned i changed the driver for interface 0 as below

image

but same issue.

@MCUdude
Copy link
Collaborator

MCUdude commented Nov 24, 2023

OK. You may have to use the original driver. I think it's called hidusb.
You can't use Zadig to select this, but you can do it under the Windows Device Manager.
On the bright size, this is the same driver as Atmel Studio uses, so one doesn't need to switch between drivers anymore.

@feroze-mohamed
Copy link
Author

I tested on another laptop where ATMEL STUDIO works without any driver change but it gives similar error:
I thought that was due to not using ZADIG. but as per your inputs this should have worked correct ?

avrdude error: no device found matching VID 0x03eb and PID list: 0x2141 
avrdude error: unable to open programmer atmelice on port usb 
avrdude done.  Thank you.

@MCUdude
Copy link
Collaborator

MCUdude commented Nov 24, 2023

I don't use Windows on a regular basis, so I don't really know. @mcuee would have to chime in.

@mcuee mcuee added the unconfirmed Maybe a bug, needs to be reproduced by someone else label Nov 24, 2023
@mcuee
Copy link
Collaborator

mcuee commented Nov 24, 2023

@feroze-mohamed

Please do not use Zadig to change driver but rather using the original driver from Atmel.

Please try my MinGW build to see if it works.
https://github.com/mcuee/avrdude/releases/tag/v7.2

For example:
avrdude-v7.2_mingw64.zip

If the above build works (using libusb-1.0+libusb-compat-0.1) and the offcial Windows binary (using avrdude-libusb) does not work, it could be that you hit the existing bug.

@feroze-mohamed
Copy link
Author

Thank you WIll update my findings

@feroze-mohamed
Copy link
Author

offcial

on my windows 11 "avrdude-v7.2_mingw64" didnt work with libusb but worked with WinUSB v6.1.xxxx (using Zadig)

I need to try this on the remote system i was facing issue with.

@feroze-mohamed
Copy link
Author

ok so i have no clue whats hapennign but its working so thats good news for me.

I am using the mingw version you shared and it works great with LIBUSB driver on the remote system that initially i was having issues with . so this is great news and thank you a lot.

however on my system same mingw version works with WINUSB but not with LIBUSB

Basically both systesm work with mingw version with different drivers.

Thank you for your support

@stefanrueger
Copy link
Collaborator

Basically both systesm work with mingw version with different drivers.

Thank you for your support

Thanks for reporting back @feroze-mohamed Does this mean the issue can be closed?

@feroze-mohamed
Copy link
Author

I believe the issue can be closed. Thank you again for the support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unconfirmed Maybe a bug, needs to be reproduced by someone else
Projects
None yet
Development

No branches or pull requests

4 participants