Deploying¶
This page is being written
The two mechanisms below are decided and will not change. The step-by-step instructions are still to come.
There are two separate operations, and confusing them is the usual source of worry. The runtime is written once. The project is sent as often as you like.
| Runtime | Project package | |
|---|---|---|
| What it is | inoCORE itself, built for that exact board | the screens, logic, tags and bus configuration |
| How often | once per board, then on a version change | every time anything changes |
| Called | Download runtime | Download to panel |
| Over | a serial cable | USB, Wi-Fi or an SD card |
Why a bad deployment cannot brick a panel¶
The package is written into the inactive of two slots. Its checksum is verified, and only then is the active slot switched over. If anything fails along the way, the old package remains in force and the panel keeps running it.
A package built for a different board is refused outright — the board's identity is part of the package.
Steps¶
To be written.
What is checked before it leaves the editor¶
To be written. Covers the validation listed under getting started, and the product limits.