iot-contact/fw/rtos/modules, branch mdns IoT device to check if doors and windows are closed or open https://cgit.xengineering.eu/iot-contact/atom?h=mdns 2025-04-06T17:11:20Z fw: app: Add image signing to Meson build 2025-04-06T17:11:20Z xengineering me@xengineering.eu 2025-04-06T17:05:20Z urn:sha1:f6f6d285c318d28bddfb99cf04104a5306a97c78 This automates signing the application firmware image for the MCUboot bootloader. fw: btl: Configure bootloader build with Meson 2025-04-05T13:33:09Z xengineering me@xengineering.eu 2025-04-05T09:10:12Z urn:sha1:82fa02bcac5e278586cb2e3c9cc597699f6f640d CMake ExternalProject creates a pretty confusing build tree. Since the rest of the project anyway starts moving to Meson the bootloader is configured via Meson as a first step. fw: rtos: modules: Rename to hal_stm32 2025-03-26T20:18:23Z xengineering me@xengineering.eu 2025-03-23T17:38:04Z urn:sha1:42126a39b96817fed111a9ec271688681382f4b0 This submodule is called `hal_stm32` upstream. Thus the submodule directory should here be called exactly the same to reduce confusion compared to `stm32`. fw: rtos: modules: Move mcuboot submodule here 2025-03-26T20:18:23Z xengineering me@xengineering.eu 2025-03-23T17:33:19Z urn:sha1:1fcf9bd0d1af10c57a67d90496b5406244ca25ba The mcuboot Git submodule used to be located in `fw/btl`. Nevertheless since it is also a Zephyr module it should go to `fw/rtos/modules`. This makes sure all Zephyr modules are at the same place. fw: rtos: Restructure RTOS-related code 2025-03-22T21:30:46Z xengineering me@xengineering.eu 2025-03-22T20:53:20Z urn:sha1:e4d826addcf7941c79418a674a3b362a035f1bef This reduces nesting and makes the directory structure simpler.