iot-contact/firmware, branch binary-descriptors IoT device to check if doors and windows are closed or open https://cgit.xengineering.eu/iot-contact/atom?h=binary-descriptors 2025-02-11T05:58:50Z fw: Move content of `firmware` here 2025-02-11T05:58:50Z xengineering me@xengineering.eu 2025-02-11T05:58:50Z urn:sha1:304e1e443dc1283efbd1fe8b4a72c13f6cfc2fe4 This makes the name shorter which is especially relevant for Git commit messages. firmware: Use pip freeze for requirements.txt 2024-09-06T18:27:31Z xengineering me@xengineering.eu 2024-09-06T18:27:31Z urn:sha1:2c18a99bd24ddadd165eeabe5299ac094b0c0ee3 This results in a complete list of required Python dependencies with fixed versions. This ensures that the build works reliably given that the dependencies are still available in referenced versions. firmware: Add minimal README 2024-08-29T16:01:53Z xengineering me@xengineering.eu 2024-08-29T15:56:25Z urn:sha1:0ff8c7370ad87ac450b32955210a1ec366413d61 This adds instructions for: - Python environment setup - building the firmware - flashing the firmware - get output from the Zephyr shell - removing the firmware from the device firmware: zephyrproject: Add requirements.txt 2024-08-29T15:46:51Z xengineering me@xengineering.eu 2024-08-29T15:46:51Z urn:sha1:f60daa445ff4daf4aa40d2d5b35197b4e5eadd0d This is (hopefully) the minimal set of Python dependencies required to execute the firmware build. It is meant to be installed inside a Python virtual environment (venv). To add one which is not accidentally tracked by Git a .gitignore files is added too. firmware: Adapt CMakeLists.txt to Git submodules 2024-08-29T15:39:27Z xengineering me@xengineering.eu 2024-08-29T15:39:27Z urn:sha1:04f4abae5822fe166c9100e36e4631bbb82744e5 The following properties are now set in CMakeLists.txt: - Zephyr kernel path - required Zephyr module paths - selected board This makes the command line call for CMake trivial: cmake -Bbuild -GNinja The user does not have to specify these options on the command line. firmware: Add Zephyr sources as Git submodules 2024-08-29T14:31:35Z xengineering me@xengineering.eu 2024-08-29T12:17:58Z urn:sha1:22d914b78ece2e67d4bd2c6829f716b5760594c1 firmware: Implement printk output on button press 2024-08-23T16:47:48Z xengineering me@xengineering.eu 2024-08-23T16:47:48Z urn:sha1:73ecc1b734d4ea1102f9aa1057782a381e2768e2 firmware: Implement minimal IPv6 firmware 2024-08-23T15:33:46Z xengineering me@xengineering.eu 2024-08-23T15:24:37Z urn:sha1:fa22728ea19c81202899305fc118176ca3f7042b This firmware enables as much as required for the device to be reachable by ICMP via an link-local IPv6 address. The address can be looked up via the Zephyr shell with `net ipv6`. This is useful to check if the network stack basics work. fw: Customize shell prompt 2024-04-14T17:56:23Z xengineering me@xengineering.eu 2024-04-14T17:56:23Z urn:sha1:9ac3df7349f04733a1807d1ab5d0819d6bf08fdf The shell prompt was changed from the default 'uart:~$ ' to '[iot-contact] ' so that it is more visible which kind of firmware is running on the device. fw: Add basic Zephyr application firmware 2024-04-14T15:13:52Z xengineering me@xengineering.eu 2024-04-14T15:13:52Z urn:sha1:c852c3e4047b0a31910bf89436d620281a508029 This is enough to validate that the firmware is running by using the integrated Zephyr shell.