First item of business: Thanks. Looks great.
UI've got a custom USB bulk device (Blackfin based with my own firmware
for what it's worth). Used Zadig to install WinUSB drivers on W7x64. The
DDK USBView shows the device connected with EP In 0x85 and EP Out 0x06.
Device Manager confirms drivers a
Hello Pete.
>> Fun! Did you already verify the USB part of the firmware, or is this
>> part of what you are doing right now?
Err. Yes :) Blackfin not my favourite for this kind of gig!
USB firmware all good. I want to use libusbx for the bulk pipe in what
will be a composite device. Essentially
Hello Pete.
>> Fun! Did you already verify the USB part of the firmware, or is this
>> part of what you are doing right now?
Err. Yes :) Blackfin not my favourite for this kind of gig!
USB firmware all good. I want to use libusbx for the bulk pipe in what
will be a composite device. Essentially
Hello Xioafan
On 22/05/2012 15:15, Xiaofan Chen wrote:
> On Tue, May 22, 2012 at 9:52 PM, g...@novadsp.com wrote:
>
> That seems to be a USB hub. Is it?
> http://www.ixitools.com/hwcat/_b8139c20-cf94-11d5-aef7-0002b30625c5_vid_05e3_pid_0608/devinfo19476.html
>
Good call. It is
Hello Pete
On 22/05/2012 16:21, Pete Batard wrote:
>
> Unless there are objections, I'll produce a patch to do just that.
> Currently, I think I'll go with info, but if anyone has a strong
> preference for another severity level, let me know.
>
Thanks, your call. I've only been using the library
>> However, if Windows always considers a device with 0:0 in the device
>> descriptor an error, then the Windows backend should discard them.
>
> I don't think the Windows USB stack does any such thing, although if I
> were a real man I would have burned a device with / to test this.
>
Al
Hello Pete,
> please be aware that the Windows driver we use at the
> moment doesn't support isoch (see "Known Restrictions" for WinUSB at
> [1]),
Indeed. Why on earth make WinUSB without isoch support.
> though we're planning to add drivers that support isoch in the future.
Has anyone started
Hello Pete
> Sure, and there is an implementation, but the implementation needed
> further work before being added into the Windows backend and the
> author didn't work with Pete on that.
>
> My http://git.stuge.se/?p=libusb-stuge.git;a=shortlog;h=libusb0 branch
> has two snapshots of the downstre
Hello Pete
>
> Note that the code pointed out by Peter is _NOT_ the one that is going
> to be used by libusbx.
>
> The reasons are:
> 1. It is too old (more than 2 years) and hasn't been updated at all
> 2. It doesn't support libusbK, only libusb0
> 3. The author didn't address some shortcomings an
Hello Tim
On 25/05/2012 18:25, Tim Roberts wrote:
>
> When news of this limitation first came out 5 or 6 years ago, the USB
> team at Microsoft sent out a blast saying "We will add this if you have
> a legitimate use case for it. Let us know." No one has let them know,
> or at least no one that
Hello Sandor
On 29/05/2012 13:35, Sandor Otvos wrote:
> Hi
> Someone can advise a beginner like me...
> How can i obtain device instance string
> ( \\.\USB#VID_413C&PID_8158#7&1C3A6C5&0&2 ) with libusb ?
> I tried xusb, and libusbx can print it, if some problem occured. So this
> string is interna
Quick question:
Assuming I need a user-mode interface to a custom USB Bulk class device:
1. Can I use Zadig to install a WinUSB driver for the VID/PID?
2. If Zadig installs the driver correctly, can I then simply open the
device using the libusbx version of libusb-1.0.dll?
3. If no to 1. what pa
Hello Pete,
On 13/06/2012 10:38, Pete Batard wrote:
>
> Absolutely. This is what Zadig was designed for.
>
Does Zadig have its own list? Wondering about Zadig .INF files and
Nullsoft/Inno style installers.
>> 2. If Zadig installs the driver correctly, can I then simply open the
>> device using
My USB handler thread(s) listen on other synchronization handles for
clean shutdown etc. Once I have opened a device using LibUsbX, is there
a synchronization handle I can pend on whilst waiting for the peripheral
device to write back to the host?
i.e.
// open device etc.
libusb_open_device_wi
Peter,
On 09/08/2012 02:53, Peter Stuge wrote:
> g...@novadsp.com wrote:
>
> Another point is that the code is absolutely unportable, which kindof
> misses one big point of using the portable libusb-1.0 API.
Indeed. Not an issue here.
> No good since there can be no data from d
Hello Pete
On 09/08/2012 15:33, Peter Stuge wrote:
>>
>> ? err, no. My device might well start to write back down the pipe as
>> soon as it has been configured.
>
> That would be a violation of the USB protocol.
>
My bad. Sloppy phrasing. Configured as in 'told what to do'.
---
Blackfin based firmware gets closer to release. I'm out of time to add
composite device support to the ADI driver stack, so by default it is a
mass storage device.
Now, it would be really cool to be able to persuade the gadget to
disconnect, reconfigure and reconnect with a different PID, i.e.
Peter
On 12/10/2012 18:38, Peter Stuge wrote:
> g...@novadsp.com wrote:
>> All I really need to do is send a few bytes of configuration data over
>> the control endpoint but can see no way of doing that with the Windows
>> stack in the way ..
>
> Use bDeviceClass
Hello Pete
On 12/10/2012 20:00, Pete Batard wrote:
> On 2012.10.12 18:59, g...@novadsp.com wrote:
>> On 12/10/2012 18:38, Peter Stuge wrote:
>>> https://libusb.org/wiki/FAQ#CanIcreateadriverlessdeviceusingHIDclass
>
> The *proper* link is:
> https://github.com/li
Hello Xiaofan
On 13/10/2012 11:33, Xiaofan Chen wrote:
> It may not be as difficult as you think to make your firmware a
> USB composite device. In you case, you need to add a second
> interface (say Interface 1) without any endpoint associated
> (basically just using the control endpoint).
>
> In
Hello Xiaofan
On 15/10/2012 10:15, Xiaofan Chen wrote:
>>
>> Ah - now that sounds very promising. What I still do not get is how the
>> WinUSB driver co-exists with the in-box mass storage stack? Can you load the
>> WinUSB driver for the same VID/PID but use the 2nd interface while mass
>> storage
Hello Xiaofan
On 15/10/2012 10:15, Xiaofan Chen wrote:
>
> Yes. The USB Composite Generic Parent driver will load usb mass storage
> driver for interface 0 and the winusb driver for the interfac 1.
> http://msdn.microsoft.com/en-us/library/windows/hardware/ff537109(v=vs.85).aspx
>
Fantastic! Than
As suggested by Xiaofan firmware has two interfaces, with the second
exposing no data endpoints of its own.
Opening the device using libusb_open_device_with_vid_pid
and then enumerating the device using libusbx functions gets me the
expected:
ProductID: 0xA00A
Interfaces: 2
Number of alternate
23 matches
Mail list logo
