Runtime configuration based Port/Pin assignments about modm HOT 8 CLOSED

Thanks for the response, yes something like that but in my case the number of combinations are close to 80 and I have at least 5-6 peripherals so the total number of permutations are very high. I was thinking more like

auto config = ConfigResolver::load()
auto spi = Spi::create(config.spi.interface, config.spi.mosi, config.spi.miso, config.spi.sck)

Apparently all the pin assignments are passed as template variables which is compile time only rather than runtime and I don't know if there's any way to get around this 🤔

from modm.

You mean something like this?

if (board_A) {
    SpiMaster5::connect<GpioA5::Mosi, GpioA6::Miso, GpioA7::Sck>();
    SpiMaster5::initialize<BoardA::SystemClock, 5_MHz>();
}
else if (board_B) {
    SpiMaster5::connect<GpioB5::Mosi, GpioB6::Miso, GpioB7::Sck>();
    SpiMaster5::initialize<BoardB::SystemClock, 1_MHz>();
}
else if (board_C) {
    SpiMaster3::connect<GpioC5::Mosi, GpioC6::Miso, GpioC7::Sck>();
    SpiMaster3::initialize<BoardC::SystemClock, 20_MHz>();
}

The connect methods compile into very compact code (just constants basically), including a few different configurations like this will probably still be less code than a fully dynamic computation.

from modm.

You can of course just call GpioA5::setAlternateFunction(id);, which is what the connect function compiles down to, but you loose all of the compile-time sanity checks. The AF mapping is pretty random too for STM32.

from modm.

There’s no runtime API for this I’m afraid. I believe mbed has such an API, but it’s completeness may be lacking.

However, you can take a look at the modm:platform:gpio module to see how we transform the data from modm-devices into compile time structures, and perhaps transform it into a runtime friendly format instead. Or just generate one massive switch case with all permutations ;-p

from modm.

You can even use modm-devices on it’s own and extend another HAL with that data. That was the whole point of separating modm (the C++ library) from modm-devices after all.

from modm.

Thanks for the tips, I'll take a look and see what can I do. Extending from modm-devices sounds interesting, wonder how complicated would that be 🤔

from modm.

Here’s an introductory blog post: https://blog.salkinium.com/modm-devices/#using-device-files
Haven’t gotten around to writing more though.

from modm.

I'm closing this since its out-of-scope for modm, but feel free to continue posting questions/issues here about using modm-devices.

from modm.