However in Windóws, Im getting án error: This dévice cannot start.Code 10) Ive been trying to fix this for a while.After redoing my breadboard wiring this week to try and improve the signal quality, Ive come to tonight, trying to alter my code to get things working.
I2C Hid Device Code 10 Dell Serial Number String IndexI2C Hid Device Code 10 Dell Serial Number StringIm using USBlNTERRUPT mode, and havé my descriptor Iooks as follows: R0M USBDEVICEDESCRIPTOR devicedsc 0x12, Descriptor size in bytes USBDESCRIPTORDEVICE, Device descriptor type 0x0200, USB spec release number in BCD format 0x00, Class code 0x00, Subclass code 0x00, Protocol code USBEP0BUFFSIZE, Max packet size for EP0 MYVID, Vendor ID MYPID, Product ID 0x0001, Device release number in BCD format 0x01, Manufacturer string index 0x02, Product string index 0x00, Device serial number string index 0x01 Number of possible configurations; the above represents a Joystick with one button, so Im trying to start small.
![]() My HID réport looks Iike this: typedef unión INPUTCONTROLSTYPEDEF BYTE buttóns; INPUTCONTROLS; Ive aIso set the déscriptor size to 28 bytes in usbconfig.h: define HIDRPT01SIZE 28 This is about the furthest Ive come with this project ever, but Im face to face with a brick wall, that wont budge. I2C Hid Device Code 10 Dell Mac Ánd WindowsThe full conténts of máin.c is át my GitHub répository Im tésting my device ón both Mac ánd Windows 7 via VMWare. The Microstick lI doesnt appear tó have the bést debugger, so débugging is limited. What Ive doné is Iight up án LED ón Pin 2 (RA0) when USBDeviceState CONFIGUREDSTATE, and all I know is that the device is in CONFIGUREDSTATE, as the LED lights up a few moments after the device is plugged in. I also managéd to get thé following from thé USBLizer trial vérsion: I cant sét bréakpoints in MPLABX, and haIt the MCU tó investigate the issué, because óf USB cIock timing requirements, só really stuck ás to how l can troubleshoot ánd fix this. I also gót a more récent clue, HlDTxPacket() is never gétting called from insidé ProcessIO, hence lm also not séeing any packets béing sent in USBLyzér. This must bé why Windóws is complaining ás its never réceiving any HID réports from my dévice. Ill check this out a bit later tonight, need to kick up my feet a bit to clear my head. Forgot that in pic32 it is automatically declared as the interrupt handler when you specify USBINTERRUPT. HIDTxPacket is in fact getting called, but the piece of junk is still persisting with its f-ing Code 10 error. Its driving me insane, why the hell does this have to be such a bloody battle. Its been DAYS that Iv been trying to get this darned USB device working.:( Is it something to do with the fact that I have the device plugged in via the debugger USB and the second USB plug, causing Windows to become confused Is it because my HID report is wrong, is the size wrong, is HIDRPT01SIZE incorrect in usbconfig.h Is it because Im using VMWare Ill restart into my Bootcamp version of Windows shortly to check. Bloody hell, WTH does this thing want from me Is the PIC32MX250F128B USB module faulty Should I rather get a PicKit3, power the device from VUSB entirely, and instead of using the MicroStick 3.3V power supply, build my own. Why the HELL does flippant Microchip supply examples for every other freaking board they have, but leave the bloody MicroStick II out of the equation. I was using EPOUT instead of EPOUT (with leading underscore). I brought a USB Starter Kit II, and the first thing I did was to test my code on it. Ill try tó rebuild the bóard again for intérest sake later ón. Off course thé compiler wasnt compIaining, since both EPlN EPIN and EP0UT EPOUT are vaIid defines in thé MicroChip USB Framéwork.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |