Preparing your result...
Loading...
Press Esc to dismiss this message

Firmware flash compatibility mechanism based on firmware capability metrics (25-Aug-2009)

Thumbnail
IP.com Prior Art Database Disclosure (Source: IPCOM)
Disclosure Number IPCOM000186529D dated 25-Aug-2009
Originally published in Prior Art Database
Disclosed by: IBM
Country: Undisclosed
Disclosure File: 1 pages / 21.4 KB / English (United States)

It is desirable for multiple systems from the same company to have the same install or flash file to update multiple products. This unified update process is convenient for users. There may be situations where a flash file is not compatible with a certain level of hardware and the product would need to abort the upgrade. A system to detect the contents and capabilities of the flash image and prevent and allow flashing is needed to avoid broken devices.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Firmware flash compatibility mechanism based on firmware capability metrics

The device using the previous firmware image can inspect the bits embedded in the firmware encapsulation header and decide based on the capabilities and the current hardware configuration if the firmware is compatible with the current hardware. Redundant flash update mechanism will exist that provides flash file compatibility as well. Redundant flash will be similar in that a message will be sent to the redundant device giving it the capability field. The older devices will ignore the command and allow the redundant flash, whereas the newer devices will require the command to be sent before allowing a flash.

1

(Source: IPCOM)
First page image
(Source: IPCOM)