-
Notifications
You must be signed in to change notification settings - Fork 3
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
Return -32. can't write bulk write control message. #3
Comments
Figured out the issue, but writing now files to the device, fails:
|
@robertalks Hi, thanks for taking the time to report this! Funny to know the number of known users might be approaching 4 😂 I have never tried compiling this on Open Suse, but I don't see why it shouldn't work ... To dig into this I need to be able to reproduce it somehow. As I recently was moving, a lot of my stuff is in storage, including the wmp1, so I might not be able to get to this in a week or two. I will start with trying to get it working on Ubuntu, since that is the last known working target. It used to work on Slackware and Suse back in 2005 (and Ubuntu in 2015) ... By the way, you are using the right version of the libs? Although I know the newer libusb library has a compatibility layer to the old 0.1 libusb, I seem to recall it didn't work (my memory might fail me, though). If you are using that, I would try to get hold of the old library (libusb 0.1) for Suse, perhaps building it from scratch if it's not available on OpenSuse. I would also try running it as sudo, just to rule out permissions. If everything is the same, except our kernel versions, we can start looking deeper. But the easy options first :-) |
The original 0.1 library source can be downloaded here or here. |
Hi, @robertalks. I just searched for that exact error and guess what ... my name came up in this 2013 thread, which was about getting it working on OS X using the I "solved" it at that time by just using the original library on a Linux VM (quicker than figuring out usb programming). |
Hi, this is what is available on openSUSE and what I have installed: robert@pandora:~> rpm -qa|grep -i libusb |
Alright, took your advice and build libusb from those sources and installed them in /opt/libusb (to not damage my machine). Rebuild your code with modification to the Makefile: wmp_manager: casio_wmp.cpp usb_layer.cpp and ran the binary with:
usb_vendor_message_in(): Broken pipe
Watch needs to connect to dongle...done. |
Also: robert@pandora:~/output> /opt/libusb/bin/libusb-config --version |
@robertalks Hmm ... sorry to see that didn't work! Not quite sure what to do next ... Maybe it's finally time I looked into rewaking those C skills from university a decade ago and try changing the code made by Florian into using |
@robertalks I don't have a bug fix right now, but as a workaround I can suggest something that will at least make it possible to use your WMP right now:
Yes, it's a hack, but at least you won't need to wait for me to learn USB programming ... |
Alright, will try that. |
Alright, so did the setup using VirtualBox and Ubuntu 12.04.5, but I can't really see the USB device, the Casio to allow the VM to work with it. So this doesn't work eider. I can see 'No USB devices connected'. Could this issue be more related to USB 3.0 <-> USB 2.0 ? robert@pandora:~> lsusb|grep Casio You can see the usb device on the host, but VirtualBox doesn't see it at all. |
Are you sure you told VirtualBox to let Ubuntu access your USB devices explicitly? For instance, you need the extension pack. These articles both tell you how: |
Ahh, I don't think you understood, is not that I don't know how, its not working. |
I actually tied to attach a USB stick and same issue. Not sure what is the problem, the kernel or the machine or VirtualBox. |
Nevermind, the permissions on the user was wrong :) |
Alright, so finally I was able to use Ubuntu 12.04, but trying to write to the device ends up in the exact same errors as on openSUSE. |
Ah ... that is frustrating. I am sorry to have sent you down that rabbit hole for nothing, but I know it used to work. I'm picking up my device from storage next week, so maybe I am able to dig into it. Since this issue seems to show the same characteristics as #1, I suspect fixing this will make it work cross-platform, which would be cool. If there is any progress, I'll let you know. |
Don't worry, its a pleasure for me. Haven't played with this things for ages. Trying now Windows XP in VirtualBox, see if it makes a difference :) |
Good to hear. I was in storage today and actually managed to locate all the bits. I see that something needs to be done. Results using 64 bit version of Ubuntu 18.04.1:
I know the USB is a bit faulty on this computer, so perhaps that might be it, but I'll need to check with another pc as well to make sure. Anyway: research will follow. |
Hello, just started to use your code, but doesn't seem to work for me. Using openSUSE 42.3 and kernel 4.16.2-1.g7b2d22b-default and getting this messages from the kernel:
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: