Eric Lundby wrote:
>> How are you going to avoid specifying a COM port across platforms?
> Not sure how to take this. Sounds a bit cynical.
That was not my intent at all -- I must have worded my question poorly.
Allow me to try again.
> I'm currently using
> libusb/WinUSB on Windows to communic
On Sat, Feb 2, 2013 at 6:05 AM, Eric Lundby wrote:
>> Then why would you make this CDC ACM, instead of just using a custom
>> interface that you control completely?
>
> Couple reasons: This is chip is a drop in replacement on our hardware
> and won't require any adjustments to the firmware running
> Then why would you make this CDC ACM, instead of just using a custom
> interface that you control completely?
Couple reasons: This is chip is a drop in replacement on our hardware
and won't require any adjustments to the firmware running on the
device. Also, I didn't have much influence on the d
Eric Lundby wrote:
> The main reason for not using the Microchip provided package is we
> don't want our end users to have to specify a com port to be able to
> use our device.
Then why would you make this CDC ACM, instead of just using a custom
interface that you control completely?
> Being abl
Pete:
Thank you for the links, that definitely got me started in the right
direction. I ended up getting things to work by sending a control
transfer that matched what I saw while sniffing using VCP.
Xiaofan:
Thank you. I will educate myself a bit more on the spec. I tried to
dive right in without
On Fri, Feb 1, 2013 at 2:45 AM, Eric Lundby wrote:
> I am however still unable to get basic communication working with
> libusb. When using Microchips supplied driver that exposes a com port
> everything works correctly over serial. When trying to use libusb bulk
> transfers, my send works, but my
Hi Eric,
On 2013.01.31 18:45, Eric Lundby wrote:
> It seems that the error I was encountering is related to issue #78
> ("[winusbx_claim_interface] failed to auto-claim interface 0"). When I
> manually claim interface 0 before claiming interface 1 I no longer
> receive an error.
Yeah, as far as I
Well I have finally jumped back on this project.
It seems that the error I was encountering is related to issue #78
("[winusbx_claim_interface] failed to auto-claim interface 0"). When I
manually claim interface 0 before claiming interface 1 I no longer
receive an error.
I am however still unable
On 2012.11.21 05:38, Xiaofan Chen wrote:
> Another round of Google finds the HID report descriptors.
> http://www.protonbasic.co.uk/showthread.php/64764-USB-CDC-HID-IAD-interface
>
> So it does not have multiple HID collections.
Yeah. 46D is Logitech's VID, and Microchip is 4D8. I misread the log
On 2012.11.21 05:19, Xiaofan Chen wrote:
> I remember that the Windows HID backend does not yet support
> HID Collections. Is this still true since it is not listed in the known
> restrictions.
Good point. It's the same code as before, so the same restrictions
apply. I've updated the wiki.
Regar
On Wed, Nov 21, 2012 at 1:34 PM, Xiaofan Chen wrote:
> On Sat, Nov 17, 2012 at 8:29 AM, Pete Batard wrote:
>> If possible (you say "custom" - does that mean you control the
>> firmware?), you may also want to try to remove the collection and
>> composite aspect of your HID device, then add them a
On Sat, Nov 17, 2012 at 8:29 AM, Pete Batard wrote:
> If possible (you say "custom" - does that mean you control the
> firmware?), you may also want to try to remove the collection and
> composite aspect of your HID device, then add them again and see at
> which point it begins to fail.
>
Microch
On Sat, Nov 17, 2012 at 8:29 AM, Pete Batard wrote:
> On 2012.11.16 20:44, Eric Lundby wrote:
>> I have attached output from xusb from both the working version (1.0.12)
>> and the non working version (latest from GIT).
>
> Let's see... HID collections:
>
> [ 0.241013] [0c4c] libusbx: debug [wi
On 2012.11.16 20:44, Eric Lundby wrote:
> I have attached output from xusb from both the working version (1.0.12)
> and the non working version (latest from GIT).
Let's see... HID collections:
[ 0.241013] [0c4c] libusbx: debug [windows_get_device_list] setting
composite interface for [2A3]:
I tried libusbx git again and claim_interface is still returning -3.
My device does have an HID interface.
I notice that with 1.0.12 libusb_get_device_address returns 5 and with the
latest form git, libusb_get_device_address returns 6.
If it helps, I am interfacing with a Microchip MCP2200 USB-t
On Fri, Nov 16, 2012 at 6:33 AM, Eric Lundby
wrote:
> Hello,
>
> I have a very basic program implementing two way communication with a custom
> composite USB device using the WinUSB driver on Windows. I was having some
> strange problems that I haven't been able to overcome (partially documented
>
16 matches
Mail list logo
