Single-chip audio system mixing circuitry and methods

[0002] This is a division of application Ser. No. 08/949,563 filed Oct. 14, 1997 entitled SINGLE-CHIP AUDIO CIRCUITS, METHODS, AND SYSTEMS USING THE SAME.

[0003] This application for patent is related to the following applications for patent:

[0004] Pending U.S. patent application Ser. No. 08/949,563 entitled “SINGLE-CHIP AUDIO CIRCUITS, METHODS AND SYSTEMS USING THE SAME”, filed Oct. 14, 1997;

[0005] AUDIO SPATIAL ENHANCEMENT CIRCUITRY AND METHODS USING THE SAME, U.S. patent application Ser. No. 09/031,156, filed concurrently herewith;

[0006] SINGLE-CHIP AUDIO SYSTEM POWER REDUCTION CIRCUITRY AND METHODS, U.S. patent application Ser. No. 09/031,116, filed concurrently herewith;

[0007] SIGNAL AMPLITUDE CONTROL CIRCUITRY AND METHODS, U.S. patent application Ser. No. 09/031,439, filed concurrently herewith;

[0008] SINGLE-CHIP AUDIO SYSTEM VOLUME CONTROL CIRCUITRY AND METHODS, U.S. patent application Ser. No. 09/031,112, filed concurrently herewith;

[0009] OSCILLATOR START-UP CIRCUITRY AND SYSTEMS AND METHODS USING THE SAME, U.S. patent application Ser. No. 09/031,444, filed concurrently herewith.

[0010] These applications for patent are hereby incorporated by reference in the present disclosure as fully set forth herein.

[0011] 1. Field of the Invention

[0012] The present invention relates in general to digital data processing and in particular to single-chip audio circuits, methods and systems using the same.

[0013] 2. Description of the Related Art

[0014] The ability to process audio information has become increasingly important in the personal computer (PC) environment. Among other things, audio is important in many multimedia applications, such as gaming and telecommunications. Audio functionality is therefore typically available on most conventional PCs, either in the form of an add-on audio board or as a standard feature provided on the motherboard itself. In fact, PC users increasingly expect not only audio functionality but high quality sound capability.

[0015] The key components in most digital audio information processing systems convert input analog audio information into a digital format for processing processor, support sample rate conversion, SoundBlaster compatibility, wavetable synthesis, or DirectSound acceleration, convert outgoing signals from digital to analog format for eventual audible output to the user, and mix analog and/or digital data streams. In conventional systems, these functions must be provided through multiple chip solutions which make board design and fabrication more complex and expensive.

[0016] Thus, to meet the demands of increasingly sophisticated computer users, the need has arisen for new circuits and methods for implementing single-chip audio systems and systems using the same. Among other things, such circuits and methods should provide for the implementation of systems for use with high quality sound systems and should support the latest sound processing standards and game designs.

[0017] A single chip audio system includes a bus interface, digital to analog converters, analog mixer, and analog spatial enhancement circuitry. Digital to analog converters convert digital audio data received through bus interface into analog signals. The Analog mixer mixes signals received from digital to analog converters with an analog signal received from an external source. Analog spatial enhancement circuitry enhances first and second mixed analog signals output from analog mixer.

[0018] The principles of the present invention substantially meet the demand of increasingly sophisticated computer users for audio subsystems which produce high quality sound. Additionally, the application of the principles of the present invention allows for the provision of such features as stereo full-duplex coding/decoding, CD differential input, mono microphone input, a headphone output, as well as digital connections to a companion audio controller, as desired.

[0019] 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:

[0020] FIG. 1A is a diagram of an audio codec according to the principles of the present invention;

[0021] FIG. 1B is a diagram of an information processing system employing the audio codec of FIG. 1A;

[0022] FIG. 2 is a diagram providing a general overview of the bus structure and principle registers of the codec in FIG. 1A;

[0023] FIG. 3 is a functional block diagram of the codec: microcontroller core;

[0024] FIG. 4 is a diagram of the microcontroller memory map;

[0025] FIG. 5 is a diagram of the mapping of the program RAM space;

[0026] FIG. 6 is a diagram of the microcontroller External RAM data definition;

[0027] FIG. 7 is a diagram illustrating the timing of a Request/Grant handshake mechanism;

[0028] FIG. 8 is a diagram of the bitfields of Port 3 Bit Definitions;

[0029] FIG. 9 is a diagram providing an overview of the circuitry supporting a Plug & Play (PnP) interface to an external ISA bus;

[0030] FIG. 10A is a diagram emphasizing the configuration/interface logic for a PnP compatible device;

[0031] FIG. 10B is a diagram illustrating the typical functional elements of an LFSR device, including a series of storage/shift elements and logic;

[0032] FIG. 10C is a diagram of the LSFR checksum circuitry;

[0033] FIG. 11 is a diagram illustrating Plug and Play operating states and corresponding commands;

[0034] FIG. 12A is a diagram of the bitfields of the Plug & Play Address-Register at microcontroller Address 0x10;

[0035] FIG. 12B is a diagram of the bitfields of the Plug & Play Write_Data_Port at microcontroller Address 0x11;

[0036] FIG. 12C is a diagram of the bitfields of the Plug & Play Read_Data_Register at microcontroller Address 0x12;

[0037] FIG. 12D is a diagram of the bitfields of the Plug & Play State Register at microcontroller Address 0x13;

[0038] FIG. 12E is a diagram of the bitfields of the Plug & Play Control/Status register at microcontroller Address 0x14;

[0039] FIG. 12F is a diagram of the bitfields of the Sound System Base Address Low at microcontroller Address 0x15;

[0040] FIG. 12G is a diagram of the bitfields of the Sound System Base Address High register at microcontroller Address 0x16;

[0041] FIG. 12H is a diagram of the bitfields of the Control Base Address Low register at microcontroller Address 0x17;

[0042] FIG. 12I is a diagram of the bitfields of the Control Base Address High register at microcontroller Address 0x18;

[0043] FIG. 12J is a diagram of the bitfields of the Sound Blaster Base Address Low register at microcontroller Address 0x19;

[0044] FIG. 12K is a diagram of the bitfields of the Sound Blaster Base Address High register at microcontroller Address 0x1A;

[0045] FIG. 12L is a diagram of the bitfields of the Synthesizer Base Address Low register at microcontroller Address 0x1B;

[0046] FIG. 12M is a diagram of the bitfields of the Synthesizer Base Address High register at microcontroller Address 0x1C;

[0047] FIG. 12N is a diagram of the bitfields of the MPU-401 Base Address Low register at microcontroller Address 0x1D;

[0048] FIG. 12O is a diagram of the bitfields of the MPU-401 Base Address High register at microcontroller Address 0x1E;

[0049] FIG. 12P is a diagram of the bitfields of the Game Port Base Address Low register at microcontroller Address 0x1F;

[0050] FIG. 12Q is a diagram of the bitfields of the Game Port Base Address High register at microcontroller Address 0x20;

[0051] FIG. 12R is a diagram of the bitfields of the CDROM Base Address Low register at microcontroller Address 0x21;

[0052] FIG. 12S is a diagram of the bitfields of the CDROM Base Address High register at microcontroller Address 0x22;

[0053] FIG. 12T is a diagram of the bitfields of the Synthesizer Interrupt Select register at microcontroller Address 0x23;

[0054] FIG. 12U is a diagram of the bitfields of the Sound Blaster Interrupt Select register at microcontroller Address 0x24;

[0055] FIG. 12V is a diagram of the bitfields of the Sound System Interrupt Select register at microcontroller Address 0x25;

[0056] FIG. 12W is a diagram of the bitfields of the MPU-401 Interrupt Select register at microcontroller Address 0x26;

[0057] FIG. 12X is a diagram of the bitfields of the CDROM Interrupt Select register at microcontroller Address 0x27;

[0058] FIG. 12Y is a diagram of the bitfields of the Control Interrupt Select register at microcontroller Address 0x28;

[0059] FIG. 13 is a diagram defining the Plug and Play Port;

[0060] FIG. 14A is a diagram of the bitfields of the Sound Blaster DMA Channel Select registers at microcontroller address 0x29;

[0061] FIG. 14B is a diagram of the bitfields of the Sound System Playback/Capture DMA Channel Select registers at microcontroller address 0x2A;

[0062] FIG. 14C is a diagram of the bitfields of the Sound System Capture DMA Channel Select register at microcontroller address 0x2;

[0063] FIG. 14D is a diagram of the bitfields of the CDROM DMA Channel Select register at microcontroller Address 0x2C;

[0064] FIG. 15A is a diagram of the bitfields of the Alternate CDROM Base Address Low register at microcontroller Address 0x2D;

[0065] FIG. 15B is a diagram of the bitfields of the Alternate CDROM Base Address High registers at microcontroller Address 0x2E;

[0066] FIG. 15C is a diagram of the bitfields of the Physical Device Activation Register at microcontroller Address 0x2F;

[0067] FIG. 15D is a diagram of the bitfields of the Modem Base Address Low register at microcontroller Address 0x30;

[0068] FIG. 15E is a diagram of the bitfields of the Modem Base Address High register at microcontroller Address 0x30;

[0069] FIG. 15F is a diagram of the bitfields of the Alternate CDROM Mask Register at microcontroller Address 0x32;

[0070] FIG. 15G is a diagram of the bitfields of the Modem Mask Register at microcontroller Address 0x33;

[0071] FIG. 15H is a diagram of the bitfields of the Miscellaneous Control Bits register at microcontroller Address 0x34;

[0072] FIG. 15I is a diagram of the bitfields of the Modem Interrupt Select register at microcontroller Address 0x35;

[0073] FIG. 15J is a diagram of the bitfields of the Physical Device Activity Register at microcontroller address=0x36;

[0074] FIG. 16 is a diagram of the bitfields of the Wavetable and Serial Control Register at microcontroller address 0x40;

[0075] FIG. 17 is a diagram of the bitfields of the reserved register at address 0x41;

[0076] FIG. 18 is a diagram of the bitfields of the Port 3 Shadow Register at microcontroller address 0x42;

[0077] FIG. 19 is a diagram emphasizing the circuitry of the EEPROM interface;

[0078] FIG. 20 is a diagram which depicts a flow chart of a detect/load EEPROM sequence;

[0079] FIG. 21A is a diagram which depicts the fields o:f address mask register/alternate CDROM base address register (Byte 4);

[0080] FIG. 21B is a diagram which depicts the bitfields of Address Mask Register Modem (Byte 5);

[0081] FIG. 21C is a diagram which depicts the Miscellaneous Configuration Bits, Byte 6;

[0082] FIG. 21D is a diagram which defines the bitfields of the Misc Configuration Bits, Byte 7;

[0083] FIG. 21E is a diagram which depicts the Global Configuration, Byte 8 and is copied to 0x4003 on powerup;

[0084] FIG. 22A is a diagram which illustrates the timing relationship between the clock and data;

[0085] FIG. 22B is a diagram which depicts an EEPROM device read access;

[0086] FIG. 23 is a diagram of the Plug and Play interface;

[0087] FIG. 24A is a diagram of the bitfields of ISA DATA READ/MIXER LATCH register at microcontroller address 0x00;

[0088] FIG. 24B is a diagram of the bitfields of the Sound Blaster Data Latch register at microcontroller address 0x01;

[0089] FIG. 24C is a diagram of the bitfields of the MPU-401 Receive Data Latch at microcontroller address 0x02;

[0090] FIG. 24D is a diagram of the bitfields of the STATUS REGISTER at microcontroller Address 0x03;

[0091] FIG. 24E is a diagram of the Reserved Registers at microcontroller Addresses 0x04 through 0x07;

[0092] FIG. 24F is a diagram of the bitfields of the Reset Sound Blaster Busy 2 at microcontroller Address 0x08;

[0093] FIG. 24G is a diagram of the bitfields of the Reset Sound Blaster Busy 2 register at microcontroller address 0x00;

[0094] FIG. 24I is a diagram of the bitfields of the Sound Blaster ADPCM Data Latch at microcontroller Address 0xC;

[0095] FIG. 24J is a diagram of the bitfields of Set Sound Blaster Busy 1 at microcontroller Address MD;

[0096] FIG. 24K is a diagram of the bitfields of the Sound Blaster DMA Request Register at microcontroller Address ME which is in response to a write of a DMA command to the Sound Blaster Command Register;

[0097] FIG. 24L is a diagram of the bitfields of the Sound Blaster Interrupt Request Register at microcontroller Address 0x0F;

[0098] FIG. 25A is a diagram of the bitfields of the Miscellaneous Control Register (at control base +0);

[0099] FIG. 25B is a diagram of the bitfields of the Hardware Control Register;

[0100] FIG. 25C is a diagram of the bitfields of the Power Down Control Register;

[0101] FIG. 25D is a diagram of the bitfields of the bitfields of the Control Address/Index Register;

[0102] FIG. 25E is a diagram of the bitfields of the Control Data Register;

[0103] FIG. 25F is a diagram of the bitfields of the Command Register;

[0104] FIG. 25G is a diagram of the bitfields of the Program RAM Access End Register;

[0105] FIG. 25H is a diagram of the bitfields of the Status Register;

[0106] FIG. 25I is a diagram of the bitfields of the Miscellaneous Control register;

[0107] FIG. 25J is a diagram of the bitfields of the Version/ID at Control Index register;

[0108] FIG. 25K is a diagram of the bitfields of SRS Control Register;

[0109] FIG. 25L is a diagram of the bitfields of 3D Sound Control Register;

[0110] FIG. 25M is a diagram of the bitfields of the S/PDIF Control Register;

[0111] FIG. 25N is a diagram of the bitfields of the S/PDIF Channel Status Data register;

[0112] FIG. 25O is a diagram of the bitfields of the S/PDIF Channel Status Data register 1;

[0113] FIG. 25P is a diagram of the bitfields of the FAB Port ID register;

[0114] FIG. 25Q is a diagram of the bitfields of the Wavetable and Serial Port register;

[0115] FIG. 25R is a diagram of the bitfields of the Left Output Master Volume register;

[0116] FIG. 25S is a diagram of the bitfields of the Right Output Master Volume;

[0117] FIG. 26 is a diagram emphasizing the Codec Interface;

[0118] FIG. 27A is a diagram of the bitfields Index Address Register;

[0119] FIG. 27B is a diagram of the bitfields of Indexed Data Register;

[0120] FIG. 27C is a diagram of the bitfields of Status Register;

[0121] FIG. 27D is a diagram of the bitfields of Capture I/O Data Register;

[0122] FIG. 27E is a diagram of the bitfields of Playback I/O Data Register;

[0123] FIG. 27F is a diagram of the bitfields of Left ADC Input Control Register;

[0124] FIG. 27G is a diagram of the bitfields of Right ADC Input Control register;

[0125] FIG. 27H is a diagram of the bitfields of Left Auxiliary #1 Input Control Register;

[0126] FIG. 27I is a diagram of the bitfields of Right Auxiliary #1 Input Control Register;

[0127] FIG. 27J is a diagram of the bitfields of Left Auxiliary #2 Input Control Register;

[0128] FIG. 27K is a diagram of the bitfields of the Right Auxiliary #2 Input Control Register;

[0129] FIG. 27L is a diagram of the bitfields of Left DAC Output Control Register;

[0130] FIG. 27M is a diagram of the bitfields of Right DAC Output Control Register;

[0131] FIG. 27N is a diagram of the bitfields of Fs and Playback Data Format Register;

[0132] FIG. 27O is a diagram of the bitfields of Interface Configuration Register;

[0133] FIG. 27P is a diagram of the bitfields of the Pin Control Register;

[0134] FIG. 27Q is a diagram of the bitfields of the Error Status and Initialization Register;

[0135] FIG. 27R is a diagram of the bitfields of ODE and ID Register;

[0136] FIG. 27S is a diagram of the bitfields of Loopback Control Register;

[0137] FIG. 27T is a diagram of the bitfields of Playback Upper Base Register;

[0138] FIG. 27U is a diagram of the bitfields of Playback Lower Base Register;

[0139] FIG. 27V is a diagram of the bitfields of Alternate Feature Enable I Register;

[0140] FIG. 27W is a diagram of the bitfields of Alternate Feature Enable II Register;

[0141] FIG. 27X is a diagram of the bitfields of Left Line Input Control Register;

[0142] FIG. 27Y is a diagram of the bitfields of Right Line Input Control Register;

[0143] FIG. 27Z is a diagram of the bitfields of Timer Lower Base Register;

[0144] FIG. 27AA is a diagram of the bitfields of Timer Upper Base Register;

[0145] FIG. 27AB is a diagram of the bitfields of Alternate Sample Frequency Select Register;

[0146] FIG. 27AC is a diagram of the bitfields of Alternate Feature Enable III Register;

[0147] FIG. 27AD is a diagram of the bitfields of Alternate Feature Status Register;

[0148] FIG. 27AE is a diagram of the bitfields of Mono Input and Output Control Register;

[0149] FIG. 27AF is a diagram of the bitfields of Left Output Attenuation Register;

[0150] FIG. 27AG is a diagram of the bitfields of Capture Data Format Register;

[0151] FIG. 27AH is a diagram of the bitfields of the Right Output Attenuation Register;

[0152] FIG. 27AI is a diagram of the bitfields of Capture Upper Base Register;

[0153] FIG. 27AJ is a diagram of the bitfields of the Capture Lower Base Register;

[0154] FIG. 27AK is a diagram of the bitfields of the Left Alternate FM Input Control Register;

[0155] FIG. 27AL is a diagram of the bitfields of the Right Alternate FM Input Control Register;

[0156] FIG. 27AM is a diagram of the bitfields of the Left Mic Input Control Register;

[0157] FIG. 27AN is a diagram of the bitfields of the Right Mic Input Control Register;

[0158] FIG. 27AO is a diagram of the bitfields of Control Register;

[0159] FIG. 27AP is a diagram of the bitfields of Control Register;

[0160] FIG. 27AQ is a diagram of the bitfields of the Left FM Volume Control Register;

[0161] FIG. 27AR is a diagram of the bitfields of Right FM Volume Control Register;

[0162] FIG. 27AS is a diagram of the bitfields of Left DSP Serial Port Volume Control Register;

[0163] FIG. 27AT is a diagram of the bitfields of Right DSP Serial Port Volume Control Register;

[0164] FIG. 27AU is a diagram of the bitfields of Right Digital Loopback Volume Control Register;

[0165] FIG. 27AV is a diagram of the bitfields of DAC, SRC Control Register;

[0166] FIG. 27AW is a diagram of the bitfields of Capture Sample Rate Control Register;

[0167] FIG. 27AX is a diagram of the bitfields of Playback Sample Rate Control Register;

[0168] FIG. 27AY is a diagram of the bitfields of Left PCM Audio Volume Control Register;

[0169] FIG. 27AZ is a diagram of the bitfields of the Right PCM Audio Volume Control Register;

[0170] FIG. 27BA is a diagram of the bitfields of the Left Wavetable Volume Control Register;

[0171] FIG. 27BB is a diagram of the bitfields of Right Volume Control Register;

[0172] FIG. 28 is a diagram illustrating the timing of context switch mechanism;

[0173] FIG. 29 is a diagram of the External Peripheral Port;

[0174] FIGS. 30A and 30B are diagrams illustrating exemplary read/write operations through the external peripheral port:

[0175] FIG. 31 illustrated the synthesizer and CDROM interface;

[0176] FIG. 32 emphasizes the clocking scheme for the device

[0177] FIG. 33 is a diagram of the Game Port which provides an interface to a standard personal computer type joystick;

[0178] FIG. 34 is a diagram illustrating the speed control variation;

[0179] FIG. 35 is a timing diagram illustrating the joystick port timing;

[0180] FIG. 36A is a diagram of the Joystick control circuitry;

[0181] FIG. 36B is a diagram of the Joystick Digital Assist circuitry;

[0182] FIG. 37A is a diagram of the bitfields of the Digital Assist Control/Status Register;

[0183] FIG. 37B is a diagram of the bitfields of Joystick Trigger/X1 Position Data Low Byte;

[0184] FIG. 37C is a diagram of the bitfields of the X1 Position Data High Byte;

[0185] FIG. 37D is a diagram of the bitfields of the Y1 Position Data Low Byte;

[0186] FIG. 37E is a diagram of the bitfields of the Y1 Position Data High Byte;

[0187] FIG. 37F is a diagram of the bitfields of the X2 Position Data Low Byte;

[0188] FIG. 37G is a diagram of the bitfields of the X2 Position Data High Byte;

[0189] FIG. 37H is a diagram of the bitfields of the Y2 Position Data Low Byte;

[0190] FIG. 37I is a diagram of the bitfields of the Y2 Position Data High Byte;

[0191] FIG. 38 is an additional timing diagram illustrating the operation of joystick interface;

[0192] FIG. 39 is a diagram of one channel of the input mixer (the second channel is identical);

[0193] FIG. 40 is a diagram of one channel of the output. mixer (the second channel is also identical);

[0194] FIG. 41 is a diagram of the mono audio channel;

[0195] FIG. 42 is a diagram of the digital audio processing subsystem;

[0196] FIG. 43 is a diagram of the digital audio mixer;

[0197] FIG. 44 is a diagram illustrating the attenuation scheme for the Digital to Analog Converter Volume Control;

[0198] FIG. 45 is a more detailed diagram of the FM synthesis block 124;

[0199] FIG. 46A is a diagram of the bitfields of the Status Register;

[0200] FIG. 46B is a diagram of the bitfields of the Test Register;

[0201] FIG. 46C is a diagram of the bitfields of the Timer #1 Register;

[0202] FIG. 46D is a diagram of the bitfields of the Timer #2 Register;

[0203] FIG. 46E is a diagram of the bitfields of the Timer #1, #2 Control Register;

[0204] FIG. 46F is a diagram of the bitfields of the 4-Operator Mode Register

[0205] FIG. 46G is a diagram of the bitfields of the Expansion Register;

[0206] FIG. 46H is a diagram of the bitfields of the Keyboard Split Register;

[0207] FIG. 46I is a diagram of the bitfields of the Power Management Register;

[0208] FIG. 46J is a diagram of the bitfields of the Tremolo Effect Register;

[0209] FIG. 46K is a diagram of the bitfields of the Vibrato Effect Register;

[0210] FIG. 46L is a diagram of the bitfields of the Non-percussive/Percussive Sound Register;

[0211] FIG. 46M is a diagram of the bitfields of the Rate Key Scale Register;

[0212] FIG. 46N is a diagram of the bitfields of the Frequency Multiplier Register;

[0213] FIG. 46O is a diagram of the bitfields of the Total Level Register;

[0214] FIG. 46P is a diagram of the bitfields of the Level Key Scale Register;

[0215] FIG. 46Q is a diagram of the bitfields of the Attack Rate

[0216] FIG. 46R is a diagram of the bitfields of the Decay Rate Register;

[0217] FIG. 46S is a diagram of the bitfields of the Release Rate Register;

[0218] FIG. 46T is a diagram of the bitfields of the Sustain Level Register;

[0219] FIG. 46U is a diagram of the bitfields of the F-Number Register;

[0220] FIG. 46V is a diagram of the bitfields of the Block;

[0221] FIG. 46W is a diagram of the bitfields of the Key On;

[0222] FIG. 46X is a diagram of the bitfields of the Rhythm;

[0223] FIG. 46Y is a diagram of the bitfields of the Rhythm Instrument Selection;

[0224] FIG. 46Z is a diagram of the bitfields of the Algorithm Selection;

[0225] FIG. 46AA are a diagram of the bitfields of the Feedback Modulation;

[0226] FIG. 46AB is a diagram of the bitfields of the Output Channel Selection;

[0227] FIG. 46AC is a diagram of the bitfields of the Register Settings;

[0228] FIG. 47 is a diagram representing the implementation of two audio processing algorithms;

[0229] FIG. 48 is a diagram representing the implementation of the algorithms in the 4 operator audio processing mode;

[0230] FIG. 49 is a functional block diagram of the stereo processor portion a selected DSP;

[0231] FIG. 50A is a diagram of the zero cross volume control circuitry;

[0232] FIG. 50B is a diagram showing further detail of the zero cross volume control circuitry of FIG. 50A;

[0233] FIG. 51 is a diagram of the hysteresis circuitry for power-on of the VCO;

[0234] FIG. 52A is a diagram of the bitfields of the SRS Control Register;

[0235] FIG. 52B is a diagram of the bitfields of the 3D Sound Control at Control Index Register;

[0236] FIG. 53 is a diagram depicting the operation of the serial port during mode 1;

[0237] FIG. 54 is a diagram depicting the operation of the serial port during mode 2;

[0238] FIG. 55 is a diagram depicting the operation of the serial port during mode 3;

[0239] FIG. 56 is a diagram depicting the operation of the serial port during mode 4;

[0240] FIG. 57 is a diagram illustrating a typical block/frame for S/PDIF data;

[0241] FIG. 58 is a diagram of the typical serial subframe;

[0242] FIG. 59 is a diagram of the coupling between the Codec and a wavetable synthesizer;

[0243] FIG. 60 is a diagram of the timing of the exchange of data between the codec and the wavetable synthesizer;

[0244] FIG. 61 is a test bit chart describing this mode;

[0245] FIG. 62 is a diagram of microcontroller memory map in Test Mode;

[0246] FIG. 63 is a diagram of the pinout of the codec device;

[0247] FIG. 64A is a diagram of the external microphone circuit;

[0248] FIG. 64B is a diagram of an example of a phantom, power microphone circuit;

[0249] FIG. 65 is a diagram of a circuit that may be used to drive the Line Out and Headphones;

[0250] FIG. 66 is a diagram of an alternate mixer section 6400;

[0251] FIG. 67A is a diagram of the control register holding the Version and ID bets in an alternate embodiment;

[0252] FIG. 68 is a diagram of the bitfields of the FAB Port ID Register in alternate embodiments;

[0253] FIG. 69A is a diagram of the bitfields of the Command Register in alternate embodiments;

[0254] FIG. 69B is a diagram of the bitfields of the Program RAM Access End Register in alternate embodiments;

[0255] FIG. 70 is a diagram of the PnP status register configuration when Crystal Key 2 is employed;

[0256] FIG. 71A is a diagram of the bitfields of the Miscellaneous Control Register in alternate embodiments;

[0257] FIG. 71B is a diagram of the bitfields of the Power Down Control Register 1 in alternate embodiments;

[0258] FIG. 71C is a diagram of the bitfields of Power Down Control Register 2 in alternate embodiments;

[0259] FIG. 72 is a diagram defining the register location for the watchdog timer status bit;

[0260] FIG. 73 is a diagram of the bitfields of the interrupt select register;

[0261] FIG. 74 is a diagram of the modem mask register in alternate embodiments;

[0262] FIG. 75A is a diagram of the analog stereo expansion circuitry in alternate embodiments;

[0263] FIG. 75B is a diagram illustrating the frequency response of the analog expansion circuitry of FIG. 75A;

[0264] FIGS. 75C and 75D are diagrams of the 3D Sound/Serial Interface Control and 3D Sound Control register, respectively;

[0265] FIG. 76 is a diagram representing the serial interface connection of an accelerator/ZVPORT with an alternate embodiment of the codec;

[0266] FIG. 77 shows the connection of wavetable synthesizer 134 with the alternate embodiment of the codec;

[0267] FIG. 78 is a diagram of the timing for the Internal SCLK Mode, where 16-Bit Data is shown;

[0268] FIGS. 79A and 79B and diagrams of the I²S data format;

[0269] FIG. 80 is a diagram illustrating the ZV Port Audio Interface timing;

[0270] FIG. 81 is a diagram emphasizing one digital audio path for the alternate embodiments;

[0271] FIG. 82 depicts the bitfields of the 3D Sound/Serial Interface Control Register;

[0272] FIGS. 83 and 84 are diagrams showing Codec registers I17 and I23 in the alternate embodiments;

[0273] FIG. 85 is a diagram of the modified codec register I26 in an alternative embodiment in which the mono support logic has been eliminated;

[0274] FIG. 86 is a diagram of a modified control register C18;

[0275] FIG. 87 is a diagram depicting miscellaneous control bits in alternate embodiments;

[0276] FIG. 88 is a diagram of the Global Status Register in alternate embodiments;

[0277] FIG. 89 is a diagram of the bitfields of the Global Configuration EEPROM Byte 2; and

[0278] FIG. 90 is a diagram of the bitfields of the DMA SP, iRQ EEPROM Byte.

[0279] The principles of the present invention and their advantages are best understood by referring to the illustrated embodiment depicted in FIGS. 1-90 of the drawings, in which like numbers designate like parts. Unless otherwise noted, hexadecimal notation is indicated by 0x???? or ????. Byte ordering of words is—high byte, low byte.

[0280] FIG. 1A is a functional block diagram of an audio codec 100 according to the principles of the present invention.

[0281] The input and output of data and control signals between codec 100 and an external ISA bus is effectuated through an I/O bus interface 101. Configuration and control block within I/O bus interface 101 allows a host, via the ISA bus, to configure codec 100 for selected operating modes, and in particular those required by the Plug and Play standard. Additionally, interface 101 allows a host on the ISA bus to set-up I/O base addressing to codec 100, define the codec 100 to ISA bus interrupt mapping, and define the DMA channel mapping for the codec 100 memory space.

[0282] Along with a microcontroller 103, bus interface supports Plug & Play 1.0 as specified by Microsoft and Intel. In particular, Plug & Play is supported generally by the circuitry shown at 106. Circuitry 106 includes configuration and control block 102 discussed above, specific logic circuitry required for the interface 107, including the codec register interface 107 and decoder 108. Circuitry 107 and 108 allow the host to configure codec operations such as the input and output mixing functions.

[0283] Microcontroller 103, which includes an Intel™ 8052 core 10 Kbytes of ROM and 1 Kbyte of RAM, also supports the Sound Blaster and MPU-401 standards. MPU-401 standard data interfaces with microcontroller 103 through dedicated interface 104 and port MIDI. For example, data may be exchanged between port MIDI and microcontroller 103 using the 8052 UART standard protocol. Interface 104 also includes logic circuitry required for hardware handshaking of data to and from microcontroller 103 and the ISA bus.

[0284] Joystick logic block 105 includes a timer-like interface to the joystick port. External Peripheral EPROM block 109 provides general purpose 8-bit data path control for interfacing to external devices such as a CDROM, modem, or synthesizer chip utilizing /XIOW, /XIOR, ><7:0>, XA <2:0>+/BRESET ports.

[0285] The codec portion of codec 100 includes digital to analog converters which convert to analog form digital data such serial audio data received through the SERIAL PORT, parallel sound data received through data port SD<7:0> to interface 101, or synthesizer data generated on chip by an FM synthesizer (discussed below).

[0286] The Codec functionality is based on D/A converters 110 and A/D converters 111 utilizing switch-capacitor filter a delta sigma modulator, respectively. The sampling frequency at which the A/D and D/A converters (111 and 110) operate is fixed at 44.1 kHz. The delta-sigma modulator for the A/D conversion is implemented with a third order algorithm. The filter for the D/A conversions is a second order switched capacitor filter, with 128 FS oversampling.

[0287] Prior to digital to analog conversion by DACs 118, Sample Rate Converters 112 convert the digital interface sampling rate of the data received from the ISA bus (normally 5.51 kHz to 50.4 kHz) to 44.1 kHz at the inputs to D/A converters 110.

[0288] Similarly, analog data from the mixer function, also described below undergo reverse sample rate conversion. Sample Rate Converters 113 convert the output sampling rate from A/D converters 111 from 44.1 kHz to between 5.51 kHz to 50.4 kHz for output to the ISA bus. Only one 16.9344 MHz clock is needed with this Sample Rate Conversion scheme. Independent sample rates for the A/D and D/A converters is also supported.

[0289] The Mixer functionality is implemented with 6-channel INPUT Mixers 114aand 114band 6-channel OUTPUT Mixers 115aand 115b. The input mixer allows data output from DACs 110 to be mixed with direct audio data, the mixed signal eventually re-converted for delivery to the ISA bus. The output data function allows for selective mixing of the data output from DACs 110 with analog sound data received directly from line in left and right (LLINE, RLINE), the auxiliary lines (LAUX, RAUX and LAUX2, LAUX1) or the microphone line (MIC). Output from the output mixer function is output directly through left, right and middle lines out (LOUT, ROUT, MOUT). The AUX2 input which is typically used for CD-ROM, features a differential input to eliminate ground loop noise. The Microphone stereo inputs can also be configured as mono differential inputs.

[0290] An FM Synthesis Engine 124 is also provided. The digital output of FM Synthesis Engine 124 is converted to analog by the Codec function, described above.

[0291] Joystick logic block 105 implements a standard interface to two joysticks. The second joystick pins are dual function in that the pins may be switched over to support Serial Port Interface 117. Special Digital Assist hardware has also been included to eliminate the need for the Host to poll the joystick data.

[0292] Audio Codec 100 incorporates DSP engine 118 to implement the industry SRS “3D” and QSound “3D” Stereo audio algorithms.

[0293] As will be discussed further below, data is input to and output from the mixing function through first-In-First-Out registers (queue) 121. Circuitry 120 allows for standard μlaw, A-law and ADPCM linear processing on both data being input to DACs 110 and output from A to D converters 111.

[0294] Synthesis interface 123 allows codec 100 to interface with an external conventional wavetable synthesizer. Sound Blaster (SB) and Windows Sound system (WSS) registers are generally shown at 127 and all discussed more fully below. Generally, these registers allow the host to set-up for industry sound protocols such as Sound Blaster and Microsoft Windows Sound System.

[0295] S/PDIF circuitry 119 supports digital data output from Serial Port formatted to the Sony Phillips Digital Interface Format. S/PDIF data can be input directly for transfer to the ISA bus, via sample rate converters 113 or sent to the mixer functions through DACs 110, through serial port 117 discussed above.

[0296] FIG. 1B is a diagram of one of a number of possible system applications for codec 100. In this case an audio accelerator 125, such as a Crystal Semiconductor CS461x audio accelerator, receives and accelerates audio from a PCI bus 126. Accelerator 125 also provides in this example a direct interface for SPDIF and/or I²S formatted audio data. Accelerator 125 exchanges data with codec 100 through a Legacy link 127. The accelerator interface of codec 100 will be discussed in detail below.

[0297] Codec 100 receives data, such as Plug & Play audio data, directly from an ISA bus 128. This data, as well as any internally generated FM synthesizer data, are passed on to the analog mixing and codec functions of codec 100. These functions also directly interface with such external devices as a joystick, MIDI source, CD player, microphone or external speakers. As discussed below, codec 100 also has provisions for interfacing with an external wavetable synthesizer.

[0298] FIG. 2 is a diagram providing a general overview of the bus structure and principle registers of Codec 100. Codec 100 is based upon three buses: bus 201 (the E_BUS); bus 202 (the I_BUS); and bus 203.

[0299] In FIG. 2, the codec functionality is generally shown at 204. Codec 204 is associated with Codec registers 205. Microcontroller 103 is associated with microprocessor written registers 206, which also store miscellaneous status bits. Registers 207 are the ISA bus written registers and also store miscellaneous status bits.

[0300] The control base and three indirect registers are shown generally at 208. Generally shown at 209 are the C8 register and digital joystick registers.

[0301] FIG. 3 is a functional block diagram of microcontroller core 103. Microcontroller core 103 is based on the Intel™ 8052 microcontroller. Core 103 is used in conjunction with 10 Kbytes of external ROM 301 and 1 Kbytes of external RAM 302.

[0302] The timing bases from which microcontroller 103 operates are established from external clocks by clock generation circuitry 303 and timing and control circuitry 304. Interrupts are timed by interrupt serial port timers within NSFR registers/timers 305.

[0303] Set bar registers/timers 305 also support two 8-bit I/O ports SFRAB and SFRDB.

[0304] In addition to the external memory, microcontroller 103 also includes two 56-bytes of random access memory (RAM) 306.

[0305] The instruction control and processing portion of core 103 includes instruction register 307, DPT register 308, program counter 309, program counter incrementor 310, buffer 311, program address register 312, stack pointer 313 and B register 314.

[0306] The data processing portion of core 103 includes an accumulator 315, temporary storage registers 316aand 316b, and ALU 317 and PSW circuitry 318.

[0307] I/O interface 319 allows process microcontroller 103 to communicate with ISA interface 101, external ROM 301 and external RAM 302.

[0308] Core 103 operates on a 2-phase non-overlap clock with an effective clock rate of 33.8688 MHz (2×16.9344 MHz) or 32.768 MHz (2×24.576/1.5). Core 103 and Codec functions are synchronized to minimize noise generation. The clock is generated by clock generation circuitry 303 from either the 16.9344 MHz or the 24.567 MHz crystal depending on the currently defined sample rate (oscillator 120, FIG. 1). In order to minimize clock switching disturbances, the microcontroller clock is set equal to the 16.9344 MHz crystal frequency or the 24.576 MHz crystal frequency divided by 1.5 (16.384 MHz).

[0309] Clock generator circuitry 303 and timing and control circuitry also provide a second timer (“Timer2”) for MIDI baud rate generation. The MIDI baud rate is defined as 31.25 kHz+/−1%. Hence, the frequency variation of the microprocessor clock, as different crystals are selected, violates the MIDI baud rate specification. Therefore the 16.9344 MHz crystal is always used as the clock input to Timer 2. This requires that the 16.9344 MHz crystal must always be running when MIDI is in use and the Timer 2 clock must be input on the external timer input pin (EXTCLK 2). Because microcontroller 103 samples the timer 2 clock input with a clock that is {fraction (1/12)} of the processor clock, the 16.9344 MHz crystal is divided by 17 and fed to the timer 2 input. Timer 2 is then used to perform a divide by 32 to obtain the proper MIDI baud rate. 16.9344 MHz/(32* 17)=31129 kHz which is within the +/−1% specification.

