-
-
Notifications
You must be signed in to change notification settings - Fork 283
JIRA-624: I2C slave mode #218
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
return I2C_OK; | ||
} | ||
} | ||
delay(1); |
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.
I see some loops that have been "spaced out" using delay(1). That's fine, it shouldn't have any negative effects since I2C is quite slow anyway, but I don't think it will gain anything either. Remember, this is for a single-threaded MCU device.
How is this going to work without a onReceive implementation? |
Please note that the physical I2C slave mode interface is not available on the Arduino 101 hardware platform and, thus, it is not going to be part of Corelibs. This is done as a preparation for future products. |
Yes, I'm aware of that. I thought this was a software implementation or something like this. I'm not sure if this would be possible, though. |
@SidLeung @eriknyquist @linrjing |
1. added the I2C controller slave mode support for Lakemont. 2. limits to use the I2C slave driver: the I2C slave can receive max 32 bytes in a single transmission, so if the master want to transmit more than 32 bytes, please split the single transmission to multiple 32 bytes transmission.
…eed and address mode
Please do not make any additional changes to this branch until further notice. |
@bbaltz505 Please close this branch without merging it to the main trunk. |
added I2C controller slave mode support for Lakemont.