Filipe Laíns 🇵🇸
Filipe Laíns 🇵🇸
Hum, I think we can just have the build system automatically generate these files.
Instead of using the preprocessor to configure this, I was thinking about having different variants. There's actually not that much that we'd want to configure, the button count for eg....
We have to align the data to the byte level -- we can't send a half byte, we need to send full bytes -- so padding bits might as well...
I mean, it shouldn't really make *that* much of a difference, but it is a trivial thing to do, so why not do it? The worst case scenario for the...
No, I don't want any `#ifdef`, I want different structs for each :stuck_out_tongue:. And this would only be for common reports, like I mentioned in the first reply, if a...
Feel free to open a PR adding it to the README.
Yeah, you just need to create a new config for the `stm32f1-generic` target (see https://github.com/openinput-fw/openinput/blob/main/src/targets/stm32f1-generic/config/rival310.h for an example), and add a symlink to `stm32f103t6.ld` for your config in https://github.com/openinput-fw/openinput/tree/main/config/linker/stm32f1-generic.
The firmware blob for the sensor should go to https://github.com/openinput-fw/sensor-blobs, and we'll generate a header that can be used in the code. We don't have a bootloader yet, just the...
> How would I extract the firmware blob for the sensor? Your device as an external eeprom, right? It should be stored there. > How would "flashing directly" work? Plugging...
I think we want to do that in the future, but for now it is simpler to do it this way.