- #USB XHCI COMPLIANT HOST CONTROLLER ERROR 28 DRIVER#
- #USB XHCI COMPLIANT HOST CONTROLLER ERROR 28 CODE#
- #USB XHCI COMPLIANT HOST CONTROLLER ERROR 28 PC#
I then moved it in the sequence the device sends to the PC and there was no difference. I looked at it in debug and setting aside the two bytes per character for unicode, it is fine. I've checked it a bunch of times, can't find anything wrong with it. Doesn't make sense as it was working a while back but as I started to make changes to my device descriptor table, it started presenting this error. You'll see that the string descriptor table is not being read correctly. Take a look at the good device descriptor first and then mine second.
I assume it is just to turn on the lights. Yes, the device does two way with the PC or radio. I need someone that knows stm32f4 boards and USB devices to lean in here. I thought once I got the device descriptors correct I would be flying but no, of course not.
#USB XHCI COMPLIANT HOST CONTROLLER ERROR 28 DRIVER#
I think he has a generic HID driver that should have two end points instead of just this mouse code.
#USB XHCI COMPLIANT HOST CONTROLLER ERROR 28 CODE#
The guy that wrote this base code is really good with stm32Fx boards on. The real issue is that all this is new to me. The other issue is the report descriptor is wrong as I was using the mouse report descriptor (so it would be wrong). I dont even see how the string table is defined in this code as it is all macros. It could be an alignment issue, I don't know, I've been staring at it all I morning. This changed all the structure lengths but I have the device descriptor looking perfect except it isn't reading the string descriptor table correctly. So in modifying the device descriptor I had to add an "out" endpoint, which I did. I started out with a mouse end point device which is a one way transfer. I have a basic problem with my code I guess. All I have is the HIDxxx.dll (can't remember the actual name). Back to the RC-28, I searched everywhere for code. Again, I'm sure I'll purchase their remote control software, this is just for my own edification. I wrote some code in VB 2017 community and I am working my way through the roughly 1000 commands. By the way, it's a bear to code a program to do simple things. Even at that point, though I am stuck with the device, I could play around and build other control systems for the radio. I'm probably going to purchase the Rc-28 and scope it to see what codes it's using. I've been playing around, and you can almost tune by holding the left click and moving the mouse. I don't know why they can't use the freakin wheel? I mean, how hard is it? I think the reason they don't want to support the mouse wheel is that then cheap bozos like me would be able to code up a mouse program using an encoder and dupe the rc-28. Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft,, 1.Steve, what bugs me about the mouse on the 7610 is that in CW, you can click on a signal but then you need to take your hand off the mouse to finish tuning. : USB Composite Device (VID:1E7D PID:2E2C), ROCCAT, ROCCAT Kone Aimo 16K : USB Composite Device (VID:1E7D PID:3098), ROCCAT, ROCCAT Vulcan AIMO ports 1-8 were empty, deleted to save space Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft,, 1.488 SteamVR System Report created Sun Oct 25 08:15:46 2020ĭeviceID: PCI\VEN_10DE&DEV_1B80&SUBSYS_119E10DE&REV_A1ĭeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\\0003
0 kommentar(er)
