Frederic Pillon

Currently, I'm working (almost finished) on variant rework and make all pins from the pinmap array available. This will remove this restriction pointed by @matthijskooijman > * The variant defines...

Hi, I've fixed the issue in the platform.txt of the STM32 core. See https://github.com/stm32duino/Arduino_Core_STM32/pull/1018

Hi @d21d3q, yes you can ;) any feedback, contributions,... are welcome. You're right, I think it can be optimized.

Last CS pin used and its `SPISettings` have to be checked to ensure all is ok. This implies to not remove it from `SPISettings spiSettings[NB_SPI_SETTINGS];` at `endTransaction`. else one other...

@matthijskooijman Firstly, it is documented here: https://github.com/stm32duino/wiki/wiki/API#new-api-functions-1 I know, this could be improved. This "driver" has never been updated nor improved while it should. That's the purpose of this issue....

> removed ALL "PinName" references as D1, D2, D3, A1, A2, just do not make any sense when the board has PA_1, PB_13 etc. PYn, Dx, Ax,... are pin numbers...

Thanks @matthijskooijman I've planned to provide the https://github.com/xpack-dev-tools/openocd-xpack/releases/ with the core. I do not known well the mechanism for external programmers. I have to investigate this also... 🙄

Yes that would be easier to use the one from Arduino. When I've checked it was outdated that's why I think about the xpack one which seems to be more...

Thanks @matthijskooijman managing bootloader upload was also in my huge todo list. Seems promising. For the unified shell scripts naming you can use the master of the tools repo: https://github.com/stm32duino/Arduino_Tools

Is there any update on this ? Thanks in advance.