Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Automatic Update of Flash Electrically Erasable Read Only Storage to Driver Level at IPL Time

IP.com Disclosure Number: IPCOM000108373D
Original Publication Date: 1992-May-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 3 page(s) / 112K

Publishing Venue

IBM

Related People

Gliem, LL: AUTHOR

Abstract

There is a very minimum amount of code needed in order to update a read-only storage (ROS) to the latest level. When the card is PORed, ROS tests run. Upon their successful completion, the update code is loaded into RAM. The update code will check for the correct ROS level. If the level is found to be correct, then the IPL is continued and operational code is loaded into RAM. If the level is not correct, then the update code will download the correct code from the system and update the ROS. After the ROS is updated, the card will then be re-IPLed and operational code loaded.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Automatic Update of Flash Electrically Erasable Read Only Storage to Driver Level at IPL Time

       There is a very minimum amount of code needed in order to
update a read-only storage (ROS) to the latest level.  When the card
is PORed, ROS tests run.  Upon their successful completion, the
update code is loaded into RAM.  The update code will check for the
correct ROS level.  If the level is found to be correct, then the IPL
is continued and operational code is loaded into RAM.  If the level
is not correct, then the update code will download the correct code
from the system and update the ROS.  After the ROS is updated, the
card will then be re-IPLed and operational code loaded.

      The following ordered list numbers correspond to the numbers
listed in the figure.
1. POR is applied.
2. ROS tests run.
3. Update utility loaded in RAM.
4. The utility will load the ROS image into RAM and verify that the
part number in the ROS image equals the part number in the update
utilities table.
5. If they do not, then an error describing that the part numbers do
not match will be sent to the system.
6. If they do, the ROS will be erased and written with the new image.
7. If after a specific number of attempts the ROS has not been
updated, then an error stating the failure will be sent to the
system.
8. If the ROS has been updated and is good, then the card is
re-IPLed.
9. Then RAM operational code is loaded.

      Prior to this code, communications IOP cards on the AS/400* had
no way to completely be reburned on the card itself under normal
operating conditions.  This was very costly as most problems in ROS
would require that a CE be sent out to replace the card with a new
level.  The following were problems with the previous update code:
1. Required 3 LIDs on every system.
2. Had no checking to ensure LID and card are compatible.
3. The LIDs were built manually which caused many problems.
4. Ran very late in IPL cycle which made it impossible to update some
cards.
5. Only two system reference codes (SRCs) which allow for no
granularity.

      By use of the Flash Update Utility, now a communications IOP
can be up- or down-leveled to match the driver installed on the
machine and hence...