Open usr97629238 opened 8 months ago
Hi @usr97629238 ,
Is the USBasp's device driver WINUSB ? You can check using the device manager ( the image at https://github.com/dioannidis/usbasp/discussions/29 shows how the USBasp using WINUSB looks like ) .
Also, maybe there are driver conflicts from previous libusb and/or zadig installations . Use device manager to uninstall / delete all the drivers that Windows associates to USBasp device . Using device manager, right click on the usbasp device and uninstall / delete all the drivers assigned to it until windows reports it as unknown . Then unplugged it and plugged it again. It should work .
regards,
Thanks! Uninstalling the drivers somehow fixed it, despite the fact that there weren't any libusb and/or zadig drivers ever installed.
Actually there is more to the issue:
- It turns out it only works until the next disconnect, then (on the next reconnect) it would require another round of uninstall the driver, reconnect the dongle. That's on USB 2.0 ports that are Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller (PCI\VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_05)
ASMedia USB 3.0 controller (PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00)
and show "There are no compatible drivers for this device"
, if I manually install the winusb.sys it would accept it but fail the same at avrdude usbasp_transmit()
All these use WHQL drivers autoinstalled by windows. And there aren't any newer drivers anyway.Disregard the 1st issue, that only happens after tinkering with the ASMedia USB 3.0 controller, and that controller is actually known to be flaky as it comes back from the days when USB 3.0 was in beta. Still strange though, never had any problems with any devices, and strange how (and if) that might affect the USB 2.0 controller.
Hi,
maybe you should clean the Windows Registry reg. USBasp .
This is how I do it using USBDview . Run USBDView as Administrator, go to Options and check the "Display Disconnected Devices" . Sort the list clicking at the VendorID Header, select all the devices with VendorID = 16c0 and ProductID = 05dc. Right-Click on one of the selected device and uninstall them using the "Uninstall Selected Devices" menu item .
i.e. :
Hope it helps .
regards,
Nah, like I've said, there were no other drivers, as I'm usually wary about spamming the system with hacks like zadig and questionable drivers.
Hi,
did you uninstalled those devices I see in your post, tried again and you get the same results ?
regards,
Yes, removed all the 5 drivers and did a fresh re-test and here how it goes:
usbasp_transmit() [usbasp.c:365] OS error: No such file or directory
) unless I do the "uninstall the driver, reconnect the dongle"And I now believe that it wasn't working (the first post) because I've inserted it into the ASMedia controller first.
So it's up to you to decide if you want to investigate this any further or just close the issue. My take is that it's due to a flaky ASMedia controller or driver. If you want me to perform any tests of what might be wrong with it - feel free to ask.
Works perfect across the table on linux, but no matter what I try it won't work with windows (tried with avrdude 7.0 and 7.2_mingw64.zip)
In device manager it's listed under USB Devices as USBasp and is using the winusb.sys driver and USBaspHIDUART.exe sees it connected:
But avrdude fails at avrdude usbasp_transmit():
Changing the -B parameter affects nothing.