-
-
Notifications
You must be signed in to change notification settings - Fork 7k
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
USB-Core Fixes #3562
USB-Core Fixes #3562
Conversation
Needs this PR to be merged: arduino/Arduino#3562
This way a key can be specified in the pins_arduino.h file
IMHO, a single big commit that just says "Applied fixes from HID-Project development" messes up the history badly, those changes should at least be documented in detail, but preferably be split into multiple commits. If you already have them as separate commits in your HID-project repository, you can probably fiddle a bit with Regarding the |
I am not that git pro. But I can make a new PR if wanted. The Events were made for this usage: |
@NicoHood You should be able to implement the same sketch by simply polling the |
Could be possible, have to check that. Wouldnt it also make sense to mark the USB functions as weak, so one can overwrite the USB clock settings etc? Then other MCUs can be supported with a library via a strong implementation which overwrites those functions. Or even with a .cpp file in the pins_arduino.h This would help if the Arduino team does not want to include my u2 support code to the core itself (if there is any reason for this, dunno). |
Should I open a new PR with this branch? I had so many problems to get my git in sync with the master, I am not able to repair this PR, so I'd create a new one if desired. This patch has nothing complicated in it and the commits are now more clean. Please have a look. |
Moved to #3640 |
Backported a few fixes from https://github.com/NicoHood/HID
Keywords for the Serial functions should be added as well. Inlining those functions doesnt work since its a static variable. I think this is the most save and easy way to access the data for advanced users.
Should we change the Bootkey (for the non 32u4 boards) to a 1byte value? Thats normally enough and saves flash in the bootloader and sketch itself. I'd go for it, since I have to change my HoodLoader2 anyways.