iot-contact, branch main

fw: Remove radvd.conf

2025-08-10T17:57:35Z

This is meanwhile replaced by `systemd-networkd` which supports sending router advertisements.

fw: Remove simulate-network.sh

2025-08-10T17:53:44Z

This script requires root privileges. It is annoying to always type a password for it and in general to start this script to test the native sim firmware. Thus the new approach is to provide the network infrastructure with a system-wide NetworkManager connection and the required servers (IPv6 router advertisement, MQTT, IPv4 DHCP in the future) with systemd services constantly. That way the full network environment for the simulation is always just there for the `zeth` interface and the firmware executable can just be started with user privileges.

pcb: io: Add relay indication LEDs

2025-08-10T15:41:22Z

To be able to debug the relay functionality it is useful to actually see it. Thus LEDs are added which light up whenever the assigned relay is actuated.

pcb: Place test points

2025-08-10T15:36:15Z

They should be used to easier connect cables to the board to debug hardware or firmware issues.

pcb: main: Set all part values

2025-08-10T15:28:31Z

pcb: Implement RJ45 termination and shielding

2025-08-10T14:38:52Z

fw: sim: srv: Add this folder

2025-08-10T13:58:49Z

This folder contains material to set up a network environment for the native sim firmware.

Add opt-in for nucleo_f767zi firmwares

2025-08-07T19:36:49Z

This partially reverts commit ce098756d79d8e4240bedc2bd74ff9a3a77fcedb. The reverted commit dropped the build logic for all nucleo_f767zi-related artifacts and thus for everything except the native sim firmware. Instead this commit reverts this change but comments out the `update_image` and `factory_image` targets from the `artifacts` variable in the top-level `meson.build`. This allows to build these two targets explicitly with `ninja -C build ` but does not include it into the deploy tar archive. Since this archive is the only target of the project with `build_by_default: true` this effectively disables the build with minimal code changes.

doc: api: future: Switch to `mqtt/url` setting

2025-07-30T17:50:18Z

doc: api: future: Switch to `set` topic suffix

2025-07-30T17:50:18Z

If a writable topic should correlate to a readable topic the new convention is a suffix (`my/topic/set`) instead of the old prefix (`request/my/topic`). This keeps the alphabetical ordering the same.

doc: api: future: Order MQTT topic by alphabet

2025-07-30T17:50:18Z

doc: api: future: Remove update automation

2025-07-30T17:50:18Z

With the change to MQTT the device will not be usable anymore without server infrastructure. This design change allows to reduce the complexity of configuration and implementation here significantly. The device only supports MQTT-triggered HTTP pull updates and the server should take care of regularly triggering this via MQTT.

gitignore: Add flash.bin

2025-07-30T17:49:14Z

This file gets created whenever the native sim build of the application firmware is executed from the repository root. This is quite common. Nevertheless the flash content of the native sim firmware should never be committed.

pcb: Fail build in case of bad ERC

2025-07-29T09:55:37Z

The electrical rules check already found multiple significant hardware design issues. Thus the build has to fail to indicate these issues early.

pcb: Add TODO for RJ45 connector

2025-07-29T09:52:27Z

Adding this TODO text and marking the termination and shielding related pins as unconnected makes the ERC clean. This allows to right now fail the build in case of bad ERC. This is preferred to not unintentionally inject other issues. The RJ45 connector and shielding / termination has to be reworked anyway.

pcb: power: Add DC fuse

2025-07-29T09:50:59Z

While the AC fuse is more critical it still might be a good idea to not completely rely on the fuse of the PoE PSE.

pcb: Use `kicad-cli` with Meson `find_program()`

2025-07-28T13:55:56Z

This gives better user feedback when the program is not available (as currently in the latest Debian stable version).

pcb: Add ERC report to build and deploy trees

2025-07-28T13:50:46Z

The report of the KiCad electrical rules check (ERC) is added with this commit to the default build and also written to the deploy tree. Since there are still minor issues a failing ERC will not yet break the build. This will be introduced later by adding the `--exit-code-violations` flag to the `kicad-cli sch erc` call.

fw: Remove nucleo_f767zi firmwares

2025-07-27T20:57:21Z

The bootloader and application firmware resulting in the factory- and update-image are removed from the build. The reason is a planned first release of this project with hardware design files for a first `iot-contact` board. The release is required to build this board with matching version specifiers. Since the release should contain a consistent set of hardware and firmware the firmware targeting the development board is removed. Handling firmware for multiple boards is also an option but has no use since the biggest part of the firmware features can be developed using the simulation only which should stay in long term.

pcb: power: Fix missing pull-up on regulator EN

2025-07-27T16:16:16Z

The +3.3V regulator has an enable (EN) pin. This was connected to the power-good (PG) output of the +5V regulator. It was overlooked that the PG pin is an open-collector pin and thus a pull-up resistor is required. This issue was found with the KiCad electrical rules check (ERC).

pcb: processor: Fix missing pull-up on STM32 RESET

2025-07-27T16:09:30Z

This is a significant design bug which would leave the RESET line of the MCU in a floating state. Thanks to ERC this is detected early.

pcb: Fix +3V3 and +3.3V confusion

2025-07-27T16:01:47Z

ERC brought up that those two global power labels were mixed. This is of course a design bug which is now fixed by consistently using +3.3V.

pcb: Remove 4-pin blind connector

2025-07-27T15:43:05Z

The old concept was to have three connectors: - 2-pin for contact loop - 3-pin for AC supply (PE, N, L) - 4-pin for blind connection (PE, N, L_UP, L_DOWN) The new concept is: - 2-pin for contact loop - 3-pin for AC supply (L) and blind connection (L_UP, L_DOWN) This saves the PCB space for one of the biggest parts. Furthermore it reduces space constraints for the PCB routing. The removed neutral and protective earth pins should not be a problem. It is less convenient for mounting since additional connectors between the supply and blind cable are required but apart from that N and PE would not have safety benefits in the current design. This used to be different when an aluminium case was considered at least as option. But the requirements for PE connection of the two halves of the housing would have a huge space requirement. Thus an anyway cheaper plastic case is the current goal.

doc: api: future: Update MQTT API

2025-07-27T09:45:54Z

doc: api: future: Introduce device info concept

2025-07-26T21:16:34Z

This reduces the HTTP endpoints and overhead.

doc: api: future: Switch to pull updates

2025-07-26T20:53:50Z

fw: Document TAP iface with NetworkManager

2025-07-26T19:43:38Z

This will be moved later to the user documentation so that the native sim build of the application firmware can easily be used on Linux machines using NetworkManager.

Merge implementation of tar archive deployment

2025-07-26T17:15:06Z

Deploying all build artifacts in a single tar archive file makes deployment easier. The bundle stays consistent, GPG signatures can later easily provided too, the archive and its top-level directory can have the same and long name and the further paths in the archive can stay short.

README: Document tar archive and deploy script

2025-07-26T17:08:56Z

tools: Re-introduce deploy.py script

2025-07-26T17:02:33Z

After the transition to tar archive based deployment it can now be re-introduced with small changes.