-
Notifications
You must be signed in to change notification settings - Fork 948
board/teensy40: Add I2C support #1471
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
Conversation
db7c6cf
to
8f75d04
Compare
bad12d2
to
6e663e9
Compare
Please rebase this branch against dev to resolve merge conflicts. Thanks. |
6e663e9
to
30531f4
Compare
rebased against |
30531f4
to
30221e4
Compare
f21f112
to
0b29887
Compare
rebased against dev |
Sorry I have not looked at this PR sooner. I will get out my Teensy 4.0 and try it out in a bit. |
Was trying this PR but #1454 (comment) General comment: should define a I2C0 to point to I2C1 in this PR? |
0b29887
to
bb3185e
Compare
rebased against dev (3eb9dca) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ardnew
Both i2c0 and i2c2 worked, but i2c4 did not.
I think it needs a few fixes, but for the most part it is very good.
5539664
to
f171d9e
Compare
Addressed remaining comments and rebased against dev (b5c5d95) |
This PR is baselined on top of the Teensy 4.0 UART support PR (#1454)
This PR adds support for 3 (three!) I2C interfaces on the Teensy 4.0.
The public I2C API is the same as most other TinyGo devices with no substantial deviations I'm aware of.
Testing this implementation has been done entirely through 2 new drivers I'm actively developing and are not yet available.
The following table (from
src/machine/board_teensy40.go
) succinctly describes all of the important properties of each of the 3 supported I2C interfaces available in TinyGo: