OpenMV OTA

Secure over-the-air updates for OpenMV cameras: build your application into a signed ROMFS image, publish it, and a camera downloads, verifies, and installs it — falling back to the last release that worked if anything goes wrong.

What a camera downloads is encrypted, under a key minted with the project and baked into your own firmware, so a published release is ciphertext to the update server, to the store it sits in, and to anyone who gets hold of it.

Start with the tutorial — the complete, navigable reference for every command and the update server's HTTP API, in the order you use them: install → project → build → flash → device runtime → update server. The command documentation lives there and only there, so it has one place to be right.

Shipping in the EU? The compliance mapping lays out how this stack lines up with the Cyber Resilience Act and RED 3.3 — what's covered, and the residual threats that aren't — and project new --ota scaffolds the fill-in templates (conformity checklist, EU DoC, disclosure policy, security.txt) into your project's compliance/. Found a vulnerability in this stack itself? See the security policy.

Installation

Not yet published. Once the package lands on PyPI, all tools install together:

pip install openmv-ota

For development, install from a checkout:

pip install -e .

Contributing to the project

Contributions are most welcome. If you are interested in contributing to the project, start by creating a fork of the repository:

• https://github.com/openmv/openmv-ota.git

Clone the forked repository, and add a remote to the main openmv-ota repository:

git clone https://github.com/<username>/openmv-ota.git
git -C openmv-ota remote add upstream https://github.com/openmv/openmv-ota.git

Now the repository is ready for pull requests. To send a pull request, create a new feature branch and push it to origin, and use Github to create the pull request from the forked repository to the upstream openmv/openmv-ota repository. For example:

git checkout -b <some_branch_name>
<commit changes>
git push origin -u <some_branch_name>

Contribution guidelines

Please follow the best practices when sending pull requests upstream. In general, the pull request should:

• Fix one problem. Don't try to tackle multiple issues at once.
• Split the changes into logical groups using git commits.
• Pull request title should be less than 78 characters, and match this pattern:
  • <scope>:<1 space><description><.>
• Commit subject line should be less than 78 characters, and match this pattern:
  • <scope>:<1 space><description><.>