-
Notifications
You must be signed in to change notification settings - Fork 0
boards/nucleo-f091: add i2c config #7
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
Thanks, but to minimize the final size of this PR, I wanted to do this once the new I2C interface feature branch is merged. Is it ok ? |
I don't mind, I needed this to test on one of the f0 I have ;) I'll rebase this once everything is merged. |
I should have configured this one, since I also have it. But finally went for the f070... |
d4a77a6
to
fce19d1
Compare
0ba7d9d
to
5275fa9
Compare
8209dfb
to
fafec43
Compare
@vincent-d, now that I2C refactoring is in, you can rebase and PR this upstream. I have the hardware for testing :) |
see RIOT-OS#9727 |
suit/examples: add wireless examples and doc
Consider the following configuration: nib prefix 2001:16b8:4569:88fc::/62 dev #7 expires 7081 sec deprecates 3481 sec 2001:16b8:4569:88fe::/63 dev #6 If `_on_link()` stops at the first match, a packet received from #7 with a destination in the downstream subnet in #6 would always be sent back via #7 if this happens to be the first entry in the list. Instead, consider all prefixes and return the one that is the closest match.
Contribution description
Add config for stm32f091 and nucleo-f091
Issues/PRs references