Howto14r2:Firmware Upgrade V14r1 V14r2: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
(Created page with "== Applies To == This information applies to: * All 14r2 capable innovaphone devices : For a general overview of the upgrade process and a list of supported devices with 14r2, see Howto:Firmware Upgrade == Licenses == If the system is licensed on premise, you'll need to regenerate the license file for V14 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date). In case of cloud or rental model, don't...")
 
No edit summary
Line 1: Line 1:
{{FIXME|reason=This article is still in progress and not finished not yet finished!}}
== Applies To ==
== Applies To ==
This information applies to:
This information applies to:

Revision as of 16:57, 13 March 2024

Tools clipart.png FIXME: This article is still in progress and not finished not yet finished!

Applies To

This information applies to:

  • All 14r2 capable innovaphone devices
For a general overview of the upgrade process and a list of supported devices with 14r2, see Howto:Firmware Upgrade

Licenses

If the system is licensed on premise, you'll need to regenerate the license file for V14 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

In case of cloud or rental model, don't worry about licenses.

Migration Policy

Here is how you upgrade a system to 14r1 from 14r2.


Changes visible to the end customers

Listed here are changes that should be communicated by resellers to end users prior to a 14r2 upgrade, as the change will be visible/audible in the behaviour of the application/device.

Changed Apps

If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

New Apps

New Apps will not be installed automatically by the 14r1 to 14r1 upgrade. The installation description of new 14r2 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

Needed configuration changes

Removed in 14r2

The following software is no longer included in 14r2.

Deprecated in 14r2

The following software is based on legacy technology with no further development and limited maintenance and support. We strongly recommend migrating to our successor products that are fully compatible with 14r2 and myApps technology.

Known Problems

Long Update-duration

When you update, it can be up to 10 minutes before you have access to your app platform again.

Resources Considerations

New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.

Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.

RAM

As a rough rule of thumb, a 14r2 release will consume the same amount of RAM compared to a v14r1 firmware.

Flash Memory

As a rough rule of thumb, a v14r2 release will consume ~ xxxxx TBD MB more flash memory compared to a v14r1 firmware. New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r2. Here is the recommended procedure for upgrade on such devices:

  • save entire configuration
  • reset to factory defaults
  • load saved configuration (this will reorganize the flash memory usage)
  • upgrade to new firmware

When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a Firmwareupdate failed:no space / Update client end in a Error 0x00130001 Major FLASHMAN0 no space event) please open a support case with your current configuration file.