Update the firmware
From SpinetiX Support Wiki
Introduction
The SpinetiX players' firmware has a built-in update mechanism to allow for over-the-air (OTA) updates. This ensures the device can receive the latest features, bug fixes, and security patches without needing physical access.
The simplest way to have the latest firmware version on your player is to update the firmware from Control Center – by default, the SpinetiX update server is used. If for any reasons (such as bandwidth saving, network security), updating from SpinetiX server is not an option, you can always update the firmware from a USB drive plugged into the player or from your own web server (better when having many players).
The advantage of the incremental firmware update, comparing to a installation from scratch, is that the content and configuration settings are preserved on the player; the disadvantages are that:
- it is possible only to update to a newer firmware version, if one is present at the specified source path, but not to downgrade (this is not recommended anyway);
- it takes usually longer than a full reinstall from Recovery Console - which is faster, but the player settings are reset and any user content removed;
- the update from a really old firmware may be done in two steps.
Updating via Control Center can take awhile depending on many factors:
- The difference between the current and the new firmware versions - the greater the gap, the longer the process;
- Network connection speed in case of updating from an external source, like the SpinetiX server;
- The content playing on the device while updating - restore the default content to speed up the process.
Note:Update from SpinetiX server
When updating the firmware from the SpinetiX server, the player must have access to the Internet and be able to reach the SpinetiX update server – we are using Amazon CloudFront as content delivery network (CDN). Otherwise, one of the alternative firmware update methods, detailed further down on this page, can be used instead.
To check if a new firmware version is available and to update to it, follow these steps:
- Connect to the player web interface by entering
http(s)://Player_address/in the browser's address bar, where Player_address can be its IPv4, IPv6, or hostname address.- If you don't see the Control Center home page (like shown on the righ side), click the gear icon
on the top bar menu. - If you are getting redirected to SpinetiX ARYA™, you need to remove it first from ARYA and/or create a new admin user (players with more than one admin user, allow access to Control Center instead of redirecting to ARYA).
- If you don't see the Control Center home page (like shown on the righ side), click the gear icon
- An automatic check is done each time the Control Center home page is accessed – the result is shown within the firmware information box; an exclamation mark is shown when updates are available.
- Click on the box to see more details about the available updates.
- Press the "Update Now" button to proceed with the firmware update.
In case the new firmware is not detected, follow these steps:
- Go to the Control Center → Operations → Firmware Update section.
- Check that the "Update source" is set to the SpinetiX server, accordingly to the player model, as follows:
- DiVA ⇾ http://download.spinetix.com/diva/updates/
- HMP300 ⇾ http://download.spinetix.com/hmp300/updates/
- HMP350 ⇾ http://download.spinetix.com/hmp350/updates/
- HMP400 ⇾ http://download.spinetix.com/hmp400/updates/
- HMP400W ⇾ http://download.spinetix.com/hmp400w/updates/
- iBX410 ⇾ http://download.spinetix.com/ibx410/updates/
- iBX410W ⇾ http://download.spinetix.com/ibx410w/updates/
- iBX440 ⇾ http://download.spinetix.com/ibx440/updates/
- If it is not, then revert it to the default address from the Operations → Reset page.
- Click on the "Check Now" button.
- At the end of the check, the page reports the status, which can be:
- X updates available: Firmware version 4.7.x (build 1.x.xxxxx).
- No updates available: The player is using the latest version.
- Update failed or Fatal Error: See the Troubleshooting section for more details.
- If there are updates available, press the "Update Now" button to proceed with the firmware update.
Notes:- Make sure that the device is not powered off during the firmware update.
- During the firmware update, each library is downloaded, uncompressed, verified for integrity, and then installed. At the end, the player is automatically rebooted.
- You can monitor the firmware update process by pressing the "Show" button.
- The firmware update server URI can be configured from Advanced Applications → Firmware. This might be useful in case of major releases, which are not published right away on the mainstream update channel, but are available at http://download.spinetix.com/hmp-next/updates/ instead.
Update from USB drive
To update the firmware from a USB flash drive, follow these steps:
- Make sure that the USB drive is formatted as FAT32. (NTFS is not supported)
- Download the relevant spinetix-***-updates.zip file(s) for the firmware you want to update to onto your PC. (See also the note below)
- Extract this zip archive file into the root of the USB drive and check that a folder named "updates" was created. The directory structure must not be modified!
- Connect the USB drive to the player and wait a few seconds for the USB device to be recognized.
- Open the Control Center ⇾ Peripherals ⇾ USB on that player and make sure that the USB drive is detected as "Used as Updates".
- Go to the Operations ⇾ Firmware Update page, change the "Update source" to "USB Key" and press the "Check Now".
- You will see a message informing you of which updates are available.
Update from firmware 4.6.x (or older)
For the HMP350, HMP300, and DiVA players running firmware 4.6.x (or older), updating to the latest DSOS must be done as follows:
- Download and use this special firmware update file.
- This will first update the player's firmware to 4.6.5 build 3 to prepare the system for the upgrade to DSOS;
- Then, once that's completed, it will update the firmware to DSOS 4.7.2;
- During this second part, the player will automatically boot in Recovery mode to perform the OS update, and boot afterwards back in normal operating mode using the new firmware, the same configuration as before, and with all user data and previous logs preserved.
- Download and use the relevant spinetix-***-updates.zip file for the latest DSOS version.
Update from your server
To update the firmware from your own web server, follow these steps:
- Download the relevant spinetix-***-updates.zip file(s) to your PC. (See also the note below)
- Extract this zip archive file into a location on your web server, accessible via HTTP (e.g.,
~/public_html/hmp/). - Open Control Center ⇾ Advanced Applications ⇾ Firmware page.
- Under the "Server URI", enter the path to the "updates" folder within (e.g.,
http://myupdateserver/hmp/updates/).- Optionally, you can enable automatic updates and set at what time the player should daily check your local web server for updates.
- Click the "Apply" button to save the modifications.
- Go to the Operations ⇾ Firmware Update page and click the "Check Now" button.
- You will see a message informing you of which updates are available.
Update from firmware 4.6.x (or older)
For the HMP350, HMP300, and DiVA players running firmware 4.6.x (or older), updating to the latest DSOS must be done as follows:
- Download and use this special firmware update file.
- This will first update the player's firmware to 4.6.5 build 3 to prepare the system for the upgrade to DSOS;
- Then, once that's completed, it will update the firmware to DSOS 4.7.2;
- During this second part, the player will automatically boot in Recovery mode to perform the OS update, and boot afterwards back in normal operating mode using the new firmware, the same configuration as before, and with all user data and previous logs preserved.
- Download and use the relevant spinetix-***-updates.zip file for the latest DSOS version.
Automatic updates
It is possible to configure the player to check daily and automatically update the firmware, from SpinetiX server or from your own web server, as follows:
- Open Control Center ⇾ Advanced Applications ⇾ Firmware page.
- Check the "Automatic updates" box.
- Set the hour during the day when the player should check the server for updates.
- Click the "Apply" button to save the modifications.
Troubleshooting
Update failed
The most probable source of this error is that the player could not contact the update server. Check that the network settings are correct and it has Internet connection. Then check out the error message reported in the update log against the ones detailed below:
- failed parsing repository URI
- The updates website is temporarily unavailable or a proxy server / ISP warning page is being returned instead of the SpinetiX site page. Check the Server URI in a browser on a PC running the same network configuration.
- failed retrieving repository path 'repodata/repomd.xml' (could not connect to server)
- There is a problem with the player connection to the Internet. Fix the connection issue and try again.
- failed fetching 'repodata/repomd.xml' (404 Not Found)
- The update server name is most likely misspelled. Reset to the default SpinetiX server and try again.
- failed fetching 'repodata/repomd.xml' (server or proxy hostname lookup failed)
- Make sure that a network gateway and DNS servers are correctly configured and that the player is connected to the network.
- failed fetching 'repodata/repomd.xml' (403 Forbidden)
- Most probably the player is configured to use a proxy for Internet access and the proxy is returning the 403 error; either remove the proxy or change the settings on the proxy server to allow the access to our server.
Otherwise, it could be a transparent proxy or firewall in between that forbids this file - a possible workaround is to use HTTPS instead of HTTP.
- Most probably the player is configured to use a proxy for Internet access and the proxy is returning the 403 error; either remove the proxy or change the settings on the proxy server to allow the access to our server.
- failed fetching '***.rpm' (400 Bad Request or 403 Forbidden)
- This can happen when using a proxy to connect to the Internet. The download of the repomd.xml was successful, but the *.rpm files are blocked by the proxy. Contact your network administrator or use an alternative firmware update method.
- skipping rpm package '***.rpm' of non-compatible arch '***' [...] ERROR: unsatisfied non-file dependencies
- This can happen when updating the HMP350, HMP300, and DiVA players running firmware 4.6.x (or older) to DSOS 4.7.x using either a USB drive plugged into the player or your own web server. The solution is to download and use this update file.
- authentication failed on server
- In this case, contact SpinetiX Support and provide a report from the player.
Fatal error
This is usually the result of a firmware update being stopped during the process, leaving the player in a non-stable state; in this case see how to install the firmware in Recovery mode.