Actually, I am genuinely happy to see this one - it’s the Windows USB device error message:
Why am I happy about seeing this? Because it means I’m making progress. That error is now generated in response to enabling the MyUSB driver on my USBKEY board.
The error itself isn’t important just yet, as while the control endpoints for configuring the device are set up correctly, they aren’t used and so the device doesn’t do anything more than indicate that it’s attached to Windows. Later on when I get the control system working and provide some descriptors I should be able to get the driver to enumerate as any device I like.
I’m still using the original Atmel driver as a guide for how to structure the top-level of my driver. I’ve made some major changes to the last revision, with the VBUS notification now comming from the VBUS interrupt of the general USB interrupt vector.
The test app now runs as the joystick monitor on startup. Upon pressing the HWB, the USB interface is started as a device, and the joystick monitor is disabled. When in USB mode, the first Bicolor LED indicates if the USB interface is enabled (you can press HWB multiple times to start/stop the interface) while the second LED indicates the VBUS status. When waiting for the USB plug to be inserted, this LED is orange, and changes to green when the USB power is detected.
I’m investigating what I need to do for the control endpoint now - hopefully I’ll have some real, interesting progress done by the end of next week. I sure hope so - semester 2 of University begins on the 23rd which will severely limit my free time once again.
As an aside - yes, that time on the above screenshot is correct. I frequently stay up to odd hours on long holiday breaks. I can’t stop working on my AVR projects!
Recent Comments