summaryrefslogtreecommitdiff
path: root/web
diff options
context:
space:
mode:
authorxengineering <me@xengineering.eu>2025-05-24 11:20:28 +0200
committerxengineering <me@xengineering.eu>2025-05-24 11:20:28 +0200
commitbf8d20fe4d8d3369dd7f63e95f53613dbbfa3603 (patch)
tree539d4610508c1bb3069c5f11ee63977e534b2a68 /web
parent4af0ed8242ab24b2b222a9ebbf417e12f608b756 (diff)
downloadiot-contact-bf8d20fe4d8d3369dd7f63e95f53613dbbfa3603.tar
iot-contact-bf8d20fe4d8d3369dd7f63e95f53613dbbfa3603.tar.zst
iot-contact-bf8d20fe4d8d3369dd7f63e95f53613dbbfa3603.zip
artifacts: Provide `{factory,update}-image.bin`
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.
Diffstat (limited to 'web')
-rw-r--r--web/index.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/web/index.html b/web/index.html
index 1f23096..e5bf005 100644
--- a/web/index.html
+++ b/web/index.html
@@ -18,8 +18,8 @@
<h4>Firmware</h4>
<ul>
- <li><a href="application.signed.bin">application.signed.bin</a></li>
- <li><a href="bootloader.bin">bootloader.bin</a></li>
+ <li><a href="factory-image.bin">factory-image.bin</a></li>
+ <li><a href="update-image.bin">update-image.bin</a></li>
<li><a href="simulation-linux-amd64.exe">simulation-linux-amd64.exe</a></li>
</ul>
</main>