Browse Prior Art Database

Flash algorithms in the flash

IP.com Disclosure Number: IPCOM000014394D
Original Publication Date: 2000-Dec-15
Included in the Prior Art Database: 2003-Jun-19
Document File: 4 page(s) / 110K

Publishing Venue

IBM

Abstract

The flash routines needed to change the code in a flash part must be stored in the part itself because of new technologies such as BIS. Because of changes in Flash parts (new vendors, algorithm changes, this code must be dynamic in nature. Traditionally, if a new flash part is introduced, the customer is forced to use this new flash image. This creates a real problem for corporate customers who want to only test a single flash image across their organization. If they must retest their images every time a new flash part is introduced, a lot of time is spent re-qualifying a new flash level. Modifying the flash utility to merge the flash algorithms dynamically when the system is flashed can solve this problem. The attributes for this design is: Routines will be available on the flash part and on the flash program. In order to conserve space on the flash, only routines needed for the specific flash should be saved on it. A revision control method needs to be used to determine if the routines in the flash part should be updated. A revision control method needs to be used to determine if the algorithm in the flash part or the program should be used to update the flash. The code should be written so that protected mode or real mode OS can use it. BIS, Security code, manufacturing routines (VPD, UUID, machine type/model, serial #,...), and system flash routines (conventional under the OS) need to change the data in the flash all the time. Each of these functions need to create and maintain separate flash algorithms. This is duplicated effort that has to be maintained in several places. Any problems in this area could mean a severe problem for the customer. New flash parts become available after a product ships. This means that our customers have to use a new level flash program, which will support the new part. In their business process, some of our customers have qualified the system at a system at a specific flash level. For them to change their flash level to one that supports the new part, they need to re-qualify the systems. They cannot use the flash programs they have qualified to support systems they receive at a date after the original shipment.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 4

Flash algorithms in the flash

The flash routines needed to change the code in a flash part must be stored in the part itself because of new technologies such as BIS. Because of changes in Flash parts (new vendors, algorithm changes, this code must be dynamic in nature. Traditionally, if a new flash part is introduced, the customer is forced to use this new flash image. This creates a real problem for corporate customers who want to only test a single flash image across their organization. If they must retest their images every time a new flash part is introduced, a lot of time is spent re-qualifying a new flash level. Modifying the flash utility to merge the flash algorithms dynamically when the system is flashed can solve this problem. The attributes for this design is:

Routines will be available on the flash part and on the flash program. In order to conserve space on the flash, only routines needed for the specific flash should be saved on it. A revision control method needs to be used to determine if the routines in the flash part should be updated. A revision control method needs to be used to determine if the algorithm in the flash part or the program should be used to update the flash. The code should be written so that protected mode or real mode OS can use it.

BIS, Security code, manufacturing routines (VPD, UUID, machine type/model, serial #,...), and system flash routines (conventional & under the OS) need to change the data in the flash all the time. Each of these functions need to create and maintain separate flash algorithms. This is duplicated effort that has to be maintained in several places. Any problems in this area could mean a severe problem for the customer.

New flash parts become available after a product ships. This means that our customers have to use a new level flash program, which will support the new part. In their business process, some of our customers h...