Skip to content

Improve SPI communication using SPISettings #35

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

Merged
merged 1 commit into from
Nov 18, 2019

Conversation

fabyte
Copy link
Contributor

@fabyte fabyte commented Oct 19, 2019

Using SPISettings together with begin/endTransaction allows using
multiple systems communicating over the same SPI bus. Thus far, the
initial SPI configuration was overridden by other systems that
configured SPI.

Additionally, due to compiler and linker optimizations, adjusting the
SPI settings via BME280_SPI_CLOCK, a much smaller memory footprint
is possible.

Finally, allow modification of the SPI mode by defining BME280_SPI_MODE.

Using SPISettings together with begin/endTransaction allows using
multiple systems communicating over the same SPI bus. Thus far, the
initial SPI configuration was overridden by other systems that
configured SPI.

Additionally, due to compiler and linker optimizations, adjusting the
SPI settings via BME280_SPI_CLOCK, a much smaller memory footprint
is possible.

Finally, allow modification of the SPI mode by defining BME280_SPI_MODE.
@fabyte
Copy link
Contributor Author

fabyte commented Nov 15, 2019

Any suggestions on this pull request?

@AndyEngland521 AndyEngland521 merged commit adeed2e into sparkfun:master Nov 18, 2019
@AndyEngland521
Copy link
Contributor

Thanks! pushed out in v2.0.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants