gnupic: Traffic lights as extreme feedback device controlled by a PIC via USB
Subject:
Re: Traffic lights as extreme feedback device controlled by a PIC
via USB
From:
Peter Stuge ####@####.####
Date:
10 Aug 2012 13:13:45 -0000
Message-Id: <20120810131342.31188.qmail@stuge.se>
Hi Holger,
Holger Oehm wrote:
> > What remains to do for me is now:
> > 1. change the firmware: change the device class, add the 0xee string
> > and the descriptor that says that the device wants the WinUSB driver.
> > 2. describe (for windows users) how to use that Zadig standalone
> > driver installer.
> > Or better: configure libwdi to setup the WinUSB driver on
> > Windows Vista and Windows 7, setup my Linux box to cross-compile
> > it and create an installer. In the java application check if the
> > driver is present and if not run that installer.
> > 3. Get rid of that HID descriptor!
>
> ad 1.+3.: Done.
>
> I created a branch named noHid [1] for the removal of the HID stuff from
> the project. In that branch I changed the firmware to use the vendor
> specific class (0xFF) and also added the string descriptor and the
> compatibility descriptor stuff.
Wow, OK, as the final test you could try a Windows 8 Preview
installation if Microsoft still make that available. It should
then be enough to simply plug the device in, to make it run.
How do you feel about the idea to make the generic USB stack a
separate project? I think it would be fantastic, and a very nice way
to spread gputils even wider in the industry if the license is also
less restrictive. (I very much think that it is worthwhile to make a
separate project even without changing the license.)
> ad 2.: No success so far.
>
> So far so good, but I cannot get zadig to install the WinUSB driver
> successfully.
Huh - strange - that has always worked for me when other things
failed. If the device is attached, you have to manually select
'display attached devices' or somesuch in the menu, after that
it's literally just one click on the install button.
Ah - are you doing the system-wide COMP_WINUSB setup, or an explicit
setup for the device? I've so far only tried the latter.
> Using the advanced option and turning the debug level to
> debug I see that the driver installation complains about
> a file not found (from my memory: it was something like
> C:\usb_driver\Winusb_.....inf). But I could open the file in question
> with an editor, it was there. I have no idea what went wrong.
>
> I am kinda stuck there, do you think I should open an issue at libwdi[3]?
Perhaps you can try one or two older versions of the zadig build? I
didn't use it for maybe a month or so, but the latest version at that
time worked for me, for device-specific driver installation.
> And for the option to include libwdi to automate WinUSB driver
> installation: I understand that I need to have:
> 1. Windows DDK (download ISO image from MS, burn DVD, etc. etc.)
> 2. A cross compiler environment set up to compile it
What is your development environment? Linux? Which distribution?
Or do you develop also on a Windows system?
Many Linux distributions already have a mingw cross-toolchain
packaged.
As for the DDK, it would be enough to download the ISO and mount it
using loopback, if you are on Linux. IIRC the needed files are
available directly, without having to install everything.
> And I don't see how I can integrate all that stuff into the CI build of
> the project[4].
Yes, adding a cross-toolchain may be tricky if you don't control the
CI system. :\
> So I think I wont do that part.
Well, maybe someone can help do it!
> This of course means for a user of the device on windows the usage
> experience will definitely be somewhat worse than now (as long as
> WinUSB is not pre-installed).
Hopefully doesn't have to happen. Let's see.
//Peter
