-
-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
ARM I2C driver not implemented for KINETIS MCU's (i.e. Teensy 3.2/3.5/3.6/LC) #7574
Comments
you can move #define USE_I2CV1 from mcuconf.h to config.h which could bypass this issue. And after pr #7526 was merged, you can add the KINETIS support easier. |
Also need this for the input club keyboards, as they use a custom i2c implementation but need the |
It was already on config.h along with #define I2C_DRIVER I2CD1, i just copied and pasted on the wrong field while writing the post. I edited it, sorry. |
There is a small amount of change required outside of |
Thanks a lot @zvecr. I will wait until it's ready and then test :) |
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. |
The I2C driver used for OLED functionality does not support KINETIS ARM microcontrollers.
Feature Request Type
Description
I have been waiting to implement this functionality on my finished keyboard i made about 3 months ago. This has been discussed on the discord server and while some process was made, the driver has no proper definitions to compile and work with the Chibios hal driver.
Setting the following in:
mcuconf.h
config.h
will result in the following compilation output:
Default values for OPMODE_I2C and STD_DUTY_CYCLE are missing (that's why they are set in the config file), and USE_I2CV1 should be defined by the driver.
This is the furthest i could get with my skills.
Functionality is already supported in Chibios.
Hopefully the community can implement this properly since it will open up the functionality of QMK even further:)
I can provide hardware testing since it is already build and used daily.
The text was updated successfully, but these errors were encountered: