Skip to content
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

boards/nucleo-f303re: fix I2C[1] sda_pin and scl_af settings #16275

Merged
merged 1 commit into from
Apr 7, 2021
Merged

boards/nucleo-f303re: fix I2C[1] sda_pin and scl_af settings #16275

merged 1 commit into from
Apr 7, 2021

Conversation

roh849
Copy link
Contributor

@roh849 roh849 commented Apr 3, 2021

Contribution description

boards/nucleo-f303re: fix I2C[1] sda_pin and scl_af settings

The config-values of second i2c-device did not match the values given in stm32f303re datasheet - now they do.

Testing procedure

The new configuration has been tested with tests/periph_i2c, tests/driver_bmx280, tests/driver_at24cxxx and suitable i2c devices (bme280-sensor, 24lc512-eeprom)

@roh849 roh849 requested review from aabadie and fjmolinas as code owners April 3, 2021 03:56
@chrysn chrysn changed the title changed some parameter values in i2c_config array boards/nucleo-f303re: Change I2C1 SCA/SCL pin settings Apr 3, 2021
@chrysn chrysn added the Area: boards Area: Board ports label Apr 3, 2021
@chrysn
Copy link
Member

chrysn commented Apr 3, 2021

The changes are consistent with the 303xE datasheet (whereas the original values were not).

Is there a particular reason why for SCL the AF was adjusted to the pin, and for SDA the pin was adjusted to the AF?

@chrysn chrysn added the Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) label Apr 3, 2021
@fjmolinas
Copy link
Contributor

The changes are consistent with the 303xE datasheet (whereas the original values were not).

Is there a particular reason why for SCL the AF was adjusted to the pin, and for SDA the pin was adjusted to the AF?

I think it mainly to match a layout where both pins are close to each other:

image

So since @chrysn verified the datasheet values this one seems good to go, @roh849 can you modify the commit message to fit our coding conventions, there are some details here, but basically, the commit should be something like boards/nucleo-f303re: fixe I2C2 SCA/SCL pin settings

@roh849 roh849 changed the title boards/nucleo-f303re: Change I2C1 SCA/SCL pin settings boards/nucleo-f303re: fix I2C[1] sda_pin and scl_af settings Apr 6, 2021
@roh849
Copy link
Contributor Author

roh849 commented Apr 6, 2021

The changes are consistent with the 303xE datasheet (whereas the original values were not).
Is there a particular reason why for SCL the AF was adjusted to the pin, and for SDA the pin was adjusted to the AF?

I think it mainly to match a layout where both pins are close to each other:

image

So since @chrysn verified the datasheet values this one seems good to go, @roh849 can you modify the commit message to fit our coding conventions, there are some details here, but basically, the commit should be something like boards/nucleo-f303re: fixe I2C2 SCA/SCL pin settings

I modified the commit message title. @chrysn: Thanks for removing the comment markers.

@fjmolinas fjmolinas added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR and removed CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Apr 6, 2021
@fjmolinas
Copy link
Contributor

@roh849 you modified the PR title, not the commit message ;)

@roh849
Copy link
Contributor Author

roh849 commented Apr 6, 2021

@roh849 you modified the PR title, not the commit message ;)

I modified the commit message too.

@fjmolinas
Copy link
Contributor

@roh849 you modified the PR title, not the commit message ;)

I modified the commit message too.

Did you push? I don't see the change in github

@benpicco
Copy link
Contributor

benpicco commented Apr 6, 2021

You can edit your commit with git commit --amend.
Since that means you are re-writing history, a force push is necessary (git push -f)

@roh849
Copy link
Contributor Author

roh849 commented Apr 7, 2021

seems to be a difficult birth ;)
-changed the commit message on my local copy
-pushed it to my remote fork
-PR has been changed automatically(?)

@fjmolinas fjmolinas added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Apr 7, 2021
@fjmolinas
Copy link
Contributor

fjmolinas commented Apr 7, 2021

Thanks @roh849 its all good now, let see if murdock agrees, I triggered the CI!

Copy link
Contributor

@fjmolinas fjmolinas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK!

@chrysn chrysn merged commit a8e0ded into RIOT-OS:master Apr 7, 2021
@roh849 roh849 deleted the nucleo-f303re-i2c-conf branch April 9, 2021 15:26
@kaspar030 kaspar030 added this to the Release 2021.04 milestone Apr 23, 2021
@chrysn chrysn added the Release notes: added Set on PRs that have been processed into the release notes for the current release. label Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: boards Area: Board ports CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Release notes: added Set on PRs that have been processed into the release notes for the current release. Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants