US5640507A - Method and apparatus for identifying read only memory - Google Patents

Method and apparatus for identifying read only memory Download PDF

Info

Publication number
US5640507A
US5640507A US07/844,239 US84423992A US5640507A US 5640507 A US5640507 A US 5640507A US 84423992 A US84423992 A US 84423992A US 5640507 A US5640507 A US 5640507A
Authority
US
United States
Prior art keywords
memory
data
read
reading
memory block
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US07/844,239
Inventor
Ralph Lipe
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to US07/844,239 priority Critical patent/US5640507A/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST. Assignors: LIPE, RALPH
Priority to US08/798,707 priority patent/US6032273A/en
Application granted granted Critical
Publication of US5640507A publication Critical patent/US5640507A/en
Anticipated expiration legal-status Critical
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/06Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication
    • G06F12/0646Configuration or reconfiguration
    • G06F12/0684Configuration or reconfiguration with feedback, e.g. presence or absence of unit detected by addressing, overflow detection

Definitions

  • the subject invention is directed toward a method for identifying read only memory (ROM) and, more particularly, toward a method for locating read only memory without relying upon the memory containing a predetermined signature.
  • ROM read only memory
  • PCs personal computers
  • a central processing device capable of addressing a predetermined range of memory. This predetermined range of memory is typically referred to as the address space of the central processor. Any devices that are to be addressed by the central processor must respond to an address located within the central processor's address space.
  • the address space of a central processor is divided, or partitioned, into two portions.
  • a first portion sometimes referred to as the main memory block, is used to accommodate random access memory (RAM) of the central processor for temporary storage of data and instructions.
  • a second portion sometimes referred to as the adapter region or the upper memory block, is used to accommodate various other memory and hardware devices such as read only memory (ROM), video adapters, disk drives, etc.
  • ROM read only memory
  • a particular device is located in the main memory block if the device is responsive to an address falling within the range of addresses for the main memory block and is located in the upper memory block if the device is responsive to an address falling within the range of addresses for the upper memory block.
  • a portion of the address space of the central processor is occupied if a device is located in that portion of the address space.
  • central processors include conventional microprocessors wherein the microprocessor, and therefore the central processor, has a 1 megabyte address space.
  • 640K of the 1 megabyte range is allocated to the main memory block and is dedicated to random access memory (RAM) for use by the microprocessor for selective storage of data and instructions.
  • the remaining 360K of the 1 megabyte range is allocated to the upper memory block and is used to accommodate other devices to be used with the microprocessor.
  • the central processor For the central processor to map random access memory into unoccupied regions of the upper memory block, the central processor must first identify which regions are not occupied by devices and/or memory. Conventionally, this is performed by searching each memory location of each memory unit of the adapter region for a predetermined data word, referred to as a signature.
  • the data word, or signature identifies the memory unit in which it is found as being occupied by a device or read only memory.
  • the upper memory block of the central processor's address space is often occupied by read only memory devices that have no signature. This prevents conventional central processors from locating these devices and, therefore, may result in a device being mapped to an occupied portion of the upper memory block. Such mapping can cause the computer system to crash or may cause unstable performance. Accordingly, it is desirable to provide a method for identifying occupied memory units of a central processor's address space, without relying upon the presence of a predetermined data word, or signature, in the occupied memory units.
  • the subject invention addresses the foregoing inadequacies of the prior art by providing various methods and apparatus for determining whether a portion of address space of a computer system is occupied by read only memory.
  • the method comprises the step of reading the bytes of the portion of the address space and comparing the values of the bytes read to one another to determine how many different values are read from the portion of the address space and, if the number of different values exceeds a predetermined minimum value, then identifying the portion of the address space as being occupied by read only memory.
  • the additional step of reading the bytes of the portion of the address space at least first and second times to determine whether the same data is read from the bytes both the first and second time is also performed. If the same data is read, then the portion of the address space is identified as being occupied by read only memory.
  • FIG. 1 is an illustrative block diagram of a central processor for use with a presently preferred embodiment of the invention.
  • FIGS. 2A, 2B, and 2C are decision flow diagrams illustrating a presently preferred embodiment of the method that is the subject of the present invention.
  • the present invention is a method and apparatus for identifying unoccupied portions of a central processor's address space, without relying upon a signature stored in occupied portions of the address space. More particularly, the present invention provides method and apparatus for identifying the location of read only memory (ROM) in the address space of a central processor.
  • ROM read only memory
  • a presently preferred embodiment of the subject method "looks" for read only memory. Specifically, the subject method identifies unoccupied memory units as those memory units that do not "look” like read only memory.
  • FIG. 1 A data processing system 100 for use with a presently preferred embodiment of the subject invention is illustrated in FIG. 1.
  • the data processing system 100 includes a central processor 102 coupled for data communication with random access memory 104, read only memory and devices 106, and a user interface 108 over a system bus 110.
  • the central processor 102 may comprise any conventional data processor such as, for example, a microprocessor, and any devices required for interfacing the central processor with the system bus 110.
  • the random access memory 104 may comprise any conventional memory device for selectively storing data and instructions for use by the central processor 102.
  • the random access memory 104 is that memory that occupies the main memory block of the central processor's address space.
  • the read only memory and devices 106 are typically device drivers that are stored in read only memory for interfacing the central processor 102 with a peripheral device.
  • the read only memory and devices 106 occupy the upper memory block of the central data processor 102.
  • FIG. 1 one read only memory and devices 106 is illustrated in FIG. 1, those skilled in the art will appreciate that several read only memory and devices 106 may be coupled to the system bus 110 for occupying one or more memory units of the upper memory block.
  • the read only memory and devices 106 do not occupy the entire upper memory block but may instead be comprised of several devices, each of which occupies a portion of the upper memory block, and the total of which does not occupy all of the upper memory block.
  • the read only memory and devices 106 may comprise a plurality of conventional devices commonly used with a data processing system such as disk drives, modems, etc.
  • the user interface 108 may comprise any device, or combination of devices, for interfacing a user with the system bus 110 and, therefore, with the central processor 102.
  • the interface 108 may comprise a standard keyboard, a computer display, and a mouse.
  • the user interface 108 will also have device driver read only memory located in the upper memory block of the address space of the central processor 102.
  • the system bus 110 comprises a plurality of parallel electrical connectors for transmitting a plurality of parallel digital signals, commonly referred to as data bytes, data words, etc., between the devices connected to the system bus.
  • the system bus 110 may be divided into a data bus portion, an address bus portion, and a control bus portion for transmitting data, address, and control signals, respectively, wherein each of the data, address and control signals includes a plurality of discrete electrical connections referred to herein, and in the art, as bits or data bits.
  • the central processor 102 performs the method illustrated in the decision flow diagram of FIGS. 2A, 2B, and 2C, to identify portions of the upper memory block that are not occupied.
  • the central processor 102 will first identify the random access memory 104, the read only memory and devices 106 and the user interface 108 using standard techniques, step 202.
  • standard techniques for identifying the random access memory 104, the read only memory 106, and the user interface 108 are known in the art.
  • random access memory is typically identified by writing a predetermined data word to a particular address of a memory unit and, thereafter, reading the data stored in the address. If the predetermined data word is read from the particular address, then the memory unit is occupied by random access memory. However, if data other than that written to the address is read back, then the memory unit is not occupied by random access memory.
  • Conventional methods for identifying read only memory comprise searching each address location of a memory unit of address space for a predetermined signature. If the signature is read from any address of the memory unit, then the memory unit of address space is occupied by read only memory. Otherwise, the memory unit is not believed to be occupied by read only memory. Use of the above-noted methods will be sufficient to identify a portion of the random access memory and read only memory located in the address space of the central processor 102. Other conventional methods may be substituted for those discussed above for identifying the random access memory 104, read only memory 106, and the user interface 108.
  • the above-noted methods will not identify read only memory that does not include a signature. Accordingly, another method should be employed to insure that all read only memory has been located.
  • the method of the subject invention relies upon the observation that unoccupied memory space will not always place the same data on the system bus 110 and upon the observation that unoccupied memory space typically places very similar noise signals on the system bus 110. Accordingly, the method of the subject invention attempts to determine, first, whether the same data can be read out of each address location of a memory unit during successive reads and, second, whether the data contained in the address locations of the memory unit is the same for each address location or, whether a minimum number of distinct data bytes are stored in the address locations of the memory unit.
  • each memory unit of the address space that has not been identified as being occupied is examined.
  • each memory unit is selected to be four thousand (4K) memory addresses.
  • a predetermined number of memory locations BYTEP(i), corresponding to that contained in a memory unit, are read into a temporary buffer memory, BYTET(i), step 204.
  • the temporary buffer memory may comprise a portion of the random access memory 104 located in the main memory block of the address space.
  • a number of variables are initialized, step 206. Particularly, a variable, NOB, that records the number of distinct data bytes stored in the memory unit is set equal to zero. Three index variables, i, t, and j are set equal to one. And an array of data bytes, BYTEFOUND(n), is set equal to zero. Thereafter, the first address of the memory unit is read from the temporary buffer memory, BYTET(i), step 208, and inverted, step 210. The purpose of the inversion is to ensure that each data bit of the data bus portion of the system bus 110 is inverted with respect to the data that was previously obtained and stored in the temporary buffer memory.
  • the unidentified memory location is read only memory, containing the data previously stored in the temporary buffer, then it will be capable of driving each data bit of the data portion of the system bus 110 to the opposite state.
  • the inversion of step 210 ensures that this is done.
  • the first byte of data is again read from the first address location of the memory unit and stored in a temporary memory location, step 212.
  • the temporary memory location may also comprise a portion of the random access memory 104.
  • the data stored in the first address space of the temporary buffer memory, BYTET(i) is compared to the data read from the first address location of the memory unit, BYTEP(i), step 214 (FIG. 2B), and if they are not equal, the memory unit is considered unoccupied, step 216, and the method continues with the next unidentified memory unit.
  • steps 208-216 are intended to determine whether a particular address location will provide the same data during successive reads. If the memory unit is occupied by read only memory, then the same data will be returned during successive reads. Therefore, if the same data is not provided during successive reads, then the memory unit is assumed unoccupied. To further ensure that the memory location is supplying the same data during successive reads, the data read first is inverted and placed on the system bus 110 thereby forcing the data read during the subsequent access to positively drive the system bus 110 to the proper state. As an alternative, those skilled in the art will appreciate that each memory location can be examined independently or, that a minimum number of memory locations can be required before the memory unit is assumed unoccupied.
  • the method attempts to determine how many different data bytes are provided by the plurality of address locations in the unit of memory.
  • the data byte previously stored in the temporary buffer TEMP, step 212 is compared to a byte of data previously found, BYTEFOUND(t), step 218.
  • BYTEFOUND(t) an array of BYTEFOUND data bytes 1-n were previously set to zero, step 206.
  • the index variable t is incremented, step 220 and the index variable t compared to the index variable j, step 222.
  • the index variable j is used to record one more than the number of different data bytes found in the unit of memory being examined.
  • index variable t is not greater than or equal to the index variable j
  • the data byte presently being examined i.e., TEMP
  • steps 218-222 are repeated until the data byte TEMP being examined has been compared to each byte of data previously found, i.e., until t is greater than or equal to j.
  • step 218 If the data being examined, TEMP, is the same as a byte of data previously found, BYTEFOUND(t), step 218, then the index variable t is returned to its value of 1, step 224, and the method proceeds to step 230. However, if the byte, TEMP, being examined is not the same as any byte previously found, BYTEFOUND(D, then the number of bytes found, NOB, is incremented by 1, step 226, and the byte being examined TEMP is stored as the new byte found, BYTEFOUND(j). Next, the variable j is incremented by 1 to indicate that a new byte has been found and the index variable t is set equal to 1, step 228.
  • the index variable i is compared to the index variable n to determine whether each byte of data in the predetermined unit has been examined, step 230. If not, then the index variable i is incremented by 1 and the next byte of data from the predetermined unit of memory is examined, step 208.
  • the number of bytes found, NOB is compared to a predetermined minimum number, step 234. Comparison of the number of bytes found, NOB, to the minimum number is used as the second method of determining whether read only memory is located in the memory unit being examined. If the number of different bytes of data found in the unit of memory exceeds 20, then the predetermined unit of memory is considered to be occupied by read only memory, step 236. If, however, the number of different bytes found is less than or equal to 20, then the unit of memory being examined is considered to be unoccupied, step 238. Those skilled in the art will appreciate that although a predetermined minimum number of different bits is selected herein as 20, other numbers may be readily substituted therefor.

Abstract

A method is disclosed for identifying ROM memories. The method first determines whether the same data is read from a predetermined unit of memory during successive reads and, if so, determines whether the read data includes more than a predetermined minimum number of different data bytes. If both tests are true, then the predetermined unit of memory is considered to be occupied by read only memory. If either test fails, then the predetermined unit of memory is considered to be unoccupied.

Description

FIELD OF THE INVENTION
The subject invention is directed toward a method for identifying read only memory (ROM) and, more particularly, toward a method for locating read only memory without relying upon the memory containing a predetermined signature.
BACKGROUND OF THE INVENTION
Conventional computer architecture, and particularly personal computers (PCs), include a central processing device capable of addressing a predetermined range of memory. This predetermined range of memory is typically referred to as the address space of the central processor. Any devices that are to be addressed by the central processor must respond to an address located within the central processor's address space.
Usually, the address space of a central processor is divided, or partitioned, into two portions. A first portion, sometimes referred to as the main memory block, is used to accommodate random access memory (RAM) of the central processor for temporary storage of data and instructions. A second portion, sometimes referred to as the adapter region or the upper memory block, is used to accommodate various other memory and hardware devices such as read only memory (ROM), video adapters, disk drives, etc. As used herein, and in the art, a particular device is located in the main memory block if the device is responsive to an address falling within the range of addresses for the main memory block and is located in the upper memory block if the device is responsive to an address falling within the range of addresses for the upper memory block. Similarly, a portion of the address space of the central processor is occupied if a device is located in that portion of the address space.
Many central processors include conventional microprocessors wherein the microprocessor, and therefore the central processor, has a 1 megabyte address space. In these devices, 640K of the 1 megabyte range is allocated to the main memory block and is dedicated to random access memory (RAM) for use by the microprocessor for selective storage of data and instructions. The remaining 360K of the 1 megabyte range is allocated to the upper memory block and is used to accommodate other devices to be used with the microprocessor.
To gain full advantage of the entire address space of a central processor, it is often desirable to map random access memory, normally located in the main memory block, into the upper memory block. Conventional programs are available for mapping random access memory into the upper memory block of a central processor. Also, newer processors, such as the Intel 386 and 486 processors, include a paging mode that automatically maps a page of random access memory into the upper memory block, wherein a page of memory is simply a predetermined unit of memory referred to herein as a memory unit.
However, for the central processor to map random access memory into unoccupied regions of the upper memory block, the central processor must first identify which regions are not occupied by devices and/or memory. Conventionally, this is performed by searching each memory location of each memory unit of the adapter region for a predetermined data word, referred to as a signature. The data word, or signature, identifies the memory unit in which it is found as being occupied by a device or read only memory. However, the upper memory block of the central processor's address space is often occupied by read only memory devices that have no signature. This prevents conventional central processors from locating these devices and, therefore, may result in a device being mapped to an occupied portion of the upper memory block. Such mapping can cause the computer system to crash or may cause unstable performance. Accordingly, it is desirable to provide a method for identifying occupied memory units of a central processor's address space, without relying upon the presence of a predetermined data word, or signature, in the occupied memory units.
SUMMARY OF THE INVENTION
The subject invention addresses the foregoing inadequacies of the prior art by providing various methods and apparatus for determining whether a portion of address space of a computer system is occupied by read only memory. In one embodiment, the method comprises the step of reading the bytes of the portion of the address space and comparing the values of the bytes read to one another to determine how many different values are read from the portion of the address space and, if the number of different values exceeds a predetermined minimum value, then identifying the portion of the address space as being occupied by read only memory.
In an alternative embodiment of the invention, the additional step of reading the bytes of the portion of the address space at least first and second times to determine whether the same data is read from the bytes both the first and second time is also performed. If the same data is read, then the portion of the address space is identified as being occupied by read only memory.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is an illustrative block diagram of a central processor for use with a presently preferred embodiment of the invention; and
FIGS. 2A, 2B, and 2C are decision flow diagrams illustrating a presently preferred embodiment of the method that is the subject of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
The present invention is a method and apparatus for identifying unoccupied portions of a central processor's address space, without relying upon a signature stored in occupied portions of the address space. More particularly, the present invention provides method and apparatus for identifying the location of read only memory (ROM) in the address space of a central processor. Those skilled in the art will appreciate that devices located in the upper memory block of the address space of a central processor are typically accessed through read only memory devices that respond to addresses in this region. Accordingly, to identify occupied portions of the upper memory block, a presently preferred embodiment of the subject method "looks" for read only memory. Specifically, the subject method identifies unoccupied memory units as those memory units that do not "look" like read only memory.
A data processing system 100 for use with a presently preferred embodiment of the subject invention is illustrated in FIG. 1. Therein, the data processing system 100 includes a central processor 102 coupled for data communication with random access memory 104, read only memory and devices 106, and a user interface 108 over a system bus 110. The central processor 102 may comprise any conventional data processor such as, for example, a microprocessor, and any devices required for interfacing the central processor with the system bus 110. The random access memory 104 may comprise any conventional memory device for selectively storing data and instructions for use by the central processor 102. As used herein, the random access memory 104 is that memory that occupies the main memory block of the central processor's address space.
The read only memory and devices 106 are typically device drivers that are stored in read only memory for interfacing the central processor 102 with a peripheral device. The read only memory and devices 106 occupy the upper memory block of the central data processor 102. Although one read only memory and devices 106 is illustrated in FIG. 1, those skilled in the art will appreciate that several read only memory and devices 106 may be coupled to the system bus 110 for occupying one or more memory units of the upper memory block. Also, those skilled in the art will appreciate that the read only memory and devices 106 do not occupy the entire upper memory block but may instead be comprised of several devices, each of which occupies a portion of the upper memory block, and the total of which does not occupy all of the upper memory block. The read only memory and devices 106 may comprise a plurality of conventional devices commonly used with a data processing system such as disk drives, modems, etc.
The user interface 108 may comprise any device, or combination of devices, for interfacing a user with the system bus 110 and, therefore, with the central processor 102. As an example, the interface 108 may comprise a standard keyboard, a computer display, and a mouse. Those skilled in the art will appreciate that the user interface 108 will also have device driver read only memory located in the upper memory block of the address space of the central processor 102.
The system bus 110 comprises a plurality of parallel electrical connectors for transmitting a plurality of parallel digital signals, commonly referred to as data bytes, data words, etc., between the devices connected to the system bus. As is known in the art, the system bus 110 may be divided into a data bus portion, an address bus portion, and a control bus portion for transmitting data, address, and control signals, respectively, wherein each of the data, address and control signals includes a plurality of discrete electrical connections referred to herein, and in the art, as bits or data bits.
In accordance with a presently preferred embodiment of the invention, the central processor 102 performs the method illustrated in the decision flow diagram of FIGS. 2A, 2B, and 2C, to identify portions of the upper memory block that are not occupied. In accordance with the method illustrated in FIG. 2A, the central processor 102 will first identify the random access memory 104, the read only memory and devices 106 and the user interface 108 using standard techniques, step 202. Several standard techniques for identifying the random access memory 104, the read only memory 106, and the user interface 108 are known in the art. As examples, random access memory is typically identified by writing a predetermined data word to a particular address of a memory unit and, thereafter, reading the data stored in the address. If the predetermined data word is read from the particular address, then the memory unit is occupied by random access memory. However, if data other than that written to the address is read back, then the memory unit is not occupied by random access memory.
Conventional methods for identifying read only memory comprise searching each address location of a memory unit of address space for a predetermined signature. If the signature is read from any address of the memory unit, then the memory unit of address space is occupied by read only memory. Otherwise, the memory unit is not believed to be occupied by read only memory. Use of the above-noted methods will be sufficient to identify a portion of the random access memory and read only memory located in the address space of the central processor 102. Other conventional methods may be substituted for those discussed above for identifying the random access memory 104, read only memory 106, and the user interface 108.
Those skilled in the art will appreciate, however, that the above-noted methods will not identify read only memory that does not include a signature. Accordingly, another method should be employed to insure that all read only memory has been located. The method of the subject invention relies upon the observation that unoccupied memory space will not always place the same data on the system bus 110 and upon the observation that unoccupied memory space typically places very similar noise signals on the system bus 110. Accordingly, the method of the subject invention attempts to determine, first, whether the same data can be read out of each address location of a memory unit during successive reads and, second, whether the data contained in the address locations of the memory unit is the same for each address location or, whether a minimum number of distinct data bytes are stored in the address locations of the memory unit.
To this end, after the conventional methods have been utilized for identifying the random access memory 104, the read only memory and devices 106, and the user interface 108 in the address space of the central processor 106, step 202, each memory unit of the address space that has not been identified as being occupied is examined. In a presently preferred embodiment of the invention, each memory unit is selected to be four thousand (4K) memory addresses. However, those skilled in the art will appreciate that other memory units may be easily substituted therefor. A predetermined number of memory locations BYTEP(i), corresponding to that contained in a memory unit, are read into a temporary buffer memory, BYTET(i), step 204. As is known in the art, the temporary buffer memory may comprise a portion of the random access memory 104 located in the main memory block of the address space.
After the data stored in the memory unit is copied into the temporary buffer memory, a number of variables are initialized, step 206. Particularly, a variable, NOB, that records the number of distinct data bytes stored in the memory unit is set equal to zero. Three index variables, i, t, and j are set equal to one. And an array of data bytes, BYTEFOUND(n), is set equal to zero. Thereafter, the first address of the memory unit is read from the temporary buffer memory, BYTET(i), step 208, and inverted, step 210. The purpose of the inversion is to ensure that each data bit of the data bus portion of the system bus 110 is inverted with respect to the data that was previously obtained and stored in the temporary buffer memory. Accordingly, if the unidentified memory location is read only memory, containing the data previously stored in the temporary buffer, then it will be capable of driving each data bit of the data portion of the system bus 110 to the opposite state. The inversion of step 210 ensures that this is done.
The first byte of data is again read from the first address location of the memory unit and stored in a temporary memory location, step 212. The temporary memory location may also comprise a portion of the random access memory 104. Thereafter, the data stored in the first address space of the temporary buffer memory, BYTET(i), is compared to the data read from the first address location of the memory unit, BYTEP(i), step 214 (FIG. 2B), and if they are not equal, the memory unit is considered unoccupied, step 216, and the method continues with the next unidentified memory unit.
Those skilled in the art will recognize that steps 208-216 are intended to determine whether a particular address location will provide the same data during successive reads. If the memory unit is occupied by read only memory, then the same data will be returned during successive reads. Therefore, if the same data is not provided during successive reads, then the memory unit is assumed unoccupied. To further ensure that the memory location is supplying the same data during successive reads, the data read first is inverted and placed on the system bus 110 thereby forcing the data read during the subsequent access to positively drive the system bus 110 to the proper state. As an alternative, those skilled in the art will appreciate that each memory location can be examined independently or, that a minimum number of memory locations can be required before the memory unit is assumed unoccupied.
If the first address location provides data that is the same as that stored in the associated address location of the temporary buffer memory, then the method attempts to determine how many different data bytes are provided by the plurality of address locations in the unit of memory. To this end, the data byte previously stored in the temporary buffer TEMP, step 212, is compared to a byte of data previously found, BYTEFOUND(t), step 218. As discussed above, an array of BYTEFOUND data bytes 1-n were previously set to zero, step 206. If the data located in the temporary location, TEMP, is not the same as the first byte found, BYTEFOUND(i), step 218, then the index variable t is incremented, step 220 and the index variable t compared to the index variable j, step 222. The index variable j is used to record one more than the number of different data bytes found in the unit of memory being examined. If the index variable t is not greater than or equal to the index variable j, then the data byte presently being examined, i.e., TEMP, must be compared to other bytes previously found, i.e., other BYTEFOUND(t), and steps 218-222 are repeated until the data byte TEMP being examined has been compared to each byte of data previously found, i.e., until t is greater than or equal to j.
If the data being examined, TEMP, is the same as a byte of data previously found, BYTEFOUND(t), step 218, then the index variable t is returned to its value of 1, step 224, and the method proceeds to step 230. However, if the byte, TEMP, being examined is not the same as any byte previously found, BYTEFOUND(D, then the number of bytes found, NOB, is incremented by 1, step 226, and the byte being examined TEMP is stored as the new byte found, BYTEFOUND(j). Next, the variable j is incremented by 1 to indicate that a new byte has been found and the index variable t is set equal to 1, step 228. Thereafter, the index variable i is compared to the index variable n to determine whether each byte of data in the predetermined unit has been examined, step 230. If not, then the index variable i is incremented by 1 and the next byte of data from the predetermined unit of memory is examined, step 208.
If, however, each byte of memory in the memory unit has been examined, then the number of bytes found, NOB, is compared to a predetermined minimum number, step 234. Comparison of the number of bytes found, NOB, to the minimum number is used as the second method of determining whether read only memory is located in the memory unit being examined. If the number of different bytes of data found in the unit of memory exceeds 20, then the predetermined unit of memory is considered to be occupied by read only memory, step 236. If, however, the number of different bytes found is less than or equal to 20, then the unit of memory being examined is considered to be unoccupied, step 238. Those skilled in the art will appreciate that although a predetermined minimum number of different bits is selected herein as 20, other numbers may be readily substituted therefor.
It will be apparent to those skilled in the art that although only several presently preferred embodiments of the invention have been described in detail herein, many modifications and variations may be provided without departing from the true scope and spirit of the invention. Accordingly, the invention is not limited except as by the appended claims.

Claims (5)

I claim:
1. A method for determining whether a group of memory devices in a computer system that each store bytes corresponding to a range of addresses contains a read only memory (ROM) device that stores bytes corresponding to a selected range of addresses, said method comprising the steps of:
(a) reading the stored bytes corresponding to the selected range of addresses a first time and a second time to determine whether the same data is read from the bytes both the first time and the second time and, if so, determining that the group of memory devices contains a read only memory (ROM) device that stores bytes corresponding to the selected range of addresses; and
(b) comparing the values of the bytes read to one another to determine how many different values are read that correspond to the selected range of addresses and, if the number of different values exceeds a predetermined minimum value, determining that the group of memory devices contains a read only memory (ROM) device that stores bytes corresponding to the selected range of addresses, wherein the predetermined minimum value is twenty.
2. An apparatus for identifying the address location of ROM memory coupled to a system bus wherein the system bus includes a data portion and an address portion, the data portion providing data signals that, when address signals placed on the address portion correspond to a valid memory address, correspond to data stored at that memory address, said apparatus comprising:
data processor means responsive to program instructions for performing specified functions, said data processor means including means for generating address signals, said data processor means being coupled to the system bus for transmitting and receiving address and data signals therebetween;
first memory means for storing a plurality of first instructions, said data processor means being responsive to said first plurality of instructions for sequentially placing a plurality of address signals on the address portion of the system bus at least first and second times and determining whether the data provided on the data portion is the same both the first and second time and, if all of the data signals appearing the second time are the same as the corresponding data signals appearing the first time, providing a ROM signal in a first state; and
second memory means for storing a plurality of second instructions, said data processor means being responsive to said plurality of second instructions for placing said plurality of addresses on the address portion of the system bus to determine whether a predetermined number of distinct data values are provided on the data portion and, if the number of distinct data values exceeds the predetermined number and if the ROM signal is in the first state then identifying said portion of said address space as ROM memory, said apparatus further comprising means for inverting the data signals appearing on the data portion of the system bus the first time, said data processor means being constructed to place the inverted data signals on the data portion of the system bus before placing the plurality of addresses on the address portion the second time.
3. A method for determining whether a memory block of a computer system is occupied by read only memory (ROM), said method comprising the step of reading the bytes of the memory block and comparing the values of the bytes read to one another to determine how many different values are read from the memory block and, if the number of different values exceeds a predetermined minimum value, indicating that the memory block is occupied by read only memory (ROM),
wherein the computer system includes a data bus and wherein the step of reading the bytes from the memory block at least first and second times to determine whether the same data read from the bytes both the first and second time comprises the substeps of:
storing the values read from the bytes during the first read so that each stored value corresponds to a byte of data in the portion of the memory block;
inverting the bits of a particular stored value and placing the inverted bit value on the data bus of the computer system; and
reading the bytes of the memory block that correspond to the particular stored value after the inverted bit value is placed on the data bus and comparing the read bytes to the corresponding stored value.
4. A method for determining whether a range of memory addresses in a computer system is unoccupied, the computer system having a data bus, the method comprising the steps of:
for each of at least a portion of the memory addresses in the range:
reading the contents of the memory address a first time,
placing the inverse of the result from reading the contents of the memory address a first time on the data bus, and
after the placing step, reading the contents of the memory address a second time; and
if the steps of reading the contents of the memory address a first time and reading the contents of the memory address a second time produce different results for more than a predetermined maximum number of the memory addresses, indicating that the range of memory is unoccupied.
5. A method for determining whether a memory block of a computer system is occupied by read only memory (ROM), occupied by random access memory (RAM), or unoccupied, the memory block comprised of memory locations, the computer system including a data bus, the method comprising the steps of:
reading the memory block to determine whether the memory block includes a signature identifying the memory block as being occupied by read only memory (ROM), and, if so, indicating that the memory block is occupied by read only memory (ROM);
if the memory block does not include a signature identifying the memory block as being occupied by read only memory (ROM), writing test information to at least a portion of the memory block and reading from the written-to portion of the memory block to determine whether the written-to portion of the memory block contains the test information, and, if so, indicating that the memory block is occupied by random access memory (RAM);
if the written-to portion of the memory block does not contain the test information, for each of at least a portion of the memory locations in the memory block:
reading the contents of the memory location a first time,
placing the inverse of the result from reading the contents of the memory location a first time on the data bus, and
after the placing step, reading the contents of the memory location a second time;
if the steps of reading the contents of the memory location a first time and reading the contents of the memory location a second time produce different results for more than a predetermined maximum number of the memory locations, indicating that the memory block is unoccupied;
if the steps of reading the contents of the memory location a first time and reading the contents of the memory location a second time do not produce different results for more than the predetermined maximum number of the memory locations, reading the information stored in each of at least a portion of the memory locations in the memory block, counting the number of different results produced by reading the information stored in each of at least a portion of the memory locations in the memory block, and, if the number of different results exceeds a predetermined number of different results, indicating that the memory block is unoccupied; and
if the number of different results does not exceed a predetermined number of different results, indicating that the memory block is unoccupied.
US07/844,239 1992-03-02 1992-03-02 Method and apparatus for identifying read only memory Expired - Lifetime US5640507A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US07/844,239 US5640507A (en) 1992-03-02 1992-03-02 Method and apparatus for identifying read only memory
US08/798,707 US6032273A (en) 1992-03-02 1997-02-12 Method and apparatus for identifying read only memory

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US07/844,239 US5640507A (en) 1992-03-02 1992-03-02 Method and apparatus for identifying read only memory

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US08/798,707 Continuation US6032273A (en) 1992-03-02 1997-02-12 Method and apparatus for identifying read only memory

Publications (1)

Publication Number Publication Date
US5640507A true US5640507A (en) 1997-06-17

Family

ID=25292198

Family Applications (2)

Application Number Title Priority Date Filing Date
US07/844,239 Expired - Lifetime US5640507A (en) 1992-03-02 1992-03-02 Method and apparatus for identifying read only memory
US08/798,707 Expired - Lifetime US6032273A (en) 1992-03-02 1997-02-12 Method and apparatus for identifying read only memory

Family Applications After (1)

Application Number Title Priority Date Filing Date
US08/798,707 Expired - Lifetime US6032273A (en) 1992-03-02 1997-02-12 Method and apparatus for identifying read only memory

Country Status (1)

Country Link
US (2) US5640507A (en)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5937423A (en) * 1996-12-26 1999-08-10 Intel Corporation Register interface for flash EEPROM memory arrays
US5946265A (en) * 1995-12-14 1999-08-31 Micron Technology, Inc. Continuous burst EDO memory device
US6032273A (en) * 1992-03-02 2000-02-29 Microsoft Corporation Method and apparatus for identifying read only memory
US6279069B1 (en) 1996-12-26 2001-08-21 Intel Corporation Interface for flash EEPROM memory arrays
US6381180B1 (en) 1994-12-23 2002-04-30 Micron Technology, Inc. Distributed write data drivers for burst access memories
US6401186B1 (en) 1996-07-03 2002-06-04 Micron Technology, Inc. Continuous burst memory which anticipates a next requested start address
US6505282B1 (en) * 1994-11-30 2003-01-07 Intel Corporation Method and apparatus for determining memory types of a multi-type memory subsystem where memory of the different types are accessed using column control signals with different timing characteristics
US6525971B2 (en) 1995-06-30 2003-02-25 Micron Technology, Inc. Distributed write data drivers for burst access memories
US6594780B1 (en) * 1999-10-19 2003-07-15 Inasoft, Inc. Operating system and data protection
US6615325B2 (en) 1996-01-11 2003-09-02 Micron Technology, Inc. Method for switching between modes of operation
US20040153718A1 (en) * 1999-10-19 2004-08-05 Shen Andrew W. Stored memory recovery system
US6804760B2 (en) * 1994-12-23 2004-10-12 Micron Technology, Inc. Method for determining a type of memory present in a system
US20060064540A1 (en) * 1996-07-03 2006-03-23 Micron Technology, Inc. Continuous interleave burst access
US7646654B2 (en) 1994-12-23 2010-01-12 Micron Technology, Inc. Distributed write data drivers for burst access memories
US8501563B2 (en) 2005-07-20 2013-08-06 Micron Technology, Inc. Devices with nanocrystals and methods of formation

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6772272B2 (en) 2002-04-25 2004-08-03 International Business Machines Corporation Apparatus and method for writing information to a designated information storage medium with an allocated data storage device using a specified information recording format
US20090198722A1 (en) * 2008-01-31 2009-08-06 Stephen Michael Hanson System and method for deriving the minimum number of bytes required to represent numeric data with different physical representations

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4455654A (en) * 1981-06-05 1984-06-19 John Fluke Mfg. Co., Inc. Test apparatus for electronic assemblies employing a microprocessor
US4876684A (en) * 1988-02-11 1989-10-24 John Fluke Mfg. Co., Inc. Method of and apparatus for diagnosing failures in read only memory systems and the like
US5091908A (en) * 1990-02-06 1992-02-25 At&T Bell Laboratories Built-in self-test technique for read-only memories
US5237669A (en) * 1991-07-15 1993-08-17 Quarterdeck Office Systems, Inc. Memory management method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5640507A (en) * 1992-03-02 1997-06-17 Microsoft Corporation Method and apparatus for identifying read only memory

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4455654A (en) * 1981-06-05 1984-06-19 John Fluke Mfg. Co., Inc. Test apparatus for electronic assemblies employing a microprocessor
US4455654B1 (en) * 1981-06-05 1991-04-30 Test apparatus for electronic assemblies employing a microprocessor
US4876684A (en) * 1988-02-11 1989-10-24 John Fluke Mfg. Co., Inc. Method of and apparatus for diagnosing failures in read only memory systems and the like
US5091908A (en) * 1990-02-06 1992-02-25 At&T Bell Laboratories Built-in self-test technique for read-only memories
US5237669A (en) * 1991-07-15 1993-08-17 Quarterdeck Office Systems, Inc. Memory management method

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6032273A (en) * 1992-03-02 2000-02-29 Microsoft Corporation Method and apparatus for identifying read only memory
US6505282B1 (en) * 1994-11-30 2003-01-07 Intel Corporation Method and apparatus for determining memory types of a multi-type memory subsystem where memory of the different types are accessed using column control signals with different timing characteristics
US7646654B2 (en) 1994-12-23 2010-01-12 Micron Technology, Inc. Distributed write data drivers for burst access memories
US6804760B2 (en) * 1994-12-23 2004-10-12 Micron Technology, Inc. Method for determining a type of memory present in a system
US6381180B1 (en) 1994-12-23 2002-04-30 Micron Technology, Inc. Distributed write data drivers for burst access memories
US8107304B2 (en) 1994-12-23 2012-01-31 Round Rock Research, Llc Distributed write data drivers for burst access memories
US8213244B2 (en) 1994-12-23 2012-07-03 Round Rock Research, Llc Distributed write data drivers for burst access memories
US7043617B2 (en) 1994-12-23 2006-05-09 Micron Technology, Inc. System supporting multiple memory modes including a burst extended data out mode
US7075857B2 (en) 1994-12-23 2006-07-11 Micron Technology, Inc. Distributed write data drivers for burst access memories
US20050036367A1 (en) * 1994-12-23 2005-02-17 Micron Technology, Inc. Distributed write data drivers for burst access memories
US6728142B2 (en) 1994-12-23 2004-04-27 Micron Technology, Inc. Distributed write data drivers for burst access memories
US20060198180A1 (en) * 1994-12-23 2006-09-07 Micron Technology, Inc. Distributed write data drivers for burst access memories
US7088625B2 (en) 1994-12-23 2006-08-08 Micron Technology, Inc. Distributed write data drivers for burst access memories
US6525971B2 (en) 1995-06-30 2003-02-25 Micron Technology, Inc. Distributed write data drivers for burst access memories
US5946265A (en) * 1995-12-14 1999-08-31 Micron Technology, Inc. Continuous burst EDO memory device
US6615325B2 (en) 1996-01-11 2003-09-02 Micron Technology, Inc. Method for switching between modes of operation
US20070239956A1 (en) * 1996-01-11 2007-10-11 Micron Technology, Inc. Asynchronously-accessible memory devices and access methods
US6601156B2 (en) 1996-07-03 2003-07-29 Micron Technology, Inc. Continuous interleave burst access
US6401186B1 (en) 1996-07-03 2002-06-04 Micron Technology, Inc. Continuous burst memory which anticipates a next requested start address
US20060064540A1 (en) * 1996-07-03 2006-03-23 Micron Technology, Inc. Continuous interleave burst access
US5937423A (en) * 1996-12-26 1999-08-10 Intel Corporation Register interface for flash EEPROM memory arrays
US6279069B1 (en) 1996-12-26 2001-08-21 Intel Corporation Interface for flash EEPROM memory arrays
US7516357B2 (en) 1999-10-19 2009-04-07 Idocrase Investments Llc Stored memory recovery system
US7783923B2 (en) * 1999-10-19 2010-08-24 Shen Andrew W Stored memory recovery system
US7337360B2 (en) 1999-10-19 2008-02-26 Idocrase Investments Llc Stored memory recovery system
US20080098156A1 (en) * 1999-10-19 2008-04-24 Shen Andrew W Operating system and data protection
US20070174681A1 (en) * 1999-10-19 2007-07-26 Idocrase Investments Llc Stored memory recovery system
US20090276662A1 (en) * 1999-10-19 2009-11-05 Shen Andrew W Stored Memory Recovery System
US6594780B1 (en) * 1999-10-19 2003-07-15 Inasoft, Inc. Operating system and data protection
US20070277055A1 (en) * 1999-10-19 2007-11-29 Idocrase Investments Llc Stored memory recovery system
US7818617B2 (en) 1999-10-19 2010-10-19 Shen Andrew W Operating system and data protection
US7844855B2 (en) 1999-10-19 2010-11-30 Shen Andrew W Stored memory recovery system
US20040153718A1 (en) * 1999-10-19 2004-08-05 Shen Andrew W. Stored memory recovery system
US6802029B2 (en) 1999-10-19 2004-10-05 Inasoft, Inc. Operating system and data protection
US8501563B2 (en) 2005-07-20 2013-08-06 Micron Technology, Inc. Devices with nanocrystals and methods of formation
US8921914B2 (en) 2005-07-20 2014-12-30 Micron Technology, Inc. Devices with nanocrystals and methods of formation

Also Published As

Publication number Publication date
US6032273A (en) 2000-02-29

Similar Documents

Publication Publication Date Title
US5640507A (en) Method and apparatus for identifying read only memory
KR940002755B1 (en) One-chip microcomputer
US4158227A (en) Paged memory mapping with elimination of recurrent decoding
US5966727A (en) Combination flash memory and dram memory board interleave-bypass memory access method, and memory access device incorporating both the same
US6021476A (en) Data processing apparatus and method for controlling access to a memory having a plurality of memory locations for storing data values
US8356210B2 (en) Programming in a simultaneous multi-threaded processor environment including permitting apparently exclusive access to multiple threads and disabling processor features during thread testing
EP0106600B1 (en) Circuit for checking storage protection
RU99124789A (en) MEMORY ACCESS PROTECTION
US4787030A (en) Data processing apparatus with fixed address space
EP0175620B1 (en) Access verification arrangement for digital data processing system which has demand-paged memory
WO1998014878A1 (en) A method of obtaining a buffer of contiguous memory and building a page table
US6842790B2 (en) Host computer virtual memory within a network interface adapter
EP0471532A2 (en) Method for determining the size of a memory
EP0509994B1 (en) Centralized reference and change table for a multiprocessor virtual memory system
US7310698B2 (en) Method and apparatus for extending memory addressing
US5027313A (en) Apparatus for determining maximum usable memory size
US5280599A (en) Computer system with memory expansion function and expansion memory setting method
EP0403124A2 (en) Overlay swapping
JP3202700B2 (en) Signal processing device
US5926620A (en) Content addressable bit replacement memory
EP0175398A2 (en) Data processing system comprising a memory access controller which is provided for combining descriptor bits of different descriptors associated with virtual addresses
US5386530A (en) Address translation device capable of obtaining a real address from a virtual address in a shorter time
US6269459B1 (en) Error reporting mechanism for an AGP chipset driver using a registry
EP0803820A2 (en) An integrated digital processing device and method for examining the operation thereof
CA1288522C (en) Method and apparatus for determining available memory size

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNOR:LIPE, RALPH;REEL/FRAME:006033/0727

Effective date: 19920124

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001

Effective date: 20141014