|Publication number||US5790890 A|
|Application number||US 08/608,745|
|Publication date||Aug 4, 1998|
|Filing date||Feb 29, 1996|
|Priority date||Feb 29, 1996|
|Also published as||EP0793169A1|
|Publication number||08608745, 608745, US 5790890 A, US 5790890A, US-A-5790890, US5790890 A, US5790890A|
|Inventors||Russell N. Mirov, Victor Odisho|
|Original Assignee||Sun Microsystems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Non-Patent Citations (2), Referenced by (18), Classifications (16), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of the Invention
The invention relates generally to the field of computer systems. More particularly, this invention relates to an identification interface for obtaining information about an option module.
2. Description of Art Related to the Invention
Many electronic systems (e.g., computers, printers and the like) are designed with a number of circuit boards which are electrically coupled together. Typically, one of these circuit boards (i.e., the "motherboard") includes a microprocessor which executes program instructions necessary for the electronic system to perform its intended functions. In addition, the motherboard further includes a plurality of sockets to receive a number of option modules including, for example, those directed to memory (i.e., "memory" modules). This provides a communicative pathway between memory and the microprocessor. Particular examples of suitable motherboards include those motherboards of desktop computers manufactured by Sun Microsystems, Inc. of Mountain View, Calif.
One well-known type of memory module is commonly referred to as a single in-line memory module ("SIMM"). SIMMs normally contain a number of electronic memory components coupled to a rectangular shaped printed circuit board. Typically, at least one edge of the printed circuit board has a plurality of contacts that can be inserted into a corresponding socket of the motherboard. As a result, the user may upgrade his or her electronic system by merely adding SIMMs or substituting a predetermined type of SIMM for another type that may be mechanically similar but has different characteristics (i.e., faster, made by a different manufacturer, etc.).
Normally, system software running on the electronic system must be coded in a fashion to retrieve certain information about the memory module(s) in order to appropriately configure a memory controller or operating system tables. Likewise, certain information about other types of option modules would be required for configuring the electronic system at power-up. Although using system software for the above-described configuration purposes has been the chosen scheme over the last few years, it is subject to a number of disadvantages.
One disadvantage is that conventional system software imposes a few upgrade restrictions. For example, this software may be able to determine the number of SIMMs implemented and the total memory size, but it is incapable of determining the speed grade of its module and/or memory components. Thus, accidental installation of older versions of a memory module having memory components with substandard access times is not likely to be detected at power-up but rather after experiencing a data storage error.
Another disadvantage is that conventional system software fails to provide reliable electrical inventory and asset controls of the option modules without opening the chassis of the computer. Instead, for current inventory and asset management techniques, the chassis of each electronic system has to be opened and each module subsequently removed from its assigned socket. Thereafter, it is inspected by scanning a bar code or recording a serial number imprinted on the components or circuit board to the option module. This inventory and asset control procedure is costly and inefficient for larger corporations having hundreds or thousands of electronic systems.
Another disadvantage is that a wide range of option modules, for example input/output ("I/O") modules, video modules and other modules without executable code, can be inserted into a socket normally assigned to a different type of option module. Thus, the conventional system software must be coded to determine any type of option module that is accidentally or intentionally connected to one of the sockets and advise the user of any incorrect couplings.
Hence, it would be advantageous to design an interface which would electrically determine the nature and characteristics of the option card or its components without software analysis or physical analysis requiring opening of the chassis and subsequent removal of that option module.
The present invention relates to an identification interface which provides a dedicated communication path between a controller or any "master device" and a plurality of identification storage components. Each identification storage component is uniquely addressed and implemented onto its respective option card that is removably coupled to a motherboard of the computer system. The identification storage component contains a plurality of bit fields which feature characteristic information about its associated option module. Upon the controller requesting information from a selected identification storage component, the selected identification storage component transfers information thereto. System software may use this information for inventory and asset control, hardware upgrades of their products and the like.
The features and advantages of the present invention will become apparent from the following detailed description of the present invention in which:
FIG. 1 is a perspective view of a computer including a number of modules coupled to the motherboard, each module is adapted with an identification storage component.
FIG. 2 is a block diagram illustrating an embodiment of the identification interface in which each of the modules includes an identification storage component which contains information pertaining to the characteristics of the option module and is linked to a controller via a communication signal path.
FIG. 3 is a more detailed block diagram of the information that may be exchanged between the identification storage component and the controller.
FIG. 4 is a flowchart of the operational steps performed by the controller and the identification storage components to take advantage of the identification interface.
The present invention describes an identification interface and its associated communication scheme which collectively enable transmission of data to and from a controller through a dedicated communication bus. Although numerous details of this interface and its protocol are set forth, it is obvious that these specific details are not required to practice the invention. In other instances, well known circuits, devices and the like may not be discussed to avoid obscuring the present invention.
Referring to FIG. 1, a simplified embodiment of a computer utilizing the present invention is shown. The computer 100 comprises a motherboard 110 implemented within a chassis 120 of the computer. The motherboard 110 comprises a processor 111 and a plurality of sockets 112a-112n, each configured to receive a particular type of option module 130a-130n such as a SIMM, video module and the like. Each of the plurality of sockets 112a-112n will accept any type of option module that is mechanically compatible with the socket even though the components of the option module, and hence the module itself, may slightly differ than the intended function, speed, module manufacturer and other characteristics assigned to that socket.
These characteristic differences between the modules 130a-130n are ascertained by software through the implementation of an identification storage component 140a-140n onto each of the option modules 130a-130n. Preferably, each identification storage component 140a-140n is non-volatile, non-alterable memory such as read-only memory "ROM" but may be implemented as flash memory, electrically programmable ROM ("EPROM") and the like. The identification storage components 140a-140n are individually imbedded to contain information about its module as described below in FIG. 3.
As shown in greater detail in FIG. 2, the identification storage components 140a-140n are coupled together via a communication bus 150 dedicated to transfer information between one or more of the identification storage components 140a-140n and a controller 160. The communication bus 150 is preferably a multiple wire bus propagating two or more bits concurrently but may be configured as a single wire bus supporting serial communication in which the identification storage components 140a-140n would support a serial output (e.g., a DC250x-UNW manufactured by Dallas Semiconductor Corporation of Dallas, Tex.). Preferably coupled to the motherboard, the controller 160 may include a micro-controller, a memory controller or any other type of controller device that can communicate with the identification storage components 140a-140n and software.
Referring now to FIG. 3, each of the identification storage components is shown with an ability to store a single 512-bit checksum protected word 200 although any word size may be used. Each word 200 is subdivided into a plurality of encoded fields, including but not limited to a "Type", "Speed", "Capacity", "Revision", "Dev-- Code", "Serial Number", "Man-- ID" and "Man-- Date" fields. It is contemplated that the number and type of encoded fields depends on the amount and nature of information needed by the controller. Likewise, of the above-listed encoded fields, only some of which may be used to provide information to the controller.
The "Type" field 205 may be used to identify the functionality of the module. This field would be queried by software before use because the information contained in this field may assist in the interpretation of other fields and may cause software to perform different initialization functions. As featured in Table 1, the type field 205 may be configured as a 3-bit encoded value to denote the nature of the module to determine whether the option module has been incorrectly coupled to the sockets of the motherboard.
TABLE 1______________________________________Type FieldENCODEDVALUE DESCRIPTION______________________________________000 DRAM Module001 NV RAM Module010 Flash011 I/O Module100 Video Module101-111 Other Module Types (TBA)______________________________________
Another encoded field is the "Speed" field 210 which, in its preferred embodiment, is 3-bits wide. The Speed field 210 provides information about the speed of the module (i.e., data transfer speed of its components) upon being queried before any attempts are made to utilize the module. Examples of possible encoded "speed" values utilized by a SIMM for example are shown in Table 2.
TABLE 2______________________________________Speed FieldENCODEDVALUE DESCRIPTION______________________________________000 SIMM contains memory components operating at a speed of 60 nanoseconds ("ns").001 SIMM contains memory components operating at a speed of 50 ns.010 SIMM contains memory components operating at a speed of 45 ns.011 SIMM contains memory components operating at a speed of 40 ns.100 SIMM contains memory components operating at a speed of 35 ns.101-111 Other Speed Values (TBA)______________________________________
It is contemplated that the remaining encoded values may be used to denote faster or slower speed times for the memory components.
As shown in FIG. 3, the "Capacity" field 215 may be configured to be 4-bits wide. The Capacity field 215 is utilized to describe the storage capacity of the module which, like the Speed field 210, is queried by software before attempts are made to use the module. Examples of possible encoded "capacity" values, for example those utilized by a SIMM, are shown in Table 3 but it is contemplated that other Capacity values may be used depending on the nature of the option module.
TABLE 3______________________________________Capacity FieldENCODEDVALUE DESCRIPTION______________________________________000 SIMM contains 16 megabytes ("MB") of memory.001 SIMM contains 32 MB of memory.010 SIMM contains 64 MB of memory.011 SIMM contains 128 MB of memory.100 SIMM contains 256 MB of memory.101-111 Other Capacity Values______________________________________
Another encoded field of the word 200 may include the "Revision" field 220 which provides a revision level of the module. This enables a user to quickly determine without removal of the module from the motherboard as to whether substitution or additional modules are necessary to appropriately upgrade the computer system. As shown, the Revision field 220 is 3-bits wide but may be any chosen bit width can be used as for any of the encoded fields.
Referring still to FIG. 3, another possible encoded field may be the Device Code ("Dev-- Code") field 225 which is a 4-bit field used to describe the architecture of certain electronic components of its module. This information may useful in a number of situations, such as to increase the effectiveness and efficiency of memory test algorithms. Examples of encoded "Dev-- Code" values are shown in Table
TABLE 4______________________________________Dev.sub.-- Code FieldENCODED ARCHITECTURE OF MEMORYVALUE COMPONENT______________________________________0000 4MB × 40001 8MB × 80010 1MB × 160011 16MB × 40100-1111 Other Architecture Schemes (TBA)______________________________________
Yet another encoded field included in the word 200 may be the "Serial Number" 230 field which could be used to contain a unique serial number/number(s) of the module/components for inventory and asset control. As a result, bar codes or serial numbers need not be attached to or imprinted on the module or components themselves. In addition, the chassis of the computer does not need to be opened. Rather, a software diagnostic program may be used to fetch this information in an appropriate format.
Other encoded fields may include a 3-bit manufacture identification ("Man-- ID") field 235 and a date of manufacture ("Man-- Date") field 240. The Man-- ID field 235 is used to identify the manufacturer of the module. Such information is valuable during electronic component recalls and other situations where identifying the vendor is important. As shown below, Table 5 lists possible encoded "Man-- ID" values identifying various electronic component manufacturers. Additionally, the "Man-- Date" field 240 may be used to ascertain the date, week, month and/or year that module was made. This attribute could also be useful in electronic component recalls and the like.
TABLE 5______________________________________Manufacturer ID FieldENCODEDVALUE DESCRIPTION______________________________________000 NEC001 Micron Technology010 Texas Instruments011 Mitsubishi100-111 Other Manufacturers (TBA)______________________________________
Referring now to FIG. 4, the communication scheme used by the identification interface is shown below. Basically, as mentioned above, the identification storage components, operating as "slave" devices, implemented onto each of the option modules is assigned a serial number to be used as its unique address (Step 300). A controller operating as a "master" device for the identification interface, namely memory controller which can be accessed by firmware, initially resets the communication bus as well as the option modules coupled thereto (Step 305). Next, since all of the identification storage components are electrically coupled to the communication bus, the controller would read the unique serial number of a first identification storage component coupled to the communication bus (Step 310). The serial number is used as its address. This process would continue until all of the identification storage components are identified (Step 315).
Thereafter, the controller issues a read command along with or prior to the address of a particular identification storage component. All of the other identification storage components will be electrically disconnected from the communication bus at this point since the address is unique (Step 320). The controller can now receive data and communicate with that particular identification storage component (Step 325). Thereafter, a check is made whether the user (or controller) desires access to another identification storage component and if so, the above-described process is repeated (Step 330).
To one skilled in the art, alternative embodiments of the invention will be apparent. The preferred embodiment provided is merely for illustrative purposes and should not be taken as limiting the scope of the invention as claimed.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4750136 *||Jan 10, 1986||Jun 7, 1988||American Telephone And Telegraph, At&T Information Systems Inc.||Communication system having automatic circuit board initialization capability|
|US5237674 *||Jun 10, 1991||Aug 17, 1993||Apple Computer, Inc.||Self identifying scheme for memory module including circuitry for identfying accessing speed|
|US5475854 *||Jan 28, 1994||Dec 12, 1995||Vlsi Technology, Inc.||Serial bus I/O system and method for serializing interrupt requests and DMA requests in a computer system|
|US5517646 *||Apr 25, 1994||May 14, 1996||Compaq Computer Corp.||Expansion device configuration system having two configuration modes which uses automatic expansion configuration sequence during first mode and configures the device individually during second mode|
|EP0281999A2 *||Mar 8, 1988||Sep 14, 1988||International Business Machines Corporation||Data processing system with pluggable option card|
|WO1994019750A1 *||Feb 24, 1994||Sep 1, 1994||Microsoft Corporation||System and method for computer interface board identification|
|1||"Book of DS 19XX Touch Memory Standards", Dallas Semiconductor of Dallas, TX, Edition 2.1 (Jun. 1995), pp. 50-55.|
|2||*||Book of DS 19XX Touch Memory Standards , Dallas Semiconductor of Dallas, TX, Edition 2.1 (Jun. 1995), pp. 50 55.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6216186 *||Jun 15, 1998||Apr 10, 2001||Sun Microsystems, Inc.||Modular computer system including compatibility evaluation logic|
|US6243282||Sep 11, 2000||Jun 5, 2001||Micron Technology Inc.||Apparatus for on-board programming of serial EEPROMs|
|US6256217||Apr 13, 2000||Jul 3, 2001||Micron Technology, Inc.||Apparatus for on-board programming of serial EEPROMS|
|US6519172||Jul 3, 2001||Feb 11, 2003||Micron Technology, Inc.||Apparatus for on-board programming of serial EEPROMS|
|US6549027 *||Nov 7, 2000||Apr 15, 2003||Sun Microsystems, Inc.||Apparatus and method for testing for compatibility between circuit boards|
|US6925616||Oct 4, 2002||Aug 2, 2005||Sun Microsystems, Inc.||Method to test power distribution system|
|US7339837 *||May 18, 2004||Mar 4, 2008||Infineon Technologies Ag||Configurable embedded processor|
|US7581040 *||Feb 28, 2007||Aug 25, 2009||Ricoh Company, Ltd.||Interface circuit, system device using the interface circuit, and data interface method, the interface circuit performing data transfer between a host and a peripheral device|
|US7821849||Feb 8, 2008||Oct 26, 2010||Infineon Technologies Ag||Configurable embedded processor|
|US7890698 *||May 12, 2005||Feb 15, 2011||Hitachi, Ltd.||Disk array apparatus including control packages each having a base package and a functional package hierarchically connected to the base package|
|US8270231||Oct 26, 2010||Sep 18, 2012||Infineon Technologies Ag||Configurable embedded processor|
|US20040068700 *||Oct 4, 2002||Apr 8, 2004||Leesa Noujeim||Method to test power distribution system|
|US20050258517 *||May 18, 2004||Nov 24, 2005||Infineon Technologies Na Corp.||Configurable embedded processor|
|US20060253863 *||May 12, 2005||Nov 9, 2006||Shinobu Kakihara||Disk Array apparatus|
|US20070208889 *||Feb 28, 2007||Sep 6, 2007||Tatsuya Irisawa||Interface circuit, system device using the interface circuit, and data interface method|
|US20080195835 *||Feb 8, 2008||Aug 14, 2008||Infineon Technologies Ag||Configurable embedded processor|
|US20110032029 *||Oct 26, 2010||Feb 10, 2011||Infineon Technologies Ag||Configurable embedded processor|
|US20110078374 *||Dec 3, 2010||Mar 31, 2011||Shinobu Kakihara||Disk array apparatus|
|U.S. Classification||710/15, 714/E11.15, 711/E12.089|
|International Classification||G06F9/445, G06F13/14, G06F15/177, G06F11/22, G06F12/06|
|Cooperative Classification||G06F9/4411, G06F11/2289, G06F12/0684, G06F15/177|
|European Classification||G06F11/22Q, G06F9/44A4, G06F15/177, G06F12/06K6|
|Feb 29, 1996||AS||Assignment|
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MIROV, RUSSELL N.;ODISHO, VICTOR;REEL/FRAME:008704/0269
Effective date: 19960228
|Feb 1, 2002||FPAY||Fee payment|
Year of fee payment: 4
|Feb 26, 2002||REMI||Maintenance fee reminder mailed|
|Jan 13, 2006||FPAY||Fee payment|
Year of fee payment: 8
|Jan 6, 2010||FPAY||Fee payment|
Year of fee payment: 12
|Dec 11, 2015||AS||Assignment|
Owner name: ORACLE AMERICA, INC., CALIFORNIA
Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:ORACLE USA, INC.;SUN MICROSYSTEMS, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037270/0121
Effective date: 20100212