Firmware idVendor/idProduct don't match

General discussions about V-USB, our firmware-only implementation of a low speed USB device on Atmel's AVR microcontrollers
Post Reply
Karlsson

Firmware idVendor/idProduct don't match

Post by Karlsson » Sun Dec 10, 2006 2:24 pm

Firmware idVendor/idProduct don't match. I'm trying to make the powerswitch project to work. I progamed the tiny2313 both with the binary version that came along and one that I compiled using winavr, both with the same reult. I think i managed installing minGW and libusb-win32 alright. When I connect the usb (using windows) found new hardware pop up labeled powerswitch. Then I run TestLibUsb with this as reult.

DLL version: 0.1.10.1
Driver version: 0.1.10.1

bus/device idVendor/idProduct
bus-0/\\.\libusb0-0000--0x10de-0x00e7 10DE/00E7
...

The problem is that the firmware idVendor/idProduct is set to:
#define USB_CFG_VENDOR_ID 0xc0, 0x16
#define USB_CFG_DEVICE_ID 0xdc, 0x05

and don't match 10DE/00E7. Any ideas? What can I rule out and what can be the source of error according to the results?

christian
Objective Development
Objective Development
Posts: 1442
Joined: Thu Nov 09, 2006 11:46 am

Post by christian » Mon Dec 11, 2006 12:12 pm

10DE/00E7 is the PCI identification of your USB controller, not a USB ID pair. If nothing else is listed for the bus, no USB devices have been found.

Karlsson

Post by Karlsson » Mon Dec 11, 2006 10:27 pm

Thanks!
But to get this straight i think I´l have to ask som more questions. When I connect the usb new hardware found pops up and it's named powerswitch dosn´t that mean that that some information is read from the tiny2313? The TestLibUsb changes from:
DLL version: 0.1.10.1
Driver version: 0.1.10.1

bus/device idVendor/idProduct


To this.

DLL version: 0.1.10.1
Driver version: 0.1.10.1

bus/device idVendor/idProduct
bus-1/\\.\libusb0-0001--0x10de-0x00e7 10DE/00E7
wTotalLength: 25
bNumInterfaces: 1
bConfigurationValue: 35
iConfiguration: 0
bmAttributes: 40h
MaxPower: 0
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: 9
bInterfaceSubClass: 1
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 81h
bmAttributes: 03h
wMaxPacketSize: 8
bInterval: 10
bRefresh: 0
bSynchAddress: 0


It dont make much sense to me but maybe it can be to some help. I haven't put in any zener diods so 5V on -d +d might be an issue. I tried to find some way to enable that in bios but didn't manage.

christian
Objective Development
Objective Development
Posts: 1442
Joined: Thu Nov 09, 2006 11:46 am

Post by christian » Tue Dec 12, 2006 10:20 am

The device descriptor you quote is of class 9 which means "USB Hub". This is probably the root hub in the USB controller chip.

If Windows identifies the device by name ("PowerSwitch"), then it must have read the descriptors correctly. This rules out voltage level problems.

I can't remember how libusb-win32 is used. Are other USB devices listed? And do you have the low level stuff (driver DLL) installed?

Karlsson

Post by Karlsson » Tue Dec 12, 2006 11:54 pm

I tried if Ubuntu liked it better and it works like a charm. He he amazing that it can be so fun lighting up some leds. I almost posted a message that it didn't work but when I copy/pasted the words Operation not permitted made me realize I forgot sudo. This clearly stats that it's the software setup in windows that is the problem. Thanks for all the help!
Linux rock

Post Reply