IoT device to check if doors and windows are closed or open https://cgit.xengineering.eu/iot-contact/atom?h=esp32s2_devkitm 2024-11-03T19:11:25Z 2024-11-03T19:11:25Z xengineering me@xengineering.eu 2024-11-03T19:11:25Z urn:sha1:13add8c6072c8311620217acd576b16ba37b13c3 TODO: This does not work currently. 2024-11-03T19:04:45Z xengineering me@xengineering.eu 2024-11-03T19:04:45Z urn:sha1:fa82565b1ce78e39452fc1370e674912cc9ca75f Otherwise the ninja call to build the firmware fails. 2024-11-03T19:03:25Z xengineering me@xengineering.eu 2024-11-03T19:03:25Z urn:sha1:e8fd8f50d3a7f5981b91ea2220f0a11222a0a288 2024-11-03T18:47:59Z xengineering me@xengineering.eu 2024-11-03T18:47:59Z urn:sha1:18198a9c68247a3d7e3ebb80336105111f8b8cf7 2024-11-03T18:42:56Z xengineering me@xengineering.eu 2024-11-03T18:42:56Z urn:sha1:7136a8074f200c2b1ed2a8f9389d7cc89014f447 2024-11-03T18:33:48Z xengineering me@xengineering.eu 2024-11-03T18:33:48Z urn:sha1:eacd4bd18409cc6e40466cd1468eb1b5bd74b35a It is planned to switch to a custom ESP32-based printed circuit board (PCB). This has the advantage that the ESP32 modules contain a lot of basic functionality and the complete network interface. This should be the minimal viable product (MVP). The esp32s2_devkitm is a development board to develop the firmware before even designing the MVP PCB. Since this board is not supported officially a patched Zephyr kernel close to v3.7.0 is used. The patch is a slight modification of the officially supported esp32s2_devkitc board. 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. 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 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. 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. 2024-08-29T14:31:35Z xengineering me@xengineering.eu 2024-08-29T12:17:58Z urn:sha1:22d914b78ece2e67d4bd2c6829f716b5760594c1 2024-08-23T16:47:48Z xengineering me@xengineering.eu 2024-08-23T16:47:48Z urn:sha1:73ecc1b734d4ea1102f9aa1057782a381e2768e2 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. 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. 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.