iot-contact/fw/app, branch mdns

WIP: fw: app: Implement mDNS proof of concept

2025-08-13T15:43:25Z

TODO: Make this work. WireShark shows that some request / response is exchanged but it is unclear why the request is always canceled after timeout on the Zephyr side.

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.

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.

artifacts: Provide `{factory,update}-image.bin`

2025-05-24T09:20:28Z

This presents only the `factory-image.bin` and `update-image.bin` for MCU firmware. A separate bootloader image is not available. The reason is that the `factory-image.bin` is used during production once (flashing at default boot address) to set up the device. Later only the `update-image.bin` of future versions would be required to remotely update devices.

Remove redundant file name in Meson code

2025-05-24T09:20:22Z

fw: app: Provide confirmed image in build tree

2025-05-24T09:19:06Z

This prepares the upcoming `factory-image.bin` which can be flashed to the default boot address of the microcontroller.

Remove installation step

2025-05-24T09:18:38Z

Using the installation step to copy selected artifacts into one folder was anyway a hack. This commit shows that the complexity can be reduced by adding copy targets. The `build/artifacts` folder contains the selected artifacts, they are always up to date, the user does not have to call the install step separately and the target definitions do not require install-related keyword arguments.

Remove `st-flash`-based build targets

2025-05-24T09:17:46Z

This was used since flashing was complex. Thus the build system should help making it easier. The new approach is more to provide artifacts by the build system which are easy to flash / remote-update. A `factory-image.bin` and `update-image.bin` should be provided.

Revert "fw: app: Enable CONFIG_NO_OPTIMIZATIONS"

2025-05-24T07:44:49Z

This reverts commit 184a41809c66868992c90ce9d420b8e4dc46253b. The change worked well for the `native_sim` board. Nevertheless the application firmware for the real microcontroller was not usable at all anymore. This regression is fixed by simply reverting the commit. Later it could be introduced only for the `native_sim` board with an overlay.

fw: app: Enable CONFIG_NO_OPTIMIZATIONS

2025-05-07T16:14:13Z

This disables compiler optimization and allows easier debugging.

fw: app: http: Refactor settings handler

2025-05-07T16:14:13Z

fw: app: http: Set settings content type to text/json

2025-05-07T16:14:13Z

fw: app: Encode settings with JSON lib

2025-05-07T16:14:05Z

fw: app: http: Add working GET /settings.json

2025-04-16T16:03:40Z

fw: app: http: Add dummy GET /settings.json

2025-04-15T19:34:34Z

fw: app: syslog: Stop supporting CONFIG_LOG_BACKEND_NET_SERVER

2025-04-15T16:41:27Z

From now on the mixed format with IP and port is not supported. The settings system should keep them separate and first only the IP is configurable. Supporting this Kconfig option too is annoying and not necessary.

fw: app: syslog: Put only IP into syslog/target/ip

2025-04-15T16:33:31Z

The old format contained `[]:`. Nevertheless the format should be as strict as possible. Thus only the IP is used in the setting.

fw: app: syslog: Implement commit target

2025-04-15T16:06:32Z

fw: app: syslog: Make target IP configurable

2025-04-15T16:00:03Z

fw: app: Enable settings with NVS backend

2025-04-15T15:43:25Z

fw: app: Fix disabled network hack

2025-04-12T10:21:54Z

This got lost during development but is an important option to compensate the hardware issues present on Nucleo F767ZI.

fw: app: Re-design web page

2025-04-12T10:11:33Z

This enables simple.css also for the device-hosted website and restructures the HTML a bit.

fw: Add flash and erase targets

2025-04-12T09:33:07Z

These targets are added: - fw/erase - fw/app/flash - fw/btl/flash They make it easier to perform a mass-erase, flashing of the bootloader and flashing of the application for development.

Simplify website structure and drop Hugo

2025-04-07T19:36:41Z

A static site generator is currently not really required. A static index.html is currently sufficient.

fw: app: Add image signing to Meson build

2025-04-06T17:11:20Z

This automates signing the application firmware image for the MCUboot bootloader.

fw: sim: Integrate into Meson build

2025-04-06T16:43:28Z

This adds a build for the native_sim board of the application firmware to the default Meson build. The resulting Linux binary is also added to the webpage.

fw: app: Build with Meson

2025-04-06T16:04:25Z

fw: app: Fix native_sim build

2025-04-02T18:43:29Z

To reduce the number of Kconfig options the network hack was added two both boards - the native_sim and nucleo_f767zi one. It reboots the device if the network connection cannot be established since this is a known bug of the nucleo board. Nevertheless it seems that for the native_sim board this command is not defined. Since it is a Linux application this makes somehow sense. This commit introduces the boolean Kconfig option `IOT_CONTACT_NETWORK_HACK` which is only enabled for the nucleo board fixing the native_sim build.

fw: app: update: Finish first HTTP PUT /update

2025-03-30T16:51:33Z

This adds marking the application firmware image in the secondary slot for a permanent update and rebooting the device. It is a known bug that the corresponding HTTP request is never properly closed since the device reboots while handling the request. Nevertheless the current state works and enables remote updates.

fw: app: update: Write uploaded image to flash

2025-03-30T16:51:33Z

This write the received firmware image data to the secondary MCUboot slot. This prepares an update. With the MCUboot shell it can be applied with: mcuboot request_upgrade permanent kernel reboot If the signature is valid the device will permanently update to the new application firmware. Otherwise it will refuse the new image and boot the old one.