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
On Tue, 12 10:06 , Tim Roberts wrote:
>
> > wValue (LSW) and wIndex (MSW) make up the address offset to write
> > the data to within device memory.
>
> Are you sure you have the ordering correct? (It probably is, because
> that lets those two fields be treated as a single little-endian dword
On 2012.06.12 18:22, Sean McBride wrote:
> Or use CMake, which abstracts the problem. That way, the CMake folks get to
> worry about keeping up-to-date with VS and Xcode project formats.
As far as I'm concerned, as long as CMake can't be used to generate VS
project files without having the targ
On Tue, 12 Jun 2012 21:37:26 +0800, Xiaofan Chen said:
>I think I have mentioned this before, the new VS11 Beta can
>not convert the existing VS2010 project properly. I think this
>is not a real problem for now but we may need to create
>a new VS11 solution in the near future.
Or use CMake, which
Markus wrote:
> As of now, I can read and write memory by using vendor request
> control transfers. According to the manufacturer this is the way
> to go for firmware dump and download.
That's a common mechanism.
> wValue (LSW) and wIndex (MSW) make up the address offset to write
> the data t
Xiaofan Chen wrote:
> I think I have mentioned this before, the new VS11 Beta can
> not convert the existing VS2010 project properly. I think this
> is not a real problem for now but we may need to create
> a new VS11 solution in the near future.
Yes, I think you would certainly want to wait until
2012/6/12 Xiaofan Chen :
> On Mon, Jun 11, 2012 at 9:44 PM, Pete Batard wrote:
>> Tarball archive at
>> https://sourceforge.net/projects/libusbx/files/releases/1.0.12/source/
>>
>> If possible please test the archive and report issues or potential
>> enhancements.
>>
>
> As already mentioned befor
On 2012.06.12 14:19, Xiaofan Chen wrote:
> I have no idea about why the error message comes out but
> xusb and libusbdotnet both work with the benchmark device.
Great. I do have issues getting the benchmark device work in a virtual
machine (VMWare) with OpenBSD. It basically it timeouts while try
Hi,
I'd like to replace a vendor tool for firmware download
to a developement board by using libusbx.
As of now, I can read and write memory by using vendor request
control transfers. According to the manufacturer this is the way
to go for firmware dump and download.
wValue (LSW) and wIndex (MS
On Tue, Jun 12, 2012 at 9:19 PM, Xiaofan Chen wrote:
> On Tue, Jun 12, 2012 at 9:07 PM, Xiaofan Chen wrote:
>> As already mentioned before, there are a few warnings
>> under NetBSD but as per Pete we are going to wait for
>> some BSD people to chime in to help resolve the warnings.
>> I think tha
On Tue, Jun 12, 2012 at 9:07 PM, Xiaofan Chen wrote:
> As already mentioned before, there are a few warnings
> under NetBSD but as per Pete we are going to wait for
> some BSD people to chime in to help resolve the warnings.
> I think that is fair.
There are no compiler warnings under OpenBSD. An
On Mon, Jun 11, 2012 at 9:44 PM, Pete Batard wrote:
> Tarball archive at
> https://sourceforge.net/projects/libusbx/files/releases/1.0.12/source/
>
> If possible please test the archive and report issues or potential
> enhancements.
>
As already mentioned before, there are a few warnings
under Ne
On Tue, Jun 12, 2012 at 7:05 PM, Pete Batard wrote:
> On 2012.06.12 07:27, Xiaofan Chen wrote:
>> One minor thing is that "USB 1.0 LowSpeed" is a bit
>> misnomer. I think "USB LowSpeed" is a bit better, it is even
>> better to use bcdUSB value (2.00 --> USB 2.0, 1.10 --> USB 1.1).
>
> Fair point
On 2012.06.12 07:27, Xiaofan Chen wrote:
> Just tested under Windows XP using Cygwin and MinGW
> and it seems to work fine, even with a mouse, nice.
Thanks for the test.
> The warning is of course valid since this is a mouse.
Yeah. On one hand, if we don't display the warning, people may wonder
14 matches
Mail list logo
