-
Notifications
You must be signed in to change notification settings - Fork 3k
SD default configuration for ST boards is already defined in TARGET_STM #9386
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
@jeromecoutant, thank you for your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeromecoutant Thanks for the cleanup.
LGTM
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@jeromecoutant there are issues in this PR, for exmple "DISCO_F429ZI": { https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F429xI/TARGET_DISCO_F429ZI/PinNames.h |
@dannybenor As all these SPI_xx are defined for all STM NUCLEO and DISCO targets, |
@jeromecoutant we found runtime issues to initialize SD component in our CI tests over the weekend for nucleo boards. @dannybenor will provide more details |
Removed from components/storage/blockdevice/COMPONENT_SD/config/mbed_lib.json in #9386
SPI_NSS = PA_4, |
@jeromecoutant which setting is correct in your view for DISCO_F429ZI |
@0xc0170 |
We did not realize these fix is changing the pins . As I understand , this is a fix but it's breaking current applications. Applications use what was defined before in the component - in most cases ppl were not aware of default config in targets.
@jeromecoutant what do you suggest? Which config is correct? As apps use the SD config, we should keep it as it is within 5.11.x and can do clean up for 5.12? |
I removed 5.11.3 label for now until we get a solution |
The right definitions are in the TARGET_ST folder, according to the spec. The removed definitions are related to special wiring done for the CI. See |
+1, means this patch is fine and 5.11.3 label should be added back (update: 5.12 as this breaks the config so rather goes to the next feature release). We will fix this on our side, correct? |
@jeromecoutant I see in the doc https://www.st.com/resource/en/user_manual/dm00244518.pdf |
@jeromecoutant also for NUCLEO-F411RE I see in the documentation |
Description
Default configuration is:
"SPI_CS": "SPI_CS",
"SPI_MOSI": "SPI_MOSI",
"SPI_MISO": "SPI_MISO",
"SPI_CLK": "SPI_SCK",
As all these SPI_xx are defined for all STM NUCLEO and DISCO targets,
we don't need extra configuration to support component_sd
If some user uses other SPI pins, better way is to configure it at application side.
Pull request type