iot-contact, branch debug-network-issueIoT device to check if doors and windows are closed or openhttps://cgit.xengineering.eu/iot-contact/atom?h=debug-network-issue2024-08-30T07:52:41Zfirmware: Add default IP for debug-network-issue.py2024-08-30T07:52:41Zxengineeringme@xengineering.eu2024-08-30T07:52:41Zurn:sha1:0820760bc556ddef7af5c7cd75565abbd3102698
That way the script works without any command line options which is
convenient. The selected IP is the default IPv4 address used by Zephyr.
firmware: Add tools/debug-network-issue.py2024-08-30T07:49:07Zxengineeringme@xengineering.eu2024-08-30T07:41:21Zurn:sha1:3b976f78160c3acca82fc2da53207cd85b548cdd
This script can be used to analyze an issue which causes that the
microcontroller is not able to communicate via the network after roughly
every second boot.
firmware: Add minimal README2024-08-29T16:01:53Zxengineeringme@xengineering.eu2024-08-29T15:56:25Zurn: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.txt2024-08-29T15:46:51Zxengineeringme@xengineering.eu2024-08-29T15:46:51Zurn: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 submodules2024-08-29T15:39:27Zxengineeringme@xengineering.eu2024-08-29T15:39:27Zurn: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 submodules2024-08-29T14:31:35Zxengineeringme@xengineering.eu2024-08-29T12:17:58Zurn:sha1:22d914b78ece2e67d4bd2c6829f716b5760594c1tools: Remove last tool download.sh2024-08-24T19:26:28Zxengineeringme@xengineering.eu2024-08-24T19:26:28Zurn:sha1:6bb372e0ca443bda11f05d19ba96742f5de2027a
The provided documentation download is not useful anymore. It might be
re-introduced later if required.
firmware: Implement printk output on button press2024-08-23T16:47:48Zxengineeringme@xengineering.eu2024-08-23T16:47:48Zurn:sha1:73ecc1b734d4ea1102f9aa1057782a381e2768e2firmware: Implement minimal IPv6 firmware2024-08-23T15:33:46Zxengineeringme@xengineering.eu2024-08-23T15:24:37Zurn: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.
pcb: Remove folder2024-08-23T14:58:30Zxengineeringme@xengineering.eu2024-08-23T14:58:30Zurn:sha1:0db3f05ade565c23bc1654b5a88af4a06c71e17e
It is planned to switch to Ethernet instead of LoRa for communication.
Thus the custom PCB with the STM32WL MCU does not make sense anymore. To
get started the Ethernet variant will use a ST NUCLEO board to avoid
creating a custom PCB first.
pcb: Add TLV70233 voltage converter2024-06-08T13:49:59Zxengineeringme@xengineering.eu2024-06-08T13:49:59Zurn:sha1:63b35a95cf6f29b867e27f9bb99fa03a4b5c4fa3
This IC has a small footprint and will provide the 3.3 V for the
microcontroller.
tools: Print doc path after executing download.sh2024-06-07T19:25:38Zxengineeringme@xengineering.eu2024-06-07T19:25:38Zurn:sha1:4d4cb2a8fd79ffd6e65c7a7546dc9aba4e867656tools: Add checksum check to download.sh2024-06-07T19:24:39Zxengineeringme@xengineering.eu2024-06-07T19:24:39Zurn:sha1:60784a9ebaa6168b03851f359a83478c70c7dbebtools: Add download.sh to get external doc files2024-06-07T15:40:14Zxengineeringme@xengineering.eu2024-06-07T15:40:14Zurn:sha1:d8f8de953044328932836a450cbb4157736ba2d2
It is unknown if it would be legal to include those external documents
like datasheets inside this Git repository. Thus the added script
provides the ability to get them directly from the vendor.
pcb: Split into a hierarchy of schematics2024-06-05T19:38:47Zxengineeringme@xengineering.eu2024-06-05T19:38:47Zurn:sha1:2b38114643b68670092d6c389c51a0ae01d50e04pcb: Add 10-pin ARM Cortex debug connector2024-06-05T19:20:48Zxengineeringme@xengineering.eu2024-06-05T19:20:22Zurn:sha1:ba97734a2cbfff1b73581fd275bbd26583fdda89pcb: Add USB-C connector to schematic2024-06-05T19:09:50Zxengineeringme@xengineering.eu2024-06-05T19:08:22Zurn:sha1:0bcd66f32c6fcd24b01fc87b0d02c9ac4431b938tools: build.sh: Export PCB drawing as PDF2024-06-05T18:03:34Zxengineeringme@xengineering.eu2024-06-05T18:03:34Zurn:sha1:98d0231116b51f2945bed8b0c9336fb3e048dea3tools: Add clean.sh2024-06-05T17:48:43Zxengineeringme@xengineering.eu2024-06-05T17:48:43Zurn:sha1:869792d4b9030e0153ae882fd2e4cb6ecab7e159
This allows to conveniently remove files which are not tracked in
version control.
tools: Add build.sh to export PDF schematics2024-06-05T17:45:11Zxengineeringme@xengineering.eu2024-06-05T17:45:11Zurn:sha1:e6fc87d14aa2fcf30812b6b7bccd35dd3026631epcb: Add outline to PCB2024-06-03T19:23:05Zxengineeringme@xengineering.eu2024-06-03T19:23:05Zurn:sha1:69d66f534ca25bce98ee1984325149891f27f76c
This makes the KiCad project a valid PCB as a minimal starting point.
pcb: Place MCU in PCB editor2024-06-03T19:10:40Zxengineeringme@xengineering.eu2024-06-03T19:10:40Zurn:sha1:618ba4fa7b6da3695dca35a49b2b3beb5c695a53pcb: Add STM32WL55JCIx microcontroller2024-06-03T19:04:28Zxengineeringme@xengineering.eu2024-06-03T19:04:28Zurn:sha1:11cb5dc9e86a92314d78999674fe675ea3d52b78
Based on UM2592 the development kit Nucleo WL55JC which is used for
firmware development is based on the STM32WL55JCI7 microcontroller.
Thus this MCU should be a good starting point for now.
pcb: Save *.kicad_pro file after first KiCad run2024-06-03T18:49:48Zxengineeringme@xengineering.eu2024-06-03T18:49:48Zurn:sha1:c0c3baed554830a8990f99da888db87beb38edc1pcb: Create empty KiCad 8.0 project2024-06-03T18:45:41Zxengineeringme@xengineering.eu2024-06-03T18:45:21Zurn:sha1:6053827028a6590196baea8a3928fa10c1f2ddc6Add KiCad documentation link to README2024-06-03T18:22:06Zxengineeringme@xengineering.eu2024-06-03T18:22:06Zurn:sha1:064934874c84ca0ed7c59076972b7031ade4a375fw: Customize shell prompt2024-04-14T17:56:23Zxengineeringme@xengineering.eu2024-04-14T17:56:23Zurn: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 firmware2024-04-14T15:13:52Zxengineeringme@xengineering.eu2024-04-14T15:13:52Zurn:sha1:c852c3e4047b0a31910bf89436d620281a508029
This is enough to validate that the firmware is running by using the
integrated Zephyr shell.
Add README.md2024-04-14T15:12:25Zxengineeringme@xengineering.eu2024-04-14T15:12:25Zurn:sha1:f950daa67777b79037cf545111d4348cfeba3c0e