Is there a recommended way to package

[regal belfry]

Lots of similar questions in the history here, but no answers? Is CP really just for blinking LEDs? Can't really be used in a production setting if there's no way to OTA code changes.

[remote cosmos]

The project itself is primarily targeted at beginners for learning coding and electronics. It's not really a primary goal of the project for it to be perfectly ready to be usable in a commercial device deployed in production setting.

If you wish to use it in that environment that are many details that you'd need to take on yourself in order to have a complete solution. Security and anti-tampering perhaps being another.

I have deployed devices built on it in relatively small batches dozens to a few hundred over a few different projects into production environments. We only had ability to update via downloading new .py files to the devices and it was fine for our usage. It really depends on the desired lifetime for the product though for longer deployments you'd want some solution for updating the core itself as well perhaps.

I believe the rp2040 devices may have a utility that allows backup and restore of the full device including where the user code is stored. That might be a helpful thing for deploying updates, but I don't think it works with other families of MCUs.

[regal belfry]

thanks for responding @remote cosmos ! it's sad that this capability is missed though, making a big gap between prototyping and "production" devices. Something as simple as being able to unzip a .zip to replace the user FS, or a simple way to package .py/libs to the app partition image (so dualbank can be used) would've been very helpful. relying on physical access to update over USB is a tough pill to swallow