Fix issue on SPI for F0, F3, F7 and L4 platforms #143
Merged
Conversation
This file contains hidden or 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
LMESTM
reviewed
Oct 31, 2017
|
Hi @cparata, It seems this field is not common to all series. |
LMESTM
reviewed
Oct 31, 2017
cparata
changed the title
fpistm
approved these changes
Nov 6, 2017
benwaffle
pushed a commit
to benwaffle/Arduino_Core_STM32
that referenced
this pull request
Apr 10, 2019
Fix issue on SPI for F0, F3, F7 and L4 platforms
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.
Hi all,
I found a potential issue in the SPI library when the SPI instance is generated using dynamic allocation. In particular the "NSSPMode" field of the “Init” structure of the "SPI_HandleTypeDef" could be randomly initialized and it could cause troubles in the "HAL_SPI_Init". In order to avoid that we need to correctly initialized this field inside the spi_init.
I also fixed some compilation warnings (for Nucleo-L476RG) due to a misalignment in the .text section of the Linker Script. Probably this issue affects other platforms too.
Best Regards,
Carlo