SpinetiX firmware lifecycle delivers quarterly security-focused updates with cryptographic verification, automatic rollback, and zero downtime deployment. Every release includes a CVE-detailed security advisory, changelog, and upgrade path. Firmware is the only software running on the player — keeping it current is the single most important maintenance task for your signage fleet.
When Firmware Updates Matter
- Security compliance — quarterly patches are required for ISO 27001, SOC2, and government security standards
- New features — each release adds capabilities (new widget types, protocol support, performance improvements)
- Fleet consistency — running mixed firmware versions across a fleet creates unpredictable behavior
- Support eligibility — SpinetiX support covers the current release and two prior versions
How Firmware Updates Work
Release Cycle
SpinetiX publishes production firmware releases quarterly (March, June, September, December). Each release is tested for 4–6 weeks in beta before production release. Critical security hotfixes are released immediately outside the quarterly cycle.
Cryptographic Verification
Every firmware image is signed with SpinetiX's private key. Before installation, the player verifies the signature using its built-in public key (TPM 2.0 + UEFI Secure Boot chain). If the signature doesn't match — the firmware is rejected. No unsigned, modified, or third-party code can execute on the player.
Deployment Methods
- Arya Cloud — schedule firmware deployment from the dashboard. Players download and install during the next maintenance window
- Elementi — push firmware from the desktop application to selected players or groups
- USB (initial provisioning only) — during first-time setup, firmware can be loaded via USB. After provisioning, USB firmware loading is disabled
Rollback Protection
If the new firmware fails to boot (power failure during update, corrupted download), the player automatically reverts to the previous working firmware. No intervention needed. The player does not "brick" — it always has a fallback image.
Staged Rollouts
Best practice: update 10% of your fleet first. Monitor for 48 hours. If everything works — roll out to the remaining 90%. This reduces risk of fleet-wide issues from a single firmware release. Arya Cloud supports group-based rollout natively.
Key Parameters
| Parameter | Value |
|---|---|
| Release frequency | Quarterly (+ hotfixes as needed) |
| Firmware signing | RSA + TPM 2.0 + UEFI Secure Boot |
| Rollback mechanism | Automatic — dual-image fallback |
| Deployment method | Arya Cloud, Elementi, USB (first-time only) |
| Downtime during update | ~60 seconds reboot |
| Support coverage | Current version + 2 prior releases |
| Security advisories | CVE-detailed, published with each release |
Common Mistakes in Firmware Management
- Never updating. "It works, don't touch it" means accumulating 2+ years of unpatched vulnerabilities. Quarterly updates are designed to be safe and non-disruptive. Apply them.
- Updating the entire fleet at once. Even with SpinetiX's reliability, staged rollouts (10% → wait → 90%) reduce risk. One bad interaction with a specific data source or network config could affect all players simultaneously.
- Skipping release notes. Each release includes known issues, breaking changes (rare), and new features. Read them before deploying. Five minutes of reading prevents hours of debugging.
- No maintenance window. Updates require a ~60-second reboot. Schedule this during off-hours so screens don't briefly go dark during a board meeting. More about DSOS →