xu1541_update.exe cannot flash the firmware due to libusb problem?
Brought to you by:
strik
Menu
▾
▴
1 Attachments
#22 xu1541_update.exe cannot flash the firmware due to libusb problem?
Hi,
I apologize if this is not the right way to ask for support. But, I built an XU1541 from the web site https://spiro.trikaliotis.net/xu1541.
I've got the usbtiny BIOS flashed to the ATMEGA8 and I can see that the LED stays on. When I try to flash the firmware itself, I have an error with the xu1541_update.exe tool.
Please see the attached image that shows the error. From WINDOWS's Device Manager, I see the XU1541 BIOS device. Thank you for any help!
Additional USB information of the XU1541 BIOS Device.
Device USB\VID_0403&PID_C632\6&292c30d9&0&3 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_8087&PID_8001\5&8a3e110&0&1
Related
Discussion
Anonymous
And after unplugging the XU1541 device and plug it. Then attempted another xu1541_update.exe run, there is a bit more info, although still fails at the same place.
What version of OpenCBM are you using? And where did you get it from?
Why am I asking? OpenCBM has changed to libusb-1.0. For this, the old libusb-0 driver will not work anymore.
So, I need to know which version you are using in order to know how to proceed.
Please also note that I am working on the github tracker at https://github.com/OpenCBM/OpenCBM/issues now; however, it is not a problem if we discuss this issue here.
I am using OpenCBM version 0.4 that I got off XU1541 main page. Let me download the latest version from sourceforge.net and give it a try!
@strik
Hi, when I tried install the OpenCBM libusb1.0 driver on my WINDOWS 10, I get the below.
The newer OpenCBM versions do not use the libusb driver, but the WinUSB one.
In order to update, do the following:
Download the attached ZIP file and unpack it into a directory of your choice.
Now, double-click on the file update_driver.cmd (the ".cmd" part might be missing, depending upon your Windows settings). You should get the UAC prompt, asking you for elevated permissons. Accept it, wait a little bit (it might take up to some minutes!), and your driver should be updated afterwards.
The xum1541_winusb_updater.zip fails to download because Chrome/WINDOWS keeps saying that "Virus detected."
I don't know what Chrome wants you to do, but Virustotal does not complain:
https://www.virustotal.com/gui/url/a7948ad71e5a21c229bb184e6eea0e59c5c9085bcd8616e4018bf3e8673a237f?nocache=1
Thank you. I appreciate your response and help. I'll find a way somehow. It's WINDOWS 10 that complains about it. I think the contents of the zip file happens to have a binary sequence of known virus. So WINDOWS complains about it.
Do you have a special setup? I downloaded it on Windows 10, too, but did not get a complaint.
Please note: It uses the libwdi for installing the driver. libwdi allows you to install unsigned drivers (by signing it itself). In fact, that's the reason why I am using libwdi!
Of course, this is something that might be interesting for malware, too, so it is not unlikely that my code will have some or similar code paths as malware.
Unfortunately, there is nothing I can do about it, as I cannot sign the drivers myself (I do not have a corporation, and this is needed for signing Windows drivers).
Hi,
There is no special setup. I've trying and no avail. Would you please send me the zip file directly? Thank you!
xum1541_winusb_updater.zip is the file that I am talking about.
Thank you!
On Sunday, December 19, 2021, 10:52:39 PM PST, Spiro Trikaliotis strik@users.sourceforge.net wrote:
Do you have a special setup? I downloaded it on Windows 10, too, but did not get a complaint.
Please note: It uses the libwdi for installing the driver. libwdi allows you to install unsigned drivers (by signing it itself). In fact, that's the reason why I am using libwdi!
Of course, this is something that might be interesting for malware, too, so it is not unlikely that my code will have some or similar code paths as malware.
Unfortunately, there is nothing I can do about it, as I cannot sign the drivers myself (I do not have a corporation, and this is needed for signing Windows drivers).
[support-requests:#22] xu1541_update.exe cannot flash the firmware due to libusb problem?
Status: open
Group: v0.5.0
Created: Sat Nov 13, 2021 06:14 PM UTC by RetroEnthusiast
Last Updated: Mon Dec 20, 2021 05:30 AM UTC
Owner: nobody
Attachments:
Hi,
I apologize if this is not the right way to ask for support. But, I built an XU1541 from the web site https://spiro.trikaliotis.net/xu1541.
I've got the usbtiny BIOS flashed to the ATMEGA8 and I can see that the LED stays on. When I try to flash the firmware itself, I have an error with the xu1541_update.exe tool.
Please see the attached image that shows the error. From WINDOWS's Device Manager, I see the XU1541 BIOS device. Thank you for any help!
Additional USB information of the XU1541 BIOS Device.
Device USB\VID_0403&PID_C632\6&292c30d9&0&3 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_8087&PID_8001\5&8a3e110&0&1
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/opencbm/support-requests/22/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Support Requests:
#22Please re-test with OpenCBM 0.4.99.104. If this problem still occurs, re-open this ticket.
Thanks.