System signaling schemes for processor and memory module

[0002] This application claims priority under 35 USC §119(e)(1) of Pawate et al. “Processor and Memory Module”, provisional application Ser. No. 60/043,663, filed on Apr. 11, 1997 and Heape et al. “System Signaling Schemes for Processor and Memory Module”, provisional application Ser. No. 60/049,956, filed on Jun. 17, 1997.

[0003] 1. Technical Field

[0004] This invention relates in general to computers and, more particularly, to computer memory modules.

[0005] 2. Description of the Related Art

[0006] Over the last few years, the operation of the personal computer has become more oriented toward multimedia operation. Multimedia computers typically include a mass storage device with a replaceable medium, such as a CD-ROM (compact disk read only memory) or a DVD (digital versatile disk), a sound card with a FM synthesis or wave table generation processor, real-time video capabilities and three dimensional graphics. Other multimedia capabilities, such as speech synthesis and voice recognition, are becoming more mainstream as the power of the computers increase.

[0007] Multimedia capabilities such as sound, video, fax, modem, compression and decompression, however, are resource intensive. Some features are bandwidth limited, meaning that the features cannot be expanded without increasing the bandwidth of the system buses. In a typical IBM-compatible PC, the ISA (industry standard architecture) bus runs at eight megahertz (16 bits) while the PCI (Peripheral Connect Interface) bus runs at thirty-three megahertz (32 bits). Other features are processor limited. In a multitasking computer system, the main processor can be responsible for a number of activities. Therefore, multimedia features which require a large number of processor instruction cycles can slow down the system or not execute properly. Still other multimedia features are memory limited. These features require a large amount of memory in order to execute. Large memories lead to increased system cost.

[0008] For example, modem features like V.34bis are primarily processor limited. Wavetable synthesis requires large amounts of memory and is memory-limited. Decompression feature like MPEG2 is compute-limited as well as bandwidth limited. With increasing clock-speeds of Intel CPUs, some of these can be executed on the host CPU. But this loads the host CPU with fewer MIPS (million instructions per second) available for the user application. Increased clock speeds also lead to increased power consumption and reduced battery life.

[0009] One popular approach is to provide these functions in a desktop computer using multiple add-in ISA or local bus cards. These add-in cards are host dependent and cannot be used on multiple platforms. For example, an ISA card cannot work on a Sun workstation or a Macintosh. Notebook computers, palmtops and PDAs (personal digital assistants) have no space for such ISA cards. And they all suffer from the classic Von Neumann bottleneck—the CPU-Memory bandwidth limitation.

[0010] Processor technology has focused on improving raw processing speed. As an example, the instruction cycle time of a recent digital signal processor design in the TMS320 family, by Texas Instruments Incorporated of Dallas, Texas, is 5 ns (nanoseconds), as compared to the cycle time of 200 ns in the first generation. As long as the computations are on-chip, these devices provide adequate throughput. But several applications in speech, signal and image processing are memory intensive and the gain in raw processing speed is lost when the processor has to fetch and process data from slower off-chip memories. The combined effect of decreasing cycle time of processors and increasing density of memory devices is further aggravating the CPU-to-memory bandwidth—a paramount issue in computer system design.

[0011] As computers evolve from desktop size to laptop, notebook and palmtop sizes, form factor and power consumption become critical. Laptops are expected to have the capability of a desktop as users demand more functionality.

[0012] Multiprocessing promises great potential for increasing the throughput of systems as the limits of decreasing the cycle time of uniprocessor systems are approached. But multiprocessing has not yet proliferated, primarily because of the “processor-driven” approaches and the difficulty in designing systems, developing communication protocols, and designing software support routines. Application partitioning is a major problem because it requires a detailed understanding of the application that is being accelerated. Software development methodologies and partitioning tools are still in their infancy. In addition, there is no standard way of connecting two or more processors.

[0013] Accordingly, a need has arisen for a method and apparatus for providing flexible, compatible processing for multimedia and other resource intensive features.

[0014] In accordance with one embodiment of the present invention, the present invention provides a memory module comprising a semiconductor memory and one or more processors coupled to the semiconductor memory on an integrated module. Circuitry on the integrated module provides communications between system processing circuitry and the processor, such that said system processing circuitry can access the semiconductor memory as main memory and can instruct the processor to transform data and store transformed data in said semiconductor memory for access by the system processing circuitry.

[0015] The invention provides significant advantages over the prior art. Adding a digital signal processor to a computer system to enable enhanced functions is as easy as expanding the memory of a MPU (main processing unit). The memory module can use a form factor of the type standardized by organizations like IEEE, JEDEC, and so on, such as a SIMM (single in-line memory module) or DIMM (dual in-line memory module) form factor.

[0016] Different applications may be downloaded by the MPU to the memory module for local execution. The memory module therefore supports multiple functionality, i.e., downloadable, multiple functions under software control of the MPU.

[0017] The DSP/memory module offers the highest possible bandwidth between the MPU and coprocessor at any given time and technology. The DSP/memory module is both bus-independent, and host-independent, for use with PCs (personal computers), PDAs (personal digital assistants), workstations and other computer systems.

[0018] The DSP/memory module reduces system cost by sharing system memory over a number of multimedia functions.

[0019] The module provides a framework for easily scaling up the processing power of a computer system; an existing single processor system can be transformed into a scaleable, multiprocessing system simply by adding a memory module

[0020] Users do not have to change their product platforms in order to get/offer new, value-added functions. Adding the DSP/memory module and software can allow users to increase the capability of their computers.

[0021] In accordance with other embodiments of the present invention, implementation of the memory module with the interrupt request, IREQ, and WAIT signals are described further in this application. Six options are presented in accordance with other embodiments describing how to implement these signals (including their timing and relation to the host memory controller).

[0022] For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0023] FIG. 1 illustrates a prior art computer architecture;

[0024] FIG. 2 illustrates a DSP/memory module;

[0025] FIG. 3 illustrates the organization of memory space between the system MPU and the DSP on the DSP/memory module;

[0026] FIGS. 4a, 4b, 4cand 4dillustrate definitions of control words used to control the operation of the DSP/memory module;

[0027] FIG. 5 illustrates a flow chart describing the operation of a hunting protocol for determining whether a DSP/memory module is located in the main memory of a computer;

[0028] FIG. 6 illustrates a memory map in standard mode;

[0029] FIG. 7 illustrates a memory map in smart-local mode;

[0030] FIG. 8 illustrate a memory map in smart-shared mode;

[0031] FIG. 9 illustrates a first embodiment of the DSP/memory module;

[0032] FIG. 10 illustrates a second embodiment of the DSP/memory module;

[0033] FIG. 11 illustrates a third embodiment of the DSP/memory module;

[0034] FIG. 12 illustrates a DSP/memory module in a computer system using an analog front end directly connected to the module;

[0035] FIG. 13 illustrates a DS/memory module in a computer system using an analog front end coupled to the memory module via a local bus card;

[0036] FIG. 14 illustrates the memory module(s) to host controller block diagram as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 1”;

[0037] FIG. 15 illustrates the timing for the WAIT signal for FPM or EDO DRAM as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 1”;

[0038] FIG. 16 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 1, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 1”;

[0039] FIG. 17 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 2, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 1”;

[0040] FIG. 18 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 3, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 1”;

[0041] FIG. 19 illustrates the memory module(s) to host controller block diagram as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 2”;

[0042] FIG. 20 illustrates the timing for the WAIT signal for FPM or EDO DRAM as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 2”;

[0043] FIG. 21 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 1, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 2”;

[0044] FIG. 22 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 2, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 2”;

[0045] FIG. 23 illustrates the timing for the WAIT signal for DDR-S/S DRAM, eligibility option 3, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 2”;

[0046] FIG. 24 illustrates the memory module(s) to host controller block diagram as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 3”;

[0047] FIG. 25 illustrates the timing for the WAIT and IREQ signals for FPM or EDO DRAM as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 3”;

[0048] FIG. 26 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 1, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 3”;

[0049] FIG. 27 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 2, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 3”;

[0050] FIG. 28 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 3, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 3”;

[0051] FIG. 29 illustrates the memory module(s) to host controller block diagram as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 4”;

[0052] FIG. 30 illustrates the memory module(s) to host controller block diagram as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 5”;

[0053] FIG. 31 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 1, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 5”;

[0054] FIG. 32 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 2, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 5”;

[0055] FIG. 33 illustrates the timing for the WAIT and IREQ signals for DDR-S/S DRAM, eligibility option 3, as discussed in “IMPLEMENTATION OF IREQ AND WAIT SIGNALS: OPTION 5”; and

[0056] FIG. 34 illustrates a possible solution for module-to-module communication via a 2 wire bus.

[0057] The present invention is best understood in relation to FIGS. 1-12 of the drawings, like numerals being used for like elements of the various drawings.

[0058] FIG. 1 illustrates a prior art computer system 10. A main processor (hereinafter MPU) 12 communicates with other electronic devices over one or more paths. In FIG. 1, the MPU 12 is coupled to a memory management unit (MMU) 14, a PCI bridge 16, an AT interface unit 18 and a PCMCIA (Personal Computer Memory Card International Association) b ridge 20. The MMU 14 couples the MPU 12 to main memory 22 via a memory bus 24, which is typically a vendor specified bus. The main memory 22 is typically formed of a plurality of memory modules 26 packaged in a standard form factor. The most popular form factor is currently the SIMM module, although DIMM modules are gaining in popularity.

[0059] The PCI Bridge 16 couples the MPU 12 to a PCI local bus 28. The PCI local bus provides slots for one or more peripheral cards 30. Because the PCI bus is faster than the AT bus, it is generally used for higher speed peripherals such as the video/graphics card.

[0060] The AT interface unit 18 couples the MPU 12 with the AT bus 32 (also known as the ISA—industry standard architecture—bus). The AT bus 32 can receive one or more peripheral cards 34. The PCMCIA bridge 20 is coupled to the AT interface unit and provides a PCMCIA bus 36 to support externally replaceable peripherals 38 (also known under the name “PC Cards”) which are commonly used in notebook computers.

[0061] A card having one or more processors can be added to an existing PC platform via the ISA bus 32 or, more recently, the PCI bus 28. The ISA bus 32 was developed several years ago and many popular peripheral cards subscribe to this standard. However, the bandwidth between the MPU and a processor on a ISA card is limited to 8 MHz*16 bits per second. There are several sound applications today that cannot run due to this bandwidth limitation. Later, the PCI bus was proposed as a standard bus; its bandwidth is limited to 33 MHz*32 bits per second. In either case, the technology has developed faster than the bus technology.

[0062] In order to reduce bus traffic somewhat, MMX technology is currently available. While MMX technology allows the MPU to perform some multimedia functions through an enhanced instruction set, it has significant disadvantages. Data must be moved from main memory to the MPU 12 for processing. This results in significant bus traffic, loads the MPU 12 and demands faster and faster processor speeds. For example, it is estimated that MPEG2 video and audio decoding in real-time at a rate of thirty frames per second requires a 225 MHz Pentium processor. In order to provide the MMX instructions, the MPU 12 must switch between floating point mode and fixed point mode. There is a significant overhead in switching between modes and switching can be frequent in multitasking systems where both floating point applications (such as a spreadsheet) and fixed point applications are being used.

[0063] FIG. 2 illustrates a DSP/memory module which provides a solution to many of the problems associated with the architecture shown in FIG. 1, using a concept referred to herein as “Basava” technology. The DSP/memory module 40 includes one or more memory circuits 42 and DSP circuitry 44 disposed on a substrate 46. A plurality of contacts 48 are formed on substrate 46 to electrically connect the DSP/memory module 40 to the system board which houses the MPU 12. In the preferred embodiment, the DSP/memory module 40 is inserted into a standard memory slot, such as a SIMM slot or a DIMM slot.

[0064] In operation, the DSP/memory module 40 is placed onto the system board of the computer in a slot connected to the memory bus 24. The DSP functions of the DSP/memory module 40 are initially transparent to the MPU 12; the DSP/memory module 40 operates as a standard memory module 26 until the DSP features are enabled. Once enabled (discussed in greater detail hereinbelow), the MPU 12 can control the DSP circuitry 44 through a plurality of control registers and pass data to and from the DSP circuitry 44 using some or all of the memory circuits 42.

[0065] Many applications in digital signal processing, speech, and image processing are structured and lend themselves to be partitioned and concurrently executed. With adequate on-chip memory, several self-contained tasks can be executed in parallel. Typically, there are small routines or operations that are applied to a very large set of data. For example, in speech or image recognition, the unknown input vector is compared against several stored reference vectors. Typically, a Euclidean distance is used as a similarity measure between the unknown vector and the known reference vector. This calculation involves fetching the reference vectors from memory to the MPU 12 where the unknown input vector is kept, performing the Euclidean distance calculation, and writing the computed result back to memory. Moving the large number of reference vectors to the MPU 12 increases the traffic of data on the bus. However, using the DSP/memory module 40, the input vector can be moved to the memory storing the reference vectors, previously loaded on the DSP/memory module 40, performing the Euclidean calculation locally, and storing the results locally. Now, the MPU 12 need only fetch the results from the DSP/memory module 40. This leads to several benefits. First, the data traffic on the buses is reduced since the MPU 12 must read only the compared results. Second, the MPU is free to perform other tasks while the DSP/memory module 40 performs the cycle intensive Euclidean computation. Third, due to reduced bus traffic, power consumption is reduced leading to increased battery life—an important feature for portable system users.

[0066] With the density of DRAM increasing, memory intensive applications, such as a voice dialing application, which typically requires a megabit of memory, can easily be supported on the DSP/memory module 40.

[0067] FIG. 3 illustrates a diagram showing the interaction between the MPU 12, memory circuits 42 and the DSP circuitry 44. The main memory of the computer system is generally divided into “banks,” with each bank 50 comprising one or more memory modules. In the computer system of FIG. 3, four banks are shown, BANK0, BANK1, BANK2 AND BANK3. BANK3 contains the DSP/memory module 40 (although any bank could contain the module); in another instance, all the banks 50 may contain a DSP/memory module 40.

[0068] Each bank 50 has an associated address space, through which the MPU 12 addresses the memory (via the MMU 14). For a Pentium type processor, the address range is from 0 to 4 gigabytes. Typically, the actual memory addresses are in a much smaller range, for example, between 0 and 64 megabytes. Within the address space associated with BANK3, a certain range of addresses are allocated for control registers 52 associated with the DSP circuitry 44, used when the DSP circuitry is enabled. These control registers are described in further detail hereinbelow. Further, a portion of the memory can be designated as shared memory 54, i.e., for use with both the MPU 12 and the DSP 56 (multiple DSPs could also be used on a single module). DSP 56 is typically a digital signal processor, but could alternatively be any type of programmable processor. In addition to the main memory, the DSP circuitry 44 also has a local memory 58 (preferably a static random access memory) for temporary storage of information.

[0069] When the DSP circuitry 44 is not enabled (“standard mode”), the DSP/memory module 40 operates as a standard memory module. In the diagram of FIG. 3, the MPU 12 would have sole access to the entire memory address space of BANK3, just as it would any other memory bank 50. When the DSP/memory module 40 has its DSP circuitry 44 enabled (“smart mode”), the MPU 12 can write to the control registers 52 to control the DSP functions and can transfer data to and from the DSP circuitry 44 via the shared memory.

[0070] In a third mode, configuration mode, the MPU 12 can access the control registers 52 and local memory 54 present on the DSP/memory module 40, via the Index and Data registers that are in the memory space of the DSP/memory module 40. On powerup, these control registers 52 are located at the base of the address space of the DSP/memory module 40. The intent of the configuration mode is two fold. First, configuration mode enables the MPU 12 to read specific information regarding the DSP/memory module 40, referred to as the Module Information Structure (MIS). MIS contains information regarding the size of memory available on the DSP/memory module 40, size of the local memories, and the type of processor(s) available. The MPU 12 accesses this MIS and stores this information in its registry for future reference and actions. The MIS is typically stored in slow memories like ROM and the MPU 12 must poll the status bits in the DSPSR register before reading from the data register. The specific bits are explained further below. Second, the configuration mode is used to relocate the base address of the control registers 52 and the shared memory 54 to a desired address location within the boundary of the module. Note that the default base address is zero, i.e., the control registers are located at the starting address of the bank 50.

[0071] The following provides a preferred procedure for switching between modes. To switch from standard mode to configuration mode, the MPU 12 writes a signature pattern, n times, in succession, to the signature register (SIGR) located in its address space. This signature pattern is written a certain number of times, without doing any other accesses. For example, a signature pattern, “A320”, could be written four times in succession to the SIGR register to enter configuration mode.

[0072] To switch from configuration mode to standard mode, the MPU 12 writes to the DSPLOC register the “relocation address” to which it wishes to relocate the control register's base address to be relocated. If it does not wish to relocate the control registers, a “0” is written to the DSPLOC registers. After writing the relocation address, the MPU 12 writes the signature pattern to the SIGR/Index register.

[0073] To switch from standard mode to smart mode, the MPU 12 writes a signature pattern (n+1) times, in succession, to the signature register (SIGR) located in its address space. This signature pattern is written a certain number of times, without doing any other accesses. For example, the signature pattern, “A320”, is written five times in succession to the SIGR register.

[0074] If for any reason, the computer is reset, or shut-down, the driver in the OS will switch the module back to the standard mode before allowing the computer to shutdown. Alternatively, on power-up, the boot sequence might always force the module to be in standard mode.

[0075] Control of the module's operating mode is accomplished via the signature, control, status, and communication registers defined in the module controller, shown in connection with FIGS. 9-11. Some of these are accessible only by the MPU 12, some only by the DSP 56, and some by both MPU 12 and DSP 56. Some of these registers are mapped in the memory space of the MPU 12 and I/O space of the DSP 56. Note that for both MPU 12 and DSP, some of these registers are “Reserved” as marked. In the standard mode, only the Signature Register (SIGR) is accessible to the MPU 12. Other registers exist only when the DSP/memory module 40 is in the configuration or smart mode of operation.

[0076] Initially, these registers are mapped into the first 32 bytes of the associated bank 50.

[0077] SIGR Register

[0078] The Signature (SIGR) register is defined only in the standard mode. The DSP/memory module 40 monitors all MPU writes to this location for valid signature pattern (while it writes to the standard memory typically available on the module). When the module operates in the configuration mode, this register is redefined as the Index Register. The module still monitors for a write of a signature pattern (for example, “A320”) and if this occurs after a write to the DSPLOC register, then the module is switched back to the Standard mode. During the smart mode, this register is redefined as the Index Register.

[0079] Index Register

[0080] The Index Register which is available in the configuration and smart modes enables access to other registers like DSPCR, etc. The MPU 12 must write the address of the control registers that it wishes to access to this register.

[0081] Data Register

[0082] The Data register is a read/write register available in the Configuration and Smart modes. The MPU 12 writes the data to this register which is transferred by the module to the appropriate control register 52 whose address has been previously setup in the Index register.

[0083] The Index and Data registers have been defined to facilitate ease of hardware circuit implementation; since meeting the tight memory-access timings in Fast-Page mode are difficult to meet. Ideally all control registers 52 could be directly accessible by the host MPU 12.

[0084] DSPLOC Register

[0085] The DSPLOC is a 16-bit R/W register that allows the MPU 12 to relocate the base of the control registers 52 to another address in the MPU's address space, but still within the boundary of the module's address limits.

[0086] DSP Control Register (DSPCR)

[0087] The DSPCR, shown in FIG. 4a, is a 16 bit R/W register used to control DSP operation, interrupt of the MPU, memory bus arbitration, standard-smart mode switching, and level interrupt clear. Definition of individual bits are as follows.

[0088] Note that with the DSP specific bits, though some protections have been included, the operation is not fully automated. Thus, the user must program DSPCR while taking into consideration DSP operation. The DSPCR bits are explained in the following Table IV.

[0089] DSP Status Register

[0090] The DSPSR, shown in FIG. 4b, is a read-only, 16-bit register. It is used to monitor DSP operation, module interrupt of the MPU 12, and memory/DSP bus arbitration. Definition of individual bits are as follows in Table V:

[0091] DSP Data Transmit Register

[0092] DSPTXD is a 16 bit register used by the DSP to communicate to the host MPU 12. The MPU 12 has only read access to this register and any MPU write to this register is ignored. The DSP has only write access to this register and any DSP read from this register causes invalid data to be read. A DSP write to this register generates a TXFULL interrupt to the MPU 12 if enabled. Similarly, an MPU 12 read from this register generates a TXEMPTY interrupt to the DSP if enabled.

[0093] DSP Data Receive Register

[0094] DSPRXD is a 16 bit register used by the MPU 12 to communicate to the DSP. The MPU 12 has only write access to this register and any MPU 12 read from this register causes invalid data to be read. The DSP has only read access to this register and any DSP write to this register is ignored. A DSP read from this register generates a RXEMPTY interrupt to the MPU 12 enabled. Similarly a MPU 12 write to this register generates a RXFULL interrupt to the DSP if enabled.

[0095] MPU 12 Status Register

[0096] The PCSR, shown in FIG. 4c, is a 16 bit read-only register to the DSP located at I/O address 0052h when the DSP/memory module 40 is in smart mode. It is used by the DSP space to determine status of the host communication registers. Its bits are defined in Table VI.

[0097] Bit I/O Register (Reserved)

[0098] The BIOR is a 16 bit read/write||read-only register to the DSP located at I/O address 0053h when the DSP/memory module 40 is in Smart Mode. BIOR receives information from an analog front end (described in connection with FIG. 12) so that the DSP/memory module 40 can receive information through external signals, such as a line-in/out, microphone input, telephone line or cellular connection.