[0310] FIG. 4 is a diagram of the microcontroller 103 memory map. As shown in FIG. 4, microcontroller 103 includes three separate memory spaces as follows: ROM, Internal RAM, and External RAM.

[0311] 10 Kbytes of the microcontroller 103 64 Kbyte ROM space (at addresses 0000H to 27FFH) is used to store the program code for microcontroller 103. After power-on reset microcontroller 103 will start executing instructions from location 0000H.

[0312] PnP Serial ID is reported to the host during a PnP ISOLATION operation, discussed below, and is dependent on the following: Whether a Honst Load with PNP_UPDATE command has occurred or an EEPROM is present at Port 109, the resource data sent to the part via a Host Load (host shoot) or EEPROM, or the value seen in register I25 by the Codec 100. A default PNP Serial ID in ROM 301 identifies, among other things, the vendor port number, vendor ROM ID number, program code version and ROM resident LSFR.

[0313] A default ROM image of PnP data including the default PnP serial ID is copied from ROM 301 to RAM 302 at powerup, before an external EEPROM coupled to port 109 is detected. The image in RAM 302 is used as the operating program code. If no EEPROM is present on port 109 and no host resource shoot has been performed, the PnP resource data that was copied from ROM to RAM is used. Specifically, the PnP serial ID copied from ROM is used if no EEPROM is present or no host resource shoot has taken place.

[0314] The Default ROM PnP Image is defined in TABLE 1:

[0315] If an EEPROM is detected, the EEPROM resource data is copied over the default ROM image in RAM. Firmware then examines the EEPROM serial ID (in RAM) for the 0x0E, 0x63 Vendor EISA ID in the first two serial ID bytes. If these two bytes are not found, the RAM serial ID remains the same as the EEPROM serial ID.

[0316] If the first two bytes of EEPROM serial ID are 0x0E, 0x63, then the contents of register I25, which changes based on Bond Out, is used to determine the ‘Vendor Part ID’ portion of the PnP serial ID.

[0317] For a host resource shoot followed by a PNP_UPDATE command, the serial ID is examined for a 0x0E, 0x63 in the first two bytes. As in the EEPROM case, if these two byte are, not found, the RAM serial ID (host shoot) remains unchanged.

[0318] If the first two bytes of the host shoot serial ID are 0x0E, 0x63, then the contents of register I25 are used to determine the ‘Vendor Part ID’ portion of the PnP serial ID. The serial ID is examined and changed if necessary during the PNP-UPDATE command.

[0319] If the firmware causes an update the PnP Serial ID based on the criterion above, I25 will be read and the table scanned for a matching value in the lower five bits. If no match is found, no change will be made. If a match is found, the Vendor Part ID will be replaced with the table value, the OEM ID and serial number are preserved and a new LSFR checksum is calculated.

[0320] To facilitate segregation of EEPROM based code shoots among the various past and future pin compatible devices, a ‘Family Byte’ has been created/defined. If the EEPROM supplied Family Byte does not match the ROM expected value, the EEPROM firmware RAM patch will be ignored. The resource data, however, will be loaded normally. This byte allows the firmware to ignore patch code intended for a different release when the EEPROM has not been updated.

[0321] EEPROM Hardware configuration byte 9, RAM location 0x4004, is used by the firmware to match EEPROM code shoots to ROM firmware releases. This byte is compared to a stored ROM value for a given ROM release. If the bytes do not match, the EEPROM image load is terminated by the firmware at 0x417F, after the resource data (0x417F is the top of resource data and 0x4190 is the beginning of the firmware RAM patch table).

[0322] Support for a Digitally Assisted Joystick is included in the firmware. This feature will be discussed further below with regards to the detailed description of the Game Port. A set of commands issued by the Host which initiates actions to be taken by the microcontroller 103. The Host port is through joystick base+7, but the ROM firmware will mirror this port at joystick base+6.

[0323] Codec 100 includes a set of defined pins (Up, Down, Mute) which may be used with external switches to control the overall audio level driven out the line outputs. Microcontroller 103 is used in conjunction with Master Volume control registers I27A and I29A 205. The Master Volume Control provides a dynamic Range of +12 dB to −36 dB. The Master Volume Control will be discussed in detail in conjunction with the Codec Interface.

[0324] The firmware revision bytes are used by the host to identify which patch is present in the part and what patch options are set.

[0325] The Features Byte/REVISION Byte at 0x41BF indicates major feature sets of the embedded microcode. Each bit in this byte represents a feature or feature set. This byte is written 0x22 on powerup. This byte definition changes definition with each chip family.

[0326] The Firmware Revision Number Byte indicates the current revision of the embedded microcode patch.

[0327] FIG. 5 is a more detailed diagram of the mapping of the program RAM spacing within RAM 302. In view of FIG. 5, the program RAM of Codec 100 can now be discussed in detail.

[0328] In addition to the ROM memory 301, 1.5 Kbytes of Program RAM 302 are included for microcontroller code changes and as a storage area for Plug and Play configuration data. Because microcontroller 103 instructions may only be executed from ROM addressable memory (read only), the Program RAM is mapped into the microcontroller 103 ROM 301 address space. In order to allow the Program RAM to be written via microcontroller 103, the Program RAM is directly mapped into the microcontroller 103 external RAM memory space. In this way the Program RAM may be accessed (read/write) via microcontroller 103 MOVX instructions as well as read during ROM instruction fetches. In this way code changes may be made via the ISA Interface by loading new code into the Program (Instruction) RAM area and then changing the subroutine vector location to correspond to the new code location.

[0329] On power-up the microcontroller 103 will load Codec 100 configuration data, Plug-n-Play resource data, and RAM patch code, from external EEPROM into the Program RAM. The data stored in the Program RAM is then used to configure Codec 100 internal hardware.

[0330] The fact that the configuration and resource requirements are determined via data that is stored in Program RAM allows the configuration and resource signature of Codec 100 to modified by the host. The host downloads updated configuration and resource data through the Codec 100BA RAM Access Register, discussed further below.

[0331] The method by which the Program RAM is accessed by the microcontroller 103 is defined as follows. Strategically placed within the ROM code are a set of instructions. These instructions cause the microcontroller 103 to store an identifier in microcontroller 103 register R7 and a subroutine CALL to address 0x41C0 is made. Address 0x41C0 is located in the Program RAM patch area. Once the CALL is made to 0x41C0, patch RAM routines may read microcontroller 103 register R7 to identify where in the ROM code that the CALL to address 0x41C0 was made. In this way ROM coded routines may be replaced or modified in function by Program RAM resident patch code.

[0332] To prevent accidental execution of invalid code, when loading the Program RAM via the host, the Program RAM must be loaded in segments. The very last segment must be a one byte load to address 0x41C0.

[0333] Multiple Patch RAM entry points from ROM in locations from 0x4190 to 0x41C0. Initialization code fills all these locations with a RET (0x22) instruction. At strategic points in the ROM code, these entry points are called with the mRAMx macro (macro RAM) where ‘x’ refers to the particular entry point.

[0334] The following is an example of an MRAM macro. These macros are placed in the code source to allow RAM based code changes.

[0335] Multiple CALLs can be made to the same mRAM entry point as each use of the particular mRAMx has a unique value in R7.

[0336] If patches have not been loaded, RAM locations 0x4190 through 0x41C0 will contain a 0x22. After a patch is loaded, addresses 0x41BD through 0x41BF contain Firmware Revision data and 0x41C0 will contain a value other than 0x22. Upon a RESET or SW RESET command, the region from 0x4190 to 0x41C0 will be filled with a RET (RAM entry) opcode (0x22). The RAM entry points are identified in TABLE 2. The CALLing points, scattered throughout the ROM, CALL RAM and return. Once a host based (or EEPROM) load image is written to RAM, the code effectively vectors to the patch code when the entry point is called. A JUMP_TO_ROM command is used before loading RAM via the control port to insure code is not loaded over code that is currently executing from RAM (from a previous load).

[0337] Codec 100 will detect an existing configuration/code load sequence by identifying a RAM load starting at memory location 2090h. Codec 100 will then insure that configuration data is moved to the new RAM area. REVC Sound Blaster code is ignored. Pnp resource data RAM writes to address 2090h are captured by the Codec 100 and translated and written to address 400Ch for resource data compatibility.

[0338] The Program Ram is accessible from ISA Bus interface 101 via a Program RAM Access Register (Control_Base +5) and a Program RAM Access End Register (Control_Base +6), When either the Codec 100 Program RAM Access Register or Program RAM Access End Register is read or written by the ISA Bus, an interrupt is generated to the microcontroller 103. The microcontroller 103 reads the data and processes it. These registers locations are discussed below with regards to the Central Register.

[0339] Commands and data are written to a Program RAM Access Register. The data may be a command, command parameter data, or data to be loaded into RAM. The Codec 100 supports additional commands other than those specific to RAM access. The Program RAM Access End Register is used to terminate the command/data transfer sequence. Each Program RAM read or write sequence must be terminated with a write to the Program RAM Access End Register.

[0340] A command is executed by writing the command data value to the Program RAM Access Register. The available commands, which are also discussed in conjunction with the Control Register description, are as follows:

[0341] DISABLE_PNP,

[0342] DISABLE_CSC,

[0343] UPDATE PNP (0x5A),

[0344] RAM_LOAD (0xAA),

[0345] FINISH,

[0346] RESUME,

[0347] RAM_PTR_LOAD,

[0348] HOLD,

[0349] GO,

[0350] JUMP_TO_ROM,

[0351] SET_READ_ROM_FLAG,

[0352] SET_ACC_INT_FLAG.

[0353] A typical sequence to load the Program RAM is as follows:

[0354] 1. The Codec 100 base I/O address is configured so that the Program Access Registers are accessible:

[0355] a. the host sends 32 byte “Key” sequence; and

[0356] b. the Codec 100 base I/O address is configured by the host writing the following 8-bytes to address 0x279: 0x15, 0x02, 0x47, 0x_base address high byte, 0x_base address low byte,0x33, 0x01, 0x79.

[0357] 2. The host downloads the data to Program RAM:

[0358] a. the host sends a RAM_LOAD command by writing a 0xAA to Codec 100 base address +5;

[0359] b. the host sends a starting download address (0x4000) by writing low byte starting RAM address (0x00) to Codec 100 base +5 and writing high byte starting RAM address (0x40) to Codec 100 base +5; and

[0360] c. the host downloads the data by writing successive bytes to Codec 100 base +5.

[0361] 3. The host terminates Program RAM download by executing a write of 0x00 to Codec 100 address base +6.

[0362] 4. The host instructs Codec 100 to update configuration by sending UPDATE_PNP command and writing 0x5A to Codec 100 base address +5.

[0363] The External microcontroller 103 RAM area is used for communication to devices external to microcontroller 103. This includes Sound Blaster/MPU-401/wavetable registers and the Program RAM. FIG. 5 emphasizes the interface between microcontroller 103 and external RAM 302 and Codec 100 external registers. The IOHAD[7:0] and XDBAL[7:0] address outputs from microcontroller 103 core are decoded with read/write (RD/WR) circuitry 501 to generate strobes and read enables. Additionally, XDBAL[5:0], and IOHAD[6] are decoded to generate device decodes for all microcontroller 103 externally accessible registers. Bits XDBAL[7:0], IOHAD[3:0], and IOHAD[6] are used in accessing the Program RAM. The XDB[7:0] output from microcontroller 103 core is a bi-directional data bus over which data flows between microcontroller 103 and external devices.

[0364] As noted above, in Codec 100 internal microcontroller 103 is used to support any number of functions. These include: PnP, Sound Blaster, MPU-401, and Control Port commands. Microcontroller 103 interrupt capability (Block 305, FIG. 3) is used to call microcontroller 103 when specific ISA Bus host accesses have occurred.

[0365] The INTO interrupt input to microcontroller 103 is used for the Plug-n-Play and Crystal Key. Microcontroller 103 INT1 interrupt is used for Sound Blaster, MPU-401, and Control Port commands. Timer interrupt TR0 is used for Sound Blaster ADPCM. (These signals are shown as inputs to block 305 of FIG. 3.)

[0366] Because microcontroller 103 requires on the order of 2 usec to respond to an interrupt, the interrupting ISA Bus access is held visa a signal IOCHRDY until microcontroller 103 acknowledges the interrupt request. The way in which microcontroller 103 acknowledges each interrupt is unique.

[0367] During Plug-n-Play sequences, the INT0 input to microcontroller 103 is forced active whenever a “Plug-n-Play Key” or “Vendor Key” is received.

[0368] In order for microcontroller 103 to be able to identify specific host accesses to Sound Blaster, MPU-401, and Control Ports, Port 1 of microcontroller 103 is used to specify an 8-bit Interrupt Identification byte, the bitfields of which are shown in FIG. 6 and described as follows:

[0369] TABLE 3 describes the interrupts for the Sound Blaster and Sound System modes (where INT0, INT1, and TRO are inputs to circuitry 305, FIG. 3):

[0370] When a ISA bus Sound Blaster ADPCM DMA write occurs, this interrupt is generated to microcontroller 103. Microcontroller 103 responds by reading the data from external microcontroller 103 address 0x0C.

[0371] Significant Sound Blaster performance gains are realized by mapping Codec registers 107 directly into microcontroller 103 SFR address space. This change allows microcontroller 103 independent access to the codec registers (i.e. mixer functions) while DMA data is transferred to and from the FIFO's (discussed later).

[0372] TABLE 4 specifies the mapping of codec registers into microcontroller 103 SFR address space. The codec register R0 is only implemented to support the MCE and TRD bits. All other bits in register R0 are don't cares. Codec registers R2 and R3 function normally.

[0373] Codec 100 normally does not allow access to Codec registers 107 by the ISA Bus and microcontroller 103 at the same time. However in the case of Sound System operation with master volume control, Sound System accesses can occur simultaneously with microcontroller 103 access to the master volume control registers I27A and I29A (Codec Registers 205, FIG. 3). To address this problem a Request/Grant handshake mechanism has been developed. The timing is shown in the diagram of FIG. 7.

[0374] Two microcontroller 103 accessible bits are defined as a codec access REQUEST and GRANT. These bits are reset to zero via RESDRV and software reset via bits PM1, PM0. Microcontroller 103 sets the REQUEST bit to a one when it requires access to any codec register 205 (I27A, I29A) and when the Context Switch status is in Sound System mode. Once this bit is set the GRANT bit will be generated immediately if no ISA bus access to any codec register is in progress. Otherwise, if an ISA bus access to any codec register is in progress then the generation of GRANT will be delayed until the current ISA bus cycle has finished.

[0375] Once the GRANT bit is set, any further ISA Bus cycles to any codec registers are held off via the IOCHRDY signal. Microcontroller 103 is then free to access registers Codec 127A and 129A without contention with the ISA Bus codec register accesses. Once microcontroller 103 has finished its access, it clears the REQUEST bit. The clearing of the REQUEST bit also clears the GRANT bit which in turn releases IOCHRDY. The current ISA Bus codec access being held is then allowed to complete.

[0376] The REQUEST/GRANT bits are mapped into microcontroller 103 Port 3 register. For test purposes the bits available on Port 3 are also available at microcontroller 103 external address 0x42. All bits are read only except for the REQUEST bit which is read/write. The mapping of the Port 3 bits at microcontroller 103 external address of 0x42 allows external chip access via Test Mode 4 (discussed below). The function of these bits can thus be verified with and without microcontroller 103 operation.

[0377] Port 3 Bit Definitions are shown in FIG. 8 and can be described as follows:

[0378] P3.3—REQUEST—Read/Write.

[0379] This is set to a one when microcontroller 103 is updating codec registers and there is possible contention with ISA bus accesses (Sound System mode). After polling for GRANT=1, microcontroller 103 may access codec registers as needed. After microcontroller 103 has finished its codec accesses, the REQUEST bit should be set to zero to re-enable ISA access to the codec registers.

[0380] P3.4—GRANT—Read Only.

[0381] This bit is polled by microcontroller 103 after setting the REQUEST bit=1. When GRANT is equal to one, microcontroller 103 may access codec registers without contention with the ISA bus. When GRANT=1 and subsequent ISA codec accesses are held off via IOCHRDY until the REQUEST bit is set to zero by microcontroller 103.

[0382] In Codec 100, microcontroller 103 is used to perform and control a variety of functions. The microcontroller 103 controls these functions through a number of registers that are mapped into microcontroller 103 external memory space. These registers are shown generally at I27 FIG. 1. An external device memory map is provided in TABLE 5:

[0383] FIG. 9 is a diagram providing an overview of the circuitry of Codec 100 supporting a Plug & Play (PnP) interface to external ISA bus 130. Included within ISA Interface 101 is an interface to microcontroller 103 core (including control logic 901, data buffer 902, and address latch 903), an interface to Codec 204, and configuration logic 904 that is Intel/Microsoft “Plug & Play” (PnP) compatible. ISA interface 101 also generally includes data buffers 905, circuitry 906 for generating signal IOCHRDY from wait state status information, DMA mapping logic 907 and Interrupt Mapping logic 908.

[0384] Codec 100 operates in conjunction with a number of other associated Plug & Play devices 909 also coupled to the ISA bus of independent blocks 909 that are mapped to the ISA Bus. Each block 909 has associated with it a set of resource requirements and associated configuration registers, organized into groups called physical devices. TABLE 6 below lists the maximum resource requirements for each physical device. The Intel/Microsoft Plug & Play specification organizes devices into logical groupings (logical devices) comprised of one or more physical devices.

[0385] The Plug & Play Specification 1.0a describes a hardware and software mechanism whereby ISA cards are isolated, identified, and then optimally allocated within a system's resource environment. To be Plug & Play compatible, each interface to the ISA bus, such as ISA 10 Interface logic 101, must respond appropriately to a defined sequence of configuration commands. In Codec 100, microcontroller 103, in conjunction with logic is used to implement the various Plug & Play commands and responses. The end result of a Plug & Play configuration sequence is that the I/O base address decodes, DMA channel selects, and interrupt selects for the various Codec 100 circuit blocks are programmed to specific values.

[0386] FIG. 10 is a diagram emphasizing the configuration/interface logic for a PnP compatible device, for example Plug and Play Interface 106 of Codec 100. Configuration/interface 106 includes an address decoder 1001 which receives control bits and 12 address bits from the ISA bus, an address register 1002, linear feedback shift register 1003, plug and play (PnP) registers 1004, output enable circuitry 1005 and register output selector 1006. PnP registers include card control register 1004a,logical device control register 1004band logical device configuration register 1004c.The theory of Plug and Play operation can now be described in conjunction with FIG. 10A, and the associated functional diagram of FIG. 11, assuming Codec 100 is the PnP compatible device under configuration.

[0387] After a power-up sequence or hardware reset via RESDRV, Codec 100 is in the Wait_for_Key state. In this state Plug & Play devices monitor writes to address 0x279. Specifically, Linear Feedback Shift Register (LFSR) 1003 is used in hardware to detect a matching byte sequence. If at any time the data written to address 0x279 does not match the LFSR then the LFSR is reset. The cycle continues until an Initialization Key is received. Once the “Key” has been received, microcontroller 103 writes address 0x13 (the P&P State Register) to a 0x1 so that the configuration logic is now in the “Sleep State.”

[0388] FIG. 10B is a diagram generally illustrating the functional elements of LFSR 1003, including a series of storage/shift elements 1201 and logic 1202. LFSR 1003 also includes logic that enables an additional key sequence to be detected. This additional key sequence is referred to as the “Vendor Key”. This Key allows the Plug & Play logic to be bypassed so that Plug & Play configuration registers 1004 may be programmed directly.

[0389] Plug & Play Key Sequence

[0390] 6A, B5, DA, ED, F6, FB, 7D, BE, DF, 6F, 37, 1B, 0D, 86, C3, 61 B0, 58, 2C, 16, 8B, 45, A2, D1, E8, 74, 3A, 9D, CE, E7, 73, 39

[0391] Vendor Key Sequence

[0392] 96, 35, 9A, CD, E6, F3, 79, BC 5E, AF, 57, 2B, 15, 8A, C5, E2 F1, F8, 7C, 3E, 9F, 4F, 27, 1309, 84, 42, A1, D0, 68, 34, 1A

[0393] In the Sleep State, a P&P device, such as circuitry 1904 waits for a Wake[CSN] command with write data set 0x00. All accesses to P&P registers 1004 in this state (0x279, 0xA79) cause the logic to force IOCHRDY low (hold current bus cycle) and set an appropriate bit in microcontroller Port 1. Once microcontroller 103 reads either address 0x10 or 0x11, the Port I bit is cleared and IOCHRDY is released. After the Wake[CSN] is detected microcontroller 103 sets a serial identifier/resource data pointer to the beginning and writes a 0x2 to microcontroller 103 address 0x13 to transition the logic to the Isolation State.

[0394] The first time Plug&Play device enters the Isolation State, the Read_Data port address is set using a Set_RD_DATA port command. Codec 100 hardware detects this command and latches the Read_Data port address into a register 2004C and uses it to decode accesses to the Read_Data port 901.

[0395] Next, 72 pairs of reads are performed to a PnP Serial Isolation register within registers 1004c.The Serial Isolation register holds a 72-bit serial identifier. The 72-bit Serial Identifier is used in identifying and isolating individual Plug & Play devices. Microcontroller 103 uses the transition to the Isolation State to retrieve the first bit of the 72-bit serial identifier and writes this bit to microcontroller address 0x14 bit 0.

[0396] The isolation sequence proceeds as follows. If the current bit, of the 72-bit serial identifier, is a one then the logic forces a 0x55 onto the ISA data bus when Read Data port 910 is read. When Read_Data port 910 is read a second time, then the logic forces a 0xAA onto the ISA Data bus. After the Read_Data port is read the second time microcontroller 103 is notified via a bit to Port 1 and the next bit of the serial identifier is written to microcontroller 103 address 0x14 bit 0. This sequence continues until either the logic detects an isolation lose condition or all 72 bits have been read.

[0397] Otherwise, if the current bit is a zero, the configuration logic tri-states the ISA data bus buffer and monitors the data on the ISA data bus during a read of the Read_Data port 910. If the logic detects that another P&P device is driving the ISA data bus (i.e. detects a 0x55, 0xAA sequence) then the ILS (Isolation lose) bit is set in microcontroller 103 Command/Status register. Upon microcontroller 103 being notified of an Isolation lose the logic is then transitions back to the Sleep State (microcontroller 103 address 0x13=01).

[0398] If Codec 100 does not lose isolation during the current isolation sequence then a CSN (Card Select Number) is assigned by the PnP host software. The CSN is a unique value that is assigned to each isolated Plug & Play device. The CSN is used by the host to select individual Plug & Play devices during configuration. Microcontroller 103 stores this CSN in memory and uses it when detecting a Wake[CSN] command. The assigning of the CSN number causes microcontroller 103 to transition to the Config State which in turn causes microcontroller 103 to write address 0x13 to a 0x3.

[0399] Card resource data may only be read while in the Config State. A card may get to the Config State by one of two methods: in response to “winning” the serial isolation protocol and having a CSN assigned, as discussed above, or in response to receiving a Wake[CSN] command that matches the card's CSN. Only one Plug & Play device is in the Config State at one time. In this state, resource data are retrieved and the host software uses this information to program the corresponding configuration register 2004c.Once the resource data has been accessed then the configuration register 2004care written and each logical device is activated.

[0400] In Codec 100 all accesses to PnP registers 2004 in the Configuration State (write 0x279, write 0xA79, read Read_Data port except resource data reads) result in IOCHRDY being forced low (hold current bus cycle) and the setting of a bit in microcontroller Port 1. Once microcontroller 103 reads either address 0x10, 0x11, or writes 0x12, respectively, then the particular Port 1 bit is cleared and IOCHRDY is released.

[0401] During resource data reads a polled handshake mechanism is used. Logic in Codec 100 outputs a ready indicator when a read from the PnP status register occurs. This ready bit is initially set “not ready” until microcontroller 103 outputs the first byte of a resource data read. The bit then remains ready until an ISA bus cycle occurs to read the byte. The occurrence of the ISA bus resource data read resets the ready bit to its “not ready” condition. A bit located on Port I (RDR P1-3 set=one) is used to indicate to microcontroller 103 when the resource data byte has been read. Microcontroller 103 then outputs the next resource byte (microcontroller 103 address-0x12) and the RDR bit is reset to zero. Configuration register data are written one logical device at a time. The individual logical device is selected by the Plug&Play Configuration Manager writing the logical device number to PnP address-0x7. Microcontroller 103 detects this and enables access to the appropriate logical device configuration registers.

[0402] After all logical devices have been configured logical device activation occurs one logical device at a time. Microcontroller 103 detects this and then sets the appropriate bit in the Logical Device Activate Register (microcontroller 103 address=0x1F). Each logical device is now enabled onto the ISA bus and should respond to the I/O address range, DMA channel, and interrupts that have been defined.

[0403] Plug-n-Play requires that the Plug-n-Play device contain data that indicates what system resources it requires. These resources may include memory space, I/O space, DMA channels, or Interrupts. In the case of Codec 100 the resources include a number of system I/O spaces, DMA channels, and Interrupts. Codec 100 supports two methods (EEPROM loaded, or host downloaded) of storing resource data. Both of these methods are flexible in that the resource data can be customized to support particular requirements.

[0404] Plug and Play cards return read-only configuration information in two formats. The serial identifier is returned bit-wise by the Plug and Play devices in response to reads from the Serial Isolation register. This information is returned in a serial format to facilitate the Plug and Play device selection algorithm described earlier. Plug and Play cards also provide resource data sequentially a byte at a time in response to reads from the Resource Data register. The resource configuration data completely describes all resource needs and options of the device and includes a header followed by a set of resource data structures which end with an End Tag:

[0405] The header holds the 72 serial identifier that is used during the Isolation sequence described earlier in TABLE 7.

[0406] The 32-bit Vendor ID (Bytes 0-3) is an EISA Product Identifier (ID). This ID consists of:

[0407] (1) Bits[15:0] are a three character compressed ASCII EISA ID, (Compressed ASCII is defined as 5 bits per character, “00001”=“A” . . . “11010”−“Z”. This field is assigned to each manufacturer by the EISA administrative agent); and

[0408] (2) bits[31:16] define a manufacturer specific product number and revision. It is the responsibility of each vendor to select unique values for this field.

[0409] The purpose of this field is to serve as a unique board identifier that allows Plug and Play card selection through the isolation algorithm described earlier.

[0410] The 32-bit serial number (Bytes 4-7)is used only in the isolation process for selection of individual Plug and Play ISA cards. This unique number differentiates between multiple cards with the same Vendor ID when they are plugged into one system. If this feature is not supported then this field is returned as “FFFFFFFF.” Lack of a unique serial number implies that only one instance of a Vendor ID can be supported in a system.

[0411] The checksum field (Byte 8) is used to ensure that no conflicts have occurred while reading the device identifier information. The checksum is generated by using a LFSR mechanism 1007 shown in FIG. 10C. LFSR 1007 includes a series of storage/shift elements 1008 and a pair of exclusive-OR (XOR) gates 1009 and 1010. The LFSR resets to 0x6A upon receiving the WAKE[CSN] command. The next shift value for the LFSR is calculated as LFSR[1] XOR LFSR[0] XOR Serial Data. The LFSR value is shifted right one bit at the conclusion of each pair of reads to the Serial Isolation register. The LFSR[7] is assigned the next shift value again described above.

[0412] As indicated above, Plug and Play resource data fully describes all resource requirements of a Plug and Play device as well as resource programmability and interdependencies. Plug and Play resource data are supplied as a series of “tagged” data structures. Two types are supported: large items and small items. The first byte defines the type and size and is followed by one or more bytes of actual information. Bit [7] of the first byte is used as the tag identifier to differentiate between small and large data types.

[0413] A Plug and Play logical device may use any number of resources and any combination of small item or large item data types. The general format is:

[0414] (1) Plug and Play version number type;

[0415] (2) Identifier string resource type;

[0416] (3) Logical device ID resource type which identifies;

[0417] a) Any compatible device ID resource type for this logical device;

[0418] b) Resource data types to match what the function uses (IRQ, memory, I/O, DMA)-the order is not important; and

[0419] c) Any dependent functions needed if the Plug and Play card is configurable. The order of the resource data establishes the binding to the configuration registers. (Note: Step 3 is repeated for each logical device present on the Plug and Play card.); and

[0420] (4) End tag resource type to indicate the end of resources for this Plug and Play card.

[0421] The order of resource descriptors is significant because configuration registers are programmed in the same order that descriptors are read. This may be important in some hardware implementations. Further, in the case of Dependent Functions it may be necessary to include null descriptors (“filler”) in order to maintain the desired descriptor-to-register mapping regardless of which Dependent Function is programmed by the software.

[0422] The 3-byte Plug & Play Version Number identifies the version of the Plug and Play specification with which the card is compatible. A vendor specific number is included and may be used by a device driver to verify the version of the card. TABLE 8 summarizes these version numbers.

[0423] The Identifier String is an ASCII string used to identify the card type or function. This string is displayed to the user during a Plug n Play sequence. Example: “Crystal Semiconductor Codec 100 Sound Chip.” TABLE 9 summarizes the ASCII string fields and fields related thereto.

[0424] Each logical device must be defined in order for the operating system to be able to allocate resources and identify and load appropriate device drivers. For each logical device the following data structures are required:

[0425] Logical Device ID

[0426] Configuration

[0427] DMA

[0428] IRQ

[0429] I/O Descriptors

[0430] ANSI ID String

[0431] The following data structures are optional:

[0432] Compatible Device ID

[0433] The Logical Device ID provides a mechanism for uniquely identifying multiple logical devices embedded in a single physical board. The fields of the Logical Device ID are summarized in TABLE 10. The format of the logical device ID is identical to the Vendor ID field discussed above:

[0434] (1) bits[15:0]—three character compressed ASCII EISA ID) and compressed ASCII is defined as 5 bits per character, “00001”=“A” . . . “11010”=“Z”. This field must contain a valid EISA ID, although it is not required to have the same 3 letters as the Vendor ID); and

[0435] (2) bits[31:16]—manufacturer-specific function number and revision. It is the manufacturer's responsibility to have unique bits[31:16] for different functions.

[0436] This identifier may be used to select a device driver for the device. Because of this, Logical Device IDs must be uniquely associated with a specific function. However, there is no need for the Logical Device ID itself to have a unique value, either on a card, or across cards. For instance, a card that implements two communications ports may use the exact same Logical Device ID for both. Similarly, two different products (different Vendor IDs) may both implement the same function, and therefore will use the same Logical Device ID for it. The Logical Device ID is required on all cards. On single-function cards, the Logical Device ID may be the same as the card's vendor ID.

[0437] A compatible device ID provides the IDs of other devices with which the given Plug n Play device (e.g., Codec 100) is compatible. The host operating system uses this information to load compatible device drivers if necessary. There can be several compatible device identifiers for each logical device. The order of these device IDs may be used by the operating system as a criteria for determining which driver should be searched for and loaded first. TABLE 11 summarizes the fields of the Compatible Device ID.

[0438] As an example of the use of compatible IDs, consider a card vendor who ships a device with logical ID 0xABCD0000. At a later date, this vendor ships a new device with a logical ID 0xABCD0001. This new device is 100% compatible with the old device but also has added functionality. For this device, the vendor could include the Compatible device ID 0xABCD0000. In this case, the exact driver for 0xABCD0001 will be loaded if it can be located. If the driver for 0xABCD0001 can not be found, the driver for device 0xABCD0000 will be loaded for the device.

[0439] The IRQ data structure indicates that the Plug n Play device uses an interrupt level and supplies a mask with bits set indicating the levels implemented in the device. For a standard ISA implementation there are 16 possible interrupt levels so a two byte field is used. This structure is repeated for each separate interrupt level required. TABLE 12 summarizes the fields of the IRQ data structure.

[0440] The DMA data structure, summarized in TABLE 13, indicates that the PnP device uses a DMA channel and supplies a mask with bits set indicating the channels actually implemented in this device. This structure is repeated for each separate channel required.

[0441] Each logical device requires a set of resources. This set of resources may have interdependencies that need to be expressed to allow arbitration software to make resource allocation decisions about the logical device. Dependent functions are used to express these interdependencies. The data structure definitions for dependent functions are shown in TABLE 14.

[0442] Start Dependent Function fields may be of length 0 or 1 bytes. The extra byte is optionally used to denote priority for the resource group following the Start DF tag. If the extra byte is not included, this indicates the dependent function priority is ‘acceptable’. If the Priority byte is included, the priorities are defined in TABLE 15:

[0443] Note that if multiple Dependent Functions have the same priority, they are further prioritized by the order in which they appear in the resource data structure. The Dependent Function which appears earliest (nearest the beginning) in the structure has the highest priority, and so on.

[0444] TABLE 16 defines the structure for end dependent functions.

[0445] Note that only one End Dependent Function item is allowed per logical device. This enforces the fact that Dependent Functions are not nettable.

[0446] There are two types of descriptors for I/O ranges. The first type of descriptor is a full function descriptor for programmable ISA cards defined in TABLE 31. The second type of descriptor is a minimal descriptor (Fixed Location I/O Descriptor) for ISA cards with fixed I/O requirements and use a 10-bit ISA address decode. The second type of descriptor is defined in TABLE 17. The first type of descriptor can also be used to describe fixed 1/0 requirements for ISA cards that require a 16-bit address decode. This is accomplished by setting the range minimum base address and range maximum base address to the same fixed I/O value.

[0447] The vendor defined resource data type is for vendor use and is defined in TABLE 19.

[0448] The End Tag, defined in TABLE 20, identifies an end of resource data. If the checksum field is zero, the resource data are treated as if it checksummed properly. Configuration proceeds normally.

[0449] As indicated above, Plug-n-Play organizes physical devices into groups of logical devices. A logical device may be comprised of up to four non-contiguous Memory Address ranges, eight non-contiguous I/O Address ranges, two Interrupts, and two DMA channels. Codec 100 only supports I/O, interrupts, and DMA.

[0450] Codec 100 has a fixed physical-to-logical device mapping summarized in TABLE 21. The Plug-n-Play resource data must match the Logical-to-Physical device mapping defined in TABLE 20. Controller 103 firmware translates Plug-n-Play logical device configuration cycles into writes of the appropriate hardware configuration registers.

[0451] To support environments in which Codec 100 is located directly on Motherboards, a Host Load mechanism is used to download Plug-n-Play resource data to Codec 100. In this environment the Motherboard BIOS loads the resource data into Codec 100 prior to any Plug-n-Play activity taking place.

[0452] To download configuration and Plug-n-Play resource data Codec 100 Control logical device must first be mapped into the host I/O space. This is accomplished by sending the Plug-n-Play key sequence described above followed by an isolation and configuration sequence to configure the Control logical device. Once the Control logical device has been mapped then the Plug-n-Play resource data may be loaded into Codec 100 via the Control Port at Control base +5.

[0453] For non-motherboard applications and external EEPROM is required to load configuration and resource data into Codec 100. On power-up microcontroller 103 checks for the existence of the EEPROM. If one is found then the EEPROM data, including Plug-n-Play resource data are down loaded from the EEPROM. A description of EEPROM formats that are supported by Codec 100 is discussed in detail below.

[0454] In Codec 100 the Plug-n-Play compatibility is accomplished through the use of the internal microcontroller 103 and logic gates. Microcontroller 103 interfaces to the external logic through the use of memory mapped registers. These registers control the mapping of the various Codec 100 physical devices as well as provide a means to control the external logic during certain phases of Plug-n-Play sequences.

[0455] As mentioned immediately above a set of registers is memory mapped into microcontroller 103 address space. Microcontroller 103 accesses these registers through specific memory access instructions (MOVX). To facilitate hardware test modes of Codec 100, all Plug & Play configuration registers are reset to default values on power-up. These default values will remain intact only if microcontroller 103 is not operating; which is the case for Test Modes 3, 4, 5, and 6 (discussed below). In non-test mode (normal) operation of Codec 100, microcontroller 103 will modify all the configuration defaults to off/disabled states.

[0456] FIGS. 12A-12Y are diagrams of the bitfields of the ISA/PNP Configuration registers.

[0457] FIG. 12A is a diagram of the bitfields of the Plug & Play Address-Register at microcontroller 103 Address 0x10. This register stores the last 8-bit data value written to the Plug & Play_Address Register (location 0x279).

[0458] FIG. 12B is a diagram of the bitfields of Plug & Play Write_Data_Port at microcontroller 103 Address 0x11. When this address is read the current data on the ISA data bus is enabled onto Codec 100 internal data bus. The read in response to an ISA bus write to the Plug & Play Write_Data register location 0xA79. This register is written by microcontroller 103 during resource data reads.

[0459] FIG. 12C is a diagram of the bitfields of the Plug & Play Read_Data_Register at microcontroller 103 Address 0x12. This register is written by microcontroller 103 in response to a read from the Plug & Play Read_Data_Port.

[0460] FIG. 12D is a diagram of the bitfields of the Plug & Play State Register at microcontroller 103 Address 0x13. These bits are updated by microcontroller 103 as a Plug & Play sequence progresses through its various states. The hardware requires these bits in order to effect the appropriate responses during a Plug & Play sequence. The decoding to PS0 and PS1 fields is shown in Table 22:

