I am going state the obvious.
First, and most importantly, every protocol that talks to the terminals MUST be
versioned or there will be chaos.
Secondly, your server end has to be able to handle multiple protocol versions
because you may not know which device has been upgraded successfully or
Robert: You should be thinking more of CI/CD. The main page at
mender.io says"We have created an infrastructure that allows us to do
automated unit, acceptance and integration tests on each code change we
make to the product. We run tests on both virtual and physical devices."
When some sof
for an upcoming project, one of the longer-term goals is to
establish a secure OTA update system for potentially hundreds or
thousands of remote (internet-connected) devices, which might need to
be updated en masse identically, or updated individually.
i'm currently collecting examples of av
i am currently going over the newest openembedded/yocto project
manuals, and the section "Making Images More Secure" in the dev
manual:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#making-images-more-secure
refers to some really, really, *really* old online material, s