[0099] System Configuration Register

[0100] The SYSCFG register, shown in FIG. 4d, is a 16 bit read/write register to the DSP located at I/O address 0054h when the DSP/memory module 40 is in Smart Mode. It is used by the DSP to control the frequency of the clock input to the DSP when CLKMD1=0, bus arbitration, Global Data paging, external memory configuration and paging.

[0101] If the appropriate driver is installed before the DSP/memory module 40 is plugged in, when the system power is cycled, the driver is invoked, and it automatically searches the entire-space to identify where the DSP/memory module 40 located. The protocol and procedure for identifying where the DSP/memory module 40 is located is referred to as the hunting protocol. The MPU 12, under control of the driver, locates the DSP/memory module 40 as shown in FIG. 5.

[0102] In blocks 60 and 62, MPU 12 writes a signature or fixed pattern, e.g. A320, n times to each memory location starting from one end of the memory space and working upwards(or downwards). n is a number that is typically 4, but could be any other number; however, it has to be specified in the driver which is decided by the hardware. This fixed pattern is referred to as the signature pattern.

[0103] In block 64, MPU 12 reads the memory location where it wrote the fixed pattern. If, in decision block 66, the value read is identical to the value that was written, then the MPU 12 increments the address counter and proceeds to repeat the above process for the next consecutive memory location (blocks 68 and 70).

[0104] If the value read is not identical to the value just written in decision block 66, and if it is equal to a predetermined response value (for example, the complement of the signature) in decision block 72, the driver assumes it has located the DSP/memory mode 40. This address value is the address of the Signature Register (SIGR). The driver remembers this address for future reference. If the data read is not equal to the response value in decision block 72, then an error has occurred.

[0105] Configuration Mode

[0106] FIG. 6 illustrates the memory map as seen by the MPU 12 when the DSP/memory module 40 is in configuration mode. As described above, when the MPU 12 decides to use the DSP circuitry 44 on the DSP/memory module 40, it writes the signature pattern, n times, to the SIGR register directly. This switches the module to the configuration mode. The DSP 56 on the module is still not powered . The MPU 12 can access several addresses following the SIGR register to obtain information regarding the module. This can be in the form of a header that is several bytes long stored in a module information structure (MIS) memory 72. This header will specify the type of DSP(s) on the DSP/memory module 40, whether the DSP/memory module 40 is a 32-bit or 16-bit processor, the size of local memory 58 associated with the DSP, the size of the memory on the DSP/memory module 40, and other related information. The driver saves this Configuration Header for future reference. (And if for some reason the power is recycled on the PC, then the DSP/memory module 40 should always boot-up in the standard mode.)

[0107] Using the appropriate control registers 52 that are now available, following the SIGR register, the MPU 12 downloads program and data to the DSP's local memory 58. (This means that the local memory associated with the DSP 56 must be powered up, but the DSP 56 should still be off).

[0108] The DSPLOC register, available in the configuration mode, allows the MPU 12 to relocate the SIGR and other control registers to another location on the DSP/memory module 40. Even if the MPU 12 decides not to relocate the control registers 52 to a new address, it must still write a zero to the DSPLOC registers. The MPU 12 now writes the signature pattern, A320, to the SIGR register to switch the module from configuration mode back to standard mode.

[0109] Smart Mode

[0110] When the MPU 12 invokes the power of the DSP 56 on the DSP/memory module 40, it will first determine if there is memory available on the module. Some current application programs may have allocated memory in the address space of the DSP/memory module 40. Hence, the MPU 12 will move any existing application memories to new locations. Alternatively, the MPU 12 may decide to relocate the control registers to another address on the DSP/memory module 40. In order to relocate the address of the control registers 52, the MPU 12 enters the configuration mode of the DSP/memory module 40, described above. The DSPLOC register in the configuration mode allows the MPU 12 to relocate the SIGR register and other shared registers to another location on the DSP/memory module 40; this flexibility is required since the MPU 12 may have previously allocated an application on the DSP/memory module 40 which has memory allocated that overlaps on the SIGR register. Then the MPU 12 will switch from configuration mode to standard mode and from standard mode to smart mode. In smart mode, the MPU 12 will download the necessary digital signal processing program(s) and data to the local memory 58 of the DSP 56. By writing to the control register, the MPU 12 can start the DSP 56.

[0111] In addition to writing to the base register, the MPU 12 writes to a Shared Memory Size register on the SRAM associated with the DSP, which specifies the amount of shared memory between the host MPU 12 and the DSP 56. Shared memory is accessible by both the MPU 12 as well as the DSP 56.

[0112] If the shared memory was specified by the MPU as zero, then the DSP/memory module 40 is said to be in the smart-local mode. In this case, only the control registers 52 are accessible by the MPU. A diagram of the memory map seen by MPU 12 in smart-local mode is shown in FIG. 7. In this mode, the MPU can read and write from the control registers 52. Through the control registers 52, the MPU can access the MIS 72 and local memory 58 (DSP_PM is the DSP's local program memory and DSP_DM is the DSP's local data memory) through control registers LM_RW_ADDR, LM_RW_DATA and LM_ADR_OFFSET, and the MPU 12 can access the I/O registers 74 of the DSP 56 through control registers DSPTxD and DSPRxD.

[0113] However, if the shared memory was specified by the MPU as a non-zero value, then the mode is referred to as the smart-shared mode. In this mode the specified amount of memory is available as shared memory 54 between the MPU and the DSP(s). FIG. 8 illustrates the memory map seen by the MPU 12 in smart-shared mode.

[0114] In smart-shared mode, the MPU 12 first reads the semaphore bit, tests it to decide if the shared memory is currently being accessed by the DSP, and if it is not being used, the MPU 12 will set the semaphore bit prior to accessing the shared memory (and return the bit to “0” once the access is complete). However if the semaphore bit is already set, indicating that the DSP 56 is currently accessing the shared memory 54, MPU 12 can write a “1” to the Shared Memory request bit (referred to as Manual Hold bit in the DSPCR register). This write is detected by the hardware module on the DSP/memory module 40. The module controller now does the appropriate actions to put the DSP 56 on hold; i.e., the module controller will stop the DSP's access to the shared memory 54, and return the access of the shared memory 54 to the MPU 12. The Shared Memory Request bit therefore allows the MPU to demand access to the shared memory, even though it is being used by the DSP 56.

[0115] Alternatively, this protocol can be avoided to speed accesses to the shared memory 54. However, avoiding the protocol requires hardware which can switch quickly enough to respond to MPU shared memory requests or the use of dual port DRAMs.

[0116] FIGS. 9-12 illustrate different embodiments for the DSP/memory module 40 and DSP circuitry 44. In FIG. 9 an embodiment is shown where the data and address buses 75 from MMU 14 (see FIG. 1) are received by module controller 76. The memory and address buses 75 are also connected to one or more DRAMs (dynamic random access memories) 78 which form the conventional memory on the DSP/memory module 40. In addition, one or more DPRAMs (dual ported random access memories) 80 are coupled to the module controller. The DPRAMs are mapped by the module controller 76 to the address specified as the shared memory. The outputs of the DPRAMs 80 are coupled to a DSP local bus 82 connecting the module controller 76 with the DSP(s) 56, shared memory 58 and (optionally) a CODEC (compressor/decompressor) 84.

[0117] This module has the standard memory bus signals coming into it from the MMU. For example there are address lines, data lines, and control lines that are typically found in a SIMM, DIMM, or other memory expansion modules found in notebook computers, PCs and PDAs. This prototype supports the standard, configuration and smart modes of operation as discussed above.

[0118] In operation, the DRAM 78 on the module is not shared between the MPU 12 and the DSP(s) 56. In standard mode, the MPU 12 reads and writes to the DRAM 78 which spans the entire memory space of the DSP/memory module 40. In smart mode, however, the module controller 76 passes reads and writes by the MPU 12 to the shared memory 54 to the DPRAMs 80, instead of to the corresponding locations in the DRAMs 78. The DSP 56 can read and write only to the DPRAMs 80, not to the DRAMs 78. This architecture reduces memory access conflicts between the MPU 12 and the DSP 56.

[0119] The control registers 42 and the MIS 72 could be implemented within the module controller 76.

[0120] In FIG. 10, a second embodiment of the DSP/memory module 40 is shown, wherein the module controller 76 switches access to the DRAMs 78 between the data and address bus 75 and the DSP local bus 82 through switch 86. In this embodiment, the DSP 56 can read and write to the DRAMs 78. However, the MPU 12 has a higher priority to the shared addresses in the DRAMs 78; when both the DSP 56 and MPU 12 try to access the DRAM 78 simultaneously, the module controller puts the DSP 56 on hold and switches to the MPU memory bus 75.

[0121] The MPU memory bus 75 is a typical memory bus consisting of the usual data, address, and control lines. The MPU's access to the DRAMs 58 is transparent, i.e., the module controller 76 accomplishes the switch such that the MPU 12 does not incur any delays. As far as the MPU 12 is concerned, it incurs the same delay in accessing the DRAM 78 if the module were to contain only the DRAM 78 as in a normal memory expansion module.

[0122] In order to provide transparent switching, it may be necessary to use DRAMs 78 which are of a higher speed rating than the stated speed rating of the DSP/memory module 40. For example, in order to provide a 70 ns DSP/memory module 40, it may be necessary to use 60 ns DRAMs 78 to compensate for the slight switching delay.

[0123] FIG. 11 illustrates a third embodiment of the DSP/memory module 40. In this embodiment, because of delays in switching between the MPU memory bus 75 and the DSP local bus 82, a WAIT signal is provided. This signal can be asserted during a switch between buses to hold the MPU access while the switch is occurring. The WAIT signal may be implemented by using an additional line or by using a combination of the existing standard memory bus signals, e.g., a unique combination of the refresh and write enable signals which would notify the MMU, and the MPU 12, that a WAIT had been asserted. Alternatively, a separate signal line or pin may be allocated in future standard memory modules.

[0124] In addition, this embodiment also supports an Interrupt Request Signal (IREQ) that allows the module to send an interrupt to the external device such as an MPU 12. The interrupt may be used, for example, to notify the MPU 12 that the DSP has completed its demanded task. For instance, the MPU 12 could place data in shared memory for translation to wavetable sounds, and the DSP could interrupt the MPU when the operation was complete, in order to allow the MPU 12 to work on other tasks while the transformation was being performed by the DSP 56. The IREQ signal may be implemented by using a combination of the existing standard memory bus signals, e.g., a combination of the refresh and write enable signals may be used to signal the host of a pending service request. Alternatively, a separate signal line or pin may be allocated in a future standard memory module design.

[0125] The following sections describe ways to implement the WAIT and IREQ signals. Six options are discussed, showing how these signals may be connected and handled by a host controller. (The host controller is also referred to as the memory controller 76 in this document.) We discuss these signals for memory modules (MMs) 98; in the examples shown below, we have considered Dual-in-line memory-modules(DIMMs) with either Fast Page Mode (FPM), Extended Data Output (EDO), Synchronous (S) or Double Data Rate Synchronous (DDR-S) Dynamic Random Access Memories (DRAMs). However these teachings are applicable to other types of memory/memory modules as well. Each of these DIMMs 98 have two or more banks of memory.

[0126] DIMM Impact

[0127] This option shall add 4 signals to each DIMM module 98, /MWAIT0 signal 101, MWAIT1 signal 102, /MIRQ0 signal 103, and /MIRQ1 signal 104.

[0128] See the block diagram in FIG. 14.

[0129] Memory Controller Impact

[0130] The memory controller shall have one /MWAITn signal (101 or 102) and one /MIRQn signal (103 or 104) added for each of n banks. Thus 2n extra pins are needed where n is the total number of memory banks.

[0131] The memory controller 76 shall include the necessary logic to comprehend the added signals above.

[0132] The memory controller 76 shall include setup registers 76a(if needed).

[0133] See the block diagram in FIG. 14.

[0134] Signal List and Description

[0135] Memory Eligibility for DSP Access (DDR-S/SDRAM Only)

[0136] Unlike conventional DRAMs, synchronous DRAMS have 2 or 4 internal banks. Because of this feature, the memory controller has the ability to open 2 or 4 pages at a time and instantly switch between them for read and write access. This feature makes the eligibility of DSP access to the memory slightly more complicated than with conventional DRAMs. A set of rules for eligibility must be defined.

[0137] Option 1: The shared SDRAM is only eligible for DSP access when all pages are known to be closed (after a PALL command). This will ensure that there are no page conflicts between the host and the DSP. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV command can then be asserted in the cycle following the cycle where /MWAITn is sampled as high. This option would work most efficiently if the host controller closed all pages at the end of every memory access. This option treats the SDRAM much like a (single bank) standard DRAM. See FIG. 16.

[0138] Option 2: The memory is eligible for DSP access on a bank-by-bank basis after the host controller executes a READA, WRITEA, or PRE command for the specific bank that the DSP wishes to access. This approach is slightly less straightforward and would require the DSP to monitor the bank that the host controller is currently accessing. Also, the DSP may not gain access to the memory directly after one of these three commands, for the host controller may choose to immediately execute a WRITE or READ command on a different internal bank. When the desired bank is known to be precharged, the memory is eligible for DSP access after a burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. Because other pages may still be open, however, it is possible that the host controller may incur several waits during a same page access. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV, WRITE or READ commands can then be asserted in the cycle following the cycle where /MWAITn is sampled as high. See FIG. 17.

[0139] Option 3: The memory is eligible for DSP access at any time. This option would allow the DSP to break pages, accessing the memory whenever the host controller is not currently busy with a memory transaction. The memory will be eligible for DSP access after any burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. The DSP, after gaining access to the memory would be responsible for issuing a precharge for all banks that it wishes to access via a PALL or one or more PRE command(s). After precharging is complete, the DSP may issue an ACTV command for its desired row. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. If /MWAITn is sampled to be low, then the controller must re-open the page with a new ACTV command. See FIG. 18.

[0140] At the end of a non-interrupted DSP access, the DSP has two options:

[0141] a) The DSP precharges its accessed banks and re-opens the distrusted pages (via an ACTV command) and drives the /MWAITn signal back high. (This of course would require the DSP to register the last host controller page address.)

[0142] b) The DSP precharges its accessed banks and continues to drive the /MWAITn signal low, indicating to the controller that any desired page(s) must be re-opened via an ACTV command.

[0143] Memory Controller Setup Registers

[0144] It may be helpful to add n register bits to the memory controller to pre-define which of n banks will drive the /MWAITn signal. Access to memory banks that do not drive the /MWAITn signal need not suffer the possible controller latency associated with sampling the /MWAITn signal for each memory access.

[0145] DIMM Impact

[0146] This option shall add 3 signals to each DIMM module 98, /MWAIT signal 105, MIRQ0 signal 103, and /MIRQ1 signal 104.

[0147] See the block diagram in FIG. 19.

[0148] Memory Controller Impact

[0149] The memory controller shall have one /MIRQn signal (103 or 104) added for each of n banks. The memory controller shall have one and only one /MWAIT signal (105) added. Thus (1+n) extra pins are needed where n is the total number of memory banks.

[0150] The memory controller shall include the necessary logic to comprehend the added signals above.

[0151] The memory controller shall include setup registers (if needed).

[0152] See the block diagram in FIG. 19.

[0153] Signal List and Description

[0154] Memory Eligibility for DSP Access (DDR-S/SDRAM Only)

[0155] Unlike conventional DRAMs, synchronous DRAMS have 2 or 4 internal banks. Because of this feature, the memory controller has the ability to open 2 or 4 pages at a time and instantly switch between them for read and write access. This feature makes the eligibility of DSP access to the memory slightly more complicated than with conventional DRAMs. A set of rules for eligibility must be defined.

[0156] Option 1: The shared SDRAM is only eligible for DSP access when all pages are known to be closed (after a PALL command). This will ensure that there are no page conflicts between the host and the DSP. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV command can then be asserted in the cycle following the cycle where /MWAIT is sampled as high. This option would work most efficiently if the host controller closed all pages at the end of every memory access. This option treats the SDRAM much like a (single bank) standard DRAM. See FIG. 21.

[0157] Option 2: The memory is eligible for DSP access on a bank-by-bank basis after the host controller executes a READA, WRITEA, or PRE command for the specific bank that the DSP wishes to access. This approach is slightly less straightforward and would require the DSP to monitor the bank that the host controller is currently accessing. Also, the DSP may not gain access to the memory directly after one of these three commands, for the host controller may choose to immediately execute a WRITE or READ command on a different internal bank. When the desired bank is known to be precharged, the memory is eligible for DSP access after a burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. Because other pages may still be open, however, it is possible that the host controller may incur several waits during a same page access. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV, WRITE or READ commands can then be asserted in the cycle following the cycle where /MWAIT is sampled as high. See FIG. 22.

[0158] Option 3: The memory is eligible for DSP access at any time. This option would allow the DSP to break pages, accessing the memory whenever the host controller is not currently busy with a memory transaction. The memory will be eligible for DSP access after any burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. The DSP, after gaining access to the memory would be responsible for issuing a precharge for all banks that it wishes to access via a PALL or one or more PRE command(s). After precharging is complete, the DSP may issue an ACTV command for its desired row. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. If /MWAIT is sampled to be low, then the controller must re-open the page with a new ACTV command. See FIG. 23.

[0159] At the end of a non-interrupted DSP access, the DSP has two options:

[0160] a) The DSP precharges its accessed banks and re-opens the distrusted pages (via an ACTV command). The next time that /Sn is driven low, /MWAIT will respond as high. (This of course would require the DSP to register the last host controller page address.)

[0161] b) The DSP precharges its accessed banks. The next time that /Sn is driven low, /MWAIT will respond as low, indicating to the controller that any desired page(s) must be re-opened via an ACTV command.

[0162] Memory Controller Setup Registers

[0163] It may be helpful to add n register bits to the memory controller to pre-define which of n banks will drive the /MWAIT signal. Access to memory banks that do not drive the /MWAIT signal need not suffer the possible controller latency associated with sampling, the /MWAIT signal for each memory access.

[0164] Impact to DIMM

[0165] This option shall add 2 signals to each DIMM module 98, /M0WAIT/IRQ signal 107, and /M1WAIT/IRQ signal 108.

[0166] See the block diagram in FIG. 24.

[0167] Impact to Memory Controller

[0168] The memory controller shall have one MnWAIT/IRQ signal (107 or 108) added for each of n banks. Thus n extra pins are needed where n is the total number of memory banks.

[0169] The memory controller shall include necessary logic to comprehend the added signals above.

[0170] The memory controller shall include setup registers (if needed).

[0171] See the block diagram in FIG. 24.

[0172] Signal List and Description

[0173] Memory Eligibility for DSP Access (DDR-S/SDRAM Only)

[0174] Unlike conventional DRAMs, synchronous DRAMS have 2 or 4 internal banks. Because of this feature, the memory controller has the ability to open 2 or 4 pages at a time and instantly switch between them for read and write access. This feature makes the eligibility of DSP access to the memory slightly more complicated than with conventional DRAMs. A set of rules for eligibility must be defined.

[0175] Option 1: The shared SDRAM is only eligible for DSP access when all pages are known to be closed (after a PALL command). This will ensure that there are no page conflicts between the host and the DSP. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV command can then be asserted in the cycle following the cycle where /MnWAIT/IRQ is sampled as high. This option would work most efficiently if the host controller closed all pages at the end of every memory access. This option treats the SDRAM much like a (single bank) standard DRAM. See FIG. 26.

[0176] Option 2: The memory is eligible for DSP access on a bank-by-bank basis after the host controller executes a READA, WRITEA, or PRE command for the specific bank that the DSP wishes to access. This approach is slightly less straightforward and would require the DSP to monitor the bank that the host controller is currently accessing. Also, the DSP may not gain access to the memory directly after one of these three commands, for the host controller may choose to immediately execute a WRITE or READ command on a different internal bank. When the desired bank is known to be precharged, the memory is eligible for DSP access after a burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. Because other pages may still be open, however, it is possible that the host controller may incur several waits during a same page access. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV, WRITE or READ commands can then be asserted in the cycle following the cycle where /MnWAIT/IRQ is sampled as high. See FIG. 27.

[0177] Option 3: The memory is eligible for DSP access at any time. This option would allow the DSP to break pages, accessing the memory whenever the host controller is not currently busy with a memory transaction. The memory will be eligible for DSP access after any burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. The DSP, after gaining access to the memory would be responsible for issuing a precharge for all banks that it wishes to access via a PALL or one or more PRE command(s). After precharging is complete, the DSP may issue an ACTV command for its desired row. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. If /MnWAIT/IRQ is sampled to be low, then the controller must re-open the page with a new ACTV command. See FIG. 28.

[0178] At the end of a non-interrupted DSP access, the DSP has two options:

[0179] a) The DSP precharges its accessed banks and re-opens the distrusted pages (via an ACTV command). The next time that /Sn is driven low, /MnWAIT/IRQ will respond as high. (This of course would require the DSP to register the last host controller page address.)

[0180] b) The DSP precharges its accessed banks. The next time that /Sn is driven low, /MnWAIT/IRQ will respond as low, indicating to the controller that any desired page(s) must be re-opened via an ACTV command.

[0181] Memory Controller Setup Registers

[0182] It may be helpful to add n register bits to the memory controller to pre-define which of n banks will drive the /MnWAIT/IRQ signal. Access to memory banks that do not drive the /MnWAIT/IRQ signal need not suffer the possible controller latency associated with sampling the /MnWAIT/IRQ signal for each memory access.

[0183] Impact to DIMM

[0184] This option shall add 2 signals to each DIMM module 98, /MIRQ0 signal 103 and /MIRQ1 signal 104.

