by Dren » Wed Aug 10, 2016 12:15 pm
I tried posting this reply on Microchip forums... gave up !!!
When I send a report I send either a keyboard report or a mouse report, which works fine when the USB is declared as a keyboard or mouse. When the USB is declared as a composite device, I still sending the same Keyboard report, do I need to send a composite report ? I thought that the 2 devices would be independent ? There is only 1 input report ?
Personally I feel like wiping the whole lot and starting from scratch with a new microprocessor, this is wasting days of my time ! However amateur and messy the USB framework is below the waterline, the User interface should be nice and clear. ONE file that sets up the descriptor and ONE file that handles the interface, all the other repeated defines + status checking + rubbish (even clutter in MAIN !) should be swept away behind the scenes. Oh and the ridiculously complex interdependences of the USB Stack files sorted out.. You define and enumerate what you need in a main USB header, NOT merrily create them willy-nilly as you go along ! BTW why is it USB Stack, with a SPACE ! That throws out command line compilers, keep to a standard, say usb or USB or even USBStack or USB_Stack. Then the MLA itself has dozens and dozens of copies of the same dozen USB files, why not a common directory ? In fact why so many files in the first place ?
case you hadn't guessed I have really had enough of trying to working with this really disappointing framework code. I just haven't got the time to waste so much of it getting to understand this badly written microchip muddle. Esp when I shouldn't need to !
I needed to let off some steam... ahhhhh that's better. Now a cup of tea, then I can get back to it... thinking good thoughts....