To modify the SD driver initialization for the FMU-v2 target board #130
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
…hich previously caused the compilation to use the FMU-v5 driver for initialization.
|
Thanks for your notice. It seems your change is not completely correct. I'll fix this issue in the near future commit |
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.
To modify the SD driver initialization for the FMU-v2 target board, which previously caused the compilation to use the FMU-v5 driver for initialization.
The implementation in target/pixhawk/fmu-v2/drivers/sdio/drv_sdio.c is rt_err_t drv_sdio_init(const char* device_name), but in target/pixhawk/fmu-v2/drivers/sdio/drv_sdio.h and the implementation in board.c, it is declared and implemented as rt_err_t drv_sdio_init(void). This discrepancy leads to the usage of the FMU-v5 SD driver during compilation, utilizing the SD read/write functionalities from the F7 HAL library. It is likely that both FMU-v2 and FMU-v5 share the same register addresses for SD operations.