Objective Development Forums

drive wizard

2007-11-19T07:17:08+02:00

Go to http://sourceforge.net/project/showfile ... p_id=78138 and download libusb-win32-device-bin-0.1.12.1.tar.gz uncompress it and go to bin folder, run inf-wizard.exe and u will can to make the driver for whatever device you want.

Daniel Barragan
Argus Smart / Parquesoft
Colombia - South America

danielbcr.blogspot.com

Statistics: Posted by Guest — Mon Nov 19, 2007 7:17 am

Problems building bootloadHID

2007-11-02T07:55:56+02:00

Thank gert!
I found the libusb in Windriver folder of Powerswitch but it not suppose for the USB-LED-Fader!
Anyway thanks!

Statistics: Posted by Guest — Fri Nov 02, 2007 7:55 am

Problems building bootloadHID

2007-11-01T20:55:08+02:00

highlanderf1

Sorry, but I didn't try USB-LED-Fader under WinXP, and currently I don't even have a WinXP installation for testing,

If you're looking for libusb, it's included in the powerSwitch archive.

Cheers
gert

Statistics: Posted by gert — Thu Nov 01, 2007 8:55 pm

Problems building bootloadHID

2007-11-01T18:47:03+02:00

to gert: do you get the driver for the USB-LED-Fader that control by WinXP?
Ive built it but i used Winxp not Linux so that i cant control the Leds via USB!
Thank in advance!

Statistics: Posted by highlanderf1 — Thu Nov 01, 2007 6:47 pm

Problems building bootloadHID

2007-10-24T20:15:21+02:00

I tested HIDBoot with a different WinXP installation, and this time it worked. A closer examination of the first PC showed a badly broken USB enumeration (even attaching a USB 1.1 hub requires a manual driver installation).

Sorry for having bothered you for nothing!
/G

Statistics: Posted by gert — Wed Oct 24, 2007 8:15 pm

Problems building bootloadHID

2007-10-24T16:25:21+02:00

Sorry, I overlooked that Windows recognizes the device.

If you have configured libusb-win32 to attach to the HID device, then bootloadHID will probably not be able to connect to it. Maybe the result of a previous experiment?

The first thing bootloadHID does is to enumerate the devices, ask them for their IDs and names and compare these to the expected values. If the device is not found, this enumeration step fails. I don't think that any HID specific commands are used for that.

Statistics: Posted by christian — Wed Oct 24, 2007 4:25 pm

Problems building bootloadHID

2007-10-24T16:21:31+02:00

Christian

As I wrote above the device is being detected under WinXP. It shows up in the hardware settings as "HIDBoot", and I have no reason to think that there is anything wrong with it. It's just the bootloaderHID.exe that casts the error message above, and doesn't do anything useful,

If I got it right, the use of the HID class should make extra drivers unnecessary. So I can't see what mistake I could have made with the installation. A brief test with the bootloaderHID.exe binary from the first release shows the same error message.

I'm sorry that I can't be more specific, but unless I get a working MinGW installation. Someone else with WinXP and the MinGW toolchain should give it a try. Blame it on a broken WinXP installation if it works for them.

Cheers
Gert

Statistics: Posted by gert — Wed Oct 24, 2007 4:21 pm

Problems building bootloadHID

2007-10-24T13:39:16+02:00

It's hard to analyze the Windows problem with only this message. Is the device recognized as HID at all? You should see some kind of bubble info when you connect it.

Statistics: Posted by christian — Wed Oct 24, 2007 1:39 pm

Problems building bootloadHID

2007-10-24T00:25:25+02:00

Great, thanks!

This time "make" works, and the bootloader almost works as smoothly as one could wish: In bootloader mode the device is detected under linux (kernel 2.6.22, udev) and WinXP/SP2, both with the included and the self compiled binary.

Test under Linux:
I made a new bootloadHID binary in Linux, and when I run it as root, it works as expected:

Code:

root@mbili:/home/uuser/avr_proj/usb-led-fader/firmware# ./bootloadHID main_061002.hex
Warning: could not set configuration: could not set config 1: Device or resource busy
Page size   = 64 (0x40)
Device size = 8192 (0x2000); 6144 bytes remaining
Uploading 5504 (0x1580) bytes starting at 0 (0x0)
0x01500 ... 0x01580

The warning comes from a failed access to my USB-mouse. I don't like warnings that are "normal", so maybe I'll patch bootloaderHID.

Under ubuntu > 7.xx, with the following udev rules all USB devices with the"public" AVRUSB idVendor:idProduct pairs can be used with ordinary user rights:

Code:

uuser@mbili:~/avr_proj/usbasp/firmware$ cat /etc/udev/rules.d/45-avrusb.rules 
#custom (libusb)
SYSFS{idVendor}=="16c0", SYSFS{idProduct}=="05dc", MODE="0660", GROUP="plugdev"
#HID
SYSFS{idVendor}=="16c0", SYSFS{idProduct}=="05df", MODE="0660", GROUP="plugdev"
#CDC
SYSFS{idVendor}=="16c0", SYSFS{idProduct}=="05e1", MODE="0660", GROUP="plugdev"

Note that I only verified "custom" and "HID". Reloading the udev rules is necessary (e.g. reboot).

Test under Windows:
I currently have no working Win32 compiler setup, so I tried the binary "bootloadHID.exe" from the recent zip file. I got the following error message:

Code:

E:\>bootloadHID.exe main_061002.hex
Error opening HIDBoot device: The specified device was not found

Maybe I did something wrong, and someone else should try this.

Best
Gert

Statistics: Posted by gert — Wed Oct 24, 2007 12:25 am

Problems building bootloadHID

2007-10-23T15:15:12+02:00

The new version should be online already...

Statistics: Posted by christian — Tue Oct 23, 2007 3:15 pm