Skip to content
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

New SD pins management: setxxx() usage ignored #75

Closed
fpistm opened this issue Sep 17, 2024 · 0 comments · Fixed by #76
Closed

New SD pins management: setxxx() usage ignored #75

fpistm opened this issue Sep 17, 2024 · 0 comments · Fixed by #76
Labels
bug 🐛 Something isn't working
Milestone

Comments

@fpistm
Copy link
Member

fpistm commented Sep 17, 2024

Since #58, it ist possible to dynamically define the SD pins using:

  • setxxx() methods: setDx, setCK, setCMD, setCKIN, setCDIR or setDxDIR.
  • init() or begin()

Example of code:

  card.setDx(PC8, PC9, PC10, PC11);
  while(!card.init(SD_DETECT_PIN)) {

As init() or begin() called the setDx methods with default arguments the first call is simply not applied.

@fpistm fpistm added the bug 🐛 Something isn't working label Sep 17, 2024
@fpistm fpistm added this to the 1.3.3 milestone Sep 17, 2024
fpistm added a commit to fpistm/STM32SD that referenced this issue Sep 17, 2024
Only set*() methods and SDx_* definitions allows to manage the pins
else the first pin available in the associated PinMap_SD_* arrays
will be used.

Fixes stm32duino#75.

Signed-off-by: Frederic Pillon <[email protected]>
fpistm added a commit to fpistm/STM32SD that referenced this issue Sep 17, 2024
Only set*() methods and SDx_* definitions allows to manage the pins
else the first pin available in the associated PinMap_SD_* arrays
will be used.

Fixes stm32duino#75.

Signed-off-by: Frederic Pillon <[email protected]>
@fpistm fpistm closed this as completed in d8cf24c Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
Development

Successfully merging a pull request may close this issue.

1 participant