| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
This commit removes the path transformations apart from
project-prefixing from the deploy tree / artifact file archive.
This gives the source tree, build tree and deploy tree the same
directory hierarchy.
The advantages are simple implementation and maintenance and a common
structure for all parties (users, developers, producers, ...).
The disadvantage is obviously that the deploy tree structure cannot be
customized on its own. At least for now the approach "there is one right
structure to rule them all" is taken.
|
|
This can be used to order the PCB depending on the manufacturers
software capabilities.
|
|
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.
|
|
simple.css requires to use the `<main>` tag for the main page content.
Otherwise the spacing between page elements is way too large.
|
|
A static site generator is currently not really required. A static
index.html is currently sufficient.
|