[0461] FIG. 12E is a diagram of the bitfields of the Plug & Play Control/Status register at microcontroller 103 Address 0x14. This register is reset to zero when RESDRV is high. The decoding is as follows:

[0462] Isolation Lose ILS—this bit indicates that the Plug & Play hardware has lost isolation during the current isolation sequence;

[0463] Serial Identifier/Sound Blaster Busy SID/SBB—this bit is written by microcontroller 103 during an isolation sequence and holds a serialized version of the 72-bit identifier. The hardware uses this bit to determine how the data bus should be driven (0x55/0xAA or tri-state) during a PnP Isolation sequence, as well as during Sound Blaster operation to enable/disable OR'ing of the current SB Busy with the codec playback DMA request;

[0464] Enable E2PROM EEP—this bit when set to a one enables the Port 1 pins 6 and 7 onto the EDATA[0] and EA[0] pins; and

[0465] EA2 Function—when 0 will force XCTL0 onto the EA2 pin. When this bit is=1, then the normal EA2 function is output on the EA2 pin.

[0466] FIG. 12F is a diagram of the bitfields of the Sound System Base Address Low at microcontroller 103 Address 0x15. This register is reset to zero when RESDRV is high and is used to specify the lower 6-bits of the 12-bit Sound System Codec base address. The number of consecutive locations decoded at this base address is fixed at four bytes.

[0467] FIG. 12G is a diagram of the bitfields of the Sound System Base Address High register at microcontroller 103 Address 0x16. This register is reset to zero when RESDRV is high and is used to specify the upper 4-bits of the 12-bit Sound System Codec base address.

[0468] FIG. 12H is a diagram of the bitfields of the Control Base Address Low register at microcontroller 103 Address 0x17. This register is reset to zero when RESDRV is high and is used to specify the lower 6-bits of the 12-bit Control base address. The number of consecutive locations decoded at this base address is fixed at eight bytes.

[0469] FIG. 12I is a diagram of the bitfields of the Control Base Address High register at microcontroller 103 Address 0x18. This register is reset to zero when RESDRV is high and is used to specify the upper 4-bits of the 12-bit Control base address.

[0470] FIG. 12J is a diagram of the bitfields of the Sound Blaster Base Address Low register at microcontroller 103 Address 0x19. This register is reset to zero when RESDRV is high and is used to specify the lower 4-bits of the 10-bit Sound Blaster base address. The number of consecutive locations decoded at this base address is fixed at sixteen bytes.

[0471] FIG. 12K is a diagram of the bitfields of the Sound Blaster Base Address High register at microcontroller 103 Address 0x1A. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit Sound Blaster base address.

[0472] FIG. 12L is a diagram of the bitfields of the Synth Base Address Low register at microcontroller 103 Address 0x1B. This register is reset to zero when RESDRV is high and is used to specify the lower 6-bits of the 10-bit Synthesizer OPL3 base address. The number of consecutive locations decoded at this base address is fixed at four bytes.

[0473] FIG. 12M is a diagram of the bitfields of the Synth Base Address High register at microcontroller 103 Address 0x1C. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit Synthesizer OPL3 base address.

[0474] FIG. 12N is a diagram of the bitfields of the MPU-401 Base Address Low register at microcontroller 103 Address 0x1D. This register is reset to zero when RESDRV is high and is used to specify the lower 7-bits of the 10-bit MPU-401 base address. The number of consecutive locations decoded at this base address is fixed at two bytes.

[0475] FIG. 12O is a diagram of the bitfields of the MPU-401 Base Address High register at microcontroller 103 Address 0x1E. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit MPU-401 base address.

[0476] FIG. 12P is a diagram of the bitfields of the Game Port Base Address Low register at microcontroller 103 Address 0x1F. This register is reset to zero when RESDRV is high and is used to specify the lower 5-bits of the 10-bit Game Port base address. The number of consecutive locations decoded at this base address is fixed at eight bytes.

[0477] FIG. 12Q is a diagram of the bitfields of the Game Port Base Address High register at microcontroller 103 Address 0x20. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit Game Port base address.

[0478] FIG. 12R is a diagram of the bitfields of the CDROM Base Address Low register at microcontroller 103 Address 0x21. This register is reset to zero when RESDRV is high and is used to specify the lower 6-bits of the I/O-bit CDROM base address. The number of consecutive locations decoded at this base address is fixed at four bytes.

[0479] FIG. 12S is a diagram of the bitfields of the CDROM Base Address High register at microcontroller 103 Address 0x22. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit CDROM base address.

[0480] TABLE 23 describes the bit decodings for the interrupt select registers depicted in FIGS. 12T-12Y, and discussed below, where IRQA-IRQE describe the interrupt pins enabled by the interrupt mapping value written into the given register.

[0481] FIG. 12T is a diagram of the bitfields of the Synth Interrupt Select register at microcontroller 103 Address 0x23. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the Synthesizer interrupt is mapped.

[0482] FIG. 12U is a diagram of the bitfields of the Sound Blaster Interrupt Select register at microcontroller 103 Address 0x24. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the Sound Blaster interrupt is mapped.

[0483] FIG. 12V is a diagram of the bitfields of the Sound System Interrupt Select register at microcontroller 103 Address 0x25. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the Synthesizer interrupt is mapped.

[0484] FIG. 12W is a diagram of the bitfields of the MPU-401 Interrupt Select register at microcontroller 103 Address 0x26. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the MPU-401 interrupt is mapped.

[0485] FIG. 12X is a diagram of the bitfields of the CDROM Interrupt Select register at microcontroller 103 Address 0x27. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the CDROM interrupt is mapped.

[0486] FIG. 12Y is a diagram of the bitfields of the Control Interrupt Select register at microcontroller 103 Address 0x28. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the Control interrupt is mapped.

[0487] Microcontroller 103 I/O on port 1 is a ISA bus monitoring port. The data present on the I/O port 1 pins indicates to microcontroller 103 what is happening on the ISA Bus as far as Plug & Play register accesses are concerned. Once Codec 100 has made a transition out of the Wait for-Key State then Port 1 is polled for Plug & Play register accesses. FIG. 13 defines PnP Port I, where:

[0488] AWR-Address Write Pending—when set to a one indicates that a write to the PnP Address Register(0x279) has occurred. When this bit is a one during Sleep and Configure states, IOCHRDY will be forced high, effectively holding the current ISA bus cycle until microcontroller 103 has accessed microcontroller 103 address 0x10. This bit is cleared to zero upon a read of microcontroller 103 address 0x10.

[0489] DWR-Data Write Pending—when set to a one indicates that a write to the PnP Data Write Register has occurred. When this bit is a one during Sleep and Configure states, IOCHRDY WILL be forced high, effectively holding the current ISA bus cycle until microcontroller 103 has accessed microcontroller 103 address 0x11. This bit is cleared to zero upon a read of microcontroller 103 address 0x11.

[0490] DRD-Data Read Pending—when set to a one indicates that a read from the PnP Read Data Port has occurred. This bit is cleared to zero upon a write to microcontroller 103 address 0x12 or during an Isolation sequence by a write to microcontroller 103 address 0x14.

[0491] KEY/RDR—Key/Resource Data Read—When Codec 100 is in a WAIT_FOR_KEY state and a “PnP Key” or “Crystal Key” sequence (discussed above) is detected, microcontroller 103 is interrupted via INT0. This bit then indicates what “Key” was detected. KEY=0 for “PnP Key” and KEY=1 for “Crystal Key”. Alternately during a Resource Data Read sequence this bit when set to a one indicates that the current resource data byte has been read and that the ISA interface is ready for the next byte. This bit is cleared to zero upon a write to microcontroller 103 address 0x12. This bit is also set when a “Crystal Key Sequence” has been received.

[0492] For applications that do not require Plug-n-Play capability the “Crystal Key” backdoor mechanism may be used to program the configuration of Codec 100. Each Codec 100 logical device is configured one at a time. The configuration data must match or be a subset of the logical device definition described above. All commands including the “Crystal Key” sequence are written to the Plug-n-Play port at ISA Bus address 0x279. The following commands are used in performing a configuration sequence.

[0493] Typical Programming Sequence bypassing the PnP interface is as follows:

[0494] The instructions and commands in the foregoing exemplary programmed sequence can be described as follows:

[0495] Send Crystal Key—The “Crystal Key” is not a command but a sequence of 32 bytes that are written in succession. When Codec 100 receives the correct sequence of 32 bytes the Plug-n-Play logic of Codec 100 transitions to the Configuration State. The configuration registers of Codec 100 may only be modified when Codec 100 is in the Configuration State.

[0496] Program the CSN (Card Select Number) 0x6—The CSN number for Codec 100 may optionally be programmed by executing this command. This command is executed by writing a 0x6 followed by the 8-bit CSN number. If this command is not used then the CSN number for Codec 100 will default to zero.

[0497] Select Logical Device (0x15)—The configuration registers of Codec 100 are programmed one logical device at a time. This command is executed by writing a 0x15 followed by an 8-bit logical device number. Codec 100 supports eight physical devices (0:7) as previously noted.

[0498] IO Port Base Address 0 (0x47)—This command is executed by writing a 0x47 followed by a write of the low byte of the I/O base address, and a write of the high byte of the I/O base address.

[0499] IO Port Base Address I (0x48)—This command is executed by writing a 0x48 followed by a write of the low byte of the I/O base address, and a write of the high byte of the I/O base address.

[0500] IO Port Base Address 2 (0x42)—This command is executed by writing a 0x42 followed by a write of the low byte of the I/O base address, and a write of the high byte of the I/O base address.

[0501] Interrupt Select 0 (0x2A)—This command is executed by writing a 0x22 followed by a write of the interrupt line to generate an interrupt on.

[0502] Interrupt Select 1 (0x27)—This command is executed by writing a 0x27 followed by a write of the interrupt line to generate an interrupt on.

[0503] DMA Select 0 (WA)—This command is executed by writing a 0x2A followed by a write of the DMA channel that is to be used.

[0504] DMA Select 1 (0x25)—This command is executed by writing a 0x25 followed by a write of the DMA channel that is to be used.

[0505] Activate Logical Device (0x33)—This command is executed by writing a 0x33 followed by a byte of one to activate the currently selected logical device.

[0506] Deactivate Logical Device (0x33)—This command is executed by writing a 0x33 followed by a byte of zero to deactivate the currently selected logical device.

[0507] Activate Codec 100 (0x79) The configuration data are processed and transferred to the appropriate Codec 100 registers upon execution of this command. This command puts Codec 100 into the Wait_For_Key_State.

[0508] Once a Plug & Play sequence has transpired each logical device, including Codec 100, will have an I/O base address assigned to it. This assigned base address is stored in each I/O base address register. ISA bus address bits A12 . . . A0 are compared with the values stored in the I/O base address registers, and if a match is found, then the appropriate logical device is selected for access. Each physical device occupies a number of consecutive byte locations. TABLE 24 sets out the address decoding for a selected number of PnP devices, including Codec 100. For 9-bit decodes A11 . . . A10 are assumed to be zero.

[0509] Because the ISA bus provides 16-bit address for I/O decoding, Codec 100 10-bit and 12-bit decoded address ranges will alias into the upper addresses due to the fact that address bits [A15 . . . A11] and [A15 . . . A13] are not decoded. Normally this is not a problem, but it could be for some mother board manufacturers. In order to prevent the address decoding from aliasing, Codec 100 supports a mode where by the high order address bits (A15 . . . A12) are input via CDROM interface 120. CDROM/Modem interface 120 is not available in this mode. The address bits A15 . . . A12 are then decoded along with [A11 . . . A10] to generate logical device selects for Sound System and Codec 100 registers. A valid logical device decode occurs when bits [A15 . . . A12] are equal to [0,0,0,0] and bits [A11 . . . A0] match one of the current programmed base address registers. For all other address decodes, bits A15 . . . A10 are decoded along with bits [A.9 . . . A0] to generate device selects. A valid logical device decode occurs when [A15 . . . A10] are equal to [0,0,0,0,0,0] and [A9 . . . A0] match one of the current programmed base address registers.

[0510] The 16-bit address decode function is selected by the XIOR pin being high at the time the RESDRV pin transitions from a high to low.

[0511] Several user defined registers are available in the Card Level Vendor Defined area specified by Plug and Play ISA Specification Version 1.0a.

[0512] The RAM Access Register at address 0x28 will allow the host to access program RAM in the similar access through the Control Registers but using PnP ADDRESS, WRITE_DATA and READ_DATA ports instead of Control ports (Control Base +5 and Control Base +6). All control port accessible commands are available with this access method. The JUMP_TO_ROM (57h) command should not be used through this PnP method nor should mixing of control port and PnP accesses be mixed, e.g. a PnP HOLD and a control port GO. A separate PnP JUMP TO ROM command is provided. The following is a typical sequence to access the RAM:

[0513] 1) Write an 0x28 to the ADDRESS port;

[0514] 2) Write a relevant function byte to the WRITE_DATA port (such as 0x55 for disable PnP, 0x56 for disable Crystal key, 0x5A for update, 0xAA for RAM write/read, etc.) (For RAM write/read only, steps 3 and 4 are needed.);

[0515] 3) Write a low byte and high byte of the RAM starting address to the WRITE_DATA port and then write/read the data to/from the WRITE_DATA/READ-DATA port; and

[0516] 4) Finally execute a RAM END command to finish the RAM write/read.

[0517] The RAM END Register 0x2A allows the host to execute a RAM END by:

[0518] 1) Writing an 0x2A to the ADDRESS port; and

[0519] 2) Then writing an 0x00 to the WRITE_DATA port.

[0520] The RAM JUMP TO ROM Register 0x2B forces code jump to a tight loop in ROM:

[0521] 1) Write an 0x2B to the ADDRESS port; and

[0522] 2) Then write an 0x57 to the WRITE_DATA port.

[0523] The Chip “Black_out” Register 0x2F causes the chip to enter into “Black_out” state, which will shut down all activated logical devices, cause PnP and Crystal keys to be disabled and force the part go into WAIT_FOR_KEY state.

[0524] FIGS. 14A-14D are diagrams of the bitfields of the DMA Channel Select Registers, the bits in each of these registers operate as shown in TABLE 25, where DMA-A to DMA-D are the four available DMA channels enabled:

[0525] FIG. 14A is a diagram of the bitfields of the Sound Blaster DMA Channel Select registers at microcontroller 103 address 0x29. This register is reset to zero when RESDRV is high and is used to specify one of the four ISA DMA channels to which the Sound Blaster DMA signals is mapped.

[0526] FIG. 14B is a diagram of the bitfields of the Sound System Playback/Capture DMA Channel Select registers at microcontroller 103 address 0x2A. This register is reset to zero when RESDRV is high and is used to specify one of four the ISA DMA channels to which the Sound System Playback/Capture DMA signals is mapped

[0527] FIG. 14C is a diagram of the bitfields of the Sound System Capture DMA Channel Select register at microcontroller 103 address 0x2. This register is reset to zero when RESDRV is high and is used to specify one of the four ISA DMA channels to which the Sound System Capture DMA signals is mapped.

[0528] FIG. 14D is a diagram of the bitfields of the CDROM DMA Channel Select register at microcontroller 103 Address 0x2C. This register is reset to zero when RESDRV is high and is used to specify one of the four ISA DMA channels to which the CDROM DMA signals is mapped.

[0529] FIGS. 15A-15J are diagrams of the bitfields of miscellaneous registers.

[0530] FIG. 15A is a diagram of the bitfields of the Alternate CDROM Base Address Low register at microcontroller 103 Address 0x2D. This register is reset to zero when RESDRV is high and is used to specify the lower 8-bits of the 10-bit CDROM base address. The number of consecutive locations decoded at this base address is fixed at four bytes.

[0531] FIG. 15B is a diagram of the bitfields of the Alternate CDROM Base Address High registers at microcontroller Address 0x2E. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit CDROM base address.

[0532] FIG. 15C is a diagram of the bitfields of the Physical Device Activation Register at microcontroller 103 Address 0x2F. This register is used to enable specific physical devices after the configuration registers have been programmed. Each bit set equal to a one will enable the particular physical device as shown in TABLE 26. A value of zero will disable the corresponding physical device. When disabled, a particular physical device is physically disconnected (I/O base address, Interrupt and DMA) from ISA bus interface 101.

[0533] FIG. 15D is a diagram of the bitfields of the Modem Base Address Low register at microcontroller 103 Address 0x30. This register is reset to zero when RESDRV is high and is used to specify the lower 8-bits of the 10-bit Modem base address. The number of consecutive locations decoded at this base address is fixed at four bytes.

[0534] FIG. 15E is a diagram of the bitfields of the Modem Base Address High register at microcontroller 103 Address 0x30. This register is reset to zero when RESDRV is high and is used to specify the upper 2-bits of the 10-bit Modem base address.

[0535] FIG. 15F is a diagram of the bitfields of the Alternate CDROM Mask Register at microcontroller 103 Address 0x32. The CDROM Address Mask Register provides a means to vary the number of consecutive byte locations that a secondary CDROM I/O decode may occupy. Each mask bit is used to prevent specific address bits from being decoded in generating the secondary CDROM I/O decode. The valid bit combinations are as shown in TABLE 27.

[0536] FIG. 15G is a diagram of the bitfields of the Modem Mask Register at microcontroller 103 Address 0x33. The Modem Address Mask Register provides a means to vary the number of consecutive byte locations that the modem decode may occupy. Each mask bit is used to prevent specific address bits from being decoded in generating the modem I/O decode. The valid bit combinations are as shown in TABLE 28.

[0537] FIG. 15H is a diagram of the bitfields of the Miscellaneous Control Bits register at microcontroller 103 Address 0x34. A description of these bits is as follows:

[0538] PCDINT—Polarity CDROM Interrupt specifies polarity of CDROM interrupt input:

[0539] 0=CDROM interrupt is active low; and

[0540] 1=CDROM interrupt is active high.

[0541] PSINT—Polarity Synthesizer Interrupt specifies the polarity of synthesizer interrupt input:

[0542] 0=synthesizer interrupt is active low; and

[0543] 1=synthesizer interrupt is active high.

[0544] PMINT—Polarity Modem Interrupt specifies the polarity of modem interrupt input:

[0545] 0=modem interrupt is active low; and

[0546] 1=modem interrupt is active high.

[0547] XBUF—Transceiver buffer control:

[0548] XBUF=0 Codec drives data bus on reads of

[0549] CDROM addresses; and

[0550] XBUF=1 Codec tri-states data bus on reads of CDROM addresses.

[0551] SD7DE—SD7 Disable:

[0552] SD7DE 0=SD7-SD0 driven during reads of CDROM

[0553] Alternate Base +1

[0554] SD7DE 1=SD7 tri-stated, SD6-SD0 driven during reads of CDROM Alternate Base +1.

[0555] FIG. 15I is a diagram of the bitfields of the Modem Interrupt Select register at microcontroller Address 0x35. This register is reset to zero when RESDRV is high and is used to specify one of the six interrupt pins to which the Modem interrupt is mapped.

[0556] FIG. 15J is a diagram of the bitfields of the Physical Device Activity Register at microcontroller address=0x36. Each bit indicates that an ISA Bus access (read or write)to a particular physical device has occurred. The bit is set upon an ISA read or write access to one of eight physical devices as shown in TABLE 29. All bits are reset to zero upon an microcontroller 103 read of the register. In addition any DMA activity to the codec (PDACK,CDACK=0) also sets the Sound System (DA0) and Sound Blaster (DA6) bits.

[0557] FIG. 16 is a diagram of the bitfields of the Wavetable and Serial Control Register at microcontroller address 0x40. This register Reset to zero when RESDRV=1. The specific bitfields can be described as follows:

[0558] SBSP Sound Blaster Swap Playback—when this bit is set to a zero the current ordering of samples for DMA playback are swapped, relative to the current defined format. This bit affects only 8-bit playback in Sound Blaster mode.

[0559] SBSC Sound Blaster Swap Capture—when this bit is set to a one, the current ordering of samples for DMA capture are swapped, relative to the current defined format. This bit affects only 8-bit capture in Sound Blaster mode.

[0560] res Reserved

[0561] WTEN Wave Table Enable—When this bit is set to a one, the XD7:XD5 pins are switched to support a digital wavetable interface. When this bit is a zero the XD7:XD5 pins operate normally. TABLE 30 describes the decoding of the WTEN bit:

[0562] SPS Serial Port Switch—When this bit is set to a one, and the SPE bit in register I16 is set to a one, the DSP serial port pins are switched from the second joystick pins to the XD pins. If SPS is a zero and the SPE bit in register I16 is set to a one the DSP serial port pins are routed to the second joystick pins. If the SPE bit in register I16 is a zero then the serial port pins do not appear anywhere.

[0563] TABLE 31 describes the functioning of the SPS bit:

[0564] Codec 100 has the ability to override the current bond out definition by allowing microcontroller 103 access to a register that replaces the bond out wires. The mechanism by which this register is modified is a Control Port Command (RAM Write) to Control_base +5. Registers I25 and C1 should reflect the bond out as defined by either the pads or the register bits BO1:BO0 depending on the state of BOE2:BOE0.

[0565] FIG. 17 is a diagram of the bitfields of microcontroller address 0x41. (Reset to 0x00). The bitfields are decoded in TABLE 32 as follows:

[0566] res Reserved for future use. Always read back as zero's;

[0567] FIG. 18 is a diagram of the bitfields of the Port 3 Shadow Register at microcontroller address 0x42. The bitfields of this register function as follows:

[0568] P3.0—UP—This bit follows the state of Codec 100 UP pin when VCEN is set.

[0569] P3.1—DOWN—This bit follows the state of Codec 100 Down pin when VCEN is set.

[0570] P3.2—MUTE—This bit follows the state of Codec 100 Mute pin when VCEN is set.

[0571] P3.3—REQUEST—This field is set to a one to update codec registers that may be in contention with ISA bus accesses (WSS mode). After polling for GRANT=1, microcontroller 103 may access codec registers as needed. After microcontroller 103 has finished its codec accesses, the REQUEST bit should be set to zero to re-enable ISA access to the codec registers.

[0572] P3.4—GRANT—This bit is polled by microcontroller 103 after setting the REQUEST bit=1. When GRANT is equal to one, microcontroller 103 may access codec registers without contention with the ISA bus. When GRANT=1 and subsequent ISA codec accesses are held off via IOCHRDY (discussed below in conjunction with FIG. 19) until the REQUEST bit is set to zero by microcontroller 103.

[0573] P3.5—Codec INT—Read Only. This bit follow the state of the internal codec interrupt signal (not

[0574] 1) Write the appropriate Crystal Key Disable of PnP Key Disable command using the RAM Access Register defined above. The command numbers are identical to the Control Port Command Interface command numbers;

[0575] 2) Write an 10x2F to the ADDRESS port;

[0576] 3) Write a zero TO PNP_WRITE_DATA PORT to deactivate the logical; and

[0577] 4) Either the Crystal Key, or the PnP, or Both functions will be inactive.

[0578] External EEPROM

[0579] As mentioned above, an external EEPROM is typically for all Codec 100 environments. The EEPROM is coupled to Codec 100 through the EEPROM interface circuitry of block 109. The EEPROM is used for specifying configuration data that is used in setting up Codec 100 operation, Plug-n-Play resource data, and RAM patch data. The EEPROM supports two modes of operation which will be discussed in detail below. The mode identifiers are shown in TABLE 33. FIG. 19 emphasizes the circuitry of the EEPROM interface. Refer to FIG. 20 for a flow chart of a detect/load EEPROM sequence.

[0580] The existence and type of EEPROM is determined by two bytes that are located in the first two locations of the EEPROM memory. On power-up Codec 100 looks for the existence of these two bytes via the EEPROM interface. If the first two EEPROM locations are found to contain these matching bytes then Codec 100 will load the EEPROM data into Codec 100 internal memory. How the EEPROM data are interpreted and acted upon is determined by the defined EEPROM mode.

[0581] The first mode of operation assumes that a compatible EEPROM exists. The EEPROM data format for this mode is defined in TABLE 34. The data supports specification of Peripheral Port address length, mapping of interrupt and DMA pins to specific ISA bus lines, and definition of Plug-n-Play resource data. Upon a power-up reset the EEPROM data will be copied into Codec 100 RAM starting at address 0x400C. The additional configuration data needed (0x4000 to 0x400B) will have been copied from ROM defaults to RAM (as the result of a power-on reset) before the EEPROM is detected. The contents of the RAM will then bee used to update the hardware.

[0582] The Data Length Bytes (2,3) specify the total length of data contained in the EEPROM not including the two validation bytes or the two data length bytes.

[0583] The External Peripheral Port I/O Decode Address Length Byte (4) determines which devices connected to the External Peripheral 109 Port may require an I/O decode address length of four or eight:

[0584] 0x00=I/O Length Four Bytes; and

[0585] 0x08=I/O Length Eight Bytes

[0586] The Mixer Input Mapping Byte (5) (default 0x40) determines what physical devices are connected to the various mixer inputs. TABLE 35 described the available selections.

[0587] The Interrupt Selection A,B Bytes (6) determine what physical ISA Bus interrupt pin is connected to the IRQA and IRQB pins of Codec 100. The available connections are shown in TABLE 36.

[0588] C,D, Byte (7) determines what physical ISA Bus interrupt pin is connected to the IRQC and IRQD pins of Codec 100. TABLE 37 shows the possible connections.

[0589] The Interrupt Selection E,F, Byte (8) determines what physical ISA Bus interrupt pin is connected to the IRQD and IRQE pins of Codec 100. The possible connections are described in TABLE 38.

[0590] The DMA Selection A,B Byte (9) determines what physical pair of ISA Bus DMA pins are connected to the DRQA, DRQB and DACKA, DACKB pins of Codec 100. TABLE 39 describes the available connections.

[0591] The DMA Selection C Byte (A) determines what physical pair of ISA Bus DMA pins are connected to the DRQA, DRQB and DACKA, DACKB pins of Codec 100. TABLE 40 describes the available connections.

[0592] Bytes 11 through L are reserved for Plug-n-Play resource data. The format of the Plug-n-Play data are described above.

[0593] Codec 100 EEPROM resource data format for the second mode in TABLE 33 is shown in TABLE 41. The data is copied into Codec 100 RAM memory and the hardware will be updated based on the stored RAM values. The identification word for this format is 0xBB55.

[0594] The fields of address mask register/alternate CDROM base address register (Byte 4) is depicted in FIG. 21A. The CDROM Address Mask Register provides a means to vary the number of consecutive byte locations that the secondary CDROM I/O decode may occupy. Each mask bit is used to prevent specific address bits from being decoded in generating the secondary CDROM I/O decode. The valid bit combinations are as shown in TABLE 42. All other combinations are invalid and may cause erroneous operation.

[0595] The bitfields of Address Mask Register Modem (Byte 5) are shown in FIG. 21B. The Modem Address Mask Register provides a means to vary the number of consecutive byte locations that the modem decode may occupy. Each mask bit is used to prevent specific address bits from being decoded in generating the modem I/O decode. The valid bit combinations are as shown in TABLE 43. All other combinations are invalid and may cause erroneous operation.

[0596] The Miscellaneous Configuration Bits, Byte 6, are shown in FIG. 21C.

[0597] PCDINT—Polarity CDROM Interrupt bit specifies polarity of CDROM interrupt input:

[0598] 0=CDROM interrupt is active low; and

[0599] 1=CDROM interrupt is active high.

[0600] PSINT—Polarity Synthesizer Interrupt bit specifies polarity of synthesizer interrupt input:

[0601] 0=synthesizer interrupt is active low; and

[0602] 1—synthesizer interrupt is active high.

[0603] CKD—Crystal Key Disable bit controls response of Codec 100 to the Crystal Key Sequence:

[0604] CKD 0=Enable—Codec 100 will Respond to Crystal Key; and

[0605] PKD 1=Disable—Codec 100 will NOT Respond to Crystal Key.

[0606] PKD—Plug-n-Play Key Disable bit controls response of Codec 100 to the PnP Key Sequence:

[0607] PKDO=Enable—Codec 100 will Respond to Pnp Key; and

[0608] PKD1=Disable—Codec 100 will NOT Respond to PnP Key.

[0609] RES—Reserved, always defined as zero (0);

[0610] PMINT—Polarity Modem Interrupt bit specifies polarity of modem interrupt input:

[0611] 0=modem interrupt is active low; and

[0612] 1=modem interrupt is active high.

[0613] XBUF—Transceiver buffer control:

[0614] XBUF=0CS4232 drives data bus on reads of CDROM addresses; and

[0615] XBUF=I CS4232 tri-states data bus on reads of CDROM addresses.

[0616] SD7DE—SD7 Disable:

[0617] SD7DE 0−SD7-SDO driven during reads of CDROM Alternate Base +1; and

[0618] SD7DE 1=SD7 tri-stated, SD6-SDO driven during reads of CDROM Alternate Base +1.

[0619] FIG. 21D defines the bitfields of the Misc. Configuration Bits, Byte 7. This byte is copied to microcontroller 103 addresses 0x4002 on powerup and 0x34 on powerup or PNP_UPDATE command.

[0620] VCEN—Volume Control Enable—This bit is copied to the corresponding VCEN bit in microcontroller 103 register 0x34. The Firmware also uses this bit to enable up/down/mute external pushbutton volume control.

[0621] The Global Configuration Byte,Byte 8 is depicted in FIG. 21E and is copied to 0x4003 on powerup. The actions taken based on the data in this byte occur at powerup in the EEPROM case and during a PNP_UPDATE command in the case of a host resource data shoot. NOTE: All defined bits other than D3 and D2 in register 0x40 are preserved. The bit decoding is as follows:

[0622] Reserved—These bits are reserved for future use and should be set to zero;

[0623] SPS—Serial Port Switch—This bit is copied to the corresponding SPS bit in microcontroller 103 register 0x40;

[0624] WTEN—Wave Table Enable—This bit is copied to the corresponding WTEN bit in microcontroller 103 register 0x40;

[0625] AIDIS—Alternate Input Disable—This bit, when set, will cause SB initiated writes to registers I18, I19 to NOT be mapped to X0, X1 if IFM or WTEN are set;

[0626] VCF0—This bit, along with the VCF1 bit, is used to specify which volume control button scheme is used;

[0627] VCF1—This bit, along with the VCF0 bit, is used to specify which volume control button scheme is used; and

[0628] IFM—When this bit is set to a one the internal FM synthesizer is enabled.

[0629] Firmware Revision information bytes are used by the host to identify which patch is present in the part and what patch options are set.

[0630] Features Byte indicates major feature sets of the embedded microcode. Each bit in this byte represents a feature or feature set.

[0631] Firmware REVISION at 0x41BE byte indicates the current revision of the embedded microcode patch and is written 0x22 on powerup.

[0632] The Logical-to-Physical Device Mapping, Bytes 8-15, are used to map Logical Devices to Physical Devices. Each Logical Device has a byte associated with it. To map physical devices into a particular logical device a one is programmed into the corresponding bit location. TABLE 44 defines the mapping. The physical device bits are mapped the same as the Physical Device Activation register. As an example, to define Logical Device 0 as Sound System/Sound Blaster/Synth, Byte 0 should be written as a 0x43 to mapped the three physical devices to Logical Device 0.

[0633] Codec 100 EEPROM may also optionally include RAM patch data starting at offset L+1 and continuing to N (max=0x43FD).

[0634] Because all implementations of Codec 100 will require either a host resource load or EEPROM, the default (ROM) resource data and configuration has been minimized to save code space and therefore does not contain a full set of Plug-n-Play resource data. However, without an EEPROM, using the default ROM data, Codec 100 will still be able to participate in a PnP or Crystal Key sequence but will have no resource data to report. An example of this feature follows:

[0635] As shown in FIG. 19, Codec 100 interfaces to an external EEPROM device via Peripheral Port Interface 109. The acutal pins used are as follows. The XD0 pin connects to the EEPROM data pin and the XA0 pin connects to the EEPROM address pin. To XD0 pin is open-collector and therefore requires a 5K pull-up resistor. The interface is designed to be compatible with a variety of EEPROM devices that are I²C compatible.

[0636] The EEPROM is accessible via microcontroller 103 microcontroller and directly via the ISA bus via multiplexer 1901 and read drivers 1902.

[0637] Microcontroller 103 access to the EEPROM is enabled via the EPP bit in the Plug-n-Play Control/Status Register (microcontroller 103 address=0x14). When the EPP bit is equal to one microcontroller 103 Port 1 pins 6 and 7 are enabled onto the XD0 and XA0 pins respectively. The only time in which microcontroller 103 enables access to the EEPROM is after a Codec 100 reset (RESDRV=1 or PD1, PD0=10). In this instance, as part of a initialization sequence, microcontroller 103 checks for the existence of an EEPROM device. If a compatible EEPROM is found then its contents are loaded into Codec 100. Microcontroller 103 only reads EEPROM devices it does not have the ability to write EEPROM devices. Writing of the EEPROM is accomplished by using the ISA Bus EEPROM access port via Codec 100 Control Base +1 register. The timing of the data and clock signals are determined by microcontroller 103 ROM code. The timing relationship between the clock and data are shown in FIG. 22A. The state of the data line can change only when the clock line is low. A state change of the data line during the time that the clock line is high is used to indicate start and stop conditions.

[0638] Codec 100 supports a single EEPROM up to 2K bytes. EEPROM device read access is shown in FIG. 22B. The timing follows that of a random read sequence. Prior to issuing the slave address with the R/W bit set to a one, Codec 100 first performs a “dummy” write operation. Codec 100 first generates a start condition followed by the slave device address and the byte address of zero. The slave address is made up of a device identifier (0xA) and a bank select (bits A2 . . . A0) which are always zero. Codec 100 always begins access at byte address zero and continues access a byte at a time. The byte address automatically increments by one until a stop condition is detected.

[0639] ISA Bus access to the EEPROM is enabled via the DATAIN bit in Codec 100 Control Base+1 register. When the DATAIN bit is set to a one then the CLOCK and DATAOUT bits are enabled on to the XA0 and XD0 pins respectively. The timing of the clock and data signals is completely determined by the host based software program and should be the timing requirements shown in FIG. 28. It should be noted that in order to read back data from the EEPROM device, the DATAOUT bit must be set to a one.

[0640] Sound Blaster

[0641] The Sound Blaster/MPU-401 to microcontroller 103 interface 2300 is shown in FIG. 23A and consists of a number of data latches 2301 and transceivers 2302 that are used to send and receive data between ISA bus 130 and microcontroller 103. The particular ISA Bus base I/O addresses, as defined by the Plug & Play configuration data, are decoded by ISA address decoder 2303. When a ISA Bus generated read/write occurs to a Sound Blaster or MPU-401 device then an interrupt (active low) is generated on the INT1 TRO input of microcontroller 103. At the same time the ISA Bus IOCHRDY line is driven low to force the current ISA BUS cycle to wait. Data are put on PORT1 to indicate to microcontroller 103 what ISA Bus access has generated the interrupt microcontroller 103 then performs a read or write of the ISA Data Port depending on the current cycle type (read/write). The trailing edge of microcontroller 103 read/write strobe tri-states (releases) the IOCHRDY line and the current ISA cycle is allowed to complete.

[0642] It is not required in all cases for microcontroller 103 to access the ISA Data Port immediately after receiving an interrupt. Microcontroller 103 may perform a number of processing tasks, while IOCHRDY holds off the ISA Bus, before the access to the ISA Data Port occurs which releases IOCHRDY. However the amount of time in which IOCHRDY is asserted should be keep to a minimum to minimize the impact on system performance.

[0643] The Plug & Play block 106 maps the Sound Blaster functions into the ISA environment. The Sound Blaster I/O map is shown in TABLE 45:

[0644] The FM registers addresses 0-3 and 8-9 are maps to a synthesizer connected externally to Codec 100 via the External Peripheral Port 109. The Mixer Address and Data registers are mapped into the codec mixer by microcontroller 103. The DSP registers are used to send/receive Sound Blaster commands and data from microcontroller 103. Addresses 0xB, 0xD, and 0xF are aliases from addresses 0xA, 0xC, and 0xE respectively. Unused bits (6 . . . 0) at addresses 0xC, 0xD, 0xE, and 0xF are mapped to bits 6 . . . 0 in latch at address 0xA, B.

[0645] The Sound Blaster digital audio DMA functions are supported by the Windows Sound System codec (external to Codec 100). It should be noted that in the Sound Blaster mode (via a context switch) Codec 100 swaps the left right samples in the codec (capture and playback) so that they match the Sound Blaster standard.

[0646] The Sound Blaster mixer functions are mapped into codec mixer 204. This mapping is illustrated in FIG. 31 and TABLE 46.

[0647] The mixer data are buffered by microcontroller 103 into internal memory. Then, during a time in which Codec 100 is holding the ISA bus via IOCHRDY, the appropriate codec mixer writes are done to affect the mixer change. This is done because microcontroller 103 cannot access the codec registers while DMA audio is being transferred to the codec 100. While IOCHRDY is asserted DMA activity to codec 100 is suspended and the Sound Blaster mixer registers are shadowed by microcontroller 103. The Input Filter, DNF1, and VSTC (mono/stereo) bits do not have a CS4231 codec equivalent function and therefore are don't cares.

[0648] Sound Blaster Mixer accesses operate as follows:

[0649] Mixer Write

[0650] 1. An ISA Bus write occurs to Sound Blaster Mixer Address Register (Base +5);

[0651] Codec 100 drives IOCHRDY low to hold bus. Data are put on PORT1 and a microcontroller 103 interrupt is generated;

[0652] microcontroller 103 reads the ISA Data Port (External RAM address=0) and stores address value in local memory; and

[0653] IOCHRDY is released and the ISA Bus cycle completes.

[0654] 2. An ISA Bus write occurs to Sound Blaster Mixer Data Register (Base +6);

[0655] Codec 100 drives IOCHRDY low to hold bus, data are put on PORT1 and a microcontroller 103 interrupt is generated;

[0656] microcontroller 103 reads ISA Data Port (External RAM address=0) and stores data value in local memory; and

[0657] IOCHRDY is released and the ISA Bus cycle completes.

[0658] 3. Microcontroller 103 then writes codec 100 registers to perform mixer function that was specified.

[0659] Mixer Read

[0660] 1. An ISA Bus write occurs to Sound Blaster Mixer Address Register (Base +5);

[0661] Codec 100 drives IOCHRDY low to hold bus, data are put on PORT1, and a microcontroller 103 interrupt is generated;

[0662] microcontroller 103 reads ISA Data Port (External RAM address=0) and stores addressed value in local memory; and

[0663] IOCHRDY is released and the ISA Bus cycle completes.

[0664] 2. An ISA Bus read occurs to Sound Blaster Mixer Data Register (Base +6);

[0665] Codec 100 drives IOCHRDY low to hold bus, data are put on PORT1, and microcontroller 103 interrupt is generated;

[0666] microcontroller 103 writes Mixer Data Latch (External RAM address=0) with shadow Sound

[0667] Blaster mixer register contents; and

[0668] IOCHRDY is released and the ISA Bus cycle completes.

[0669] Sound Blaster interface 2300 further includes uses a hardware handshake mechanism 2304 for processing commands. The mixer does not use a handshake mechanism and is always assumed to be available for ISA bus accesses. Two handshake bits are used: Command Busy, and Data Available. The Command Busy is located in the Write Buffer Status Register (bit 7). The Data Available bit is located in the Data Available Status Register (bit 7). The Command Busy bit indicates when microcontroller 103 is busy processing a command. The Data Available bit is used to indicate when microcontroller 103 has responded to a command with some data. The handshake works as follows:

[0670] 1. The Command Busy bit is generated by the logical OR of two independently controlled microcontroller 103 accessible bits; SB_BUSY1 and SB_BUSY 2;

[0671] Writes to the Sound Blaster Command Register (SB_Base+C) immediately set the Command Busy bit (via SB_BUSY 1);

[0672] Microcontroller 103 reads and processes the command. Once the command is processed, a read of the Sound Blaster Data Register (External RAM address 0x01), by microcontroller 103, will clear this bit. This bit is set to a 1 on a reset (RESDRV); and

[0673] Writes to the Sound Blaster Reset Register (SB_Base +6) with a D0 value of one immediately sets the Command Busy bit (via SB_BUSY 2). Microcontroller 103 processes the reset command and clears the Command Busy bit by executing a write of microcontroller 103 address 0x8.

[0674] 2. When microcontroller 103 writes data to the SB Data Register (microcontroller 103 External RAM address 0x02) the Data Available bit is set to a one. This bit is cleared once the Read Data Port (Sound Blaster base address+A) is read via the ISA bus. This bit defaults to 0 on reset.

[0675] Codec 100 supports Sound Blaster ADPCM 2:1, 3:1, and 4:1 decompression. When a ADPCM byte is transferred to Codec 100 via DMA, an interrupt is generated to microcontroller 103 via input TRO, and the data are latched. Microcontroller 103 is then able to read the data from the latch by reading from memory location 0xC.

[0676] The Sound Blaster RESET command is generated by writing a one to register index 6 and then writing index register 6 to a zero. In Codec 100 hardware detects the zero-one-zero transition and interrupts microcontroller 103 on the one-to-zero transition. The interrupt is acknowledged by microcontroller 103 reading the ISA Data Latch.

[0677] In addition,to the standard codec DMA request generation the Sound Blaster hardware has the capability of generating a DMA request via a number of commands. In Codec 100 microcontroller 103 detects these commands and writes microcontroller 103 External RAM address 0xE. The Sound Blaster hardware senses this write and generates a DMA Request on the ISA Bus. In addition microcontroller 103 may write a byte to the Sound Blaster Data Latch depending on which command is being responded to. The ISA Bus will in turn generate a DMA Acknowledge. If the DMA acknowledge is a read then the DMA request is cleared and the data that was written to the Sound Blaster Data Latch is put onto the ISA data bus. If the DMA acknowledge is a write then an interrupt is generated to microcontroller 103 microcontroller via INT1 and the data present on the ISA Data Bus is written into the Sound Blaster ADPCM Data Latch with the trailing edge of the IOW strobe. The leading edge of the IOW strobe clears the DMA Request. Microcontroller 103 responds to the interrupt by reading the Sound Blaster ADFCM Data Latch (microcontroller 103 address 0x0C).

[0678] In addition the Sound Blaster hardware may generate its own interrupt. This is accomplished by microcontroller 103 writing to External RAM address 0xFH which will generate an interrupt on the ISA bus. The Sound Blaster interrupt is cleared when a read from Sound Blaster Data Available Register (index 0xE). The MPU-401 has become the defacto standard for controlling MIDI devices via IBM-PC compatible personal computers.

[0679] A MPU401 logical device interface occupies 2 I/O locations and utilizes 10-bit address decoding. The standard base address is 330h. This device also requires an interrupt, typically 9.

[0680] Codec 100 implements the UART mode of the MPU-401 functionality. This mode is used to send and receive MIDI data to and from the host computer and a external MIDI device through interface 104. MPU-401 Interface 104 consists of two registers (Command/Status Register, Transmit/Receive Register) that are mapped into the host I/O space. MPU-401 interface 104 is idle until a Enter UART Mode command is written to the Command register. Once UART mode is entered, MIDI data are written to or read from the Transmit/Receive register a byte at a time. Microcontroller 103 stores the data in separate receive and transmit FIFO's. Each transfer of a byte into the receive FIFO should generate an interrupt to the host computer.

[0681] The Transmit (TXD) and Receive (RXD) pins of microcontroller 103 UART should connect to the MIDI OUT and MIDI IN pins respectively. After power-up reset, the interface is in “non-UART” mode. Non-UART mode operation is defined as follows:

[0682] 1. All writes to the Transmit Port, MPUbase+0, are ignored;

[0683] 2. All reads of the Receive Port, MPUbase+0, return the last received buffer data; and

[0684] 3. All writes to the Command Port, MPUbase+1, are monitored and acknowledged as follows:

[0685] a. A write of 3Fh sets the interface into UART operating mode. An acknowledge is generated by putting an FEh into the receive buffer FIFO which generates an interrupt;

[0686] b. A write of A0-A7, ABh, ACh, ADh, AFh places an FEh into the receive buffer FIFO (which generates an interrupt) followed by a one byte write to the receive buffer FIFO of 00h for A0-A7, and ABh commands, 15h for ACh, 01h for ADh, and 64h for AFh commands; and

[0687] c. All other writes to the Command Port are ignored and an acknowledge is generated by putting an FEh into the receive buffer FIFO which generates an interrupt.

[0688] UART mode operation is defined as follows:

[0689] 1. All writes to the Transmit Port, MPUbase+0, are placed in the transmit buffer FIFO. Whenever the transmit buffer FIFO is not empty, the next byte is read from the buffer and sent out the MIDOUT pin.

[0690] The Status Register, MPUbase+1, bit 6, TXS is updated to reflect the transmit buffer FIFO status;

[0691] 2. All reads of the Receive Port, MPUbase+0, return the next byte in the receive buffer FIFO. When serial data are received from the MDIN pin, it is placed in the next receive buffer FIFO location. If the buffer is full, the last location is overwritten with the new data. The Status Register, MPUbase+1, bit 7, RXS is updated to reflect the new receive buffer FIFO state;

[0692] 3. A write to the Command Register, MPUbase+1, of FFh will return the interface to non-UART mode; and

[0693] 4. All other writes to the Command Register, MPUbase+1, are ignored.

[0694] MPU-401 interface 104 also uses a hardware handshake mechanism. The MPU-401 interface incorporates receive and transmit FIFO's implemented by microcontroller 103. External handshake bits indicate to the host the current FIFO status. The two handshake bits are as follows: Transmit FIFO Full Flag, and Receive Buffer Empty Flag. The status of both flags is output onto the ISA bus in response to a read of the MPU Commands/Status Register (MPU-401 base address +1). The flags function as follows:

[0695] 1. Transmit FIFO Full Flag is set when a ISA write cycle occurs to the MPU-401 Transmit/Receive Data Port or the Command/Status Register. This flag is reset when a microcontroller 103 read of the MPU Data Register (External RAM address=0x02) occurs; and

[0696] 2. Receive Buffer Empty Flag is set to one when an ISA read cycle occurs to the Transmit/Receive Data Port. This flag is reset to zero when microcontroller 103 performs a write to the MPU Data Register (External RAM address=0x02). This write also generates an interrupt on ISA bus. When an ISA Bus read of the Transmit/Receive Register occurs the interrupt will be cleared.

[0697] TABLES 47A-47E summarize the Sound Blaster/MPU 401 Hardware Interface Definition and Protocol.

[0698] FIGS. 24A-24L are diagrams of the bitfields of the Sound Blaster/MPU-401 registers.

[0699] FIG. 24A is a diagram of the ISA DATA READ/MIXER LATCH register at microcontroller address 0x00. This microcontroller 103 address location is read by microcontroller 103 in response to a ISA bus write cycle to the Sound Blaster DSP Command Register, Mixer Address Register, Mixer Data Register, or the MPU-401 Command Register. When microcontroller 103 read strobe is low, ISA bus data is enabled onto microcontroller 103 XDB[7:0] bus (FIG. 3). A write to this location occurs in response to read from the Mixer Data Port. The write strobe of microcontroller 103 is used to clock the data from XDB[7:0] into a latch. The output from the latch is then enabled onto the ISA data bus where it is read.

[0700] FIG. 24B is a diagram of the bitfields of the Sound Blaster Data Latch register at microcontroller address 0x01. This microcontroller 103 address location is written by microcontroller 103 in response to a ISA bus write to the Sound Blaster Command Register. The write strobe of microcontroller 103 is used to clock the data from XDB[7:0] into a latch. The output from the latch is then enabled onto the ISA data bus-where it is read.

[0701] FIG. 24C is a diagram of the bitfields of the MPU-401 Receive Data Latch at microcontroller address 0x02. This microcontroller 103 address location is written by microcontroller 103 in response to a ISA bus write to the MPU-401 Command Register or read by the ISA bus of the MPU-401 Transmit/Receive Register. The write strobe of microcontroller 103 is used to clock the data from XDB[7:0] into a latch. The output from the latch is then enabled onto the ISA data bus where it is read.

[0702] FIG. 24D is a diagram of the bitfields of the STATUS REGISTER at Address 0x03. This microcontroller address location when read by microcontroller 103 returns the current status of the Sound Blaster, MPU-401 ISA bus handshake bits, codec interrupt, and Sound Blaster ADPCM data ready:

[0703] RXS-MPU-401 Receive Buffer Status 0=not empt, 1=empty;

[0704] TXS-MPU-401 Transmit Buffer Status 0=not full, 1=full;

[0705] SCB-Sound Blaster Command Busy 0=not busy, 1=busy;

[0706] SDA-Sound Blaster Data Available 0=no data available, 1=data available;

[0707] CINT-Codec Interrupt Status 0=no interrupt pending, 1=interrupt pending; and

[0708] SBAD Sound Blaster ADPCM Status 0=old ADPCM data, 1=new ADPCM data.

[0709] FIG. 24E is a diagram of the Reserved Registers at microcontroller Addresses 0x04 through 0x07.

[0710] FIG. 24F is a diagram of the bitfields of Reset Sound Blaster Busy 2 at microcontroller 103 Address 0x08.

[0711] FIG. 24G is a diagram of the bitfields of the Reset Sound Blaster Busy 2 register at microcontroller address 0x08. When this microcontroller 103 address is written, the Sound Blaster Command Busy 2 flag is forced to a zero.

[0712] FIG. 24I is a diagram of the bitfields of the Sound Blaster ADPCM Data Latch at microcontroller 103 Address 0xC. This address is read in response to a Sound Blaster ADPCM DMA write (ADPCM Status bit=1 and TR0 interrupt active). A microcontroller 103 read of this address resets the ADPCM Status bit to a zero.

[0713] FIG. 24J is a diagram of the bitfields of Set Sound Blaster Busy 1 at microcontroller 103 Address MD. When this microcontroller 103 address is written the Sound Blaster Command Busy 1 flag is forced to a one.

[0714] FIG. 24K is a diagram of the bitfields of the Sound Blaster DMA Request Register at microcontroller 103 Address ME which is in response to a write of a DMA command to the Sound Blaster Command Register. The write strobe of microcontroller 103 is used to clock the data from XDB[7:0] into a latch which also results in a DMA Request being generated on the ISA bus. When the ISA bus responds via a DMA acknowledge, the data that was written to this register is enabled onto the ISA bus where it is read. The DMA request may also be cleared by microcontroller 103 performing a read of this register.

[0715] FIG. 24L is a diagram of the bitfields of the Sound Blaster Interrupt Request Register at microcontroller 103 Address 0x0F. When this microcontroller 103 register is written an interrupt is generated on the ISA bus. The interrupt is cleared when the Sound Blaster DSP Data Port is read.

[0716] Control Register Interface

[0717] In the Control Logical Device space exits a set of registers for Codec 100 specific functions. These functions include EEPROM programming, power management modes, host interrupt generation, Sound Enhancement control, SP/DIF control, and various other miscellaneous control bits. The control registers are summarized in TABLES 48A and 48B.

[0718] FIGS. 25A-25S and the accompanying text describe each of the Control Registers in detail.

[0719] FIG. 25A is a diagram of the Miscellaneous Control Register (at base +0, default=0x00000000). Microcontroller 103 reads this register and controls the various functions accordingly. An ISA bus write of this register will also generate an interrupt to microcontroller 103 microcontroller via INT1. The bitfields can be described as follows.

[0720] JS1, JS0 These bits select among four joystick operating speeds:

[0721] 0 0=slowest speed;

[0722] 0 1−medium slow speed;

[0723] 1 0−medium fast speed;

[0724] 1 1=fastest speed

[0725] The CONSW bit controls host interrupt generation when a context switch occurs. The interrupt will only be passed through to the ISA bus if an interrupt resource was specified for Codec 100 logical device and the PlugnPlay configuration manager mapped the interrupt. Thus setting CONSW to a one does not necessarily guarantee that an ISA bus interrupt will get generated on a context switch. The decoding is:

[0726] 0−no interrupt generated on context switch

[0727] 1−interrupt generated on context switch

[0728] The PM1, PM0 bits control the various power down modes of Codec 100.

[0729] 0 0=normal operation with bits PDC, PDP, PDM enabled;

[0730] 0 1=A/D and D/A of codec are powered down. Analog mixer is still active in this mode, but gain/attenuation values are frozen. Bits PDC and PDM disabled;

[0731] 1 0=full Codec 100 power down. All Codec 100 functions are disabled except reads and writes to this register. This is a software version of the RESDRV pin. A reset will be generated (all clocks disabled), and held, to all Codec 100 internal logic including microcontroller 103 and all internal registers. The reset is released once these bits are written to 00 and the clocks are re-enabled;

[0732] 1 1=In this mode the A/D and DIA of the Codec, microcontroller 103, and the codec mixer including VREF are all powered down. Microcontroller 103 is forced into idle mode. An interrupt to microcontroller 103 will cause microcontroller 103 to exit idle mode and resume normal operation, but the codec A/D, D/A, and mixer will remained powered down. The mixer register settings are reset to default settings in this mode. When these bits are set to one all accesses to codec registers are disabled. When these bits are toggled from a 11 to a zero there will be a delay, caused by VREF capacitor charging, until the codec registers may be accessed reliably. The delay is determined by the capacitor value on the VREF pin and typically is on the order of 200 ms.

[0733] The PDC bit (Power Down Codec) controls codec power down:

[0734] 0=Normal operation

[0735] 1=A/D and D/A functions of codec are powered down.; the codec interface remains active and registers, including mixer registers, may be read or written.

[0736] The PDP Power Down Processor bit:

[0737] 0=Normal operation

[0738] 1=microcontroller 103 is forced into idle mode. Any interrupts generated to microcontroller 103 (PnP, Sound Blaster, MPU-401, Context Switch) will cause microcontroller 103 to exit IDLE mode and resume normal operation. Microcontroller 103 will clear this bit when idle mode operation is exited.

[0739] The PDM Power Down Mixer:

[0740] 0=Normal operation

[0741] 1=Mixer is powered down. While in this mode the codec interface is enabled and the codec registers are accessible.

[0742] RES—The RES bits are reserved bits that may be required for future changes or additions. These bits should have physical storage elements associated with them.

[0743] FIG. 25B is a diagram of the Hardware Control Register (at address base +1, default=0x10000000). This bitfield of this register can be described as follows:

[0744] The PCDINT (Polarity CDROM Interrupt) bit specifies polarity of CDROM interrupt input:

[0745] 0=CDROM interrupt is active low; and

[0746] 1=CDROM interrupt is active high.

[0747] The PSINT (Polarity Synthesizer Interrupt) bit specifies polarity of synthesizer interrupt input:

[0748] 0=synthesizer interrupt is active low; and

[0749] 1=synthesizer interrupt is active high.

[0750] The PMINT (Polarity Modem Interrupt) bit specifies polarity of modem interrupt input:

[0751] 0−modem interrupt is active low; and

[0752] 1=modem interrupt is active high.

[0753] The ADC1, ADCO (A/D Control 1,0) bits are used to control an additional analog mix/feedback path into the A/D converters:

[0754] 00=normal operation. A/D input from input mux/gain, stage. No mix of Input MLJX to output;

[0755] 01=output from Input Mux is mixed into line outputs. A/Dinput is from Input Mux;

[0756] 10=output from Input Mux is mixed into line outputs. A/D input is from line outputs; and

[0757] 11−reserved.

[0758] FIG. 25C is a diagram of the Power Down Control Register (at address control base +2, default=00000000). Microcontroller 103 reads this register and controls the various functions accordingly. An ISA bus write of this register will also generate an interrupt to microcontroller 103 microcontroller via INT1. This register is decoded:

[0759] FIG. 25D is a diagram of the bitfields of the Control Address/Index Register (at address, base +3, default=00000000). The Control Address/Index Register is used to specify an index into a set of extended control registers, discussed further below. Once a particular register index has been specified the register may be accessed by reading or writing the Control Data Register. Bits D7 . . . D4 are decoded and must be zero's to access the extended control registers.

[0760] FIG. 25E is a diagram of the bitfields of Control Data Register (at address base +4, default=00000000). The Control Data Register is used to access data from an extended control register that is specified in the Control Address/Data Register.

[0761] FIG. 25F is a diagram of the bitfields of the Command Register (at address base +5, default=00000000). This register is used to control various functions of Codec 100. A Command is executed after the appropriate Command identifier is written to this register. When this register is either read or written via the ISA bus an interrupt will occur to microcontroller 103 via INT1. The support commands are listed below:

[0762] FIG. 25G is a diagram of the bitfields of the Program RAM Access End Register (at address base +6, default=00000000). This register is used to end access to the Program RAM memory of Codec 100. When this register is written via the ISA bus, an interrupt will occur to microcontroller 103 via INT1.

[0763] FIG. 25H is a diagram of the bitfields of the Status Register (at address base +7, default=00000000). The bitfields decoding is as follows:

[0764] CSS (Context Switch Status) bit indicates current operating mode of Codec 100:

[0765] 0=Sound Blaster; and

[0766] 1=Sound System.

[0767] The CSI (Context Switch Interrupt Status) bit indicates current status of Context Switch Interrupt:

[0768] 0=no interrupt pending; and

[0769] 1=interrupt pending.

[0770] The SBI (Sound Blaster Interrupt Status) bit indicates current status of Sound Blaster Interrupt:

[0771] 0=no interrupt pending; and

[0772] 1=interrupt pending.

[0773] The CDECI (Codec Interrupt Status) bit indicates current status of Codec Interrupt:

[0774] 0=no interrupt pending; and

[0775] 1=interrupt pending.

[0776] The MPUI (MPU401 Interrupt Status) bit indicates current status of MPU-401 Interrupt:

[0777] 0=no interrupt pending; and

[0778] 1=interrupt pending.

[0779] Control Indirect Registers (C10-C131) are summarized in TABLE 48B above. The individual registers can now be described in further detail

[0780] FIG. 25I is a diagram of the bitfields of the Miscellaneous Control at Control Index register (C0, default=00000000). The bitfields decoding is as follows:

[0781] FIG. 25J is a diagram of the bitfields of the Version/ID at Control Index register (C1, default=10000100). This read only register shadows the current contents of codec indirect register I25. The register holds the current chip identifier and version number where:

[0782] FIG. 25K is a diagram of the bitfields of SRS Control Register at Control Index (C2, default=00000010). The bitfield decodings are:

[0783] SPC (Space) 3-0, SRS processed signal gain termed “SPACE”. The least significant bit represents −1.5 dB, the attenuation range is from 0 dB to −22.5 dB, with 0000=(0 dB or min attenuation). TABLE 49A associates the SPC register values with the resulting attenuation.

[0784] CNT (Center) 3-0, SRS processed signal gain termed “CENTER”. The least significant bit represents −1.5 dB, the attenuation range is from 0 dB to −22.5 dB, with 0000=(0 dB or min attenuation). TABLE 49B associates the CNT register values with the resulting attenuation.

[0785] When the SRS/MONO bit is set to a one this register is reset to 00100000.

[0786] FIG. 25L is a diagram of the bitfields of 3D Sound Control Register at Control Index (C3, default=00000000). The field decodings are as follows:

[0787] FIG. 25M is a diagram of the bitfields of the S/PDIF Control Register at Control Index (C4, default=00000000). The decodings are as follows:

[0788] FIG. 25N is a diagram of the bitfields of S/PDIF Channel Status Data −0 at Control Index (C5, Default=00000000). The bitfields are decoded as follows:

[0789] FIG. 25O is a diagram of the bitfields of S/PDIF Channel Status Data −1 at Control Index (C6) (Default=00000000). The bitfields are decoded as follows:

[0790] FIG. 25P is a diagram of the bitfields of FAB Port ID at Control Index (C7, Default=00000000). In order to track the various FAB ports of Codec 100 this register is updated each time any changes are done to the current revision in order to accommodate FAB specific requirements.

[0791] FIG. 25Q is a diagram of the bitfields of Wavetable and Serial Port at Control Index (C8, Default=00000000). The bitfield encodings are as follows:

[0792] WTEN Wavetable Enable—When this bit is set to a one the XD7:XD5 pins are switched to support a wavetable interface as shown in TABLE 50:

[0793] If either WTEN or SPS are set to a one then the XBUF bit in CDROM Interface Control Register at microcontroller 103 address 0x34 is forced to a one.

[0794] FIG. 25R is a diagram of the bitfields of Left Output Master Volume at Control Index (C27, default=001x0000) where:

[0795] LOA3-LOA0 are the Left Output Master Volume bit LOA0 is the least significant bit and represents 2 dB steps. The range is +12 db to −18 db; and

[0796] LMS1:LMS0 are the Left Output Mixer Summer Attenuation bits and:

[0797] FIG. 25S is a diagram of the bitfields of Right Output Master Volume at Control Index (c29, default=001x000) where:

[0798] ROA3-ROA0 are the Right Output Master Volume bits.

[0799] ROA0 is the least significant bit and represents 2 dB steps. The range is +12 dB to −18 dB; and

[0800] RMS1:RMS0 Right Output Mixer Summer Attenuation

[0801] where:

[0802] Codec Interface

[0803] Codec Interface 107 includes logic that enables access to the registers located in core from either the ISA bus (through Plug-n-Play configuration registers) or microcontroller 103. FIG. 26 is a diagram emphasizing Codec Interface 100.

[0804] The Sound System Codec software interface consists of 4 I/O locations starting at the Plug and Play address values ‘WSSbase’ shown in TABLE 52A, and supports 12-bit address decoding. If the upper address bits, SA12-SA15 are used, they must be a 0 to decode a valid address. The SS Codec also requires one interrupt and one or preferably two DMA channels, one for playback and one for capture. Since the SS Codec and Sound Blaster device are mutually exclusive, the two devices share the same interrupt and DMA playback channel.

[0805] The WSS Codec functions 204 include FIFOs 121 and 122 (FIG. 1) 16-sample FIFOs in both the playback and capture digital audio data paths. The FIFOs are transparent and have no programming associated with them.

[0806] When playback is enabled, playback FIFO 121 continually requests data until the FIFO is full, and then makes requests as positions inside the FIFO are emptied, thereby keeping as full as possible. Thus, when Codec 100 cannot respond within a sample period, the FIFO starts to empty, avoiding a momentary loss of audio data output to the ISA bus. If the FIFO runs out of data, the last valid sample can be continuously output to the DACs (if DACZ in register I16 is set) which will eliminate pops from occurring.

[0807] When capture is enabled, capture FIFO 121 continually makes requests to the ISA bus every sample period thereby attempting to remain empty. Thus, when codec 100 cannot respond within a sample period, capture FIFO 121 starts filling, thereby avoiding a loss of data in the audio data stream.

[0808] Four I/O mapped locations (block 107, FIG. 1) are available for accessing the Codec functions and mixer. The control registers allow access to status, audio data, and all indirect registers via the index registers. The IOR and IOW signals are used to define the read and write cycles respectively. A PIO access to the Codec begins when the host puts an address on the ISA bus which matches WSSbase and drives AEN low. WSSbase is programmed during a Plug and Play configuration sequence. Once a valid base address has been decoded then the assertion of IOR will cause the WSS Codec to drive data on the ISA data bus lines. Write cycles require the host to assert data on the ISA data bus lines and strobe the IOW signal. The WSS Codec will latch data into the PIO register on the rising edge of the IOW strobe.

[0809] The audio data interface typically uses DMA request/grant pins to transfer the digital audio data between WSS Codec 204 functions and the bus. WSS Codec 204 functions is responsible for asserting a request signal whenever the Codec's internal buffers need updating. The bus responds with an acknowledge signal and strobes data to and from the Codec, 8 bits at a time. WSS Codec functions keep the request pin active until the appropriate number of 8-bit cycles have occurred to transfer one audio sample. Note that different audio data types require a different number of 8-bit transfers.

[0810] The second type of parallel bus cycle from WSS Codec 204 is a DMA transfer. DMA cycles are distinguished from PIO register cycles by the assertion of a DRQ, while AEN is inactive, followed by an acknowledgment by the host by the assertion of DACK. While the acknowledgment is received from the host, WSS Codec 204 assumes that any cycles occurring are DMA cycles and ignores the addresses on the address lines.

[0811] WSS Codec 204 may assert the DMA request signal at any time. Once asserted, the DMA request will remain asserted until a complete DMA cycle occurs. DMA transfers may be terminated by resetting the PEN and/or CEN bits in the Interface Configuration register (I9), depending on the DMA that is in progress (playback, capture, or both). Termination of DMA transfers may only happen between sample transfers on the bus. If DRQ goes active while resetting PEN and/or CEN, the request must be acknowledged with DACK and a final sample transfer completed.

[0812] Mapping of the WSS Codec DRQ and DACK onto the ISA bus is accomplished by the Plug and Play configuration registers. If the Plug and Play resource data specifies only one DMA channel for the Codec (or the codec is placed in SDC mode discussed below) then both the playback and capture DMA requests should be routed to the same DRQ/DACK pair (DMA Channel Select 0). If the Plug and Play resource data specifies two DMA channels for the Codec, then the playback DMA request will be routed to the DMA pair specified by the DMA Channel Select 0 resource data, and the capture DMA requests will be routed to the DMA pair specified by the DMA Channel Select 1 resource data.

[0813] WSS Codec 204 supports a single and a dual DMA channel mode. In dual DMA channel mode, playback and capture DMA requests and acknowledges occur on independent DMA channels. In dual DMA mode, SDC should be set to 0. The Playback- and Capture-Enables (PEN, CEN, I9) can be changed without a Mode Change Enable (MCE, R0). This allows for proper full duplex control where applications are independently using playback and capture.

[0814] When two DMA channels are not available, the SDC mode forces all DMA transfers (capture or playback) to occur on a single DMA channel (playback channel). The trade-off is that the WSS Codec will no longer be able to perform simultaneous DMA capture and playback.

[0815] To enable the SDC mode, set the SDC bit in the Interface Configuration register (I9). With the SDC bit asserted, the internal workings of the WSS Codec remain exactly the same as dual mode, except for the manner in which DMA request and acknowledges are handled.

[0816] The playback of audio data will occur on the playback channel exactly as dual channel operation; however, the capture audio channel is now diverted to the playback channel. Alternatively stated, the capture DMA request occurs on DMA channel select 0 for WSS Codec 204. (In MODE 2, the capture data format is always set in register I28.) If both the both playback and capture are enabled, the default will be playback. SDC does not have any affect when using PIO accesses.

[0817] As discussed briefly above, Windows Sound System codec 204 is mapped via four locations. The I/O base address, WSSbase, is determined by the Plug and Play configuration. The WSSbase supports four direct registers, shown in TABLE 52A. The first two direct registers are used to access 32 indirect registers shown in TABLE 52B. The Index Address register (WSSbase+0) points to the indirect register that is accessed through the Indexed Data register (WSSbase+1).

[0818] The Master Volume Control uses a 26-step linear mapping of 2 dB per step. The Sound Blaster Mixer Master Fader Control uses the non-linear Sound Blaster mapping with a range of 0 dB to −28 dB in eight steps.

[0819] The ISA bus writes to the Sound Blaster Mixer Master address and Volume change button pushes are mapped to the CODEC_MASTER_OUT registers, I27A and I29A. The Sound Blaster mixer range is implemented as a gain reduction to the current CODEC Master Volume setting. Thus, the Master Volume setting of +2 dB will allow a 2 dB to −26 dB Sound Blaster Master Out control gain range. A Master Volume setting of −30 dB will allow a −30 db to −36 dB range for the Sound Blaster Master Out control. In all cases, moving the Sound Blaster Master Out Control to the bottom of its range (zero or one) will cause a CODEC mute. Also the lowest CODEC Master Volume step (twenty six) will cause a CODEC mute.

[0820] The default for the Master Volume control is 0 dB. The default for the Sound Blaster Master Out Control is −11 dB.

[0821] The UP/DOWN/MUTE pins are accessible by microcontroller 103 at Port 3 when the VCEN bit has been set to a one at microcontroller 103 address 0x34. FIG. 8, discussed briefly above, generally describes the bit fields of Port 3. Once VCEN=1, microcontroller 103 access to Port 3 will return the current data present on the UP/DOWN/MUTE pins (TTL levels).

[0822] The 26-step volume control is implemented using a 26 byte table which maps the numbers 0-25 with the Summer and Gain settings.

[0823] The user changes the Sound Blaster Master Volume by using ISA bus writes to the Sound Blaster mixer (external) mapped at I/O addresses 0x224 and 0x225.

[0824] The embedded code uses a combination of 2 groups of internal RAM variables and the I27A/I29A codec registers to accomplish Master volume control. The user hits buttons and the embedded code increments or decrements a count to keep track of the Master volume. This value is then combined with the appropriate mode fader (SB Master volume for Sound Blaster mode or WSS Master volume for Windows Sound System mode) to arrive at the final register value which will be written to the Codec registers I27A and I29A 205. TABLE 53 defines the Codec Master Map which correlates index values, register values and dB settings.

[0825] Master Volume Algorithm:

[0826] dCodecMasterVoiL/R+dWSSMasterVoil/*R=“index into CODEC_MASTER_MAP_TABLE ”

[0827] “CODEC_MASTER_MAP_TABLE Register Value”=I27A/I29A value.

[0828] *It is assumed that because the driver will vary the Codec Master Volume that the WSS Master Volume will not be used and therefore will always remain at its default value of 0 (db). Because of this the dWSSMasterVoiL and dWSSMasterVolR values can be ignored when handling the Master Volume Control.

[0829] To read the Codec Master volume:

[0830] 1. Read dCodecMasterVolL/dCodecMasterVolR (using a RAM Internal Access command)to obtain Index Value.

[0831] 2. Convert Index Value to dB setting using the CODEC_MASTER_MAP_TABLE.

[0832] To write the Codec Master volume:

[0833] 1. Receive user dB setting;

[0834] 2. Convert dB setting to Index Value based on CODEC_MASTER_MAP_TABLE;

[0835] 3. Convert dB setting to Register Value based on CODEC_MASTER_MAP_TABLE;

[0836] 4. Write dCodecMasterVolL/dCodecMasterVolR registers with Index Value (using new RAM Internal Access command);

[0837] 5. Write dLMasterHold/dRMasterHold registers with the Register Value (using new RAM Internal Access command); and

[0838] 6. Perform Hold/Go OR Write I27/I29 via the Hold/Go mechanism using the Register Value. (Any Hold/Go sequence will cause I27/I29 registers to be updated with the register values in dLMasterHold/dRMasterHold).

[0839] The Codec Master Volume Buttons are set at Max (+12 dB) volume. If a 0x16 is written to dWSSMasterVolL and dWSSMasterVolR via the control port commands, then the Master output level will be −32 dB.

[0840] In both Sound Blaster mode and WSS mode, the user may change the CODEC Master Volume via pins connected to physical switches or buttons. There are four different “button schemes” supported by the Codec 100.

[0841] The user selects one of these four schemes by setting the VCF1 and VCF0 bits in the Hardware Configuration Data, Global Configuration Byte, contained in external EEPROM.

[0842] In the first scheme, the Up and Down pins are connected to momentary SPST switches and the Mute pin connected to a Push on/push off SPST switch. This scheme is selected by setting VCF1 and VCF0 to 00. The first scheme provides the functionality described in TABLE 54.

[0843] In the second scheme, the Up, Down and Mute pins are connected to momentary SPST switches and is selected by setting VCF1 and VCF0 to 01. TABLE 55 describes button operations in this scheme.

[0844] In the third scheme, the Up and Down pins are connected to momentary SPST switches and the Mute pin is NOT connected. This scheme is selected by setting VCF1 and VCF0 to 10. TABLE 56 describes the button operations in this scheme.

[0845] In the fourth scheme, the Mute and Down pins are connected to momentary SPST switches. The Mute pin is connect to the Up button momentary SPST switch. The Up pin is NOT connected. This scheme is selected by setting VCF1 and VCF0 to 11. Button functionality for the fourth scheme is described in TABLE 57.

[0846] FIG. 27A-27BB and the accompanying text describe Codec Register 107 in further detail.

[0847] FIG. 27A is a diagram of the bitfield Index Address Register at address (WSSbase +0, R0). The bitfields are described below:

[0848] Immediately after RESET (and once WSS Codec 204 has left the INIT state), the state of this register is: 010x0000 (binary - where ‘x’ indicates unknown). During initialization and software power down (PMl, 0=01), this register cannot be written and always reads 10000000 (80 h).

[0849] FIG. 27B is a diagram of the bitfield of Indexed Data Register (at address WSSbase+1, R1). The bitfield decoding is as follows:

[0850] ID7-ID0 Indexed Data register: These bits are the indirect register referenced by the Indexed Address register (R0).

[0851] During initialization and software power down of WSS Codec 204, this register cannot be written and is always read 10000000 (80h).

[0852] FIG. 27C is a diagram of the bitfield Status Register (at address WSSbase+2, R2, Read Only). The bitfield decodings are:

[0853] Note on PRDY/CRDY: These two bits are designed to be read as one when action is required by the host. For example, when PRDY is set to one, the device is ready for more data; or when the CRDY is set to one, data are available to the host. The definition of the CRDY and PRDY bits are therefore consistent in this regard.

[0854] The PIO Data register is two registers mapped to the same address. Writes to this register sends data to the Playback Data register. Reads from this register will receive data from the Capture Data register.

[0855] During initialization and software power down of WSS Codec 204, this register cannot be written and is always read 10000000 (80 h).

[0856] FIG. 27D is a diagram of the bitfield Capture I/O Data Register (at address WSSbase+3, R3, Read Only). The bitfield encodings are as follows:

[0857] CD7-CF0 Capture Data Port. This is the control register where capture data are read during programmed I/O data transfers.

[0858] The reading of this register will increment a state machine so that the following read will be from the next appropriate byte in the sample. The exact byte which is next to be read can be determined by reading the Status register (R2). Once all relevant bytes have been read, the state machine will point to the last byte of the sample until a new sample is received from ADCs lll. Once the Status register (R2) is read and a new sample is received from the FIFO, the state machine and Status register (R2) will point to the first byte of the new sample.

[0859] During initialization and software power down of WSS Codec 204, this register cannot be written and is always read 10000000 (80 h).

[0860] FIG. 27E is a diagram of the bitfield of Playback I/O Data Register (at address WSSbase+3, R3, Write Only).

[0861] PD7-PD0 Playback Data Port. This is the control register where playback data are written during programmed IO data transfers.

[0862] Writing data to this register will increment the playback byte tracking state machine so that the following write will be to the correct byte of the sample. Once all bytes of a sample have been written, subsequent byte writes to this port are ignored. The state machine is reset after the Status register (R2) is read, and the current sample is sent to the DACs 110 via the FIFOs 122.

[0863] The indirect registers are accessed by placing the appropriate index in the Index Address register (R0) and then accessing the Indexed Data register (R1) discussed above. A detailed description of each indirect register is given below. All reserved bits should be written zero and may be 0 or 1 when read. Note that indirect registers 16-31 are only available when the MODE 2 bit in MODE and ID register (I12) is set.

[0864] FIG. 27F is a diagram of the bitfield of Left ADC Input Control (I0, default=000x0000). The field decodings for this register are:

[0865] FIG. 27G is a diagram of the bitfield of Right ADC Input Control (I1, default=000x0000). The bitfield decodings are:

[0866] FIG. 27H is a diagram of the bitfield of Left Auxiliary #1 Input Control (I2, default=1xx01000). The bitfield decoding for this register is:

[0867] FIG. 27I is a diagram of the bitfield of Right Auxiliary #1 Input Control (I3, default=1xx01000). The bitfields are:

[0868] FIG. 27J is a diagram of the bitfield of Left Auxiliary #2 Input Control (I4, default=1xx01000). The bitfield decodings are:

[0869] FIG. 27K is a diagram of the bitfields of Right Auxiliary #2 Input Control (I5, default=1xx01000). The bitfields decodings are:

[0870] FIG. 27L is a diagram of the bitfield of Left DAC Output Control (I6, default=1x000000).

[0871] FIG. 27M is a diagram of the bitfield of Right DAC Output Control (I7, default=1x000000). The bitfields are decoded as:

[0872] FIG. 27N is a diagram of the bitfield of Fs and Playback Data Format (I8, default=00000000). The bitfield decoding is as follows:

[0873] C/L, FMT1, and FMT0 bits set the audio data format as shown in TABLE 58. In MODE 1, FMT1, which is forced low, FMT0, and C/L are used for both playback and capture. In MODE 2, these bits are only used for playback, and the capture format is independently selected via register I28. MCE (R0) or PMCE (I16) must be set to modify the lower four bits of this register. See Changing Audio Data Formats section for more details.

[0874] FIG. 27O is a diagram of the bitfield of Interface Configuration (I9, default=00x01000). The bitfields are decoded as follows:

[0875] This register, except bits CEN and PEN, can only be written while in Mode Change Enable (either MCE or PMCE).

[0876] FIG. 27P is a diagram of the bitfields of Pin Control (I10, default=0000000x). The bitfields are:

[0877] FIG. 27Q is a diagram of the bitfields of Error Status and Initialization (I11, Read Only, default=00000000). The bitfields are decoded as:

[0878] The SER bit in the Status register (R2) is simply a logical OR of the COR and PUR bits. This enables a polling host CPU to detect an error condition while checking other status bits.

[0879] FIG. 27R is a diagram of the bitfield of ODE and ID (I12, default=10xx1010). The bitfields are decoded as follows:

[0880] FIG. 27S is a diagram of the bitfield of Loopback Control (I13, default=000000x0). The bitfields of this register are decoded as follows:

[0881] FIG. 27T is a diagram of the bitfield of Playback Upper Base (I14, default=00000000) The bitfields of this register are decoded as follows:

[0882] PUB7-PUB0 Playback Upper Base: This register is the upper byte which represents the 8 most significant bits of the 16-bit Playback Base register. Reads from this register return the same value which was written. The Current Count registers cannot be read. When set for MODE 1 or SDC, this register is used for both the Playback and Capture Base registers.

[0883] FIG. 27U is a diagram of the bitfield of Playback Lower Base (I15, default=00000000). The bitfields of this register are decoded as Follows:

[0884] PLB7-PLB0 Lower Base Bits: This register is the lower byte which represents the 8 least significant bits of the 16-bit Playback Base register. Reads from this register return the same value which was written. When set for MODE 1 or SDC, this register is used for both the Playback and Capture Base registers.

[0885] FIG. 27V is a diagram of the bitfield of Alternate Feature Enable I (I16, default=00000000). The bitfields of this register are decoded as follows:

[0886] FIG. 27W is a diagram of the bitfield of Alternate Feature Enable II (I17, default=0000x000). The bitfields of this register are decoded as follows:

[0887] FIG. 27X is a diagram of the bitfield of Left Line Input Control (I18, default=1xx01000). The bitfields of this register are described as follows:

[0888] FIG. 27Y is a diagram of the bitfield of Right Line Input Control (I19, default=1xx01000). The bitfields of this register are decoded as follows:

[0889] FIG. 27Z is a diagram of the bitfield of Timer Lower Base (I20, default=00000000). The bitfields of this register are decoded as follows:

[0890] TL7-TL0 Lower Timer Bits: This is the low order byte of the 16-bit timer base register. Writes to this register cause both timer base registers to be loaded into the internal timer, therefore, the upper timer register should be loaded before the lower. Once the count reaches zero, an interrupt is generated, if enabled, and the timer is automatically reloaded with these base registers.

[0891] FIG. 27AA is a diagram of the bitfield of Timer Upper Base (I21, default=00000000). The bitfields of this register are decoded as follows:

[0892] FIG. 27AB is a diagram of the bitfield of Alternate Sample Frequency Select (I22, default=00000000). The bitfields of this register are decoded as follows:

[0893] FIG. 27AC is a diagram of the bitfield of Alternate Feature Enable III (I23, default=xxxxxxx0). The bitfields of this register are decoded as follows:

[0894] FIG. 27AD is a diagram of the bitfield of Alternate Feature Status (I24, default=x0000000). The bitfields of this register are decoded as follows:

[0895] FIG. 27AE is a diagram of the bitfield of Mono Input and Output Control (I26, default=101x0000). The bitfields of this register are decoded as follows:

[0896] FIG. 27AF is a diagram of the bitfield of Left Output Attenuation (I27, default=0xxx0000). The bitfields of this register are decoded as follows:

[0897] FIG. 27AG is a diagram of the bitfield of Capture Data Format (I28, default=0000xxxx). The bitfields of this register are decoded as follows:

[0898] C/L, FMT1, FMT0 set the capture data format in MODE 2. The capture data format can be different from the playback data format; however, the sample frequency must be the same and is set in I8. MCE (R0) or CMCE (I16) must be set to modify this register.

[0899] FIG. 27AH is a diagram of the bitfields of Right Output Attenuation I29, default−0xxx0000). The bitfields of this register are decoded as follows:

[0900] FIG. 27AI is a diagram of the bitfield of Capture Upper Base (I30, default=00000000). The bitfields of this register are decoded as follows:

[0901] CUB7-CUB0 Capture Upper Base: This register is the upper byte which represents the 8 most significant bits of the 16-bit Capture Base register.

[0902] Reads from this register returns the same value that was written.

[0903] FIG. 27AJ is a diagram of the bitfields of Capture Lower Base (I31, default=00000000). The bitfields of this register are decoded as follows:

[0904] CLB7-CLB0 Lower Base Bits: This register is the lower byte which represents the 8 least significant bits of the 16-bit Capture Base register. Reads from this register returns the same value which was written.

[0905] The extended registers TABLE 52C are accessed by placing the appropriate index in the Index Address register (R0) and then accessing the Indexed Data register (R1). A detailed description of each indirect register is given below. All reserved bits should be written zero and may be 0 or 1 when read. Indirect registers 16-31 are only available when the MODE 2 bit in MODE and ID register (I12) is set.

[0906] FIG. 27AK is a diagram of the bitfields of Left Alternate FM Input Control (X0, default=00000000). The bitfields of this register are decoded as follows:

[0907] FIG. 27AL is a diagram of the bitfields of Right Alternate FM Input Control (X1, default=00000000). The bitfields of this register are decoded as follows:

[0908] FIG. 27AM is a diagram of the bitfields of Left Mic Input Control (X2, default=00000000). The bitfields of this register are decoded as follows:

[0909] FIG. 27AN is a diagram of the bitfields of Right Mic Input Control (X3, default=00000000). The bitfields of this register are decoded as follows:

[0910] FIG. 27AO is a diagram of the bitfield of Control (X4, default=00000100). The bitfields of this register are decoded as follows:

[0911] FIG. 27AP is a diagram of the bitfield of Control (X5, default=00000000). The bitfields of this register are decoded as follows:

[0912] FIG. 27AQ is a diagram of the bitfields of Left FM Volume Control (X6, default=10111111). The bitfields of this register are decoded as follows:

[0913] FIG. 27AR is a diagram of the bitfield of Right FM Volume Control (X7, default=10111111). The bitfields of this register are decoded as follows:

[0914] FIG. 27AS is a diagram of the bitfield of Left DSP Serial Port Volume Control (X8, default=00000000). The bitfields of this register are decoded as follows:

[0915] FIG. 27AT is a diagram of the bitfield of Right DSP Serial Port Volume Control (X9, default=00000000). The bitfields of this register are decoded as follows:

[0916] FIG. 27AU is a diagram of the bitfield of Right Digital Loopback Volume Control (X10, default=00111111). The bitfields of this register are decoded as follows:

[0917] FIG. 27AV is a diagram of the bitfield of DAC, SRC Control (X11, default=11000000). The bitfields of this register are decoded as follows:

[0918] FIG. 27AW is a diagram of the bitfield of Capture Sample Rate Control (X12, default=00110000). The bitfields of this register are decoded as follows:

[0919] CSR7-CSR0 Sets the sample rate for the A/D.

[0920] FIG. 27AX is a diagram of the bitfield of Playback Sample Rate Control (X13, default=00110000). The bitfields of this register are decoded as follows:

[0921] PSR7-PSR0 Sets the sample rate for the A/D.

[0922] FIG. 27AY is a diagram of the bitfield of Left PCM Audio Volume Control (X14, default=00000000). The bitfields of this register are decoded as follows:

[0923] LPA7-LPA0 Left PCM Audio Volume Control. Least significant bit represents 1.5 dB, with 000000=0 dB.

[0924] FIG. 27AZ is a diagram of the bitfields of Right PCM Audio Volume Control (X15, default=00000000). The bitfields of this register are decoded as follows:

[0925] RPA7-RPA0 Right PCM Audio Volume Control. Least significant bit represents 1.5 dB, with 000000=0 dB.

[0926] FIG. 27BA is a diagram of the bitfields of Left Wavetable Volume Control (X16, default=10000000).The bitfields of this register are decoded as follows:

[0927] LPA7-LPA0 Left wavetable Audio Volume Control. Least significant bit represents 1.5 dB, with 000000=+12 dB.

[0928] FIG. 27BB is a diagram of the bitfield of Right Volume Control (X17, default=10000000). The bitfields of this register are decoded as follows:

[0929] RB7-RB0 Right Wavetable Audio Volume Control. Least significant bit represents 1.5 dB, with 000000=+12 dB.

[0930] Some operating modes of Codec/mixer 204 will require that microcontroller 103 and ISA Bus both have access to the Codec data bus. An example of this is when microcontroller 103 is updating the Codec/mixer 204 mixer registers for Sound Blaster Pro functions while DMA audio is being transferred over the data bus. To arbitrate between the two devices a software arbitration scheme is used. Each Sound Blaster command (ISA write to Sound Blaster base+C) causes the ISA Bus signal IOCHRDY to be forced low thereby holding the current bus cycle (DMA cycles held off). Codec 100 makes use of this time and microcontroller 103 is guaranteed access to the codec for mixer updates. Once IOCHRDY is released, after microcontroller 103 has finished accessing the codec, the current bus cycle is allowed to complete.

[0931] A context switch mechanism is provided to enable switching between Sound Blaster mode and Windows Sound System mode transparently to the user. Logic detects when a mode change from Sound Blaster to Sound System occurs and an interrupt is generated to microcontroller 103. The switch from Sound System to Sound Blaster is done by microcontroller 103 without any additional external logic support. Optionally a ISA Bus interrupt may be generated upon detection of a Context Switch provided the interrupt is enabled via Codec 100 Miscellaneous Control Reg. (base +0). FIG. 28 is a timing diagram of a typical context switching operation.

[0932] When a context switch from Sound Blaster to WSS mode occurs IOCHRDY is forced low. The current ISA bus access to codec/mixer 204 is thereby held off until the interrupt has been acknowledged by microcontroller 103. The “Context Switch” is only recognized (enabled) when the WSS and Sound Blaster physical devices are enabled. Accordingly IOCHRDY is not driven low during a Context Switch unless both the WSS and Sound Blaster devices are enabled.

[0933] A context switch from Sound Blaster to WSS mode results in codec/mixer 204 being set to mode 1 operation and the SRE and CMCE bits will be set to zero. No other register bits are affected.

[0934] A context switch from WSS to Sound Blaster mode results in the mixer registers being restored to values that existed the last time Codec 100 was in Sound Blaster mode. In other words during context switches Sound Blaster mixer settings are retained while WSS mixer settings are not.

[0935] In Codec 100 the context switch from WSS to Sound Blaster mode occurs during the first access to the Sound Blaster Command register or a “Sound Blaster Reset Command”.

[0936] FIG. 29 is a diagram of the External Peripheral Port 109. External Peripheral Port is a general purpose programmable port that is used to connect external devices to the ISA bus with a minimum of glue logic. The External Peripheral interface includes buffers 2901 and decode-strobe generation logic 2902 to provide an independent data path to the external synthesizer chip and CDROM IDE interface. The External Peripheral Port buffers the ISA data bus and SA2:SA0 address lines, generates Read and Write strobes, and provides programmable I/O base address decoding, and DMA/Interrupt mapping. The XIOR/and XIOW/strobes are generated by gating the IOR/and IOW/signals with the CDCS0/, CDCS1/, SCS/, and MODEMCS/chip selects. The timing of External Peripheral port reads and writes is shown in FIGS. 30A and 30B.

[0937] Synthesizer Interface 123 may be used to provide a direct connection to an OPL3/4 synthesizer chip. The interface consists of an address decoder 3101 (see FIG. 31 which emphasizes the synthesizer and CDROM interfaces) and an input for an interrupt The other signals such as address bits and read/write strobes are provided by the External Peripheral Port. Address decoder generates a chip select. The address that is decoded is determined by data that is written during a Plug & Play configuration sequence. The chip select is a logical OR of the synthesizer (Adlib) decode and Sound Blaster synthesizer decode. The interrupt is mapped onto the ISA bus depending on the configuration defined during the Plug & Play sequence.

[0938] synth chip select=decode of synthesizer ISA address (338:33B) OR decode of Sound Blaster base address (0:3 and 8:9)

[0939] The CDROM interface (see also FIG. 31) provides a connection to CDROM drives 3103. The interface consists of programmable address decoders 3101 and 3102 to act as a device selects, DMA request and acknowledge mapping, and interrupt mapping. A Plug & Play sequence will determine the base address and specific DMA and interrupt mapping. Various CDROM interfaces such as Mitsumi, Sony, Panasonic, and Enhanced IDE are supported. The other signals required for the CDROM interface are provided by the External Peripheral Port.

[0940] FIG. 32 emphasizes the clocking scheme for codec 100. Microcontroller 103 clock requirement is a non-overlay 2-phase clock that is under 17.5 MHz in frequency. The 16.9344 MHz clock fits this criteria. Microcontroller 103 Timer 2, which is used as the MIDI baud rate generator, is always clocked via an externally generated clock that is derived from the 16.9344 MHz crystal/17or 996.141 kHz. The other requirement is a 2-phase non-overlap clock. The non-overlap must >=5 ns. The microcontroller clock is generated by 2-phase non-overlap clock generator 3201.

[0941] In Codec 100 the ADC and DAC operate at a fixed sample frequency of 44.1 kHz. Sample rate converters are used to convert between variable system sample rates and the 44.1 kHz required by the converters. The analog clock for the converter switched capacitor filters operates at a fixed 128 fs frequency. The delta-sigma modulators operate at a fixed 256 fs clock rate.

[0942] The internal FM clock uses the 16.9344 MHz 384 fs clock.

[0943] A large number of available sample rates are provided by two independent sample rate converters 112; one for capture and one for playback. Sample rate converters 112 convert from a variable rate to a fixed 44.1 kHz rate. The sample frequency is determined by a register value that is used to index a ROM 3202. ROM 3202 stores the coefficients used by the sample rate converter to perform the rate conversion.

[0944] FIG. 33 is a diagram of the Game Port which provides an interface to a standard personal computer type joystick. The joystick interface supports two joysticks and four push buttons. The ISA interface to the Game Port includes an address decoder and read/write strobe generator.

[0945] The Game Port hardware interface consists of four 555 like timers 3301 (two of which are shown for reference), read/write strobe generator 3305, address decode 3303 and data buffer 3304. A selected joystick itself consists of two 100K potentiometers 3302; one (3302a) for the x-axis and one (3302b) for the y-axis. As the joystick position is varied the resistance of the x and y axis potentiometers will also vary in direct proportion to the joystick movement. In addition one-to-four push buttons 3306 may be included, two of which (3303aand 3303b) are shown in FIG. 33. One timer 3301 is connected to each potentiometer. Two joysticks therefore require four timers. Once triggered the timer output pulse width is determined by the output current supplied by the timer, the joystick potentiometer resistance, and an external capacitor. Host software on the personal computer continually reads the timer pulse outputs and determines joystick position depending on the width of the pulses. The state of the push buttons are also monitored by the host software.

[0946] Digital Pulse Width=24.2 usec +0.011 (r)usecr=resistive load

[0947] Codec 100 provides for four selectable time constants. The default should match the one above and the others should offer shorter time constants.

[0948] Programmable speed control is implemented by selecting one of four reference voltages that is fed to the input of a comparator. The other input to the comparator is connected to the external joystick RC circuit. The four selectable reference voltages allow the trip-point of the comparator to be varied over a range of voltages associated with a typical RC generated curve. The speed control variation is illustrated in FIG. 34.

[0949] To minimize the noise effects of large di/dt currents generated by the discharge of the external 0.0056 uF capacitor the following techniques are used:

[0950] 1) Separate analog ground for capacitor discharge devices;

[0951] 2) Discharge control will be synchronized to the internal noise-managed digital clock; and

[0952] 3) Sequential, two-step discharge. (small device first, large device later).

[0953] FIG. 35 is a timing diagram illustrating the joystick port timing. This timing generally follows the following routine:

[0954] 1) DIS1 & DIS2 must be driven low on the first noise-managed clock after a valid joystick 10W;

[0955] 2) COMPJ output will go low T=RC later;

[0956] 3) DIS1 must be raised on the first noise-managed clock edge after COMPJ output goes low;

[0957] 4) DIS2 should go high˜lused: after DIS1 (DIS2 high will cause COMPJ output to go high); and

[0958] 5) In powerdown (PDN active), DIS1 & DOS2 must be low.

[0959] In order to support Microsoft's DirectInput™ specification for digitally assisted joysticks the Codec 100 includes the features described below.

[0960] FIG. 36A generally describes joystick interface 105. A more detailed illustration of the circuitry 3601 of FIG. 36A is provided as 36B.

[0961] Joystick coordinate block 3601 includes a 16-bit up-counter 3603 and latch 3604 for each joystick input for each joystick (i.e., a total of four). The counters all operate in parallel via the same clock (XTAL/2) with each counter gated by its corresponding joystick coordinate enable. Each individual enable signal is generated by the joystick COMPJ blocks 3602. COMPJ blocks 3602 produce a pulse in whose length is defined by the current joystick position. The trigger for COMPJ block 3602 is initiated by an ISA bus write to the Game Port address base +[0 . . . 5] or by microcontroller 103 write to memory address 0x38. In the normal operating mode one trigger is produced per ISA bus write, but when the Auto Re-trigger Enable bit is set, the circuit becomes self-triggering and further ISA bus or microcontroller 103 writes are not required. However the host is still able to generate a trigger by performing a write to the Game Port base [0 . . . 5].

[0962] Each counter increments for a period of time defined by the enable. At the end of the current pulse (trigger) period, as defined by the longest COMPJ pulse, the current counter values are clocked into the holding registers and the counters are reset. The holding registers may then be read by microcontroller 103 in response to an ISA bus read of Game Port address base +7. Each holding register requires that two addresses (16-bits) be mapped into microcontroller 103 address space. This results in eight addresses being required in total (addresses 0x38 through 0x3F). In order for microcontroller 103 to accurately read the holding registers (there is a possibility that microcontroller 103 read could occur at the same time as the holding register is clocked), a hardware locking mechanism prevents clocking of the holding registers while microcontroller 103 is in processes of accessing the registers.

[0963] Each joystick, joystick A and joystick B, independently controls the clocking of each X, Y counter pair. In other words the X1 and Y1 counters follow the joystick A movement only, and the X2 and Y2 counters follow the joystick B movement only.

[0964] The X1, Y1 and X2, Y2 counters do not wrap around. When a maximum count value of 0xFFFF is reached, the counter is prevented from incrementing further and the 0xFFFF count is held until the next one-shot trigger pulse occurs (which resets the counters to zero). This prevents unconnected joysticks from generating false count values. In normal operation the X,Y position counters should never reach a count value of 0xFFFF.

[0965] In order to provide support for joystick digital assist the PO address decoding for the standard joystick is changed as follows:

[0966] 1) Game Port address range remains at eight bytes;

[0967] 2) Standard joystick access occurs at addresses Game Port Base Address+0 through 5. A write to any of these addresses causes a trigger of the one-shots. A read from any of these addresses puts the current one-shot and button data onto the ISA bus;

[0968] 3) The Joystick Digital Assist register is located at Game Port Base+7. A read or write of Game

[0969] Port Base+7 interrupts microcontroller 103 with a PORTI. value of 0x5C (write) and 0x5E (read); and

[0970] 4) Access to Game Port Base+6 is reserved for future use. A read or write access to Game Port Base+6 will interrupt microcontroller 103 and generate a PORTI value of 0x58 (write) and 0x5A(read).

[0971] Host control and data access of the Joystick Digital Assist function occurs via a read/write port at the GamePort (base+7) address. An ISA bus read or write cycle to this address interrupts microcontroller 103 via INTI and IOCHDRY is forced low. Also a interrupt identifier of 0x5C(write) or 0x5E (read) is placed on PORT1. Microcontroller 103 responds by either a read of microcontroller 103 address 0 (ISA write) or writing to microcontroller 103 address 0x00 (ISA read). All Joystick Digital Assist commands to read joystick positional data or control its operation are sent through this port.

[0972] Microcontroller 103 may access the Digital Assist Registers at any time, but data integrity is only guaranteed with the following sequence. Microcontroller 103 read from address 0x38 (XI Position Low Byte) will cause the hardware to prevent any further updates of the Digital Assist Position Registers. Microcontroller 103 may then continue reading the other Digital Assist Position registers. As the Digital Assist Position Registers are being accessed by microcontroller 103, the one-shot counters will continue to be updated by auto-retrigger pulses in the background. Upon the final read of address 0x3F (Y2 position high byte) the clocking of the Digital Assist Position Registers will be enabled. Digital Assist Position Registers will then be clocked at the end of the next one-shot pulse period.

[0973] FIG. 37A is a diagram of the bitfields of Digital Assist Control/Status at microcontroller 103 address=0x37. The bitfields of this register are decoaed as follows:

[0974] FIG. 37B is a diagram of the bitfields of Joystick Trigger/X1 Position Data Low Byte at microcontroller 103 address=0x38. The bitfields of this register are decoded as follows:

[0975] FIG. 37C is a diagram of the bitfields of X1 Position Data High Byte at microcontroller 103 address=0x39. The bitfields of this register are decoded as follows. This register when read will return the high byte of the last known 16-bit position of the joystick #1 X coordinate.

[0976] FIG. 37D is a diagram of the bitfields of Y1 Position Data Low Byte at microcontroller 103 address=0x3A. The bitfields of this register are decoded as follows. This register when read will return the low byte of the last known 16-bit position of the joystick #1 Y coordinate.

[0977] FIG. 37E is a diagram of the bitfields of Y1 Position Data High Byte at microcontroller 103 address=0x3B. The bitfields of this register are decoded as follows. This register when read will return the high byte of the last known 16-bit position of the joystick #1 Y coordinate.

[0978] FIG. 37F is a diagram of the bitfields of X2 Position Data Low Byte at microcontroller 103 address=0x3C. The bitfields of this register are decoded as follows. This register when read will return the low byte of the last known 16-bit position of the joystick #2 X coordinate.

[0979] FIG. 37G is a diagram of the bitfields of X2 Position Data High Byte at microcontroller 103 address=0x3D. The bitfields of this register are decoded as follows. This register when read will return the high byte of the last known 16-bit position of the joystick #2 X coordinate.

[0980] FIG. 37H is a diagram of the bitfields of Y2 Position Data Low Byte at microcontroller 103 address=0x3E. The bitfields of this register are decoded as follows. This register when read will return the low byte of the last known 16-bit position of the joystick #2 Y coordinate.

[0981] FIG. 37I is a diagram of the bitfields of Y2 Position Data High Byte at microcontroller 103 address=0x3F. The bitfields of this register are decoded as follows. This register when read will return the high byte of the last known 16-bit position of the joystick #2 Y coordinate. Also this register when read will re-enable updates to all X,Y Position Data registers.

[0982] FIG. 38 is an additional timing diagram illustrating the operation of joystick interface 105. IOW to Game Port port address 200-205 initiates trigger of COMPJ. From that time on, the circuit may be self (auto) triggering in that logical AND of each X,Y DIS2 signal will continuously trigger the COMPJ blocks 3602 of each joystick when the Auto Retrigger Enable bit is set. In this way the two COMPJ blocks are retriggered simultaneously by the last DIS2 rising edge. This insures that the two counters associated with each joystick always contain valid data that is the result of the previous trigger event. The Auto Retrigger Enable bit is controlled by microcontroller 103. Alternately, microcontroller 103 may initiate a trigger by performing a write to memory address 0x38. The counter is incremented by each XTAL2 rising edge when DIS1 is high. DIS2 also locks the counter value into latch which may be read by microcontroller 103 8-bits at a time. After the data has been clocked into the latch the counter must be reset. At any point in time microcontroller 103 is able to read the last value of each joystick coordinate. The joystick position data is then transferred to the host via an ISA bus read of Game Port address base +7 after the appropriate command has been written to Game Port address base +7.

[0983] The Codec 100 includes a 6-channel Input Mixer and 6-channel Output Mixer. Both the Input and the Output Mixers are fully independent. The Input Mixer provides volume control and mixing capability for combining up to six analog audio sources into the A/D converter for sampling. The Output mixer provides volume control and mixing capability for combining up to six analog audio sources into the line outputs. FIG. 39 is a diagram of one channel of the input mixer (the second channel is identical). FIG. 40 is a diagram of one channel of the output mixer (the second channel is also identical).

[0984] The available analog audio sources into the Input and Output Mixer are Line In, Aux1, Aux2, Digital (DAC) Audio, Microphone, and Line Out.

[0985] The Line In, Aux1, Aux2 inputs each have an adjustable input gain stage 3901/4001 that has a gain range of +12 dB to −34.5 dB. The outputs of these adjustable gain stages feed into the Input and Output Mixer Summers 114 and 115 respectively. The Input and Output Mixer Summers have four different gain settings to allow the user to adjust for optimum signal/noise and overload.

[0986] The Aux2 inputs have the ability to accept a differential input via a “Ground Differential” reference Pin (VCM-Pin 96) that can be used to eliminate ground loop noise from a CD-ROM input source.

[0987] The stereo Microphone input has an adjustable input gain stage 3902/4002 gain range of +22.5 dB to −22.5 dB. The Microphone path to the Output mixer has an additional +20 dB gain block that may be enabled in Mode 3. The +20 dB gain block is set by the LMBST-RMBST bits in Codec Extended registers X2 and X3. To emulate the 20 db Microphone gain boost in Mode 2 (LMGE and RMGE bits set to 1), the Mode 3 microphone volume control gain stage is forced to a fixed +I 9.5 dB (via LMCG4-LMCG0, RMCG4-RMCG0=00010). The Microphone inputs can be set into a Differential Mode for enhanced noise rejection and ground loop immunity. This function is available in Mode 3 only. The differential mode is set by the DIFMIC bit in extended register X5. The left channel is connected to the inverting pin of the op-amp, and the right channel to the noninverting pin of an op-amp, with the output sent to the left and right channel inputs of the Input and Output Mixers. The Microphone volume is controlled by the left channel only when in Differential Mode.

[0988] When Differential Microphone Mode is selected, the microphone gain level is automatically reduced 6 dB.

[0989] The analog input mixer functions can now be described in detail in conjunction with FIG. 39. Mode 1, 2 does not support a true mixer, but requires a mux function that allows only one input at a time to drive the corresponding A/D converter 111. In this mode, the pre-summer gain blocks 3901 are all bypassed (0 dB gain) except for the microphone input which may have its gain block set to either 0 dB (mic boost disabled) or +19.5 dB (mic boost enabled). The Input Mixer Summer gain block 3903 is also set fixed to 0 dB. The post-summer gain block is used to adjust the gain of the currently selected input source over a range of 0 to +22.5 dB. Switches 3904 are used to mute all unselected inputs. The DAC output path to the Input Mixer Summer is also forced muted in this mode. These functions are consistent with Mode 1, 2 operation.

[0990] The input source selection is via the LSS1:LSS0 and RSS1:RSS0 bits in registers I0 and I1 (codec registers, discussed above), respectively.

[0991] The input source gain (post-summer gain block) is selected by the LAG3:LAG0 and RAG3:RAG0 bits in registers I0 and I1 respectively.

[0992] The +19.5 dB mic gain boost (pre-summer mic gain block) is selected by the LMGE and RMCE bit in registers I0 and I1 respectively.

[0993] In MODE 1, 2 operation, only one input channel at a time is selected by the LSS1-0, RSS1-0 bits. In Mode 3, all of the channels may be selected as inputs simultaneously:

[0994] The Codec 100 Mixer prevents access (switches are forced open and cannot be closed) to the input mute switches shown in TABLE 59 to implement Mode 1 and Mode 2 mixer functionality.

[0995] Mode 3 operation supports an input mix function. As such individual gain/attenuation (+12 dB to −34.6 dB) blocks are provided for each analog input source into the mixer except for the LineOut and DAC inputs. The individual analog sources are then mixed in Input Summers 114.

[0996] Input Summers blocks 114 four attenuation settings: 0 dB, −6 dB, −12 dB, and −18 dB. Input Summer attenuation is required when mixing multiple analog sources that have near full scale levels. To prevent clipping of the post-summer gain block the resultant analog source mixed signal must be attenuated.

[0997] Post-summer gain (0 dB to +22.5 dB) block 303 is included to control the gain of the summed analog sources prior to being input to the A/D converter. The flexibility afforded by the various gain blocks results in an architecture that allows for maximum control of signal levels for obtaining the best S/N ratios.

[0998] All analog input sources are enabled into Input Summer 114. The pre-summer gain blocks 3901 of the input sources affect inputs to the Input Summer and Output Summer equally. In other words when a gain is changed for a particular input source, via the pre-summer gain blocks, the resultant output drives both the Input Summer and Output Summer. The mute function, however, For each analog audio source into the Input Summer and Output Summer is independent.

[0999] AUX2 pre-summer gain is set via the LX2G4:LX2G0 and RX2G4:RX2G0 bits in codec registers I4 and I5 respectively.

[1000] AUX1 pre-summer gain is set via the LX1G4:LX1G0 and RX1G4:RX1G0 bits in codec registers 12 and I3 respectively.

[1001] LINE-IN pre-summer gain is set via the LLG4:LLG0 and RRG4:RRG0 bits in codec registers I18 and I19 respectively.

[1002] MIC pre-summer gain is set via the LMCG4:LMCG0 and RMCG4:RMCG0 bits in codec registers X2 and X-3 respectively.

[1003] Overall Mix Gain/Attenuation is determined by the Input Summer Attenuation setting (LIS1:LIS0 and RIS1:RIS0 bits in codec extended registers X4 and X5 respectively) added to the post-summer gain (LAG3:LAG0 and RAG3:RAG0 bits in codec registers I0 and I1 respectively).

[1004] Thus, the gain/attenuation setting for each analog source into the A/D converter is determined by the following equation:

[1005] Gain (into A/D)=(pre-summer gain)+(input summer attenuation)+(post-summer gain)

[1006] The analog output mixer can now be discussed in detail in conjunction with FIG. 40. The available analog audio sources into the Output Mixer are Line In, Aux1, Aux2, Digital Audio (DAC), Microphone, and Mono In. AR audio sources are stereo except for the Mono In. The organization of the Output Mixer is as follows: Each analog audio input source has associated with it a +12 dB to −34.5 dB pre-summer gain/attenuator stage 4001. All the pre-summer gain/attenuation blocks 4001 then feed into a mixer stage 115 (Output Mixer Summer) that includes four selectable attenuation settings of 0 dB, −6 dB, −12 dB, and −18 dB. The Output Mixer Summer attenuation settings are controlled through Control Registers C27 and C29. These selectable attenuation settings are provided to allow for optimal adjustment for signal/noise and overload. The output of the Summer stage then feeds into a master volume control (C27, C29) with a gain/attenuation range of +12 db to −18 dB. The output from the master volume control then drives the line outputs.

[1007] In Modes 1 and 2, the Output Mixer configuration consists of the Output Mixer Summer attenuation being fixed at −12 dB. This results in an overall attenuation adjustment range of 0 dB to −34.5 dB for the master volume control.

[1008] The Microphone input to the Output Mixer is also disabled via switches, LMM and RMM in Mode 1, 2. Mode 1, 2 operation does not support mixing the Microphone input into the output mixer. In addition in Mode 1 operation, the Line-In input is disconnected (muted) into the Output Mixer Summer.

[1009] The Codec 100 further supports a mono input source and mono output, as illustrated in FIG. 41. The Mono Input is sent to an attenuator block 4101 with a range of 0 dB to −45 dB. The output from the attenuator is sent to the left and right Output Summer blocks 115a/115bof the Output Mixer. The Mono input also has a mixer bypass (attenuation 4103 of −9 dB) path into the Mono Out when the MBY bit is set in register codec 126 bit D5. On power-on reset the MBY is forced to a 1 to enable the Mono Input to the Mono Output.

[1010] Mono Out is a summed output from the Left Line out and Right Line Out. The Left and Right Line Outputs are each attenuated at 4104 by −6 dB prior to being summed at 4105 into the Mono Out:

[1011] FIG. 42 is a diagram of the digital audio processing subsystem of Codec 100. The digital audio functions will be discussed in the following portion.

[1012] The Codec 100 features a 5 channel (stereo) Digital Mixer that feeds into the DAC. Like the Analog Mixer, the Digital Mixer has Mode 1, Mode 2, Mode 3, and Internal/External FM specific modes of operation.

[1013] FIG. 43 is a diagram of the digital audio mixer. The inputs to the Digital Mixer are PCM (wave) digital audio, Internal FM, Serial Port, External Wavetable, and A/D Monitor Loopback. Each input except for the External Wavetable input has an adjustable attenuator 4301 with a range from 0 dB to −94.5 dB. The external wavetable attenuator and FM synthesis path attenuators 4302 and 4304 have a range of +12 db to 82.5 dB.

[1014] To maximize signal-to-noise performance, a DAC attenuator is provided that is part digital and part analog. The total attenuation range (0 dB to −94.5 dB) is split into a digital controlled part 4304 and an analog controlled part 4305. Digital controlled part 4304 operates with an attenuation step size of −6 dB over a range of from 0 dB to −60 dB (10 steps). Analog controlled part 4305 operates with an attenuation step size of −1.5 dB over a range of from +12 dB to −34.5 dB (23 steps). FIG. 44 illustrates the present attenuation scheme and TABLE 61 describes the attenuation stepping/register settings.

[1015] In Mode 1 or 2, the Digital Output Mixer supports control of only the PCM (codec registers I6, I7—wave) audio and the A/D Monitor Loopback (codec registers 113). Control of Serial Port or Bach volume is not available in this mode.

[1016] The PCM Audio (wave) volume is controlled by the LDA6-0, RDA6-0 bits in codec registers I6 and I7 respectively. Volume control range is +12 dB to −94.5 dB in 1.5 dB steps.

[1017] The A/D Monitor Loopback volume is controlled by the LBA5-0 bits in codec register 113. Volume control range is 0 dB to −94.5 dB in 1.5 dB steps.

[1018] In Mode 3, additional codec registers are available for controlling the volume of Serial Port 117 (X8X9)., external wavetable (XI6,XI7), and the right channel A/D Monitor Loopback (X10).

[1019] The Serial Port volume is controlled by the LSPA5-0, RSPA5-0 bits in codec extended registers X8 and X9 respectively. Volume control range is 0 dB-−94.5 dB in 1.5 dB steps.

[1020] The external wavetable volume is controlled by the LBA5-0, LBA5-0 bits in codec extended registers X16 and X17 respectively. Volume control range is +12 dB to −82.5 dB in 1.5 dB steps.

[1021] The A/D Monitor Loopback Left Channel volume is controlled by the LBA5-0 bits in codec extended register 113. Volume control range is 0 dB to −94.5 dB in 1.5 dB steps.

[1022] The A/D Monitor Loopback Right Channel volume is controlled by the RBA.5-0 bits in codec extended register X10. Volume control range is 0 dB to −94.5 dB in 1.5 dB steps.

[1023] When Internal FM is enabled some functional changes occur in regard to mixer operation. Normally when using external FM, the FM audio is mixed into the Output Analog Mixer via the LINE_IN input. When using internal FM the FM audio source is now digital which is mixed in via the Digital Mixer. Bits IS0 and IS1 in codec extended register X4 are used to control the redirecting of certain host register accesses into specific volume control registers. IS1 controls the redirecting of host accesses for Internal FM and IS0 controls the redirecting for the wavetable.

[1024] In the Codec 100, the external FM analog source is moved to an internal digital source, and the additional support for a digital external wavetable synthesizer. The Codec 100 transparently supports control of Internal FM and external wavetable volume via existing software and still maintain compatibility with traditional external analog sources being input via the LINE_IN input.

[1025] When the Internal FM block is disabled the Digital Mixer Operates in a standard Mode 2 configuration. In this mode the DAC attenuator (I6, I7) affects all the digital audio sources; A/D Monitor Loopback, Serial Port, wavetable, and PCM(wave). The External FM or Midi volume is controlled through the LINE_IN (I18, I19) register pair. In this mode independent volume control of the Serial Port and external wavetable is not possible.

[1026] When the Internal FM block is enabled, bits IS0 and IS1 in register X4 determine the mapping of registers into specific volume controls. In the default operating mode of IS0, IS1=01 host accesses to the LINE_IN registers (I18, I19) are redirected to the FM volume control registers X6 and X7 in the Digital Mixer. In this mode the DAC attenuator (X14, X15) affects all the digital audio sources; A/D Monitor Loopback, Serial Port, external wavetable, and PCM(wave). The External FM or Midi volume is controlled through the LINE_IN (II8, I19) register pair. In this mode independent volume control of the Serial Port and external wavetable is possible.

[1027] There are cases when switching between Mode 2 and Mode 3 that will cause volume level changes or various audio input sources to be enabled that should not be. Examples are described below:

[1028] a) When Internal FM is enabled the Digital Mixer is configured differently to allow individual control of the 4 digital input sources. In this instance the DAC volume control registers I6, I7 and the Digital Loopback Monitor volume registers X14, XI 5 swap. If the settings are different between the I6, I7 and X14, X15 registers when switching between Mode 2 and Mode 3 changes in volume level will occur;

[1029] b) In Mode 3 operation the AUX1, AUX2, and LINE_IN inputs into the Input Mixer Summer have switches (LX1IM, LX1MM, RX1IM, RX1MM, LLIM, LLMM, RLIM, RLMM) that are independently controllable. These switches are all disabled in Mode 2 and will result in the Mode 3 configuration being lost until Mode 3 is again enabled. When the switch to Mode 2 occurs the input mixer reverts to a mux with the selected input source defined by the current value held in registers I0 and I1;

[1030] Also Note: In Mode 3 the LX1IM-RX1IM and LX1MM-RX1MM bits (Aux1) or the LLIM-RLIM and LLMM-RLMM bits (Line) must not be on simultaneously. Having both these switches on simultaneously connects the input and output of the pre-summer gain stage into the input mixer and will cause the signal to cancel itself out due to the fact that the pre-summer gain stage output is inverted relative to the input.

[1031] c) The Input Mixer Summer attenuator is forced to 0 dB in Mode 1, 2. If the Input Mixer Summer attenuator is set to an attenuation setting other than 0 dB, via a Mode 3 change, then switching to Mode 1, 2 will cause the Input Mixer Summer attenuator to be forced back to 0 dB;

[1032] d) In Mode 3 operation the Mono Input Mute and Mono Output Mute have independent left/right mute controls. The right channel mute controls are located in Mode 3 accessible registers only. If a Mode 3 application unmutes the right channel Mono Input or Mono Output then a switch to Mode 2 operation will leave the right channel Mono Input or Mono Output unmuted regardless of the state of the Mode 2 MIM or MOM bits; and

[1033] e) In Mode 3 operation the Monitor Loopback path from A/D to D/A has the ability to have independent left/right attenuation controls. The Monitor Loopback attenuation control becomes left/right independent when the SLBE bit in register X10 is set to 1. If the SLBE is left set to a one when switching to Mode 2 operation, the right channel Monitor Loopback attenuation control will not be affected by the Mode 2 Monitor Loopback attenuation register I13.

[1034] In Mode 3, the LIS1-LIS0 (codec register X4), RIS1-RIS0 (codec register X5) bits and the LMS1-LMS0 (codec register C27), RMS1-RMS0 (codec register C29) bits set the amount of attenuation for the Left and Right Input Mixer Summer and Output Mixer Summer. When more than one analog input source has a large voltage swing, overload may occur at the Mixer Summers. To optimize signal-to-noise performance and prevent overload, the amount of attenuation set in the Mixer Summers should be increased. By controlling the various combinations of Summer and Gain settings, signal overload can be avoided while maximizing the signal-to-noise. The host controlling software can keep track of how many input sources are used, based on which inputs are unmuted, and automatically adjust the Input and Output Mixer Summers accordingly. The concept is that, for every input level control that is unmuted (set above “0”) the summer should be adjusted to increase attenuation by −6 dB and adjust the post summer Gain block to add +6 dB of gain. In this way the overall volume level stays the same, but the ability to prevent overload is increased. It should be noted that increasing mixer headroom, by increasing the Mixer Summer attenuation and increasing the Post Summer gain, will result in poorer signal-to-noise performance.

[1035] The highest signal-to noise-ratio for PCM capture (when one input is used), is when the Input Mixer Summer bits LIS1-LIS0, and RIS1-RIS0 are set to 00, which is 0 dB attenuation, and the post-summer gain LAG4-0, RAG4-0 is set to 0000 (0 dB) gain. If signal gain is required, the so-pre-summer input gain block should be used rather than the post-summer gain block. Increasing gain prior the summer, reduces the effect of noise generated by the Input Summer and keeps the signal to ratio the highest throughout the signal path. When more than one input channel is used the Input Mixer Summer should be set to attenuate −6 dB for each additional input used. This will prevent clipping at the Input Summer.

[1036] The highest signal-to-noise ratio through the Line Out is obtained when the Output Mixer Summer bits LMS1-LMS0 and RMS1-RMS0 are set to 01 (0 dB attenuation) and the Post Summer gain is set to 0 dB. Note: Mode 2 is defaulted with the Output Mixer Summer set to 12 dB attenuation and the Gain is set to +12 dB. This was designed so that the Summer would not overload under typical usage. To obtain the best signal-to-noise ratio performance use Mode 3 and set the Output Mixer Summer to 0 dB attenuation and set the Post Summer Gain to 0 dB. When making signal-to-noise and distortion measurements the mixer should be set this way to obtain the best performance possible.

[1037] The Codec 100 includes independent Sample Rate Converters (SRC) 112 and 113 on the capture (A/D) and playback (D/A) data paths. In the Codec 100 both A/D converters and D/A converters operate at a fixed sample rate of 44.1 kHz. The SRCs 112 and 113 are then used to convert from 44.1 kHz to the desired sample rate as specified in codec registers I8 (Mode 1), I22 (Mode 2), or X12 and X13 (Mode 3). The SRCs 112 and 113 are digital filters that either decimate(capture) or interpolate(playback) the converter fixed rate data to a user specified alternate rate. This method whereby the converters operate at a fixed sample rate and digital filters are used to sample rate convert the data has distinct advantages in the area of noise management.

[1038] In the Codec 100 playback and capture sample rates may be specified by a variety of methods. The SRCs provide a wide range of available sample rates. See TABLE 62 for available sample rates.

[1039] In Mode 1, Codec Register I8 bits CSF2-CSF0 and C2SL are used to set the capture and playback sample rates. TABLES 63A and 63B show the mapping for the SRC Divider values. In this mode the sample rate for both capture and playback are identical.

[1040] In Mode 2, Codec Register 122—When the SRE bit is set to 1, bits D3-D0 of codec register I8 are ignored, and the sample rate frequency is determined by CS2, DIV5-DIV0 and OSM1-OSM0 in codec register I10. In this mode a much larger range of samples rate are available. In this mode as in Mode 1 the playback and capture rates are identical.

[1041] In Mode 3, Codec Extended register X14—When the SRCE bit is set to 1 the codec extended registers X12 and X13 are used to set the sample rate, and codec registers I8 or I22 are ignored. Register X12 (SRAD7-0) is used to specify the sample rate for capture (A/D SRC 113), and register X13 (SRDA 7-0) is used to specify the sample rate for playback (D/A SRC. This Mode thus allows independent sample rates for capture and playback. TABLE 65 tabulates the available Mode 3 sample rates.

[1042] FIG. 45 is a more detailed diagram of FM synthesis block 124 and associated circuitry within codec 100. Internal FM block 124 provides full compatibility with market standard FM-based music synthesis as used in DOS games and educational software. The register interface emulates that of the Yamaha OPL2TM, and OPUTM devices, including the OPL3-L and OPL3-LS variations.

[1043] Provision has been made in the Codec 100 internal FM block 124 to support both two operator and four operator FM compatibility modes. Two-operator mode is the most popular in DOS games. In 2-operator mode, either 18 voices are supported, or 15 voices plus five additional rhythm sounds. In 4-operator mode, either six 4-operator FM voices plus six 2-operator FM voices simultaneously, or-six 4-operator FM voices, three 2-operator FM voices plus five rhythm sounds simultaneously.

[1044] FM synthesis engine 124 generally includes a multiplier 4501, shifter 4502, a pair of adders 4503aand 4503b,registers 4504a-4504b,multiplexers 4505a-4505b,parallel to serial converter 4506, and sample rate converter summer 4507. Also provided is an OPL3 RAM 4509 and associated state machine 4510.

[1045] Included in an internal PCM waveform ROM table 4508 are 8 FM source waveforms: sine wave; half sine wave; rectified sine wave; rectified quarter sine wave x 2; half-period sine wave; rectified half-period sine wave; square wave; and a decaying square wave. The amplitude of each sine wave over time is controlled using an envelope generator which requires. the following parameters to be specified: attack rate—the speed at which a sound rises to its initial volume; decay rate—the rate at which the amplitude drops off to a sustained level; sustain level—the “normal” intensity of the tone (absolute 0 to 15 volume scale); and release rate—the speed at which the sound level drops from the sustain level to maximum attenuation. Other factors that need be specified include: pitch; volume; depth; feedback; vibrato and the particular synthesis algorithm.

[1046] Internal FM block 124 has two 2-operator synthesis algorithms to choose from and four 4-operator algorithms. Each of the 4-operator algorithms provision for the output of one waveform generator to feedback into its input. The purpose of this feedback is to distort the base waveform oscillator output to produce a spectra rich in harmonics (used for FM based string sounds and for special effects in games).

[1047] The FM synthesis registers are discussed below in conjunction with TABLE 66 (direct registers) and TABLE 66 (indirect registers).

[1048] FIG. 46A is a diagram of the bitfields of Status Register at address base +0, (default=0x00000000). The bitfields of this register are decoded as follows:

[1049] The Index Registers are accessed by first writing the specific register index to either Base +0 or Base +1 depending on the register is located in Array 0 or Array 1. Data may then be read from the specified register by performing a read from base +2 or written to the register by performing a write to either base +2 or base +3. All registers are cleared when the RESDRV pin is high.

[1050] FIG. 46B is a diagram of the bitfields of Test at Index 0x0,0x1, (default=0x00000000). The bitfields of this register are decoded as follows. All bits should be left at “0”.

[1051] FIG. 46C is a diagram of the bitfields of Timer #1 at Index 0x2, (default=0x00000000). The bitfields of this register are decoded as follows. Timer #1 has a resolution of 80.8 usec. A count of 0-255 can be programmed. When ST1 is set to a one the contents of Timer #1 register is loaded into counter #1 and counter #1 begins to count down. When counter #1 underflows the IRQ bit is brought low and FT1 is set to one. The counter is reloaded and continues to count down where:

[1052] tl(ms)=Count value (0-255)* 80.8 usec

[1053] FIG. 46D is a diagram of the bitfields of Timer #2 at Index 0x3, (default=0x00000000). The bitfields of this register are decoded as follows. Timer #2 has a resolution of 323.1 usec. A count of 0-255 can be programmed. When ST2 is set to a one the contents of Timer #1 register is loaded into counter #1 and counter #1 begins to count down. When counter #1 underflows the IRQ bit is brought low and FT2 is set to one. The counter is reloaded and continues to count down where:

[1054] tl(ms)=Count value (0-255)* 323.1 usec

[1055] FIG. 46E is a diagram of the bitfields of Timer #1, #2 Control at Index 0x4, Register Array 0, (default=0x00000000). The bitfields of this register are decoded as follows:

[1056] FIG. 46F is a diagram of the bitfields of 4-Operator Mode at Index 0x4, Register Array 1, (default=0x00000000). The bitfields of this register are decoded as follows:

[1057] CSEL5-CSEL0 When a CSEL bit is set to a one the corresponding channel can be operated in 4-operator mode:

[1058] FIG. 46G is a diagram of the bitfields of Expansion Register at Index W, Register Array 1, (default=0x00000000). The bitfields of this register are decoded as follows:

[1059] PS(power save mode), PD(power-down mode), and the BUSY are enabled.

[1060] FIG. 46H is a diagram of the bitfields of Keyboard Split at Index 0x8, Register Array 0, (default=0x00000000). The bitfields of this register are decoded as follows:

[1061] NTS Determines keyboard split separation points. When NTS is set to a zero, the separation point is determined by the second bit of the F-number. When NTS is set to a one, the separation point is determined by the MSB bit of the F-number. Rate scaling is performed by splitting 8 octaves into 16 parts. Octave splitting is called “keyboard split”.

[1062] FIG. 46I is a diagram of the bitfields of Power Management at Index 0x8, Register Array 1, (default=0x00000000). The bitfields of this register are decoded as follows:

[1063] FIGS. 46J is a diagram of the bitfields of Tremolo Effect at Index 0x20-35, 0xBD, (default=0x00000000). The bitfields of this register are decoded as follows:

[1064] FIGS. 46K is a diagram of the bitfields of Vibrato Effect at Index 0x20-35, 0xBD, (default=0x00000000). The bitfields of this register are decoded as follows:

[1065] VIB When VIB is set to a one, a vibrato effect can be applied to the corresponding slot. The vibrato modulation frequency is 6.0 Hz;

[1066] FIG. 46L is a diagram of the bitfields of Non-percussive/Percussive Sound at Index 0x20-35, (default=0x00000000). The bitfields of this register are decoded as follows:

[1067] EGT=0 Percussive Sound; and

[1068] =1 Non-percussive Sound.

[1069] FIG. 46M is a diagram of the bitfields of Rate Key Scale at Index 0x20-35, (default=0x00000000). The bitfields of this register are decoded as follows:

[1070] KSR Rate key scaling is performed when KSR=1. “Rate Key Scaling” simulates the phenomena that rise time of a sound increases as the frequency of the note increases.

[1071] FIG. 46N is a diagram of the bitfields of Frequency Multiplier at Index 0x20-35, (default=0x00000000). The bitfields of this register are decoded as follows:

[1072] FIG. 46O is a diagram of the bitfields of Total Level at Index 0x40-55, (default=0x00000000). The bitfields of this register are decoded as follows:

[1073] L5-L0 Total Level sets the envelope damping. This can be used to control the modulation rate. The total level is given by the following equation:

[1074] TL(dB)=(−24×L5)+(−12×L4)+(−6×L3)+(−3×L2)+(−1.5×L1)+(−0.75×L0).

[1075] FIG. 46P is a diagram of the bitfields of Level Key Scale at Index 0x:40-55, (default=0x00000000). The bitfields of this register are decoded as follows:

[1076] FIG. 46Q is a diagram of the bitfields of Attack Rate at Index 0x60-75, (default=0x00000000). The bitfields of this register are decoded as follows:

[1077] AR3-AR0 This register determines the attack rate. AR3:AR0 allow fifteen rates with 0 giving the largest rise time and a value of 15 giving the shortest rise time.

[1078] FIG. 46R is a diagram of the bitfields of Decay Rate at Index 0x60-75, (default=0x00000000). The bitfields of this register are decoded as follows:

[1079] DR3-DR0 This register determines the decay rate. DR3:DR0 allow fifteen rates with 0 giving the longest decay time and a value of 15 giving the shortest decay time.

[1080] FIG. 46S is a diagram of the bitfields of Release Rate at Index 0x80-95, (default=0x00000000). The bitfields of this register are decoded as follows:

[1081] RR3-RR0 This register determines the release rate. RR3:RR0 allow fifteen rates with 0 giving the slowest release rate and a value of 15 giving the longest release rate.

[1082] FIG. 46T is a diagram of the bitfields of Sustain Level at Index 0x80-95, (default=0x00000000). The bitfields of this register are decoded as follows:

[1083] SLY-SL0 This register determines the sustain rate. When EGT is set to a one, the output level from a slot is held after the attenuation reaches the level set in SL3:SL0. When EGT is set to zero (percussive), the falling rate is switched to the Release Rate from the Decay rate after the attenuation reaches the level specified in SL3:SL0. The sustain level is specified by the following equation:

[1084] SL(dB)=(−24×SL3)+(−12×SL2)+(−6×SL1)+(−3×SL0)

[1085] (When SL3:SL0—15, the sustain level=−93 dB).

[1086] FIGS. 46U is a diagram of the bitfields of F-Number at Index 0xA0-A8, 0xB0-B8, (default=0x00000000). The bitfields of this register are decoded as follows:

[1087] F9-F0 Determines the frequency for one octave. Values from 0-1023.

[1088] FIG. 46V is a diagram of the bitfields of Block at Index 0xB0-B8, (default=0x00000000). The bitfields of this register are decoded as follows:

[1089] FIG. 46W is a diagram of the bitfields of Key On at Index 0xB0, (default=0x00000000). The bitfields of this register are decoded as follows:

[1090] FIG. 46X is a diagram of the bitfields of Rhythm at Index 0xBD) Default=0x00000000). The bitfields of this register are decoded as follows:

[1091] RHY When this bit is set to a one, the corresponding slots 13 to 18 are set to rhythm mode.

[1092] FIG. 46Y is a diagram of the bitfields of Rhythm Instrument Selection at Index 0xBD, (default=0x00000000). The bitfields of this register are decoded as follows.

[1093] This register controls the synthesizing of each rhythm. In rhythm mode, the sound of rhythm instrument is synthesized when the corresponding bit of the desired instrument is set to one.

[1094] The slot number used by each rhythm instrument is shown in TABLE 70. Set the rate, etc. to match the special features of each musical instrument. The available parameters are F-NUMBER, BLOCK, EGT, MULT, TL, AR, DR, SL, PR, and WS.

[1095] When a slot is set to the rhythm mode, set KEY ON of slots 13 to 18 to zero.

[1096] FIG. 46Z is a diagram of the bitfields of Algorithm Selection at Index 0xC0-C8, (default=0x00000000). The bitfields of this register are decoded as follows:

[1097] This registers selects the algorithm. An “algorithm” is a connection scheme defining how a group of operators are combined. A different algorithm can be selected for each channel (register C0-C8H):

[1098] FIG. 47 is a diagram representing these two algorithms.

[1099] In 4-operator mode, four algorithms type are selectable by setting two CNT bits. FIG. 48 is a diagram illustrating the algorithms in the 4 operator mode.

[1100] FIGS. 46AA are diagrams of the bitfields of Feedback Modulation at Index 0xC0-C8, (default=0x00000000). The bitfields of this register are decoded as follows.

[1101] FIG. 46AB is a diagram of the bitfields of Output Channel Selection at Index 0xC0-C8, (default=0x00000000). The bitfields of this register are decoded as follows:

[1102] FIG. 46AC is a diagram of the bitfields of Register Settings at Index 0xE0-F5 (default=0x0000000). Codec 100 internal FM block 124 has 36 virtual waveform generators used for frequency modulation, created by time division multiplexing a single high-performance DSP core. Each waveform generator is called an “operator” or “slot”. One sound generated by combining two or four operators is called a “channel”. There are two kinds of registers: one is controlled by every slot unit, another is controlled by every channel unit.

[1103] The Register settings in slot units is generally as follows: Registers 20H-35H, 40H-55H, 60H-75H, 80H-95H, and E0H-F5H are controlled by every slot unit. Register addresses x6H, x7H, xEH, and xFH do not exist.

[1104] The 36 slots are numbered 1 to 36, which are called “Slot Number”. The correspondence between Slot Number and register address is determined as shown in TABLE 72.

[1105] In the two-operator mode one FM sound (one channel) is generated using 2 slots. Therefore, 18 channels are generated in two-operator mode. Channels are numbered the same as Slot Number, and are called Channel Numbers.

[1106] In case of algorithm 2, any slot of 2 slots can correspond to operator-1 (operator-2). However, in case of algorithm 1 the timbre depend on which slot is the modulator (which slot is carrier). Therefore, be careful about Slot Number.

[1107] Registers A0H-A8H, B0H-B8H, and C0H-C8H are controlled by every channel unit. The correspondence between Channel Number and register address is determined as follows. Slot Number and Channel in Four-operator Mode

[1108] In four-operator mode one FM-type sound (one channel) is generated using 4 slots. 6 channels are generated using 24 slots in four-operator mode. In four operator mode, four algorithms are available as in four-operator mode, the correspondence between slot number and each operator (operator 1, 2,3, or 4) is determined from TABLE 73:

[1109] The Register settings in channel units (Four-operator mode) are as shown in TABLE 74. Registers A0H—A2H, B0H-B2H, and C0H-C2H are controlled by every channel unit. However, the CNT bit of registers C3H-C5H is used as an algorithm parameter (refer to description of CNT bit).

[1110] Codec 100 internal FM block can generate 5 rhythm instruments (bass drum, snare drum, tomtom, top cymbal, and hi-hat cymbal) using 6 slots. Rhythm slot number are determined to 13-18.

[1111] 3D Spatial Enhancement is provided by a DSP block 118 that is located between the output of the Digital Mixer and the DAC for each channel.

[1112] FIG. 49 is a functional block diagram of stereo processor a selected DSP 118.

[1113] Because of the DSP block placement providing 3D Spatial Enhancement to analog input sources requires that the A/D Monitor Loopback path be used. Analog audio sources mixed via the output mixer will not be spatial enhanced.

[1114] SRS creates a fully immersive three dimensional soundfield through the use of a standard two speaker stereo configuration. To enable the SRS stereo process, the SRS bit in control register C3 is set. Use the “SPACE” and “CENTER” features to adjust the level of SRS signal processing. The SPACE 3—SPACE 0 bits control the amount of perceived width of the SRS three dimensional soundfield. The CENTER 3—CENTER 0 bits control the amount of mono sound (common to both left and right) such as a vocalist in music or mono game sound effects.

[1115] Sound sources that originate in digital format such as ISA Bus, internal FM Synthesis, and Serial Port data are adjusted and mixed through the Digital Mixer. Sound sources that are analog must be adjusted and mixed through the Analog Mixer and digitized by the A/D converter. This digitized data can then be sent to the Digital Mixer through the Monitor FeedBack path for SRS processing.

[1116] SRS processed digital data can be simultaneously output to the DAC, and to the Serial Port by selecting the SP3D bit in register C3.

[1117] The SRS 3D Mono to Stereo processing synthesizes a stereo signal from a mono input source. This processing creates a pleasing three dimensional sound field and eliminates many of the side effects of other stereo synthesis techniques.

[1118] Each DSP 118 further supports QSound processing. QSound creates a three dimensional soundfield through the use of a standard two speaker stereo configuration. To enable the QSound stereo process, the 3D Proc on bit in register control C3 is set. The “SPACE” and “CENTER” features discussed above to adjust the level of QSound signal processing. Using the SPACE 3—SPACE 0 bits will control the amount of perceived width of the QSound three dimensional soundfield. Using the CENTER 3—CENTER 0 bits will control the Digital Audio volume level.

[1119] Sound sources that originate in digital format such as ISA Bus, internal FM Synthesis, and Serial Port data are adjusted and mixed through the Digital Mixer. Sound sources that are analog must be adjusted and mixed through the Analog Mixer and digitized by the A/D converter. This digitized data can then be sent to the Digital Mixer through the Monitor FeedBack path for QSound processing.

[1120] QSound processed digital data can be simultaneously output to the DAC, and to the Serial Port by selecting the SP3D bit in register C3.

[1121] 3D Spacial Enhancement registers are located in the Control logical device index space accessed by Controlbase +3 and Controlbase +4, discussed above with regards to the Control Registers. As indicated, each of the control registers indexes a set of extended control registers, two of which are as follows:

[1122] FIG. 52A is a diagram of the bitfields of SRS Control Register at Control Index (C2, (default=00000010). The bitfields of this register are decoded as follows:

[1123] When the SRS/MONO bit is set to a one this register is reset to 00100000.

[1124] FIG. 52B is a diagram of the bitfields of 3D Sound Control at Control Index C3, (default 00000000). The bitfields of this register are decoded as follows:

[1125] These principles can generally be described as follows, with a detailed discussion provided below. A master/slave volume control register pair are monitored to detect a volume control change. A change is detected when the contents of the master is different from the contents of the slave. The change detect activates an analog comparitor and a timeout counter. The analog comparitor senses the level of the volume controlled output relative to analog zero. When the analog output swings within the comparitor's zero window, the comparitor outputs a digital signal that is used to update the slave register contents to match the master register. If there the analog signal does not activate the comparitor in a reasonable time, the timer will generate the update signal. Thus, a closed loop system is provided that continuously monitors it's input for a change, waits for an analog zero-cross (or near zero) or timeout, and then updates the volume control.

[1126] In the following discussion the volume control will be described as an attenuator. In practice these volume controls can have gain or attenuation, or both gain and attenuation in the same volume control.

[1127] The master and slave registers are elements 5001 and 5002. The change sensor is element 5003. The analog comparitor is element 5004. Elements 5005, 5006 and 5007 are the digitally controlled amplifier pieces. Element 5006 is a pulse stretcher. Element 5007 is the timeout counter. Element 5008 is a logical OR function. The control signal RESET initializes the volume control registers. The SLOW_CLK is a 10 ms clock used for the timeout timer. The DISABLE_ZC input forces the slave register 5002 to be transparent, so that volume control updates occur when the master register changes. The signal WR is the write enable for the master register 5001. DATA carries the digital word that will be stored in the master register. VCOM is the analog ground reference. And AIN is the analog input, AOUT the analog output.

[1128] The functional analysis begins with the RESET signal. When RESET is asserted high, during chip initialization for example, the master and slave registers are forced to the default volume control setting. In the following description it will become evident that it is not necessary to initialize the slave. During RESET active and after RESET deassertion, the Master and SLAVE registers 5001 and 5002 will have identical contents, and the change sensor, 5003, will recognize that condition and output a low level on ZC_ON. The Slave register data will be decoded by 5005, which will activate one of its 32 output signals. The decoder output is used by Attenuator block, 5006, to select one resistor tap. All this results in Opamp, 5007 operating at the default attenuation setting. This is a stable configuration where the ZC_ON signal is inactive, the comparitor is powered off, the ZEROC signal is off, Timer 5010 is disabled, the TIMEOUT signal is off, the DISABLE_ZC input is off, and the UPDATE signal is off. During normal operation the DISABLE_ZC signal will remain off, the WR signal will be used to load a digital volume control word from the DATA bus, and the SLOW_CLK signal will be running with a 10 ms period.

[1129] When a volume control change is desired, the new digital volume control value is placed on the DATA bus (not shown here) and Master latch 5001 is loaded by asserting the WR signal with a short pulse. The output of Master 5001 MASTER now holds the new volume control setting. The MASTER and SLAVE words are no longer identical, and change sensor 5003 recognizes this condition and asserts ZC_ON. Comparitor 5004, is powered up, Timer 5010, is activated. The comparitor senses the relative levels to AOUT and VCOM. If AOUT swings within the detection threshold of VCOM the ZEROC signal is asserted. ZEROC may be a very narrow pulse if AOUT is changing rapidly, and so Pulse Stretcher 5009 stretches ZEROC, and via OR gate 5008 asserts UPDATE. The UPDATE signal is the enable input of Slave Register 5002, which in this instance is implemented as a transparent latch. With the assertion of UPDATE, the SLAVE value will take the value of MASTER. The Change Sensor no longer sees a difference, and deasserts ZC_ON. Then everything returns to the stable state, the Comparitor powers off, ZEROC deasserts, the Pulse Stretcher deasserts UPDATE.

[1130] If the AOUT signal did not activate Comparitor 5008, due to a DC offset or a very low frequency signal, Timer 5010 would count several ticks of the SLOW_CLK, and then active TIMEOUT, which would force UPDATE asserted. When UPDATE asserts, the SLAVE value changes, and the system returns to its stable state. In the present implementation, Timer 5010 counts two SLOW_CLK pulses to assert TIMEOUT.

[1131] FIG. 50B depicts an exemplary embodiment of a window comparator, such as comparator 5004 of the present circuitry.

[1132] Different implementations will change many of the design features presented in this example. Some desirable tradeoffs are to use edge triggered flops for the Master and Slave registers, use longer timeout delay, use a timeout SLOW_CLK that was activated by the volume control change, or synchronize the UPDATE signal to a system clock or analog sampling clock.

[1133] A classical problem with using crystal oscillator based clocking circuits is determining when the clock in stable in frequency and duty cycle. Many digital state machines and controller logic can produce undesirable behavior, if operated at the wrong frequency or duty cycle. The common problem is at startup. The oscillator circuit will be slow in starting after power is applied. The crystal will be slow in gaining amplitude. So for some time after power is applied, the oscillator output may be unstable in both frequency and amplitude.

[1134] The crystal oscillator clock generator 5100 (FIG. 51) of the present invention has several parts. The oscillator block 5101 contains the crystal oscillator circuit. A super-hystersis buffer monitors the unbuffered oscillator output. A clock detector senses clock inactivity. And there are some other logic gates that synchronize the clock with reset and control the clock output.

[1135] The oscillator circuit, 5101, has an enable input and a buffered and non-buffered outputs. The enable input is the on-off control, with enable active, the oscillator circuit is powered up and the circuit will try to oscillate. The unbuffered oscillator output drives the super-hystersis buffer input. The super-hystersis buffer is a carefully designed buffer with about two volts of hysteris. This means that the buffer will not detect a low level until the input in one volt below the center level, and will not detect a high level until the input is one volt above the center level. The center level is designed to match the DC bias point of the crystal oscillator circuit, which is roughly one half the supply voltage. Thus, when enable is activated, the super-hysteria buffer output will be steady state until the magnitude of the crystal oscillator exceeds one volt above and below the bias level, then the super-hystersis output will be a square wave version of the unbuffered oscillator signal.

[1136] The second part is to sense the super-hystersis output for inactivity and synchronously control the buffered oscillator output so that signal presented at the clock generator output is only active when the oscillator is running with a large magnitude.

[1137] The clock-off-detect sense inactivity on its input, which is the output of the super-hystersis buffer. If the super-hystersis buffer output does not change logical states within the timeout period of the clock-off-detect block, the olk_is_on signal will go low indicating a dead oscillator. In a powerup sequence the clock-off-detect will initially detect that the oscillator is dead, the flip-flop is initialized by a power-on reset function. The initial condition disables the buffered oscillator signal from reaching the xtal_16 output pin. Once the oscillator wakes up and the clock_off_detect asserts Clk_-is_on, the next clock rising edge from the buffered oscillator output will set the lclkon signal, which enable the xtal_16 output, and the rest of the system now has a good clock,

[1138] There is other logic outside the clock generator that deals with the situation when the oscillator dies. In general if the oscillator dies, the clk_is_on signal is used to shut down normal operation, and return the system to a state where it is awaiting the clock startup.

[1139] The DISABLE-ZC input is usefully for testability, and for turning off the zero cross volume control for applications where instantaneous volume control updates are desired. Father testability improvement can be made by making the Master and Slave independently readable.

[1140] DSP serial port interface 117 is enabled by setting the SPE bit in codec register 116. Once this bit is set the DSP Serial Port pins function as specified by the SF1:SF0 bits in codec register 116 as long as the S/PDIF bit (discussed below) is set to zero. If the S/PDEF bit is set to a one then the DSP serial interface is disabled and S/PDIF data is sent out the SDOUT pin instead.

[1141] The DSP Serial Interface on codec 100 is available on two different sets of pins. By default codec 100 locates the DSP Serial Interface on the second joystick pins. The switching of the second joystick pins to the DSP Serial Interface is defined by the Serial Port Enable (SPE) bit in register I16 bit D1. The mapping is:

[1142] JBBI -- FSYNC;

[1143] JBCX -- SDOUT;

[1144] JBCY -- SDIN; and

[1145] JBB2 -- SCLK.

[1146] The DSP Serial Interface may also be located on the XDBUS. The XD4:XD1 pins are switched to this function by the SPS bit in control register C8. The mapping is:

[1147] XD4 -- FSYNC (LRCLK);

[1148] XD3 -- SDOUT;

[1149] XD2 -- SDIN; and

[1150] XD1 -- SCLK.

[1151] The DSP Serial Interface on codec 100 supports four modes of operation. Serial Port 1 is illustrated in FIG. 53, Serial Port Mode 2 is illustrated in FIG. 54, Serial Port Mode 3 is shown in FIG. 55, and Serial Port Mode 4 is illustrated in FIG. 56.

[1152] Serial Port Mode 3 is selected by setting the SF1,0 bits in register codec registers I16 to 11. This format is a 64 bit per frame format that includes ADC as well as DAC 16-bit data. This mode is intended for use by an external modem DSP so that the local audio sourced to the DAC may be cancelled from the local microphone signal (ADC). This feature is to allow only non-DAC source audio (voice) to be sent down the phone line.

[1153] S/PDIF interface 119 is a means for serially transmitting digital audio data through a single connection. It provides two channels for audio data, a control channel, and error detection capabilities. The control information is transmitted one bit per sample and is accumulated into a block structure. The data is biphase encoded, which enables the receiver to extract the clock from the data. Coding violations, defined as preambles, are used to identify sample and clock boundaries. The frame/block is shown in FIG. 57.

[1154] Digital data output from the Serial Port (sourced by the ADC or by the Playback Digital Mixer) can be formatted to the Sony Phillips Digital Interface Format (S/PDIF) by setting the S/PDIF bit in register control C4. In addition the SPE bit in codec register I16 must also be set to a one to enable the serial port interface. When the S/PDIF format is enabled, the S/PDIF formatting is for only digital output data from the Serial Data Out (SDOUT pin) only and does not support digital S/PDIF format data input (SDIN) into the Serial Port. The encoded data is output on the SDOUT pin. External circuitry is used to interface to either an optical output or to a 75 ohm coax cable interface.

[1155] The S/PDIF output conforms to the SCMS Serial Copy Management System for Digital Audio Transmission for providing protection of unauthorized digital duplication of copyrighted material.

[1156] An S/PDIF block is 192 frames long. Each frame consists of a channel A and channel B sub-frame. FIG. 58 is a diagram of the typical subframe. Each sub-frame consists of a Preamble (4-bits), auxiliary data (4-bits), audio data (20 bits), validity flag (1-bit), user data (1-bit), channel status data (1-bit), and Parity (1-bit). Codec 100 supports 16-bits of audio data. Codec 100 generates zero's for the auxiliary data and for audio data bits 17 through 20.

[1157] The Channel Status Data is 192 bits in length and is transmitted one bit at a time per Frame. A number of user programmable bits are available in the Channel Status Data and are located in the registers described below. Consumer channel status data is summarized in TABLE 75C.

[1158] The S/PDIF registers are located in the Control Logical Device Indexed Register space. Access to these registers is through the Control Registers C3 (Index) and C4 (Data), discussed above.

[1159] Codec 100 interfaces to a wavetable synthesizer, such as a Crystal Semiconductor CS0236, with zero glue logic through a block 123. FIG. 59 is a diagram of the coupling between Codec 100 and a wavetable synthesizer 5901.

[1160] The combination operates from one 16.9344 MHz crystal or clock source, Codec 100 being the master clock generator for synthesizer 5901.

[1161] The serial interface for the wavetable synthesizer requires three pins: MCLK, LRCLK, and DATA. Codec 100 generates the master clock via the MCLK pin for synthesizer 5901. Codec 100 is able to accept 3v logic levels from external wavetable and external wavetable is able to accept 5v logic levels from Codec 100. This insures that both devices operate synchronously. Because of timing skews between Codec 100 and external wavetable, Codec 100 must synchronize the data sourced from external wavetable to its internal clock. Codec 100 detects the edge of LRCLK and performs synchronization so that the digital audio from external wavetable is mixed properly with Codec 100 internal audio data before being sent to the DAC.

[1162] Four pins define pins define the Codec—wavetable synthesizer serial interface. These pins are muxed onto the XDBus by bit WTEN in Control Register C8:

[1163] DATA as XD7—input;

[1164] LRCLK as XD6—input;

[1165] MCLK as XD5—output; and

[1166] BRESET.

[1167] BRESET The BRESET pin is forced low when RESDRV high, when PM1, PM0 are set to 10 in CTRLbase +0, or when the BRESET is set to \one in control register C8.

[1168] To minimize the number of serial port timing modes required for the wavetable synthesizer, the serial port timing is defined to match the default internal SCLK mode for a 384 fs master clock. The SCLK frequency is 48×44.1 kHz. Thus, the least significant 16-bits should be accepted and the rest ignored.

[1169] FIG. 60 is a diagram illustrating this timing scheme, where:

[1170] Internal SCLK Mode;

[1171] 16-Bit Data;

[1172] Data Valid on Rising Edge of SCLK; and

[1173] INT SCLK=48 Fs if MCLK/LRCK=384.

[1174] Codec 100 supports a variety of test functions to aid in chip debug and production test. The Primary Test Modes are numbered 0 through 10. Within a number of these Test Modes, namely Test Modes 0, 1, 3, 4 and 6, are a number of secondary test functions that may operate simultaneously with the Primary Test Mode. The available Primary Test Modes are summarized in TABLE 76 and the secondary test modes in TABLE 77.

[1175] Codec 100 Primary Test Modes are enabled by forcing the TEST pin high. The rising edge of TEST will strobe the data present on the [TD3 . . . TD0] pins. The data latched from these pins determines the Test Mode. If TEST is low then codec 100 operates normally. The Secondary Test Modes available in Test Modes 0, 1, 3, 4 and 6, are selected by writing the secondary test function into register I17. The JAB2 pin is the enable pin for the Secondary Test Modes. It should be noted that even though the Secondary Test functions are available in Primary Test Modes other than 3, the fact that the JAB2 pin is remapped in these other modes means that indeterminate results could occur.

[1176] Primary Test Mode 3 has special pin mapping that is dependent on which secondary I17 mode is active. These pin mappings are:

[1177] To facilitate testing Test Modes 3, 5, 6, 9, and 10 all have the Plug-n-Play registers set to a default value. These default values define a set of I/O addresses, Interrupts, and DMA channel mapping per logic device, as shown in TABLE 78:

[1178] In this mode all RAM/ROM addresses, data lines, and control lines are brought out to codec 100 pins. This enables access to codec 100 internal ROM and read/write access to internal program RAM via an external device. This Test Mode allows testing of RAM via test pattern sequences as well as loading of the Program RAM with instructions that may be executed by microcontroller 103 during Test Mode 1. The pin remapping is shown in TABLE 79.

[1179] In Test Mode 1, microcontroller 103 ROM addresses are swapped such that location 0000 (boot location) is moved from ROM to RAM. Microcontroller 103 is not held reset in this mode. A port 1 test register is also used. The register may be read or written by microcontroller 103. The output of the register is also connected to the interrupt input lines of microcontroller 103. In this way microcontroller 103 functions may be tested via downloaded code. External pins of codec 100 allow the address, data, and control signals of microcontroller 103 to be monitored externally. The pin remapping is summarized in TABLE 80. A typical Test Mode sequence is:

[1180] 1) RESDRV=1 or RESDRV=0;

[1181] 2) TEST=1, set XD3-XD0 to 0000 to select Test Mode 0. TEST=0;

[1182] 3) Using Test Mode 0 load internal Program RAM with diagnostic code;

[1183] 4. TEST=1, set XD3-XD0 to 0001 to select Test Mode 1. microcontroller 103 is reset;

[1184] 5. TEST=0, microcontroller 103 now boots from RAM; and

[1185] 6. Monitor external pins.

[1186] In Test Mode 2 all microcontroller 103 address, data, and control signals are monitored externally via codec 100 pins. The chip operation proceeds normally, with microcontroller 103 executing from its program ROM/RAM and the codec operating normally. The purpose of this Test Mode is to allow the operation of the internal microcontroller 103 to be monitored externally as it is operating in a system environment.

[1187] In odder to monitor the codec registers, a means to identify SFR accesses to the codec registers is required. Thus the XD[7:0] bus definition is changed when codec 100 is operating in this Test Mode. The [7:0] bus is defined to normally follow the state of microcontroller 103 XDB[7:0] bus, but when a SFR access occurs, (indicated by SFRADL) the state of the SFRDB[7:0] and SFRAB[7:0] buses are output onto the XD[7:0] pins in a multiplexed manner. To indicate when the XD[7:0] bus is outputting SFR address/data the XA1:XA0 pins are both driven low simultaneously. The XA1:XA0 pins should remain low during the SFR cycle. This Test Mode 3 pin remapping is summarized in TABLE 81.

[1188] In the Codec (Sound System) codec register 117, Test Mode codec is isolated from the rest of codec 100 chip. This Test Mode will force the ISA interface logic to be enabled in a default Sound System mode. The base address, DMA and interrupt mapping is determined by power on default values. The Plug & Play interface logic is disabled in this mode. In this mode codec 100 operates as a WSS codec. All existing WSS based diagnostics and test vectors should operate normally. This mode is controlled by codec register I17, as summarized in TABLE 82.

[1189] Each of Register 117 Secondary Test Modes can be described as follows:

[1190] FIG. 61 is a test bit chart describing this mode.

[1191] In Test Mode 4 (replace internal microcontroller Test Mode) all signals from the “FPGA” logic and codec, which were connected to the internal microcontroller 103, are routed to codec 100 pins. FIG. 62 describes the microcontroller memory map in Test Mode.

[1192] Since SFR accesses are not visible outside of a standard microcontroller 103 microcontroller, some method of translating internal SFR accesses to accesses that are visible external to microcontroller 103 must be found. To accomplish this it is assumed that a special version of microcontroller 103 ROM code will be developed that will replace all codec internal SFR accesses with externally visible MOVX instructions. Also there is a one-to-one correspondence between SFR addresses and the address that is generated during the corresponding MOVX cycle. The end result of this code change is that codec accesses into the SFR address space are translated into accesses into the external RAM space. Once this has been accomplished the external microcontroller 103 read, write, address, and data signals are provided as inputs to codec 100 and are decoded to generate accesses to codec 100 codec registers.

[1193] In codec 100 the external microcontroller 103 multiplexed data/address bus XD[7:0] and a latched version of the address (XDBAL[5:0]) are input to codec 100 via external pins. Because the decoding of translated SFR addresses requires decoding 8-bits and the fact that not all address signals are input to codec 100, an internal 8-bit latch must be added to latch the address off of microcontroller 103 multiplexed address/data bus. This latch uses the ALE signal from the external microcontroller 103 to latch the data during the address phase of the multiplexed XD[7:0] bus. The XDBAL[5:0] pins are now free for other uses. The ALE signal is input via the JBB2 pin.

[1194] The Test Mode 4 Pin Remapping is summarized in TABLE 83.

[1195] Test Mode 5 allows test of the “FPGA” logic and interfaces. The ISA interface is forced to Sound System mode with the base address and DMA/Interrupt mappings at power on default settings. The codec operates in this mode, but microcontroller 103 is held reset. No remapping of pins is required in this mode.

[1196] Test Mode 6 (replace microcontroller Test Mode) tests the ISA Bus to microcontroller 103 interface logic. This mode is identical to Test Mode 4 except that the interface is forced to Sound System default settings. The codec operates normally in this mode and the internal microcontroller 103 is held reset. TABLE 84 summarized the pin remapping in this mode.

[1197] Test Mode 7 is the Outputs High Test Mode. When this Test Mode is selected all digital outputs will be forced high.

[1198] Test Mode 8 is the Outputs Low Test Mode. When this Test Mode is selected all digital outputs will be forced low.

[1199] Test Mode 9 is the Digital Joystick Test Mode A. This is the same as Test Mode 5 except forces digital joystick 16-bit counters to operate as two 8-bit counters in parallel. In this way test time can be minimized by having the upper and lower halves of the 16-bit counter increment at the same time. Thus testing the counter requires 255 clocks instead of 65536. Also joystick microcontroller 103 registers at addresses 0x38 to 0x3F are mapped into Control Register space at addresses C38 to C3F.

[1200] Test Mode 10 is the Digital Joystick Test Mode B, which is the same as Test Mode 9 except digital joystick 16-bit counters operate as one 16-bit counter. FIG. 63 is a diagram of the pinout of Codec 100. The pins can be described generally as follows. ISA Bus Interface Pins:

[1201] SA<11:0> Address, Input

[1202] These signals are decoded during I/O cycles to determine access to the various functional blocks within codec 100 as defined by the configuration data written during a Plug And Play configuration sequence.

[1203] SA<15:12>—Address, Input

[1204] These additional address lines are decoded along with SA<11:0> when the 16-bit decoding mode of codec 100 is selected.

[1205] SD<7:0>—Data Bus, Bi-directional, 24 ma drive These signals are used to transfer data to and from codec 100 and associated peripheral devices.

[1206] AEN—Address Enable, Input

[1207] This signal indicates whether the current bus cycle is an I/O cycle or a DMA cycle. This signal is low during an I/O cycle and high during a DMA cycle

[1208] .IOR/—Read Command Strobe, Input

[1209] This signal defines a read cycle to codec 100. The cycle may be a register read or a read from codec 100 DMA registers. This signal is active low.

[1210] IOW/—Write Command Strobe, Input

[1211] This signal indicates a write cycle to codec 100. The cycle may be a write to a control register or codec 100 DMA register. This signal is active low.

[1212] IOCHRDY—I/O Channel Ready, Open Collector Output, 8 ma drive

[1213] This signal is driven low by codec 100 during ISA bus cycles in which codec 100 is not able to respond within a minimum cycle time. IOCHRDY is forced low to extend the current bus cycle. The bus cycle is extended until IOCHRDY is brought high.

[1214] DRQ<A:C>—DMA Requests, Output, 24 ma drive

[1215] These active high outputs are generated when codec 100 is requesting a DMA transfer. This signal remains high until all the bytes have been transferred as defined by the current transfer data type. The DRQ<A:C> outputs must be connected to 8-bit DMA channel request signals only. These are DRQ0, DRQ1, and DRQ3 on the ISA bus.

[1216] DACK/<A:C>—DMA Acknowledge, Input

[1217] The assertion of these active low signals indicate that the current DMA request is being acknowledged and codec 100 will respond by either latching the data present on the data bus (write) or putting data on the bus(read).

[1218] The DAK<2:0> inputs must be connected to 8-bit DMA channel acknowledge lines only. These are DACK0, DACK1, and DACK3 on the ISA bus.IRQ <A:F>—Host Interrupt Pins, Output, 24 ma drive These signals are used to notify the host of events which need servicing. They are connected to specific interrupt lines on the ISA bus. The IRQ<A:F> are individually enabled as per configuration data that is generated during a Plug and Play configuration sequence.

[1219] Analog Inputs:

[1220] LLINE—Left Line Input

[1221] Nominally 1 VRMS max analog input for the Left LINE channel, centered around VREF. The LINE inputs may be selected for A/D conversion via the input multiplexer (I0). A programmable gain block (I18) also allows routing to the mixer.

[1222] RLINE—Right Line Input

[1223] Nominally 1 VRMS max analog input for the Right LINE channel, centered around VREF. The LINE inputs may be selected for A/D conversion via the input multiplexer (I1). A programmable gain block (I19) also allows routing to the. mixer.

[1224] LMIC—Left Mic Input

[1225] Microphone input for the Left MIC channel, centered around VREF. This signal can be either 1 VRMS (LMGE=0) or 0.1 VRMS (LMGE=1).The MIC inputs may be selected for A/D conversion via the input multiplexer (I0)

[1226] RMIC—Right Mic Input

[1227] Microphone input for the Right MIC channel, centered around VREF. This signal can be either 1 VRMS (RMGE=0) or 0. 1 VRMS (RMGE=1). The MIC inputs may be selected for A/D conversion via the input multiplexer (I1).

[1228] LAUX1—Left Auxiliary #1 Input

[1229] Nominally 1 VRMS max analog input for the Left AUX1 channel, centered around VREF. The AUX1 input may be selected for A/D conversion via the input multiplexer (I0). A programmable gain block (I2) also allows routing to the output mixer.

[1230] RAUX1—Right Auxiliary #1 Input

[1231] Nominally 1 VRMS max analog input for the Right AUX1 channel, centered around VREF. The ALJX1 input may be selected for A/D conversion via the input multiplexer (I1). A programmable gain block (I3) also allows routing to the output mixer.

[1232] LAUX2—Left Auxiliary #2 Input

[1233] Nominally 1 VRMS max analog input for the Left AUX2 channel, centered around VREF. A programmable gain block (I4) also allows routing of the AUX2 channels into the output mixer.

[1234] RAUX1—Right Auxiliary #1 Input

[1235] Nominally 1 VRMS max analog input for the Right AUX2 channel, centered around VREF. A programmable gain block (I5) also allows routing of the AUX2 channels into the output mixer.

[1236] MIN—Mono Input

[1237] Nominally 1 VRMS max analog input, centered around VREF, that goes through a programmable gain stage (I26) into both channels of the mixer. This is a general purpose mono analog input that is normally used to mix the typical “beeper” signal on most computers into the audio system.

[1238] Analog Outputs:

[1239] LOUT—Left Line Level Output

[1240] Analog output from the mixer for the left channel. Nominally 1 VRMS max centered around VREF when OLB=1 (I16). When OLB=0, the output is attenuated 3 dB and is a maximum of 0.707 VRMS.

[1241] ROUT—Right Line Level Output

[1242] Analog output from the mixer for the Right channel. Nominally 1 VRMS max centered around VREF when OLB=1 (I16). When OLB=0, the output is attenuated 3 dB and is a maximum of 0.707 VRMS.

[1243] MOUT—Mono Output When OL13=1 (I16),

[1244] MOUT is nominally 1 VRMS max analog output, centered around VREF. When OLB=0, the maximum output voltage is 3 dB lower, 0.707 VRMS. This output is a summed analog output from both the left and right output channels of the mixer. MOUT typically is connected to a speaker driver that drives the internal speaker in most computers. Independently mutable via MOM in I26.

[1245] MIDI Interface:

[1246] MIDOUT—Transmit Data, Output

[1247] This output is used to send MIDI data serially out to a external NMI device.MIDIN—Receive Data, Input This input is used to receive serial MIDI data from an external MIDI device.

[1248] Synthesizer Interface:

[1249] SCS/UP—Synthesizer Chip Select, Output

[1250] This active low output is forced low when a valid address decode to the synthesizer, as defined in the Plug and Play configuration registers, has occurred. This pin also become the UP input for the external master volume control.

[1251] XCTL1/SINT/DOWN/ACDCS Synthesizer Interrupt, Input /XCTL1, Output

[1252] This active low input is driven by the synthesizer interrupt output pin or outputs XCTL1 depending on state of XIOW when RESDRV goes low. This pin also outputs the alternate CDROM chip select when the alternate CDROM base address register has been programmed to a non-zero value. When using this pin as ACDCS the XIOW pin should be tied through a 10 k resistor to ground and this pin should be pulled up via a 10 k resistor. This insures that ACDCS remains high until the alternate CDROM base address register has been programmed. This pin also become the DOWN input for the external master volume control.

[1253] External Peripheral Port:

[1254] XD<7:0>—External Data, Bi-directional

[1255] These pins are used to transfer data between the ISA bus and external devices such as the synthesizer and CDROM. XD[0] is also used in conjunction with SCL to access an external I²C compatible serial E²PROM. The XD[0] is an open collector type output. A pull-up is required external to codec 100 on the XD[0] pin. The XD[0] pin should be also be connected to the data pin of the E²PROM device. The E²PROM is used to store the Plug and Play 72 bit serial identifier. The XD pins also may be switched to support the external wavetable serial interface and DSP serial interface:

[1256] XD7/DATA—External Data Bit 7, or wavetable synthesizer serial interface Data pin;

[1257] XD6/LRCLK—External Data Bit 6, or wavetable synthesizer serial interface LRCLK pin;

[1258] XD5/MCLK—External Data Bit 5, or wavetable synthesizer serial interface MCLK pin;

[1259] X 4/FSYNC—External Data Bit 4, or DSP serial interface FSYNC pin;

[1260] XD3/SDOUT—External Data Bit 3, or wavetable synthesizer serial interface SDOUT pin;

[1261] XD2/SDIN—External Data Bit 2, or DSP serial interface SDIN pin;

[1262] XD1/SCLK—External Data Bit 1, or DSP serial interface SCLK pin;

[1263] XA2/XCTL0—External Address, Output/XCTL0, Output:

[1264] This pin either outputs ISA bus address A2 or XCTL0 depending on the current Plug & Play resource data;

[1265] XA1—External Address, Output:

[1266] This pin outputs ISA bus address A1;

[1267] XA0/SCL—External Address, Output:

[1268] This pin is used to output ISA bus address A0 or the clock for the external EEPROM.

[1269] BRESET/—External Reset, Output:

[1270] This active low signal is generated whenever the RESDRV pin goes high;

[1271] XIOR/—External Read Strobe, Output—CDROM Enable, Input (Internal 100 K pull-up):

[1272] This active low signal is generated on a ISA bus read of an external peripheral device. This pin is sampled on the high to low transition of RESDRV. If this pin is sampled low then the CDROM interface operates normally. If this pin is sampled high then the CDROM interface pins operates as inputs for ISA bus address bits A12, A13, A14, and A15; and

[1273] XIOW/—External Write Strobe, Output—SINT Enable, Input (Internal 100 K pull-up):

[1274] This active low signal is generated on a ISA bus write of an external peripheral device. This pin is sampled on the high to low transition of RESDRV. If this pin is sampled low then the SINT functions as an input for the synthesizer interrupt. If this pin is sampled high then the SINT pin becomes an output for XCTL0.

[1275] Joystick/Serial Port Interface:

[1276] JACX, JACY, JAB1, JAB2, JBCX, JBCY, JBB1, JBB2—Joystick Data, Input:

[1277] These pins are used to connect directly to the game port connector. Optionally the #2 joystick pins may be programmed as a serial data interface.

[1278] JACX, JACY—Joystick A coordinates, Input:

[1279] These pins should connect directly to the game port connector and are the X/Y coordinates for Joystick A;

[1280] JAB1, JAB2—Joystick A Buttons, Input:

[1281] These pins should connect directly to the game port connector and are the switch inputs for Joystick A;

[1282] JBCX/SDOUT—Joystick B Coordinate X, Input/Serial Data Output, Output:

[1283] When this pin is used for a second joystick, it should connect directly to the X coordinate for Joystick B of the game port connector. When the serial port is enabled, via SPE=1 in I16, this pin is used to output the serial data.

[1284] JBCY/SDIN—Joystick B Coordinate Y, Input/Serial Data Input, Input;

[1285] When this pin is used for a second joystick, it should connect directly to the Y coordinate for Joystick B of the game port connector. When the serial port is enabled, via SPE=1 in I16, this pin is used to input the serial data.

[1286] JBB1/FSYNC—Joystick B Button1, Input/Frame Sync, Output:

[1287] When this pin is used for a second joystick, it should connect directly to the switch #1 input for Joystick B of the game port connector. When the serial port is enabled, via SPE=1 in I16, this pin outputs the serial frame sync;

[1288] JBB2/SCLK—Joystick B Button2, Input/Serial Clock, Output:

[1289] When this pin is used for a second joystick, it should connect directly to the switch #2 input for Joystick B of the game port connector. When the serial port is enabled, via SPE=1 in I16, this pin outputs the serial clock;

[1290] The dual functioning of the joystick interface pins is described is TABLE 85.

[1291] CDROM Interface:

[1292] CDCS/SA12—CDROM Chip Select (Output)—SA12 Address-(Input):

[1293] The function of this pin is determined by the state of the XIOR pin on the falling edge of RESDRV. If XIOR is sampled low then this pin functions as CDCS which is driven low whenever codec 100 decodes an address that matches the value programmed into the CDROM base address register. If XIOR is sampled high then this pin becomes an input for SA12;

[1294] CDACK/SA13/MCS—CDROM DMA Acknowledge (Output)—SA13 Address (Input)

[1295] Modem Chip Select (Input):

[1296] The function of this pin is determined by the state of the XIOR pin on the falling edge of RESDRV. If XIOR is sampled low then this pin functions as CDACK which is driven low whenever the ISA bus generates a low on the appropriate DACK line. If XIOR is sampled high then this pin becomes an input for SA13. If the Modem base address register is programmed to a non-zero value then the CDACK, function is switched over to the MCS function. In this case whenever codec 100 decodes an address that matches the value programmed into the Modem base address register MCS is driven low. Once this pin has been switched over to function as MCS it locked into this function until a RESDRV occurs;

[1297] CDINT/SA14—CDROM Interrupt (Input)—SA14 Address (Input);

[1298] The function of this pin is determined by the state of the XIOR pin on the falling edge of RESDRV. If XIOR is sampled low then this pin functions as CDINT which is used as an input for the CDROM interface interrupt line. If XIOR is sampled high then this pin becomes an input for SA14;

[1299] CDRQ/SA15—CDROM DMA Request (Input)—SA15 Address (Input):

[1300] The function of this pin is determined by the state of tie XIOR pin on the falling edge of go RESDRV. If XIOR is sampled low then this pin functions as CDRQ which is used as an input for the CDROM interface DMA request line. If XIOR is sampled high then this pin becomes an input for SA15;

[1301] Miscellaneous:

[1302] XTAL1I—Crystal #1 Input:

[1303] This pin will accept either a crystal with the other pin attached to XTAL1O or an external CMOS clock. XTAL1 must have a crystal or clock source attached for proper operation. The standard crystal frequency is 24.576 MHz although other frequencies can be used. The crystal should be designed for fundamental mode., parallel resonance operation;

[1304] XTAL1O—Crystal #1 Output:

[1305] This pin is used for a crystal placed between this pin and XTAL1I;

[1306] XTAL2I—Crystal #2 Input:

[1307] If a second crystal is used, is should be placed between this pin and XTAL2O. The standard crystal frequency is 16.9344 MHz although other frequencies can be used. The crystal should be designed for fundamental mode, parallel resonance operation;

[1308] XTAL2O—Crystal #2 Output:

[1309] This pin is used for a crystal placed between this pin and XTAL2I;

[1310] RESDRV—Reset Drive, Input:

[1311] When this input is high codec 100 is held reset and placed in the lowest power consumption mode. All sections of codec 100, except the digital bus interface which reads 80h, are shut down and consume minimal power. This pin is typically connected to the RESDRV pin of the ISA Bus;

[1312] VREF—Voltage Reference, Output:

[1313] All analog inputs and outputs are centered around VREF which is nominally 2.1 Volts. This pin may be used to level shift external circuitry, although any AC loads should be buffered. High internal-gain microphone inputs can be slightly improved by placing a 10 uF capacitor on VREF;

[1314] REFFILT—Voltage Reference Internal, Input:

[1315] Voltage reference used internal to codec 100 must have a 0.1 uF and a 10 uF capacitor with short fat traces to attach to this pin. No other connections should be made to this pin;

[1316] LFILT—Left Channel Antialias Filter Input:

[1317] This pin needs 1000 pF NPO capacitor attached and tied to analog ground.;

[1318] RFILT—Right Channel Antialias Filter Input:

[1319] This pin needs 1000 pF NPO capacitor attached and tied to analog ground;

[1320] TEST—Test:

[1321] This pin must be tied to ground for proper operation;

[1322] Power Supplies:

[1323] VA—Analog Supply Voltage; and

[1324] Supply to the analog section of the codec;

[1325] AGND—Analog Ground:

[1326] Ground reference to the analog section of the codec. Internally, these pins are connected to the substrate as are DGND3/4/5; therefore, optimum layout is achieved with the AGND pins on the same ground plane as DGND3/4/5 (see FIG. 17). However, other ground arrangements should yield adequate results.

[1327] VD1, VD2 Digital Supply Voltage:

[1328] Digital supply for the parallel data bus section of the codec. These pins should be connected to the digital power plane section of the board;

[1329] VD3, VD4, VD5—Digital Supply Voltage:

[1330] Digital supply for the internal digital section of the codec (except for the parallel data bus);

[1331] DGND1, DGND2—Digital Ground:

[1332] Digital ground reference for the parallel data bus section of the codec. These pins are isolated from the other digital grounds and should be connected to the digital ground section of the board:

[1333] SGND1, SGND2, SGND3—Substrate Ground:

[1334] Substrate ground reference for the internal digital section of the codec (except the parallel data bus). These pins are connected to the substrate of the die as is the AGND pin. Optimum layout is achieved by placing SGND1:3 on the analog ground plane with the AGND pin;

[1335] To support 3.3 Volt ISA Bus operation codec 100 connects all ISA Bus output pins (Data Bus, DMA Requests, and Interrupts) to a isolated digital supply (VD1 and VD2). To support 3.3 Volt ISA Bus operation the VD1 and VD2 supplies are connected to the 3.3 v power supply and the VDF1-VDF3 and VAA pins are connected to the 5 Volt supply. This mode of operation assumes that the logic levels for the 3.3 V ISA bus match that of standard TTL. Codec 100 ISA Bus inputs are not 5 v tolerant when operating with 3.3 V supplies. Thus when operating in 3.3 V mode the ISA bus signals must be at 3.3 V logic levels.

[1336] The Aux2 inputs have a “Ground Differential” reference pin (VCM-Pin 96) that can be used to eliminate ground loop noise from the CD-ROM in a PC environment. Power supply noise is introduced onto the CD-ROM audio signal by the current that is drawn by from the CD-ROM. The voltage on the ground pin of the CD-ROM audio cable is not at the same voltage potential as the other analog inputs to the Codec. This can result in CD-ROM disc drive “seeks” that can be easily heard in the background while playing music. Using a “Ground Differential” pin will reduce ground loop noise by up to 40 dB. Typical measured noise reduction is about −26 dB and is completely effective in eliminating the noise. The only component and circuitry changes that are needed are the addition of a “ground” coupling cap. Instead of connecting the CD-ROM audio cable ground to analog ground, connect a luF ceramic cap from the CD-ROM audio cable ground to pin 96 (VCM) of the CS4236. The cable that connects from the CD-ROM can be shielded or unshielded.

[1337] The microphone input, shown in FIG. 64A, can be set into a Differential mode for enhanced noise rejection and ground loop immunity. The left channel is connected to the inverting pin of the input op-amp, and the right channel to the non-inverting pin of the input op-amp. The output of the op-amp is sent to the left and right channel inputs of the Input and Output Mixer. Gain is adjusted by the left channel in extended register X2-LMCG4-0, the 20 dB boost is applied on each channel separately.

[1338] The circuit, shown in FIG. 64A, is a suggested implementation that may be used for both condenser and dynamic Microphones. The circuit supplies a switched DC bias that ramps slowly to help prevent pops when plugging in the Microphone.

[1339] FIG. 65 is a circuits implementation that may be used to drive Line Out and Headphones. The circuit has a gain of 1, as the Codec has an output impedance of 600-900 ohms. The circuit is “Pop-Free” when a 2.2 uf cap is used for VREF (pin 78) and a 10 uf cap is used for REFFLT (pin 79). Using a 2.2 uf cap for VREF instead of a 10 uF cap allows the VREF voltage to charge up smoothly, when a 10 uF cap is used the “quick charge” circuit is activated, causing a glitch in the voltage ramp-up. Note: also that the impedance seen by the Line out pins of the CS4236/7/8 must see a high DC impedance during reset or power up. The Line out pins are connected to VREF during reset by “weak” drivers and will not support low impedance loads. This will cause sagging of the signal during VREF ramp-up and glitch once VREF is complete. The circuit shown below prevents this by presenting a high DC impedance by buffering the input impedance of the op-amp by having the non-inverting input connected to VREF.

[1340] In an alternate embodiment of the present invention, codec 100 is provided in a streamlined version in which a number of features discussed above have been eliminated and new features have been added. This alternate embodiment has the substantial advantage of being less expensive while providing the essential functions in high-quality manner. Specifically, the following features that have been eliminated.

[1341] 1. u-Law/A-Law;

[1342] 2. ADPCM;

[1343] 3. Digital Joystick Assist;

[1344] 4. External Peripheral Port;

[1345] 5. External Modem Interface Support;

[1346] 6. Stereo Mic changed to Mono;

[1347] 7. Stereo AUX—In;

[1348] 8. SRS/QSound Stereo enhancement changed to Crystal method;

[1349] 9. Mono Out; ind

[1350] 10. Digital Mixer.

[1351] The added features are as follows:

[1352] 1. Internal PnP ROM;

[1353] 2. 90 dB DAC;

[1354] 3. Crystal Stereo enhancement;

[1355] 4. Internal Pullup Resistors on Joystick buttons;

[1356] 5. Seventh IRQ pin;

[1357] 6. Backdoor Non-PnP Configuration;

[1358] 7. Hardware configuration of PnP/Configuration port address;

[1359] 8. ZVPORT; and

[1360] 9. 250 mw power.

[1361] In the alternate embodiment, several of the mixer functions have been modified or eliminated. The eliminated mixer functions include:

[1362] LINE_IN (external FM/Wavetable) Stereo Analog Input;

[1363] ADC Digital Loopback—ability to monitor ADC is gone;

[1364] Independent Serial Port Volume Control—Volume control now shared between FM, external wavetable, and Clyde Serial Interface;

[1365] One MIC input channel and associated gain blocks;

[1366] Gain Control Into ADC;

[1367] Mono Out;

[1368] Digital Mixer; and

[1369] Gain Removed from output Master Volume Control.

[1370] In the alternate embodiments, a number of changes are made to the mixers. FIG. 66 is a diagram of an alternate mixer section 6400. In general, any of the following changes may be made either alone or in combination.

[1371] The mixer may operate as Mode 3 only. What this means is that switching to Mode 2 or Mode 1 operation will have no effect on mixer operation. The input sources into ADCs 111 are always controlled via a mix function and not a multiplexer function. Register accesses still have some Mode dependencies. These include Mode 2 and Mode 3 specific registers. Mode 2 registers may be accessed in Mode 2 or Mode 3 only and Mode 3 registers (i.e. Extended Registers) are accessible in Mode 3 only.

[1372] The Digital Mixer may be eliminated such that no digital audio sources are mixed digitally. The possible digital audio sources are Internal FM, external Wavetable, accelerator Digital, and ZV Port Digital Data. Instead, two DACs per channel are provided along with a number of multiplexers that control the flow of digital audio data into the DACs and then to the analog output mixer.

[1373] The two DACs are not identical. DAC1110 is the standard, 16-bit high performance, 1-bit delta sigma converter. DAC1 is used for converting .WAV streams transferred via ISA Bus interface 101 or from digital serial interface 117. The other, DAC26401, is a 12-bit R-2R parallel converter. DAC2 is primarily provided for conversion of digital audio from devices where lower performance audio is acceptable, such as from FM and Wavetable/ZV Port devices. It should be noted that the audio performance of DAC2 is limited by bit accuracy (12 bits) and distortion not signal-to-noise. The signal-to-noise performance (data at zero) is on par with that of DAC1. Since the human hearing mechanism is much more sensitive to noise than to distortion this trade off acceptable for a low cost alternate. In addition all audio performance testing uses DAC1110.

[1374] A programmable volume control and mute function is provided for each DAC110/6402. This results in the sharing of volume control between digital audio devices. Internal FM and Wavetable (external wavetable)/ZV Port are summed together and thus share a common volume control. Alternate embodiments of codec 100 include a scaler that can adjust the FM volume relative to Wavetable volume. The ISA Bus generated .WAV stream may only be controlled by the DAC1 volume control. Because a digital data stream may be directed to either DAC 110/6402, its volume may be controlled by either the DAC1 or DAC2 specific volume controls.

[1375] In order to improve power consumption based on mixer configuration, controls have been added so that when certain controls within the mixer are muted, the operational amplifiers used in implementing the function are put into an Idle State to reduce power. Functions are put into an Idle State upon the following conditions. (Note: Numbers in parenthesis represent the number of op-amps in that block. Mic, Imbst, Outbufl, and Outbufr use opa4_big type op-amps which means its op-amp can source or sink twice as much current as the other block's op-amps (800 uA vs. 400 uA).)

[1376] The routing of an accelerator 139 data to DAC1 or DAC2 depends on the system operating mode. In DOS protected mode game environments where the accelerator 139 is providing the wavetable function that data combined with Sound Blaster wave data. As such the an accelerator 139 data is routed through DAC26401 and the Sound Blaster wave data is routed through DAC1110. In WIN95 operating mode, the accelerator 139 provides all the wave mixing which is routed through DAC1 for highest audio quality output.

[1377] To utilize the DSP capability of the accelerator 139, the ability is provided to send digital audio data to the accelerator 139 via a digital serial link. A mux is provided to select between two digital audio sources. These sources are the ADC and ISA Bus playback FIFO.

[1378] By routing the ISA Bus generated audio data over to the accelerator 139 and then selecting the accelerator 139 output as the input source into DAC1, digital audio data from a Sound Blaster game may be processed/enhanced and then sent back to the codec 100 for output via the line output jacks.

[1379] In addition the ADC output can be selected as a source for digital data to the accelerator 139. This allows analog audio sources to be sent to the accelerator 139 for processing and then sent back over the serial link to the codec 100 for audio output via DAC1. This also results in the ability to mix in ZV Port data simultaneously via DAC2. One limitation to mixer is that Internal FM data cannot be digitally routed to the accelerator 139.

[1380] To enable the accelerator 139 to process both ISA Bus Wave audio and analog audio through the ADC simultaneously requires that the ISA Bus FIFO data be routed through DAC1, into the input mixer to create an analog sum of Wave and analog audio. The ADC output is then sent to the accelerator 139 of the serial link for processing. Because DAC1 is used in this instance for Wave data, DAC2 must be used for converting the serial data output from the accelerator 139 to analog.

[1381] In alternate embodiments, the Spatial Enhancement function is done in the analog domain. This advantageously enables all audio sources, whether digital or analog, to be spatially enhanced.

[1382] The LINE_IN Inputs may be removed. The eliminated analog input has been replaced by primarily digital sources such as internal FM and external Wavetable.

[1383] The volume control registers I18/19 associated with the removed LINE-IN function are retained for compatibility reasons. As such, accesses to these registers may affect volume changes to the FM or external wavetable audio streams depending on the setting of certain bits.

[1384] The output from DAC2 may be included as an input to the Input Mixer. This allows Internal FM, external wavetable, or ZV Port audio to be provided as an analog audio source into the ADC for recording purposes. The existing mute bits for the LINE_IN (I18, I19) function are changed to control the mute function of DAC2.

[1385] The MIC input may be changed to mono only. The left and right volume controls (X2, X3) are combined to operate as one. Accessing either register will affect the microphone volume. The mute controls operate similarly. The 20 dB boost stage into the output mixer may be eliminated and the existing 20 dB boost stage on the MIC input drives both the output mixer and input mixer. The bits (LMBST, RMBST) associated with enabling the, output mixer boost stage have been changed to also affect the enabling of the 20 dB boost stage.

[1386] The Volume Control Into ADC 111 may be removed. For Mode 3 operation a microphone boost amplifier is included to replace the gain amplifier that was removed.

[1387] In alternate embodiments, the Codec Register Access Redirection function is eliminated. One register mapping mode may be added to allow the AUX1 volume control to be controlled by either register pair I2/I3 or by register pair I18/I19. This function is controlled by the AUX1R bit in register X18.

[1388] The register Version/ID bits at control register C1 (default=100111xx) may change to reflect any changes in the alternative embodiments. FIG. 67A and the discussion below describe the implementation of the feature.

[1389] This read only register shadows the current contents of codec indirect register X25 to be read by microcontroller 103. This register holds the current chip identifier and version number.

[1390] FIG. 68 is a diagram of the bitfields of the FAB Port ID at Control Indirect register C17, (default=00000100). In order to track the various FAB ports of the CS4235 this register is updated each time any changes are done to the current revision in order to accommodate FAB specific requirements.

[1391] Codec registers may not in same logical device as Control Registers. For example, Map Control Registers may be moved into Codec Extended Register Space. This may be done by using Timer Registers I20 and I21 to map Control Base +5 and Control Base +6 registers. The mapping of Control Base +5,6 is enabled by (set to a one) the PAE bit in Register X18. When the PAE=0 then registers I20 and I21 become read/write only.

[1392] FIG. 69A is a diagram of the bitfields of Command Register (codec I21), (default=00000000) in alternate embodiments. This register is used to control various functions of the alternate embodiments. A Command is executed after the appropriate Command identifier is written to this register. When this register is either read or written via the ISA bus an interrupt will occur to microcontroller 103 via INT1.

[1393] FIG. 69B is a diagram of the bitfields of Program RAM Access End Register (base +6), (default=00000000). This register is used to end access to the Program RAM memory of the alternate embodiment. When this register is written via the ISA bus, an interrupt will occur to microcontroller 103 via INT1:

[1394] Map rest of Control Base +0,1,2,7 and Control Indirect Registers CI2, CI8, and CI9 into Codec Extended Register space. Note: when accessing power down functions using the X-Mapped Control Registers the clock must never be disabled (XTAL=1).

[1395] In alternate embodiments, a New Crystal Key may be defined that allows the device to be configured uniquely when two devices coexist in the same system. Microcontroller 103 should support configuring all codec 100 physical/logical devices and downloading of resource data and RAM patch data. In addition a new pin may be defined for providing a “Hardware Strap” function for providing a power-up (RESDRV) defined I/O address for receiving either the Plug-n-Play or Crystal Backdoor Keys. This address replaces the standard 0x279 address. This will enable motherboard devices to be configured through a specific hardware address that is different from the standard PnP address of 0x279. The HWSTRAP pin when pulled low (internal pull-up to VDD) will force the “Key” address port to one of three fixed addresses. The fixed address is selected by pullups/pulldowns on the HWSTRAP and SCL pins. The use of pin 2 (FSYNC) which may be either an input or an output is ok since this pin operates as input when connected to external wavetable, and external wavetable tri-states, this pin when it is held reset via BRESET.

[1396] HWSTRAP and SCL are sampled on power-up when RESDRV transitions from a one to a zero. The state of these pins determines what ISA bus I/O address is used for the PnP and Crystal Keys, TABLE 86 summarizes the relationship between HWSTRAP and FSYNC.

[1397] The following 32-byte hex sequence defines the “Crystal Key 2”. Once this 32-byte sequence is detected the following 2-bytes specify the 12-bit address for the configuration read/write data port. Logic in the device will load the 12-bit address for the traditional Plug-n-Play read_data_port address decode when this 32 byte sequence is detected. Once the address for the configuration port has been specified then the CS4235 device may be configured using standard Plug-N-Play commands.

[1398] 95, B1, D8, 6C, 36, 9B, 4D, A6,

[1399] D3, 69, B4, 5A, AD, D6, EB, 75,

[1400] BA, DD, EE, F7, 7B, 3D, 9E, CF,

[1401] 67, 33, 19, 8C, 46, A3, 51, A8, (read_data_port address)

[1402] When the Crystal Key 2 sequence is detected microcontroller 103 is interrupted via INT0 and status bits are placed on IOPORT1. When microcontroller 103 detects receipt of “Crystal Key 2” microcontroller 103 puts the CS4235 into the Plug-N-Play configuration state. The next byte (#33) sent to the “Key Port” following receipt of the 32 byte Crystal Key 2 sequence sets the Read_Data_Port address. The hardware detects this and directly writes byte #33 into the Read_Data_Port register. Plug-N-Play commands are then sent to the Read_Data_Port to configure the various logical devices.

[1403] During Plug-n-Play sequences the int0 input to microcontroller 103 is forced active whenever a “Plug-n-Play Key” or “Crystal Key2 ” is received. microcontroller 103 I/O Port 1 is used to provide further Plug-n-Play status to microcontroller 103. The PnP status register configuration when Crystal Key 2 is employed is shown in FIG. 70, where:

[1404] In alternate embodiments, Software uses Control Register Base +0 and Base +2 registers for power down. Power down values of 0xC0 for Control Base +0 and 0x7E for Control Base +2 may be used. For non-plug-n-play functions microcontroller 103 will automatically enter the idle state upon completion of each command. The only Plug-n-Play mode in which microcontroller 103 will enter the Idle State is Wait-For-Key.

[1405] Microcontroller 103 will only initialize registers from an initial power up state (RESDRV active). Microcontroller 103 will set a Flag upon initial power up (RESDRV active) which will be retained during power down. This Flag when=0 indicates that microcontroller 103 has been brought out of reset via an initial power on condition (registers must be initialized). Then when=1 indicates that microcontroller 103 has been brought out of reset via a resume condition (registers do not have to be initialized).

[1406] Some examples of possible power down scenarios are shown below. Other combinations may be possible depending on the setting of the various power down bits.

[1407] XTAL off, VREF on, microcontroller 103 held reset. All other registers retain values.

[1408] Suspend/Full Maximum power savings.

[1409] XTAL off, VREF off, microcontroller 103 held reset, all registers retain data. Resume is accomplished by turning XTAL and VREF back on and restoring microcontroller 103 state.

[1410] When physical devices are disabled, via activation register, their function may be powered down.

[1411] All device registers (including codec volume controls) may be made accessible independent of any power-down state when the clock is running (XTAL=0, RESDRV=0).

[1412] The registers used to control the various possible power down features are shown in FIGS. 71A-71C. These registers also control various functions in the alternate embodiments, as described below.

[1413] FIG. 71A is a diagram of the bitfields of Miscellaneous Control Register at CTRLbase +0, (default=0x00000000). The bitfields of this register are decoded as follows:

[1414] JS1, JS0—select among four joystick operating speeds;

[1415] FIG. 71B is a diagram of the bitfields of Power Down Control Register 1 at CTRLbase +2, (default=00000000).

[1416] FIG. 71C is a diagram of the bitfield of Power Down Control Register 2 at Control Indirect +0x9, (default=00000000):

[1417] To handle situations in which the IOCHRDY is asserted and never released a Watchdog timer may be added. A signal hung IOCHRDY scenario may occur, for example, when IOCHRDY is asserted and the hardware is waiting for a response from microcontroller 103 to clear it, which does not occur for some reason. This could occur due to corrupt host down load or via a chip defect that was not caught by test vectors. Because a hung IOCHRDY is a good indicator of a system problem a host accessible status bit is provided when the Watchdog timer has timed out.

[1418] The Watchdog timer is defined to timeout 10 msec secs after IOCHRDY has been asserted. If IOCHRDY has not been released by the time the Watchdog Timer times out, IOCHRDY will be released and a reset will be generated to microcontroller 103. In addition the time out flag will be set to a one.

[1419] When this option is implemented, Codec Timer is decoupled from registers I20 and I21 and used to implement the Watchdog Timer. The TE bit in Register I16 will no longer be functional and will always read a zero. The Timer Interrupt TI is also forced to be read as zero.

[1420] The Watchdog Timer Status (WTS) bit is defined to reside in CTRLBase +7, bit D2, as shown in FIG. 72. The Watchdog Timer is disabled in Primary Test Mode 4.

[1421] An additional interrupt map select bit for an additional interrupt IRQG may be added. Internal interrupt to interrupt pin mapping consequently operates as follows. Each interrupt pin IRQA-IRQG has an index associated with it according to TABLE 87. This index value is written to the corresponding microcontroller 103 interrupt configuration register to map a specific interrupt to a specific interrupt pin. This architecture allows multiple interrupt sources to be mapped on a single interrupt pin.

[1422] Where PIN Interrupt pin, A,B,C,D,E,F,G.

[1423] FIG. 73 is a diagram of the bitfields of the interrupt select register used to implement interrupt control.

[1424] In alternate embodiments, the modem mask register shown in FIG. 74 may be used as a CDROM Base Address Mask Register at microcontroller 103 Address 0x33. The CDROM Base Address Mask Register provides a means to vary the number of consecutive byte locations that the CDROM decode may occupy. Each mask bit is used to prevent specific address bits from being decoded in generating the modem I/O decode. The valid bit combinations are as showm below. All other combinations are invalid and may cause erroneous operation. The decoding is shown in TABLE 88:

[1425] The alternate embodiments, the SRS/QSound features may be replaced with the analog circuitry shown in FIG. 75A. This circuitry provides for spacial enhancement of stereo sources. The frequency contour is shown in FIG. 75B.

[1426] Acoustic Crosstalk arises when a stereo signal is reproduced by two loudspeakers located to the left and right in front of the listener. Each ear receives not only the wanted signal (left ear—left signal, right ear—right signal) but, additionally, an unwanted part of the opposite channel, as a result of diffraction at the head. The amount of crosstalk is frequency dependent and diminishes with increasing frequency. As a result of this crosstalk, stereo images can only be reproduced in between the two loudspeakers. Stereo images cannot be created to the extreme right or left of the loudspeakers.

[1427] The unwanted crosstalk signal can be compensated for by feeding each loudspeaker with a filtered version of the opposite channel signal inverted in sign and superimposed on the original signal. Although sophisticated frequency response shaping and phase correction can be applied to the crosstalk compensation signal to more accurately place stereo images in space, it is not the intent of this design. The intent of the design is to spread the stereo image beyond the boundaries defined by the position of the loudspeakers themselves. To this end the frequency response shaping network has been kept simple from a circuit implementation and component count point of view. The frequency response shaping characteristic was determined from a listening perspective. Because most directional information occurs at mid-band frequencies, this frequency range will be elevated in level as compared to the low and high frequency extremes. To compensate for this effect, the mid-band frequencies are filtered to provide a 6 dB dip in the response centered around 2 kHz.

[1428] In the analog enhancement circuitry illustrated in FIG. 75A, a difference amplifier (subtractor 7501) is used to create a Left minus Right signal. This signal is then filtered by a network consisting of R16, C5, R18, and C6. This filtered signal is the crosstalk compensation signal. The signal is then summed into the main left channel (summer 7505) and inverted and summed into the main right channel (inverter 7504 and summer 7506). The left channel is thus composed of Left plus a filtered left-minus-right signal. Correspondingly the right channel is composed of Right plus a filtered right-minus-left signal. The gain of ½ in the summing stage is to compensate for the fact that a momo signal will result in an overall gain of 2. Thus the summer gain of ½ will result in an overall gain of 1 (summers 7505 and 7506) when a mono signal is present.

[1429] As shown in FIG. 75A, analog spacial enhancement circuitry 7500 includes an analog subtractor 7501, notch filter 7502, inverter 7503 and a pair of summers (adders) 7505 and 7506.

[1430] FIGS. 75C and 75D are respectively the modified 3D Sound/Serial Interface Control (Codec Extended Register at X18, (default=00000000) and 3D Sound Control (Control Indirect CI3, (default=00000000). Analog 3D enhancement is enabled by either 3DEN (bit D4) in register X18 or by 3DEN (bit D4) in Control Indirect C13 when set=1. When the 3DEN bit in both registers are zero then the 3D enhancement function is disabled.

[1431] In alternate embodiments, serial interface (port) 117 may be modified to simultaneously communicate with wavetable synthesizer 134 and accelerator 139 or with accelerator 139 and ZVPORT. Specifically, either wavetable synthesizer or ZVPORT may be selected as the input to the R-ZR DAC. When the accelerator is connected to the serial port, the SVPORT data is routed to the R-ZR DAC and the accelerator data to the Delta-Sigma DAC.

[1432] The serial port 117 interface consists of seven pins. In the preferred embodiment, these pins are defined as SDATA, LRCLK, MCLK, FSYNC, SDOUT, SDIN, and SCLK. In one alternate embodiment, these pins are defined as SDATA, FSYNC(LRCLK), MCLK(SCLK), ZVLRCLK, SDOUT, ZVSDATA, ZVSCLK. TABLE 89 describes this modification, where, for the preferred embodiment:

[1433] and where for the alternate embodiment:

[1434] TABLE 89A shows the decoding of the WTEN and SPE bits which control the serial interface 117 pins in the preferred embodiment. TABLE 89B shows the decoding of the WTEN, SPEN, and ZVEN bits which control the serial interface 117 pins in the alternate embodiments.

[1435] In the alternate embodiment, the accelerator DSP serial port is enabled by setting the SPE bit in codec register I16. Once this bit is set to a one the DSP Serial Port pins function as specified by the SF1:SF0 bits in register I16. Serial Port Mode 4 are be used to transfer ADC and playback SRC data simultaneously out the Serial Data Out pin. All other Serial Port modes support transfer of ADC data out the Serial Data Out pin.

[1436] The wavetable synthesizer 134 serial interface is enabled by setting the WTEN bit in register CB to a one. If both WTEN and SPE are set then the pins are forced into a accelerator 139 DSP serial port mode.

[1437] FIG. 76 is a diagram representing the serial interface connection of accelerator 139/ZVPORT with an alternate embodiment of Codec 100.

[1438] Similarly, FIG. 77 shows the connection of wavetable synthesizer 134 with this embodiment of Codec 100. This connection is advantageously a zero glue logic connection.

[1439] Serial Port Mode 3 (SF1,0=11). Serial Port Mode 3 is selected by setting the SFI, 0 bits in register I16 to 11. This format is a 64 bit per frame format that includes ADC as well as DAC 16-bit data. This mode is intended for use by an external DSP such as accelerator 139.

[1440] The wavetable synthesizer 134-codec 100 combination in the alternative embodiments has several advantages:

[1441] 1. This combination operates from one 16.9344 MHz crystal or clock source. Codec 100 is the master clock generator for the wavetable;

[1442] 2. The serial interface for the wavetable requires only three pins: MCLK, LRCLK, and SDATA. The CS4235/Accelerator 139 generates only the master clock via the MCLK pin for wavetable synthesizer 134. This insures that both devices operate synchronously. Because of timing skews between codec 100 and the wavetable, codec 100 synchronizes the data sourced from the wavetable to its internal clock. Codec 100 detects the edge of LRCLK and performs synchronization so that the digital audio from the wavetable is mixed properly with codec 100 internal audio data before being sent to the DAC;

[1443] 3. The three pins defining the Codec/wavetable serial interface. These pins are enabled by bit WTEN in Control Indirect Register CI8; and

[1444] 4. BRESET—The BRESET pin is forced low when RESDRV high, when PM1, PM0 are set to 10 in CTRLbase +0, or when the BRESET is set to one in register C8.

[1445] To minimize the number of serial port timing modes required by the wavetable synthesizer 134, the serial port timing is defined to match the default internal SCLK mode for a 384 fs master clock. The SCLK frequency is 48×44.1 kHz. Thus the least significant 16-bits should be accepted and the rest ignored. This timing is illustrated in FIG. 78, for the Internal SCLK Mode, where 16-Bit Data is shown:

[1446] Data Valid is on Rising Edge of SCLK; and the INT SCLK=48 Fs if MCLK/LRCK=384.

[1447] The ZV Port interface requires support for a 256 Fs and 384 Fs master clock. The timing is specified as I²S. The ZV Port interface must automatically detect the ZVLRCLK/ZVSCLK ratio and set the proper data formatting. A 384 Fs, ZVMCLK results in a ZVLRCLK to ZVSCLK ratio of 32 and a 256 Fs ZVMCLK results in a ZVLRCLK to ZVSCLK ratio of 48. The ZVPORT inputs are again as follows:

[1448] Pin 4 -- ZVLRCLK—Input;

[1449] Pin 6 -- ZVSDATA—Input; and

[1450] Pin 7 -- ZVSCLK—Input.

[1451] The ZVMCLK is not required for ZVPORT support. Although the LRCLK/SCLK ratio must be detected and automatically switched to support the 256 Fs and 384 Fs ZVMCLK data formats.

[1452] The ZV Port definitions are as follows:

[1453] The ZV Port audio DAC must support a ZVMCLK frequency of 256 times and 384 times the input word rate. This results in the frequencies shown in TABLES 93A and TABLE 93B

[1454] FIG. 80 is a diagram illustrating the ZV Port Audio Interface timing. TABLE 94 tabulates the AC parameters for these audio signals.

[1455] FIG. 81 is a diagram emphasizing one digital audio path for the alternate embodiments. The Digital Audio Data Path components include the Delta Sigma ADC, Delta Sigma DACs 6401 and 6402, FIFOs 121 and 122, R-2R DACs 6401 and 6402, and Serial interface. Analog audio is digitized by the ADC, decimated, and sent to the ISA bus capture FIFO and optionally sent out the serial output pin as defined by the SPISEL (Control Index C3 bit D5) bit. Digital audio data (.WAV) sourced from the ISA bus playback FIFO 122 is sent to the Delta Sigma DAC 110 as selected by the DACSEL (Codec Extended Register bit D3) bit through multiplexer 8101. Alternately the digital audio data sourced by the accelerator Serial Interface may also be sent to the Delta Sigma DAC 110 for conversion to analog. The data audio data sourced from the FM block 123 is summed with wavetable digital audio data at block 8102 and sent to the R-2R DAC 6401 for conversion to analog. Alternately, mux 8103 allows the accelerator 139 digital audio data to also be sent to the R-2R DACs. The serial port digital output data may be either sourced from the ADC or from the ISA bus playback FIFO 120.

[1456] FIG. 82 depicts the bitfields of the 3D Sound/Serial Interface Control at Codec Extended Register, X18, (default=00000000) in the alternate embodiments. The bitfield decoding is as follows:

[1457] As described above, the Delta Sigma DACs 110 operate at a fixed 44.1 kHz rate. As such it is assumed that the accelerator 139 input data rate will be 44.1 kHz. The inclusion of the R2R DACs 6401/6402 allows for asynchronous digital audio data to be accepted via serial interface 117 as is required for ZV Port support. Accelerator/DSP digital audio data may also be converted by the R-2R DAC, but some signal degradation may result.

[1458] DAC2 (R-2R) 6401/6402 is a 13-bit device. The FM and wavetable synthesizer word widths are 16-bits. To allow the FM and external wavetable data streams to be heard at the same time, an adder/truncator 8102 is used to combine the streams into one 13-bit data stream for input to DAC26401/6402. Because the volume control function only operates as part of DAC2 some method of adjusting the relative volume level between the FM and wavetable sources is desirable. Therefore, a data selector is used to specify which 13-bits of the 16-bit FM data word are selected as an input to adder/truncator 8102. Codec Extended Register X19 is used to control this function, in accordance with TABLE 95.

[1459] In alternate embodiments, logic and ROM's associated with u-Law/A-law/ADPCM/Big Endian functions 120 may be removed. In this case, Index Register I8 is changed as indicated by highlighted and italicized boxed items in TABLE 96. Formats associated with deleted functions now default to one of two supported formats: Linear, 8-bit insigned or Linear, 16-bit two's complement, Little Endia. Additionally, index registers I17 and I23 are appropriately modified as shown in FIGS. 83 and 84, respectively.

[1460] In FIG. 83, APAR—ADPCM Playback Accumulator Reset. While set, the Playback ADPCM accumulator is held at zero. Used when pausing a playback stream.

[1461] IN FIG. 84, ACF ADPCM Capture Freeze. When set, the capture ADPCM accumulator and step size are frozen. This bit must be set to zero for adaptation to continue. This bit is used when pausing a ADPCM capture stream.

[1462] Due to the ADPCM function being deleted the APAR and ACF bits are now defined to always be zero.

[1463] The Digital Joystick Assist 16-bit counters and logic as well as the DAC gain/attenuator may also be removed. In the case of removing the DAC gain-attenuator, register accesses to I6 and I7 are mapped to the digital .WAV gain-attenuation control. Extended Registers X14 and X15 no longer have any function associated with them, but retain read/write capability. When I6 or I7 are used to mute the WAV playback the corresponding output channel of the DAC is also muted. In this way the analog noise contribution of the DAC will be muted when the digital WAV playback is muted.

[1464] The Mono Out supporting logic may be eliminated and the mono input functions minimized. Mono I26 is changed as shown in FIG. 85. The MBY and MOM bits no longer have any function associated with them. These bits remain read/write accessible. The MIA3-MIA0 bits are changed to allow 2 attenuation settings. A zero value for MIA3:MIA0 specifies a 0 dB attenuation, a non-zero value for MIA3:MIA0 specifies an attenuation setting of −9 dB. In FIG. 85:

[1465] The following additional features may be eliminated in the alternate embodiments;

[1466] 1) LINE_IN Analog Input and the associated volume control;

[1467] 2) Differential Mic Analog Inputs and the opamps associated with this function;

[1468] 3) ADC Digital Loopback Attenuator and the logic associated with ADC digital loopback attenuator. Registers I13 and X10 now have no function and should be read/write accessible from the ISA bus. The loopback function is still available in Codec Extended Register X18 bit D0; and

[1469] 4) ADC Input Master Gain Control including the analog 0-22 dB gain block between input summer and ADC. The LAG3:0 and RAG3:0 now become don't cares in the left and right ADC input control registers (codec register I0 and I1). Any value read or written to these registers results in no functional change in the device. The LSS1:0 and RSS1:0 bits function as before as they select analog loopback when=1,1. The LMGE and RMGE bits currently are disabled in MODE3.

[1470] The MIC Input may be modified as follows:

[1471] 1) Change MIC input to mono only;

[1472] 2) Delete MIC right channel gain block. Register X3 (Right MIC volume) accesses are now directed to X2 (Left MIC Volume). In this way software accesses to either register will result in the MIC volume being adjusted. The left MIC input should also feed both the left and right inputs to the Input Mixer. The RMIM (Right MIC mute to input mixer) should still function normally;

[1473] 3) Modify output mixer so that left mic input is routed to both right and left line outputs. The RMOM (Right MIC Output Mixer Mute) should still operate as before; allowing independent mute/unmute of MIC input to left or right line outputs; and

[1474] 4) Delete 20 dB gain-boost amplifier from MIC right channel. Move remaining 20 dB boost amplifier so that its output drives both the Input Mixer and Output Mixer. The RMBST (codec extended register X3), LMBST (codec extended register X2), LMGE (codec register I0), and RMGE (codec register I1) bits now all control enabling and disabling of the 20 dB boost amplifier via a Logical OR function.

[1475] In the alternate embodiments, The Master Volume registers are accessible by microcontroller 103 in SFR register space (codec registers I27A, I29A) or via ISA interface 101 through the Control Port at index I27/C27 and I29/C29. One register accessible at addresses pertaining to I27/I29, C27/C29, and I27A/I29A is all that is required. Left Master Volume is accessible at index registers I27 and C27 via the ISA bus and I27 and I27A via microcontroller 103. Right Master Volume accessible at index I29 and C29 via the ISA bus and I29 and I29A via microcontroller 103.

[1476] An external 3-button and 2-button mode of Up-Down-Mute control of master volume may be provided. This function is enabled by the VCEN bit in the EEPROM Hardware Configuration Data and in bit D2 (VCEN) of microcontroller 103 Address 0x34. External Master Volume 3-button/2-button is selected by bit D6 (VCF1) of the Control Indirect Register CI8 and microcontroller 103 Address 0x40.

[1477] A set of defined pins (Up, Down, Mute) may be used with external switches to control the overall audio level driven out the line outputs. Each change in button state, from high-to-low, will cause the master volume register to be incremented, decremented, or muted. If a button is held down then the increment/decrement will continue to occur at 500 ms intervals. The master volume control hardware allows access to the master volume control registers by the ISA bus and microcontroller 103 simultaneously with volume updates initiated by external button activity. The hardware monitors ISA/microcontroller 103 access to the master volume control registers and updates the registers between ISA/microcontroller 103 cycles.

[1478] In both Sound Blaster mode and WSS mode, the user may change the CODEC Master Volume via pins connected to physical switches or buttons. There are currently 2 different “button schemes” which may be used. The user selects 1 of the 2 schemes by setting the VCF1 and bit in the Hardware Configuration Data, Global Configuration Byte, contained in the EEPROM.

[1479] Master Volume Control Bits are added to the Wavetable and Serial Control Indirect Register CI8 indexed by Control Base +3 and accessible at Control Base +4, as depicted in FIG. 86. This register is also read/write accessible by microcontroller 103 at address 0x40. The bitfield decodings are:

[1480] The VCEN bit, shown in FIG. 87, which is a diagram depicting miscellaneous control bits at microcontroller address 0x34, enables the control of the master volume via the external buttons.

[1481] To implement the 3-button volume control scheme, the Up, Down and Mute pins is connected to momentary SPST switches. This scheme is selected by setting VCF1=0 in the EEPROM configuration data. The 3-button functioning is summarized in TABLE 97.

[1482] Pushing the Up button or the Down button will un-mute the Codec if it was muted with no volume change.

[1483] To implement the 2-button scheme, the Up and Down pins connected to momentary SPST switches. The Mute pin is not connected and is ignored. This scheme is selected by setting VCF1=1 in the EEPROM configuration data. The 2-button functioning is summarized in TABLE 98.

[1484] Pushing the Up button or the Down button will un-mute the Codec if it was muted with no volume change.

[1485] In alternate embodiments, the External Master Volume hardware control may support the generation of an interrupt upon detection of a button push. The interrupt is active high and is logically OR'd with the codec/SB interrupt. An ISA accessible enable bit is used to enable the generation of this interrupt. The location of this External Master Volume Interrupt status is in Global Status Register (CTRLbase +7), IMV field, as shown in FIG. 88. IMV=1 indicates that an interrupt has been generated in response to an external button push. The interrupt is enabled by bit D2 (VCIE) in Control Indirect Register CI8 and at microcontroller 103 Address 0x40.

[1486] In alternate embodiments, the Karoke function may be eliminated from the mixer. Consequently, the ADC1/ADC0 bits (Hardware control register base+1) now become read/write with no associated function.

[1487] The Modem Logical Device may be eliminated by removing the modem base address low (microcontroller address 0x30), modem base address high (microcontroller address 0x31) and modem interrupt select (microcontroller address 0x35) registers.

[1488] Primary Test Mode 13 is the Clock-Off Detect mode.

[1489] The firmware functioning used in the alternate embodiments of the principles of the present invention can now be described. After initialization based on EEPROM data and other ROM constants, the Plug and Play mode is entered where microcontroller 103 monitors PnP hardware for PnP events and then services the PnP commands through the PnP hardware.

[1490] When the PnP activity is over, signaled by the host as an activate command, the firmware continues initialization and then transitions into Sound Blaster emulation mode. This part of the code consists of a polling loop (Foreground Loop) and interrupt processing. The polling loop in general looks for status bits changed in the interrupt routines. The Microcontroller 103 is interrupted from the main loop for host activity like certain SB read/write, WSS/SB context switch, certain control port commands and by other events like MIDI data receive.

[1491] The Init code and PnP code refer to the hardware configuration data area in microcontroller external RAM from addresses from 0x4000 to 0x4012 and the PnP resource data area from addresses 0x4013 to 0x417F for configuration and PnP resource data. RAM locations from 0x4180 to 0x42FD in microcontroller external RAM are dedicated to patch space.

[1492] The Firmware host command interface is accessed through ControlBase +5 and 6. Commands are sent and data is read from ControlBase +5. The RAM interface command is terminated by a write of ControlBase +6 (RAM END). These commands are summarized as follows:

[1493] 0xAAh—RAM POINTER L0AD: Begins the RAM/ROM/INTERNAL start address L0AD for Read/Write access.

[1494] Command sequence is as follows:

[1495] Write to ControlBase +5−0xAA;

[1496] Write to ControlBase +5−0xLL=low byte of the microcontroller 103 xData Address;

[1497] Write to ControlBase +5−0xHH=high byte of the microcontroller 103 xData Address;

[1498] R/W of ControlBase +5−Access data starting at address, auto increment;

[1499] *** Access data starting at address, auto increment; and

[1500] Write to ControlBase +6−RAM END, Terminates command; and

[1501] 0x42h—HOLD: Puts microcontroller 103 in a tight loop, with no codec accesses;

[1502] 0x43h—GO: Causes an exit from HOLD loop and a resumption of normal code operation;

[1503] 0x57h—JUMP_TO_ROM: Forces code to jump to tight loop in ROM and overwrites the patch table with microcontroller 103 RET opcodes;

[1504] 0x33h—SUSPEND: For power management, suspends execution before powerdown. The state of microcontroller 103 is saved and made available for the HOST to read;

[1505] 0xCCh—RESUME: For power management, resume execution after power down (SUSPEND);

[1506] 0x3Ch—microcontroller 103 POWER DOWN: Causes microcontroller 103 to enter the IDLE state, consuming less power. This IDLE state is exited after any microcontroller 103 interrupt like SBRESET, SB mixer access, RAM load command, etc.;

[1507] 0x58h—SET_READ_ROM_FLAG: Next RAM/ROM/INTERNAL command will READ ROM. Execution of RAM_END clears this state;

[1508] 0x54h—SET ACC INT FLAG: Next RAM/ROM/INTERNAL command will READ/WRITE Internal RAM. Execution of RAM_END clears this state;

[1509] 0x5Ah—UPDATE_PNP: After Hardware header information is written, causes Plug and Play and other system variables to be synchronized. This command is issued after resource data and hardware configuration data are loaded by the host;

[1510] 0x56h—DISABLE_CKD: Disable Crystal Key. The Crystal key will be ignored after this command is issued; and

[1511] 0x55h—DISABLE PNP: Disable Plug & Play Key. The Plug and Play key will be ignored after this command is issued;

[1512] 0x59h—SW_RESET: Jump to location 0x0000 of the code (RESET VECTOR).

[1513] Control Port Command Delay Requirements. Certain delay periods are required when accessing commands and functions of the Firmware:

[1514] Delay between PnP or Crystal wait-for-key command and any Control Port Command >1 mS;

[1515] Delay between UPDATE_PNP and any PnP activity >1 mS;

[1516] Delay After RESUME command >1 mS; and

[1517] Delay after JUMP TO ROM command >1 mS.

[1518] A default ROM image of PnP data including default hardware header data, PnP serial ID and PnP resource data is copied from ROM to RAM at powerup, before the optional EEPROM is detected. This image in RAM is what is used for PnP resource data and hardware configuration data if no optional EEPROM is present and no host resource shoot has been done to overwrite this default image.

[1519] Below is the Default ROM PnP Image for the alternate embodiments of codec 100. The default image may be replaced at powerup by the EEPROM, or at initial time by the system BIOS. A total of 384 (decimal) bytes of resource data plus hardware header may be used. This byte count does not include the 0x55, 0xBB, and length fields.

[1520] To facilitate segregation of EEPROM based code shoots among the various pin compatible devices and to promote backward compatibility with host code of other embodiments of codec 100, a ‘Family Byte’ is defined. The family byte is located in EEPROM Hardware configuration byte 9 and RAM location 0x4004. The EEPROM byte is copied to RAM at powerup. There are two different Family Byte values; one for EEPROM load and one for Code Load.

[1521] If the Family Byte in the EEPROM does not match the expected EEPROM value, the EEPROM FIRMWARE RAM patch will be ignored. The resource data, however, will be loaded normally. The EEPROM byte is compared to a stored ROM value for a given ROM release. If the bytes do not match during EEPROM load, the load is terminated at 0x417F, after the resource data. This byte allows the firmware to ignore patch code intended for a different ROM release when the EEPROM has not been updated.

[1522] If the Family Byte in RAM does not match the expected code load value during a code load, the RAM firmware will not be overwritten. The BIOS and driver code must write the family byte before updating firmware.

[1523] The ROM firmware code is written so that the RAM is entered at selected strategic points in the code. The CALLing points, scattered throughout the ROM, call RAM and return if no patches are loaded. Initialization code fills all these called locations with a RET (0x22) instruction. mRAMx macros are used to conveniently call these RAM entry points where ‘x’ refers to the particular entry point.

[1524] The following is an example of an mRAMx macro. These macros are placed in the code source to allow RAM based code changes.

[1525] Multiple CALLs can be made to the same mRAM entry point as each use of the particular mRAMx has a unique value in R7.

[1526] If patches have not been loaded, the mRAMx entry table will contain a 0x22 (microcontroller 103 RET instruction). After a patch is loaded via the EEPROM or Host, the mRAMx entry table will contain jumps to code loaded into the patch RAM. Upon a RESET, SW RESET command, or JUMP_TO_ROM command, the mRAMx entry table will be filled with a RET opcode (0x22) again. The JUMP_TO_ROM command is used before loading RAM via the control port to insure code is not loaded over code that is currently executing from RAM (from a previous load).

[1527] In alternate embodiments, the vendor defined registers may be redefined. These registers are accessed only in Plug and Play Configuration State and may be defined as follows:

[1528] 1) Register 0x28, write only register, write a byte to this register will disable/enable PnP and Crystal keys;

[1529] Register 0x28 Definition and Access Rules are as follows:

[1530] Enter codec 100 into config_state either through PnP cycle or Crystal Key 2;

[1531] Write an 0x28 to the ADDRESS port (this ADDRESS port can be either PnP ADDRESS port or the one decided by HWSTRAP and FSYNC); and

[1532] Write a byte which has the key disable information (i.e. 0xA0 presents PnP key disable, 0xB0 presents Crystal Key disable, etc.) to the WRITE DATA port (again, this WRITE_DATA port can be either the PnP WRITE_DATA port or the one assigned by Crystal Key 2).

[1533] 2) Register 0x29, read-only register, a read to this register will obtain the port ID. Register 0x29 Definition and Access Rules are as follows:

[1534] Put chip into config_state either through PnP cycle or Crystal Key 2;

[1535] Write an 0x29 to the ADDRESS port (this ADDRESS port can be either PnP ADDRESS port or the one decided by HWSTRAP and FSYNC); and

[1536] Read the ID byte from READ_DATA port (again, this READ_DATA port can be either the PnP READ_DATA port or the one assigned by Crystal Key 2).

[1537] A 7^thinterrupt IRQ labelled G is supported. This IRQ which reflects host PC resource, is defined in the high byte of the 19^thbyte in resource head data, exclusive of EEPROM length and validation bytes. It is recommended that if this IRQ output is used, it is mapped as IRQ 10. The IRQ mapping defaults to 0 (disabled) for backward compatibility.

[1538] Microcontroller 103 int0 will not be enabled until after power-on initialization, transferring resource from microcontroller 103 ROM (or EEPROM) to its RAM, and the device be put in PnP wait_for_key state.

[1539] Crystal Key 2 will directly put codec 100 into PnP config_state without first being isolated. In this state, the codec 100 will be ready to process any PnP commands as long as they are valid in PnP config_state. After Crystal Key 2 configuration, a wait_for key reset command is expected to put the device back to normal (wait_for_key) state.

[1540] The 0x2090 to 0x400C address translation code for Windows 3.1 driver compatibility is not included in the Firmware ROM. Control Port RAM writes with a start address of 0x2090 will not be written to RAM at 0x41C0. RAM writes outside the RAM memory map range.

[1541] Control Port RAM data reads or writes to addresses in the range of 0x00 to 0x004? will read or write to the hardware registers in the microcontroller xData space. This read or write of the hardware registers through the Control Port RAM interface is referred to as the ‘Back Door’ method.

[1542] Port P1 is set to 0xFF (output drivers OFF) after the EEPROM code executes. When port P1 is used as an input for the IRQ vector, there will no longer be hardware contention.

[1543] Whenever the firmware is not holding the ISA bus (via IOCHRDY control) it uses Request/Grant to perform SFR codec register access. This is accomplished by two firmware routines: SetREQandWaitForGRANT and ClearREQ. The SetREQandWaitForGRANT routine will Set the REQUEST bit in Port 3 and then poll for the GRANT bit. The routine will return to the caller when the GRANT bit becomes true. When the GRANT bit is true, microcontroller is free to access SFR codec registers without fear of ISA bus contention. The ClearREQ routine should be called after all SFR access is complete. It will clear the REQUEST bit in Port 3 allowing ISA bus activity to proceed.

[1544] The Suspend/Resume feature is used by host APM code (either driver or BIOS) to obtain the state of microcontroller's internal RAM and one SFR (special function register), TCON. When the host issues a Suspend command, microcontroller interrupt is interrupted on INT1. The ISR that runs in this case simply sets a bit (bit 1 of dSuspResmByte) and returns with all microcontroller interrupts disabled. The code returns with microcontroller interrupts disabled so microcontroller state does not change during the suspend processing. When the control returns all the way to the main foreground loop, this bit is checked. If the bit is active, then the internal RAM is copied into external RAM (XRAM). Specifically, internal RAM location x is copied into XRAM location (4000H+0B8H−x) where x goes from 008H to 0B8H. The TCON register is copied to XRAM location 40B1H. This, of course, means that the contents of XRAM locations 4000H-40B1H must be saved before issuing the Suspend command. After the internal RAM is copied, microcontroller interrupts are restored to their state before the Suspend command and microcontroller processing continues as usual. At this time, the XRAM locations into which the microcontroller copied the internal RAM, must be restored. Note that there is no microcontroller idling or powering-down “built into” the Suspend command.

[1545] The Resume command is the inverse of the Suspend command. Host APM code should use the following steps to restore the internal state of microcontroller:

[1546] 1. Save XRAM locations 4000H-40B1H;

[1547] 2. Write microcontroller 103 internal state saved during Suspend to XRAM locations 4000H-40B1H;

[1548] 3. Issue a Resume command; and

[1549] 4. Restore XRAM locations 4000H-40B1H with the data saved in 1.

[1550] Similar to the suspend case, the ISR that runs in the resume case sets a bit (bit 0 of dSuspResmByte) and returns with all microcontroller 103 interrupts disabled. Microcontroller 103 foreground code then copies the data that the host has already written into XRAM into internal RAM.

[1551] Note that the method described above advantageously relieves microcontroller 103 from having to save/restore its stack since the copying of the state is not done until there is nothing on the stack. In other words, there is nothing on the stack when the suspend and resume flags (set in the respective ISR's) are checked.

[1552] FIG. 89 is a diagram of the bitfields of Global Configuration Byte 2 at EEPROM Byte 16, (default=00000000). This byte is a reserved byte in the preferred embodiment. The entire byte is copied to 0x400B on powerup and to X18. The bitfields are defined as follows:

[1553] AUXLR—AUX1 Remap—Switches control of the AUX1 volume control registers from I2/I3 to I18/I19 when set=1;

[1554] 3DEN—When this bit is set to 1, the 3D Audio is enabled and will process any stereo signal output from the Output Mixer;

[1555] DSSEL1—This bit selects the source of digital data for the Delta Sigma DAC (DAC 1). DSSEL1=0 for playback FIFO, DSSEL1=1 for accelerator 139/DSP serial interface;

[1556] ZVEN—ZV port Enable This bit select enables the ZV Port interface. ZVEN=0 for disabled, ZVEN=1 for enabled. When ZVEN=1, then the external wavetable/Firmware input into DAC2 is disabled; and Reserved—These bits are reserved for future use and should be set to zero.

[1557] FIG. 90 is a diagram of the bitfields of DMA C,IRQ G select at EEPROM Byte. This byte in the preferred embodiment was only the DMA C select byte. In the alternate embodiments, this byte additionally defines the IRQ G mapping to PC IRQ number. This byte is copied to 0x4012 on powerup. The bitfields are defined as:

[1558] DMAC[3 . . . 0]—DMA C select—This value determines which HOST PC DMA number the hardware pins for this DMA channel are connected to; and

[1559] IRQG[3 . . . 0]—IRQ G select—This value determines which HOST PC IRQ number the hardware pins for this IRQ channel are connected to.

[1560] The EEPROM TIMING in the alternate embodiments conforms to the following:

[1561] Although the invention has been described with reference to a specific embodiments, these descriptions are not meant to be construed in a limiting sense. Various modifications of the disclosed embodiments, as well as alternative embodiments of the invention will become apparent to persons skilled in the art upon reference to the description of the invention. It is therefore, contemplated that the claims will cover any such modifications or embodiments that fall within the true scope of the invention.