Objective Development Forums

This is the latest version of our driver. Yes, it supports 4 endpoints: One control endpoint (0), two interrupt- or bulk-in endpoints and one interrupt- or bulk-out endpoint. The interrupt-out endpoint can have the same number as one of the interrupt-in endpoints, we therefore need only one bit to d...

More endpoints would require a change in the assembler modules. Since the bits of the endpoint field are scattered over two bytes, we only evaluate one of them. To distinguish more endpoints, you must reconstruct the full endpoint address, mask it and then compare. There are no spare cycles left in ...

If you started with HIDKeys, you probably get the log from int main(void) { uchar key, lastKey = 0, keyDidChange = 0; uchar idleCounter = 0; wdt_enable(WDTO_2S); hardwareInit(); odDebugInit(); usbInit(); sei(); DBG1(0x00, 0, 0); This would...

No problem to mail you libhid.a, but I need your email address. Can you please get in contact with us through the support web form?

This looks like a stack overflow to me. The device would not suffer a RESET otherwise. Or a hardware problem which triggers brownout or other sources of reset.

The debug log

ff:
ff:
ff:
...

is printed while the USB is in RESET state. This means that the driver reads both, D+ and D- as zero. See usbdrv.c and search for DBG1(0xff, 0, 0); to see how reset is detected.

How long is the disconnect during reset? Windows detects it only (reliably) if it's at least ~ 500 ms long. Otherwise it may be "overlooked" and the device and host are out of sync with respect to the device ID. You can only rely on the "ding" sound on Windows if your disconnect ...

I'm running RemoteSensor (which uses an Intertupt-In endpoint to signal the availablility of data) through a USB 2.0 hub connected to a USB 1.1 host since years without problems. Since hubs should be transparent to the device, I have no real idea how this can happen. I should note, though, that USB ...

gPowerSwitch should still work since we have not changed the API.

PowerSwitch ships with a Windows executable and libusb-win32 which must be installed. You need minGW only if you want to compile form the source code.

Can you compile avrdude yourself and enable debug logs in ser_avrdoper.c by defining the macro USB_DEBUG?

I can't think of any reason why avrdude should not find the device, except maybe if you have registered another driver, maybe libusb-win32 for the VID/PID combination. Can you verify that?

And you are sure you compile for 12 MHz and not with an assembler module for another frequency. In this case you should really try to get a debug output with -DDEBUG_LEVEL=2...

Have you checked whether Windows Media Player supports control through these keyboard extensions at all? These key codes may be filtered by the Windows kernel driver or they may be mapped to events which are ignored by Windows Media Player. I have no experience with Windows myself, so I'm araid I ca...

It was definitely not a brown-out in my circuit because I used an AT90S2313 which has no brown-out detection. And I added all types of capacitors to the supply voltage in the hope that it would improve things.

I doubt that this is a problem with the host side driver. Switching to HID won't help. The original firmware was without the USB reset code. Inserting the reset code fixed the problem for Linux (Linux detects the disconnect condition fast enough). I think that's proof enough that the processor resta...

Please change the definition of hi8(x) in usbdrvasm.S to

# define hi8(x) (((x)>>8) & 0xff)

That should fix the problem. We'll include this change in the next release.