Page 2 of 2

Posted: Fri Jan 04, 2008 7:59 pm
by christian
This is a different problem than what you reported before. -lusb is libusb-win32. You should install it at a path where it can be found by the compiler (or add -L and -I flags to extend the search path). See http://libusb-win32.sourceforge.net/.

Posted: Sat Jan 05, 2008 3:34 pm
by Phoenix
Oke thanks I have no error now.

So I went back to the firmware and I doesn't work and my computer didn't find a device so I made some hardware asjust ments and now I finds a unknown device

So is this a firmware error ?

Posted: Sat Jan 05, 2008 4:12 pm
by christian
Does it report the device name for the unknown device? If it knows the device name and vendor name, then the USB driver works. In this case you need to associate libusb with the device. This is usually done with a .inf file.

If the device is completely unknown, there's probably a more fundamental error (such as wrong clock speed, wiring problem, logic level problem, I/O pins not configured correctly or something similar).

Posted: Sat Jan 05, 2008 4:33 pm
by Phoenix
completely unknown

Code: Select all

Device Descriptor:
bcdUSB:             0x0000
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x00 (0)
idVendor:           0x0000
idProduct:          0x0000
bcdDevice:          0x0000
iManufacturer:        0x00
iProduct:             0x00
iSerialNumber:        0x00
bNumConfigurations:   0x00

ConnectionStatus: DeviceFailedEnumeration
Current Config Value: 0x00
Device Bus Speed:      Low
Device Address:       0x00
Open Pipes:              0

Posted: Sat Jan 05, 2008 4:39 pm
by christian
This can be almost anything. That's why I recommended to start with a working example and change only one thing at a time.

Posted: Sat Jan 05, 2008 4:50 pm
by Phoenix
christian wrote:This can be almost anything. That's why I recommended to start with a working example and change only one thing at a time.
Oke thanks for everything