V3 Firmware

[jimaek]

We will most likely stop the using the current hardware and upgrade to a more powerful system. Plus we probably need to improve some things in general.
Here is a list of things I believe we need to achieve with v3:

1. New CPU support Rockchip RK3528A. Overclock if possible.
2. 1GB RAM. Ensure code updates and container updates dont crash the device.
3. Multiple containers support. Not just the probe container, but optionally. This means ability to build different firmware versions easily. Default with just GP container and optionally with a different specified containers.
4. Web interface. See Management API #57.
5. Automated container updates. We should not require the user to manually flash a new firmware to upgrade the container.
6. Consider better handling of failing SD Cards. We had plenty of failures. Need to look into ways to protect the cards, or at least notify the user when they fail or are about to fail. Test eMMC as alternative.
7. Automate the release process. The current manual hardcoding of versions is not optimal. Maybe we could even use GitHub Runners to build the firmware to avoid the time consuming manual compilation?
8. Can we use some IoT framework to simplify things like firmware updates? Ideally automated over the air. Otherwise at least via USB

[MartinKolarik]

Not just the probe container, but optionally. This means ability to build different firmware versions easily. Default with just GP container and optionally with a different specified containers.

So the list of offered containers is given by the specific FW build, and then the user has the option to disable/enable those that are included? Or is the FW just an initial config, and a user can add a new container even if not initially available?

[jimaek]

For example the CI would make a release and build 2 firmware binaries, 1 vanilla with just GP and 1 GP+Something else.
The user can decide which to download to flash. This includes myself when I'm flashing the probes, depending on the agreement I would ship different versions of the firmware to different users.
This is mostly intended at supporting partnerships with projects like Ooni. So 1 extra small container doing it's own thing and only for specific batches.