Objective Development Forums

Re: Device Recognized (Easylogger) and then...problem

2010-03-01T20:25:38+02:00

You can also remove the association somewhere in the device manager. I'd recommend separate experimental PIDs, though, unless you really know where to remove the driver association.

Statistics: Posted by christian — Mon Mar 01, 2010 8:25 pm

Re: Device Recognized (Easylogger) and then...problem

2010-03-01T20:10:17+02:00

but I did a regedit and erased all the registry that point to the VID/PID

Statistics: Posted by vsovereign — Mon Mar 01, 2010 8:10 pm

Re: Device Recognized (Easylogger) and then...problem

2010-02-28T18:49:49+02:00

You MUST NOT use the same VID/PID pair for two devices with different low level drivers. Windows caches the association of VID/PID and driver FOREVER. Simply use a new pair (see USB-IDs-for-free.txt in the latest driver).

Statistics: Posted by christian — Sun Feb 28, 2010 6:49 pm

Device Recognized (Easylogger) and then...problem

2010-02-23T17:25:59+02:00

Hey, I have a big problem here and I don't know what I did wrong.

I've uploaded VUSB firmware to my controller (ATtiny45)
Change the settings, etc.

When I plug it in, it says Found New Hardware Easylogger
and then it says Found New Hardware Human Interface Devices
and THEN it says Found New Hardware and says that there's a problem......

I mean..what causes this? Enumeration works, device recognized...
whatever can cause the error?

FYI I use the same VID/PID as there is in the HID_data example in:
vusb -> examples -> hid_data -> firmware

I just changed the usbconfig and then uploaded it.

Is there anyone out there that can help me?

Statistics: Posted by vsovereign — Tue Feb 23, 2010 5:25 pm