STM32U5: add HSPI support #3667
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
williams-one
force-pushed
the
stm32u5-add-hspi-support
branch
from
6c7458c to
3afce1e
Compare
|
I have updated DummyCycles configuration according to the driver taken from CubeMX |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds partial support for HSPI on the STM32U5 family. It also includes an example showing how to use the on-board flash on the STM32U5G9J-DK2 demo board in both OCTA-DTR and memory mapped mode.
The implementation has been modeled after the OSPI interface.
The support is partial since the inner structures define all the 16 lines of the peripheral. But the public interface only exposes constructors for Single SPI and Octa SPI (both blocking and non blocking), since these are the only two modes that I was actually able to test on my demo board.
In principle I could have added the implementation for all the other modes, but they would have been untested... So I chose not to :)
I have added this as a reminder at the beginning of the file.
Please let me know if this is OK for you