-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support 18F14K50 #2
Comments
+1 |
Change where ep0_data_stage_callback() gets called. There are three cases for a control transfer: 1. OUT with no data, 2. OUT with data, 3. IN with data. Previously, for all three cases, the callback was actually called at the end of the Status stage. This commit makes the stack call the callback at the end of the Data stage in case #2. The benefit is that now the application can optionally reject the data stage (by returning -1 from the callback). This will cause a Stall status to be sent to the host, notifying the the host of the failure.
Sorry for reviving an old issue, but does m-stack support 18F14K50 now? |
I don't have one of those chips. Have you tried it on yours? There are some differences on that one. It only has 8 endpoints, and I don't know what else is different. |
I havent tried yet, i will be able to try tomorrow. I want to port an existing application, that is using the non-free Microchip stack, so that the full source can be open, is it compatible with it? I must say, i have no idea about USB, or how it works on PIC, i am kinda hoping it will be mostly painless to do. |
Microchip's USB stack is under the Apache 2.0 license the last time I checked; what do you mean? |
Turns out you were right @DavidEGrayson ! Its Apache 2.0! Wasnt aware of that, i am trying to port over Numato's FPGA on-board programmer software, so they can open-source the entire thing. |
Yeah, I believe the license changed some time in the last few years. They also made it so the USB stack supports XC8 instead of just C18. |
Sorry for reviving an old issue as well, but does m-stack support 18F14K50 now? Has anyone ported it already? What needs to be done to do so? |
Would be nice with support for 18F14K50
The text was updated successfully, but these errors were encountered: