Browse Prior Art Database

Memory "Keep Alive" Resynchronization

IP.com Disclosure Number: IPCOM000089128D
Original Publication Date: 1977-Sep-01
Included in the Prior Art Database: 2005-Mar-04
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Lewis, JD: AUTHOR [+2]

Abstract

Recirculating memory modules which are of a volatile nature may be "kept alive" by battery power. However, synchronization of the memory with the remainder of the system is lost due to the system nonoperation while the memory recirculates.

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

Page 1 of 1

Memory "Keep Alive" Resynchronization

Recirculating memory modules which are of a volatile nature may be "kept alive" by battery power. However, synchronization of the memory with the remainder of the system is lost due to the system nonoperation while the memory recirculates.

In order to establish synchronization, a special start of memory code is stored in one of the recirculating memory modules. This special code must be unique with respect to data stored in that module. Thus, when the system is powered on, it is known that the special code is within the specific module, which is continuously searched for the code.

When the code is found, a synchronization counter is set and synched so that the memory can be accessed such that blocks of data are then read and written with the proper orientation.

The orientation of the code within the block of data can be checked during normal system operation, thus determining if an error has occurred. If synchronization has been lost, the synchronization counter must be reset.

1