[0185] See the block diagram in FIG. 29.

[0186] Impact to Memory Controller

[0187] The memory controller shall have one /MIRQn signal (103 or 104) added for each of n banks. The implementation of the wait function is described in the section 2.4.6 below. Thus n extra pins are needed where n is the total number of memory banks.

[0188] The memory controller shall include the necessary logic to comprehend the added signals above.

[0189] The memory controller shall include the appropriate setup registers and logic to implement the WAIT function.

[0190] See the block diagram in FIG. 29.

[0191] Signal List and Description

[0192] Memory Eligibility for DSP Access (DDR-S/SDRAM Only)

[0193] Unlike conventional DRAMs, synchronous DRAMS have 2 or 4 internal banks. Because of this feature, the memory controller has the ability to open 2 or 4 pages at a time and instantly switch between them for read and write access. This feature makes the eligibility of DSP access to the memory slightly more complicated than with conventional DRAMs. A set of rules for eligibility must be defined.

[0194] For this option, the shared SDRAM shall only be eligible for DSP access when all pages are known to be closed (after a PALL command). This greatly simplifies the memory controller design, making it easy for the controller to determine where the region of eligibility begins. This will ensure that there are no page conflicts between the host and the DSP. This option would work most efficiently if the host controller closed all pages at the end of every memory access. This option treats the SDRAM much like a (single bank) standard DRAM.

[0195] Memory Controller Setup Registers

[0196] When the MM is placed in “smart mode”, a RAS-to-CAS delay of memory access is necessary because the (S)DRAM in the selected bank will be shared. In the case of FPM or EDO DRAM, RAS-to-CAS delay refers to the time from the falling edge of RAS to the falling edge of /CAS. When using SDRAM, RAS-to-CAS delay refers to the number of memory clock cycles between a ROW ACTIVE and READ or WRITE command. All other timing after the first falling edge of /CAS may proceed as normal.

[0197] In order to implement this delay (or wait) function, it is necessary to add n registers to the memory controller to pre-define the RAS-to-CAS wait time for each of n banks. Many controllers have this feature today, but only on a global (not bank-by-bank) basis. The controller must also be capable of extending the RAS-to-CAS delay to a value greater than the time required for the MM to release the shared memory back to the controller. Generally, this time shall be no less than t_RC(read or write cycle time) for the particular DRAM used on the MM. Since in this option, there is no feedback from the MM to indicate when the memory is available, the RAS-to-CAS delay time must be set to a “safe” value greater than t_RC+t_MMBUSSWITCH, or the total time required to completely guarantee that the shared memory may be accessed by the memory controller.

[0198] Access to memory banks that are not pre-defined to need extended cycles shall be set at power-up to operate normally. Accesses to registers corresponding to banks with DSPs shall be done dynamically, not just at power-up. This will allow the wait length time to be changed “on the fly” when the MM is placed into and out of smart mode.

[0199] When the MM is not in the “Smart Mode,” the selected bank of the MM shall operate normally, as standard DRAM.

[0200] Impact to DIMM

[0201] This option shall add 1 signal to each DIMM module 98, /MWAIT/IRQ signal 109.

[0202] See the block diagram in FIG. 30.

[0203] Impact to Memory Controller

[0204] The memory controller shall have one MWAIT/IRQ signal 109 added for each MM (containing 2 banks). Thus n/2 extra pins are needed where n is the total number of memory banks.

[0205] The memory controller shall include necessary logic to comprehend the added signals above.

[0206] The memory controller shall include setup registers (if needed).

[0207] See the block diagram in FIG. 30.

[0208] Signal List and Description

[0209] Unlike conventional DRAMs, synchronous DRAMS have 2 or 4 internal banks. Because of this feature, the memory controller has the ability to open 2 or 4 pages at a time and instantly switch between them for read and write access. This feature makes the eligibility of DSP access to the memory slightly more complicated than with conventional DRAMs. A set of rules for eligibility must be defined.

[0210] Option 1: The shared SDRAM is only eligible for DSP access when all pages are known to be closed (after a PALL command). This will ensure that there are no page conflicts between the host and the DSP. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV command can then be asserted in the cycle following the cycle where /MWAIT/IRQ is sampled as high. This option would work most efficiently if the host controller closed all pages at the end of every memory access. This option treats the SDRAM much like a (single bank) standard DRAM. See FIG. 31.

[0211] Option 2: The memory is eligible for DSP access on a bank-by-bank basis after the host controller executes a READA, WRITEA, or PRE command for the specific bank that the DSP wishes to access. This approach is slightly less straightforward and would require the DSP to monitor the bank that the host controller is currently accessing. Also, the DSP may not gain access to the memory directly after one of these three commands, for the host controller may choose to immediately execute a WRITE or READ command on a different internal bank. When the desired bank is known to be precharged, the memory is eligible for DSP access after a burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. Because other pages may still be open, however, it is possible that the host controller may incur several waits during a same page access. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. The ACTV, WRITE or READ commands can then be asserted in the cycle following the cycle where /MWAIT/IRQ is sampled as high. See FIG. 32.

[0212] Option 3: The memory is eligible for DSP access at any time. This option would allow the DSP to break pages, accessing the memory whenever the host controller is not currently busy with a memory transaction. The memory will be eligible for DSP access after any burst read or write is complete, and the /Sn input is high, or after a pre-defined number of clock cycles without memory activity. The DSP, after gaining access to the memory would be responsible for issuing a precharge for all banks that it wishes to access via a PALL or one or more PRE command(s). After precharging is complete, the DSP may issue an ACTV command for its desired row. After the point of memory eligibility, the host controller must drive /Sn low and monitor the wait signal before issuing any new commands. If /MWAIT/IRQ is sampled to be low, then the controller must re-open the page with a new ACTV command. See FIG. 33.

[0213] At the end of a non-interrupted DSP access, the DSP has two options:

[0214] a) The DSP precharges its accessed banks and re-opens the distrusted pages (via an ACTV command). The next time that /Sn is driven low, /MWAIT/IRQ will respond as high. (This of course would require the DSP to register the last host controller page address.)

[0215] b) The DSP precharges its accessed banks. The next time that /Sn is driven low, /MWAIT will respond as low, indicating to the controller that any desired page(s) must be re-opened via an ACTV command.

[0216] Memory Controller Setup Registers

[0217] It may be helpful to add n register bits to the memory controller to pre-define which of n banks will drive the /MWAIT/IRQ signal. Access to memory banks that do not drive the /MWAIT/IRQ signal need not suffer the possible controller latency associated with sampling the /MWAIT/IRQ signal for each memory access.

[0218] Impact to DIMM

[0219] None.

[0220] Impact to Memory Controller

[0221] The memory controller shall include the necessary logic to implement the wait function by accessing the semaphore bit memory location before accessing any of the shared memory.

[0222] The memory controller shall include setup registers to pre-define which bank(s) shall be populated with shared memory.

[0223] Signal List and Description

[0224] No extra signals are required.

[0225] Block Diagram

[0226] DIMM and Memory Controller pinouts remain the same.

[0227] Memory Controller Setup Registers

[0228] In order to implement the wait function, it is necessary to add n bits of registers to the memory controller to pre-define which banks shall contain shared memory.

[0229] SSTL vs. TTL

[0230] Since all wait and interrupt signals proposed above use only the rising edge of the system memory clock (DDR-S/SDRAM case), they shall be implemented with standard TTL or LVTTL.

[0231] Refresh Handling

[0232] While in smart mode, refresh can be handled 1 of 2 ways:

[0233] Option 1: When the memory controller requests a CBR (or /RAS only for EDO & FPM DRAMs) refresh, the MM shall detect this command and execute it immediately (if not busy), or “buffer up” the refresh commands and execute them at a later time when the DSP is not accessing the memory.

[0234] Option 2: When the memory controller requests a refresh, and the DSP is accessing the shared memory, the same wait protocol defined in the options above shall be implemented. The controller must wait until the MM relinquishes the memory to complete the refresh operation.

[0235] Memory Bus Capacitance/Memory Access Time

[0236] With the high speed of today's DRAMs and SDRAMs, and the promise of even higher speed for DDR-SDRAMS for tomorrow, bus loading must be considered very carefully in MM design. The memory access time, t_ac, is also a very important parameter which cannot be violated.

[0237] For bus isolation on the Basava Memory Module, bus switches (crossbars) shall be used. This allows switchable connection to the PC's memory bus while only introducing a maximum of 0.25 ns propagation delay. Switches of this type add anywhere from 4 to 8 pF of capacitance to the lines that they are connected to, so it will be important that the design of the MM is properly within specification for the driving logic.

[0238] Module-to-Module Communication

[0239] If multiple MMs containing DSPs are placed in one system, it may be advantageous that the DSPs be able to communicate with one another. It is not necessary that motherboard connection pins be allocated on the DIMM module for this purpose, for a separate connector may be defined for this purpose.

[0240] The interface bus shall consist of 2 or 3 wires. A protocol shall be defined that allows all DSPs to communicate with one another without having to define a master/slave relationship. Actual details on this concept will soon be defined. FIG. 34 shows this concept.

[0241] The following table summarizes the five options above.

[0242] Although Option 1 is by far the easiest for the MM design, it carries a high DIMM and Memory Controller pinout.

[0243] Option 2 is the best trade-off between versatility and pins, allowing full feedback from the MM for the wait function, while only using 1+n controller pins.

[0244] Option 3 cuts the DIMM pin and controller pin by one, but requires a complicated protocol. Option 4 is far easier to implement and boasts the same low pinout as Option 3.

[0245] Option 4, however limits the DSP's accessibility to SDRAM.

[0246] Option 5 shall be used if pins on the MM are in short supply. Option 5 supports SDRAM or DDR-SDRAM operation only.

[0247] Option 6 shall only be used as a last resort if no pins are available for use on the DIMM.

[0248] FIG. 12 illustrates the DSP/memory module 40 in a typical computer architecture. In addition to the elements shown in FIG. 1, a secondary cache 90, keyboard controller 92 and external AFE (Analog Front End) are shown. The analog front end may be used to connect to the CODEC 84 on the DSP/memory module 40 to receive external data, such as voice data or video data. Typical memory expansion modules 26 have only one connector for the memory bus 24. However, in this case, in order to support direct access to external devices by the DSP 56, an AFE 94 is provided. The AFE 94 could connect to connectors on the other side of the substrate 46 (see FIG. 2) to make connection with the DSP and communicate using direct memory access, while maintaining compatibility with standard SIMMs. This AFE supports sound, modem, wireless applications.

[0249] The DSP/memory module 40 can be used in many application to increase the speed of multimedia features and reduce the load on the MPU 12. In a first example, modem information could come from a telephone line to the CODEC 84. Using the local SRAM 58, the DSP 56 could translate the data and place it in the shared memory 54. The MPU 12 would then retrieve the translated data from the shared memory 54. This is an example of an application which would otherwise require many instruction cycles of the MPU 12, but can be accomplished with very little MPU interaction using the DSP/memory module 40.

[0250] In a second example, the MPU 12 could open a file on a DVD (digital versatile disk) which has compressed audio or video. The MPU 12 would pass the data directly to the shared memory 54 and instruct the DSP 56 to decompress the data. As the data was decompressed, it would be returned to the shared memory, where the MPU 12 would retrieve the decompressed data and pass the data to the frame buffer of the video/graphics card for display. This is an example of an application which would require excessive bandwidth if the data had to be passes over the ISA bus 32 or PCI bus 28, but can be accomplished at high speed using the faster memory bus 24 and the DSP/memory module 40.

[0251] A third example uses the DSP/memory module 40 to perform wavetable synthesis. In this example, the shared memory 54 can be used to store the wavetable sounds, which normally require a large memory. The DSP 56 can use the wavetable data to perform the synthesis. Normally, a separate card would be required, along with its own memory for storing the wavetable data (typically on the order of two to four megabytes). Thus, the DSP/memory module 40 saves system costs by using the main memory to perform wavetable synthesis.

[0252] FIG. 13 illustrates a variation of the computer system of FIG. 12 wherein an AFE card 96 is connected to the PCI bus 28. The AFE card 96 would include the CODEC and would provide connections to external analog sources such as a line-in/out, microphone input, telephone line or cellular connection. In this implementation, the AFE card 96 can send data directly to the DSP/memory module 40, since the PCI bus has bus mastering capability, whereas the ISA bus does not. Similarly, the AFE card 96 could be connected to any bus which has the ability to write directly to the main memory.

[0253] In addition to providing connections to an external analog source, the AFE card 96 could poll a status register on the DSP/memory module 40 (if polling was necessary to determine whether a task had been completed by the DSP/memory module 40) at fairly high speeds. With current day processors, it is estimated that polling should be performed at intervals on the order of 20 milliseconds for optimum performance. A card in the PCI bus could poll the DSP/memory module 40 at greater speed, on the order of five milliseconds or less without degradation of performance.

[0254] The invention provides significant advantages over the prior art. Adding a digital signal processor to a computer system to enable enhanced functions is as easy as expanding the memory of a MPU. The memory module can use a form factor of the type standardized by organizations like IEEE, JEDEC, and so on, such as a SIMM (single in-line memory module) or DIMM (dual in-line memory module) form factor.

[0255] Different applications may be downloaded by the MPU to the memory module for local execution. The memory module therefore supports multiple functionality, i.e., downloadable, multiple functions under software control of the MPU.

[0256] The DSP/memory module offers the highest possible bandwidth between the MPU and coprocessor at any given time and technology. The DSP/memory module is both bus-independent, and host-independent, for use with PCs (personal computers), PDAs (personal digital assistants), workstations and other computer systems.

[0257] The DSP/memory module reduces system cost by sharing system memory over a number of multimedia functions.

[0258] The module provides a framework for easily scaling up the processing power of a computer system; an existing single processor system can be transformed into a scaleable, multiprocessing system simply by adding a memory module.

[0259] Users do not have to change their product platforms in order to get/offer new, value-added functions. Adding the DSP/memory module and software can allow users to increase the capability of their computers.

[0260] While the DSP/memory module 40 has been shown with a single DSP on each module, multiple DSPs could be provided. Additionally, a DSP/memory module 40 could be used in each memory bank 50 to provide multiple DSPs 54 under control of the MPU 12.

[0261] Although the Detailed Description of the invention has been directed to certain exemplary embodiments, various modifications of these embodiments, as well as alternative embodiments, will be suggested to those skilled in the art. The invention encompasses any modifications or alternative embodiments that fall within the scope of the claims.