Patent Grant
7134960
The present invention relates to computer graphics, and more particularly to interactive graphics systems such as home video game platforms. Still more particularly, this invention relates to external system interfaces used to connect a graphics system to audio, video, mass media storage device, other storage device, communications, printing and other electronic devices.
Many of us have seen films containing remarkably realistic dinosaurs, aliens, animated toys and other fanciful creatures. Such animations are made possible by computer graphics. Using such techniques, a computer graphics artist can specify how each object should look and how it should change in appearance over time, and a computer then models the objects and displays them on a display such as your television or a computer screen. The computer takes care of performing the many tasks required to make sure that each part of the displayed image is colored and shaped just right based on the position and orientation of each object in a scene, the direction in which light seems to strike each object, the surface texture of each object, and other factors.
Because computer graphics generation is complex, computer-generated three-dimensional graphics just a few years ago were mostly limited to expensive specialized flight simulators, high-end graphics workstations and supercomputers. The public saw some of the images generated by these computer systems in movies and expensive television advertisements, but most of us couldn't actually interact with the computers doing the graphics generation. All this has changed with the availability of relatively inexpensive 3D graphics platforms such as, for example, the Nintendo 64® and various 3D graphics cards now available for personal computers. It is now possible to interact with exciting 3D animations and simulations on relatively inexpensive computer graphics systems in your home or office.
A problem graphics system designers confronted in the past was how to efficiently couple system components together. A modern 3D graphics system is relatively complex, and requires a number of different connections between different aspects of the system. For example, it is often necessary to interface with a mass storage device such as an optical disk. In addition, in an interactive real time system such as a gaming platform, some means must be provided to interface with user-manipulable controls such as hand-held controllers or the like. Sound is typically required, so that interfaces with various sound-producing and sound-supporting components are required. It is also necessary to provide some interfacing means for interfacing the system with a display device of an appropriate configuration. Additionally, it is often desirable to interface the system with a number of other components such as, for example, read only memory, flash memory, various memory cards, modems or other network connections, and debugging facilities for game or other application development. Various solutions to this problem were offered.
One approach would be to use standardized interfaces. Computer equipment manufacturers have developed a number of standardized interfaces in the past to connect with mass storage devices, modems, and other peripheral devices. Using standardized interfaces tends to simplify design efforts and achieve component compatibility and interoperability. The typical personal computer has a number of standardized interfaces so it can be modular and compatible with hardware and peripherals designed by a number of different manufacturers. Designing a new personal computer does not require redesign of all of these interfaces.
While the standardized interface approach has certain advantages in the arena of general purpose computing, it may not be suitable for home video game platforms. Because a home video game system must be manufactured at low cost and yet achieve maximum performance, it is desirable to optimize each and every aspect of the system—including the system interfaces. The interfaces can be looked at as the highways over which information flows throughout the system. This information traffic should flow as rapidly and efficiently as possible. Using standard interfaces may be easier from a design standpoint, but a standardized interface may not provide the high performance that a customized interface might offer. “One size fits all” makes things easier, but doesn't always result in the best possible fit.
Another issue relates to hardware interoperability. Standardized interfaces provide the advantage that no one owns them, and everyone can design components that are compatible with them. For example, when you buy a personal computer having a standardized serial interface, parallel interface and expansion device interface, you know that you can go out and purchase any of a variety of different devices all of which will be compatible with those standardized interfaces. You can plug in any of a dozen different types of printers to either the serial or the parallel interface of your personal computer, and they will all work. Similarly, any of dozens of different modems or other network cards can be plugged into the PCMCIA card slot of a personal computer or laptop, and all of these different cards will work.
Open standards have the advantage that they achieve hardware interoperability between systems and a wide range of different accessories. This approach is helpful when the system manufacturer is selling a general purpose device that can be used for virtually any application, but makes less sense in the home video game arena where a given video game manufacturer is responsible for making or licensing all of the various special-purpose accessories for its brand of home video game platform.
For example, video game manufacturers in the past have expended substantial time, effort and resources to develop definitive new home video game platforms. They want to sell as many of these as possible, and therefore price them very competitively. Like the razor manufacturer who recoups his investment by selling razor blades as opposed to the razor itself, video game platform manufacturers rely on controlling access to the installed user base of home video game systems to achieve profits through licensing. If the home video game platform used open standards, then competing manufacturing could bypass the company that invested all the time, effort and resources to develop the platform to begin with, and could instead market directly to consumers. Accordingly, under this business model, it is important for the platform manufacturer to be able to control access to the platform.
One technique used successfully in the past to control access to home video game platforms was to incorporate security systems that control access to the platform. A security system can enable the platform to accept or reject things plugged into it. As one example, it is possible to include an integrated circuit chip authentication type device in home video game cartridges. Before the home video game platform interoperates with the cartridge or other accessory, it may first authenticate the cartridge or other accessory by use of the security chip. While this approach can be highly successful, it requires each accessory to include authentication type information and/or devices. This increases cost. In addition, no security system is impenetrable. Given enough time, effort and resources, any security system can be “cracked” to unlock access to the platform. Thus, further improvements are desirable.
The present invention provides an approach to solving these problems. It provides a variety of proprietary system interfaces that have been optimized to maximize system performance. Because these optimized system interfaces are non-standard and unusual, they provide uniqueness that can be used as a basis for excluding unlicensed and unauthorized people from manufacturing components that are compatible with the interfaces. This allows a home video game platform developer to protect its substantial investment in the development of the platform.
One aspect of the present invention provides a proprietary disk interface for mass storage devices such as optical disks. The disk interface can be used to interface with an optical disk drive using direct memory access with interrupt. The disk interface acts as a transport for command packets sent between a disk drive and a graphics and audio coprocessor. The interface need not interpret the packets. The disk interface provides a number of signal lines including a parallel data bus and various additional signaling lines to provide high speed data transfer and efficiently coordinate operations between the disk drive and the rest of the system.
Another aspect provided by this invention is a serial interface for interfacing an audio and graphics coprocessor with a variety of different types of accessory devices including but not limited to hand-held game controllers. The serial interface provides a single bit serial interface using a state-based interface protocol. The interface supports four separate serial interfaces to four hand-held controllers or associated devices. Each interface can be accessed in parallel. In a controller mode, the last state of the controller is stored in a double-buffered register to support simple main processor reads for determining state. The example embodiment automatically polls controller state using hardware circuitry with configurable polling periods. A bulk mode supports changeable data size. A pair of light gun signals can be used to control separate horizontal/vertical counters to support flash and shutter light guns. An LCD shutter can be supported through automatic polling and a serial control command. The system interface includes automatic control of presence detect to save effort on the part of the main processor.
In accordance with another aspect of this invention, an external accessory device interface(s) is provided for interfacing with a variety of different types of external devices such as, for example, read only memory, flash memory, memory cards, modems, debugging systems or a variety of other devices. The external interface provided in accordance with this invention can be used, for example, to interface with a single chip boot ROM and associated real time clock, as well as to on-board flash memory, an external modem, an external memory card, debugger hardware, or other external devices including but not limited to a voice recognition device. A preferred external interface provides four separate external interface channels. A channel 0 supports both expansion and on-board devices. The entire ROM is memory mapped onto the external interface, and ROM reads can be controlled entirely by hardware for boot support. Separate external interface chip selects can be used to control many different devices (e.g., ROM/RTC, flash memory, expansion modem, expansion backup memory card, debug, etc.). Maskable external interrupts can also be provided—one for each external expansion port. Maskable interrupts may provide transfer complete signaling for each channel. A pair of maskable interrupts can be provided for hot-plug status to detect insertion and removal of external devices. Direct memory access can be used to support general transfers on each channel.
In accordance with yet another aspect provided by this invention, an audio interface provides support for audio functions within a graphics system. The audio/video interface can provide support for an external digital-to-analog converter providing, for example, composite video and 16-bit stereo sound running at a desired sampling rate (e.g., fixed 48 kHz). The interface may also provide an interface for a digital audio and video output and/or input. The collection of audio interfaces may also include a mass storage device streaming audio input interface via, for example, a 16-bit serial bit interface running at a predetermined sampling rate (e.g., 32 kHz or 48 kHz). The sample rate conversion of mass storage device streaming audio can be provided “on the fly.” The collection of audio interfaces may also include an audio mixer interface for mixing two audio streams into a final output stream. The audio mixer interface can provide audio volume control, for example, for mixing the mass storage device streaming audio output with audio generated using an internal digital signal processor.
In accordance with yet another aspect of this invention, a video interface provides efficient interfacing between a graphics processor and an external video encoder. The video interface does much of the work required so as to reduce the amount of work the external encoder needs to perform. The video interface also provides a number of interesting additional features such as panning, windowing, light gun support, and color format conversion.
These and other features and advantages provided by the invention will be better and more completely understood by referring to the following detailed description of presently preferred embodiments in conjunction with the drawings, of which:
In this example, system 50 is capable of processing, interactively in real time, a digital representation or model of a three-dimensional world. System 50 can display some or all of the world from any arbitrary viewpoint. For example, system 50 can interactively change the viewpoint in response to real time inputs from handheld controllers 52a, 52b or other input devices. This allows the game player to see the world through the eyes of someone within or outside of the world. System 50 can be used for applications that do not require real time 3D interactive display (e.g., 2D display generation and/or non-interactive display), but the capability of displaying quality 3D images very quickly can be used to create very realistic and exciting game play or other graphical interactions.
To play a video game or other application using system 50, the user first connects a main unit 54 to his or her color television set 56 or other display device by connecting a cable 58 between the two. Main unit 54 produces both video signals and audio signals for controlling color television set 56. The video signals are what control the images displayed on the television screen 59, and the audio signals are played back as sound through television stereo loudspeakers 61L, 61R.
The user also needs to connect main unit 54 to a power source. This power source may be a conventional AC adapter (not shown) that plugs into a standard home electrical wall socket and converts the house current into a lower DC voltage signal suitable for powering the main unit 54. Batteries could be used in other implementations.
The user may use hand controllers 52a, 52b to control main unit 54. Controls 60 can be used, for example, to specify the direction (up or down, left or right, closer or further away) that a character displayed on television 56 should move within a 3D world. Controls 60 also provide input for other applications (e.g., menu selection, pointer/cursor control, etc.). Controllers 52 can take a variety of forms. In this example, controllers 52 shown each include controls 60 such as joysticks, push buttons and/or directional switches. Controllers 52 may be connected to main unit 54 by cables or wirelessly via electromagnetic (e.g., radio or infrared) waves.
To play an application such as a game, the user selects an appropriate storage medium 62 storing the video game or other application he or she wants to play, and inserts that storage medium into a slot 64 in main unit 54. Storage medium 62 may, for example, be a specially encoded and/or encrypted optical and/or magnetic disk. The user may operate a power switch 66 to turn on main unit 54 and cause the main unit to begin running the video game or other application based on the software stored in the storage medium 62. The user may operate controllers 52 to provide inputs to main unit 54. For example, operating a control 60 may cause the game or other application to start. Moving other controls 60 can cause animated characters to move in different directions or change the user's point of view in a 3D world. Depending upon the particular software stored within the storage medium 62, the various controls 60 on the controller 52 can perform different functions at different times.
Example Electronics of Overall System
In this example, main processor 110 (e.g., an enhanced IBM Power PC 750) receives inputs from handheld controllers 52 (and/or other input devices) via graphics and audio processor 114. Main processor 110 interactively responds to user inputs, and executes a video game or other program supplied, for example, by external storage media 62 via a mass storage access device 106 such as an optical disk drive. As one example, in the context of video game play, main processor 110 can perform collision detection and animation processing in addition to a variety of interactive and control functions.
In this example, main processor 110 generates 3D graphics and audio commands and sends them to graphics and audio processor 114. The graphics and audio processor 114 processes these commands to generate interesting visual images on display 59 and interesting stereo sound on stereo loudspeakers 61R, 61L or other suitable sound-generating devices.
Example system 50 includes a video encoder 120 that receives image signals from graphics and audio processor 114 and converts the image signals into analog and/or digital video signals suitable for display on a standard display device such as a computer monitor or home color television set 56. System 100 also includes an audio codec (compressor/decompressor) 122 that compresses and decompresses digitized audio signals and may also convert between digital and analog audio signaling formats as needed. Audio codec 122 can receive audio inputs via a buffer 124 and provide them to graphics and audio processor 114 for processing (e.g., mixing with other audio signals the processor generates and/or receives via a streaming audio output of mass storage access device 106). Graphics and audio processor 114 in this example can store audio related information in an audio memory 126 that is available for audio tasks. Graphics and audio processor 114 provides the resulting audio output signals to audio codec 122 for decompression and conversion to analog signals (e.g., via buffer amplifiers 128L, 128R) so they can be reproduced by loudspeakers 61L, 61R.
Graphics and audio processor 114 has the ability to communicate with various additional devices that may be present within system 100. For example, a parallel digital bus 130 may be used to communicate with mass storage access device 106 and/or other components. A serial peripheral bus 132 may communicate with a variety of peripheral or other devices including, for example:
3D graphics processor 154 performs graphics processing tasks. Audio digital signal processor 156 performs audio processing tasks. Display controller 164 accesses image information from main memory 112 and provides it to video encoder 120 for display on display device 56. Audio interface and mixer 1300 interfaces with audio codec 122, and can also mix audio from different sources (e.g., streaming audio from mass storage access device 106, the output of audio DSP 156, and external audio input received via audio codec 122). Processor interface 150 provides a data and control interface between main processor 110 and graphics and audio processor 114.
Memory interface 152 provides a data and control interface between graphics and audio processor 114 and memory 112. In this example, main processor 110 accesses main memory 112 via processor interface 150 and memory interface 152 that are part of graphics and audio processor 114. Peripheral controller 162 provides a data and control interface between graphics and audio processor 114 and the various peripherals mentioned above. Audio memory interface 158 provides an interface with audio memory 126.
Example Graphics Pipeline
Command processor 200 receives display commands from main processor 110 and parses them—obtaining any additional data necessary to process them from shared memory 112. The command processor 200 provides a stream of vertex commands to graphics pipeline 180 for 2D and/or 3D processing and rendering. Graphics pipeline 180 generates images based on these commands. The resulting image information may be transferred to main memory 112 for access by display controller/video interface unit 164—which displays the frame buffer output of pipeline 180 on display 56.
Command processor 200 performs command processing operations 200a that convert attribute types to floating point format, and pass the resulting complete vertex polygon data to graphics pipeline 180 for rendering/rasterization. A programmable memory arbitration circuitry 130 (see
Transform unit 300 performs a variety of 2D and 3D transform and other operations 300a (see
Setup/rasterizer 400 includes a setup unit which receives vertex data from transform unit 300 and sends triangle setup information to one or more rasterizer units (400b) performing edge rasterization, texture coordinate rasterization and color rasterization.
Texture unit 500 (which may include an on-chip texture memory (TMEM) 502) performs various tasks related to texturing including for example:
Texture unit 500 outputs filtered texture values to the texture environment unit 600 for texture environment processing (600a). Texture environment unit 600 blends polygon and texture color/alpha/depth, and can also perform texture fog processing (600b) to achieve inverse range based fog effects. Texture environment unit 600 can provide multiple stages to perform a variety of other interesting environment-related functions based for example on color/alpha modulation, embossing, detail texturing, texture swapping, clamping, and depth blending.
Pixel engine 700 performs depth (z) compare (700a) and pixel blending (700b). In this example, pixel engine 700 stores data into an embedded (on-chip) frame buffer memory 702. Graphics pipeline 180 may include one or more embedded DRAM memories 702 to store frame buffer and/or texture information locally. Z compares 700a′ can also be performed at an earlier stage in the graphics pipeline 180 depending on the rendering mode currently in effect (e.g., z compares can be performed earlier if alpha blending is not required). The pixel engine 700 includes a copy operation 700c that periodically writes on-chip frame buffer 702 to memory portion 113 of main memory 112 for access by display/video interface unit 164. This copy operation 700c can also be used to copy embedded frame buffer 702 contents to textures in the main memory 112 for dynamic texture synthesis effects. Anti-aliasing and other filtering can be performed during the copy-out operation. The frame buffer output of graphics pipeline 180 (which is ultimately stored in main memory 112) is read each frame by display/video interface unit 164. Display controller/video interface 164 provides digital RGB pixel values for display on display 56.
Example Input/Output Subsystem
In the example embodiment, the external interface 1100 and disk interface 1200 have direct access to memory controller 152 via a bus 900. Details of the operation of memory controller 152 may be found in application Ser. No. 09/726,220, filed Nov. 28, 2000 entitled “Graphics Processing System with Enhanced Memory Controller” and application Ser. No. 09/722,665, filed Nov. 28, 2000 entitled “Method and Apparatus for Accessing Shared Resources.” The contents of each of these applications are incorporated herein by reference. In addition, each one of interfaces 1000, 1100, 1200 and 1300 as well as audio digital signal processor 156 share a common bus 902 used to communicate between these components and a bus interface 904. The bus interface 904, in turn, can be used to arbitrate access to graphics unit 180 including embedded DRAM 702. In the example embodiment, there is also a connection 906 between DSP 156 and audio interface 1300.
Briefly, disk interface 1200 provides an interface to mass storage access device 106 providing a direct memory access capability with interrupt. Serial interface 1000 provides a serial interface to hand controllers 52 or other serial devices using automatic controller polling and bulk data mode including a light gun interface. The external interface 1100 provides multiple serial peripheral interface (SPI) buses as well as a memory mapped area for boot PROM 134. Audio interface 1300 provides an output to audio codec 122 as well as an input for streaming audio from mass storage access device 106. These various interfaces 1000, 1100, 1200, 1300 provide a shared memory port for direct memory access, with round robin arbitration for access to main memory.
Example Disk Interface
In the example embodiment, disk interface 1200 works primarily on a command packet and direct memory access basis. The disk interface 1200 operates as a transport for command packets sent to mass storage access device 106, and does not actually interpret the packets themselves. Operating on a packet basis allows the development of packet commands and the mechanism for mass storage access device 106 to be completed separately from the development of the actual physical interface provided by disk interface 1200.
Disk interface 1200 distinguishes between packets that comprise direct memory access commands and packets that comprise immediate commands. Direct memory access commands in the example embodiment begin with a command packet and then cause data to be sent to/from main memory 112 using direct memory access under control of direct memory access controller 1216. Immediate commands in the example embodiment begin with a command packet and result in data being transferred to/from the disk interface immediate data buffer 1212. Disk interface 1200 in the example embodiment includes the following features:
As shown in
The following describes the various signals:
The following sets forth definitions of example disk interface registers shown in
Example Serial Interface
This register is double buffered, so main processor writes to the SIC0OUTBUF will not interfere with the serial interface output transfer. Internally, a second buffer is used to hold the output data to be transferred across the serial interface. To check if SIC0OUTBUF has been transferred to the second buffer, main processor 110 polls the SISR[WRST0] register. When SIC0OUTBUF is transferred, SISR[WRST0] is cleared.
SIC0INBUFH and SIC0INBUFL are double buffered to prevent inconsistent data reads due to main processor 110 conflicting with incoming serial interface data. To insure data read from SIC0INBUFH and SIC0INFUBL are consistent, a locking mechanism prevents the double buffer from copying new data to these registers. Once SIC0INBUFH is read, both SIC0INBUFH and SIC0INBUFL are ‘locked’ until SIC0INBUFL is read. While the buffers are ‘locked’, new data is not copied into the buffers. When SIC0INBUFL is read, the buffers become unlocked again.
When programming the SICOMCSR after a SICOM transfers has already started (e.g., SICOMCSR[TSTART] is set), the example software reads the current value first, then and/or in the proper data and then write the new data back. The software should not modify any of the transfer parameters (OUTLNGTH, INLNGTH, CHANNEL) until the current transfer is complete. This is done to prevent a SICOM transfer already in progress from being disturbed. When writing the data back, the software should not set the TSTART bit again unless the current transfer is complete and another transfer is required.
Additional details of the serial interface may be found in application Ser. No. 09/722,664, filed Nov. 28, 2000 of Shimuzu et al. entitled “Controller Interface for a Graphics System”, the contents of which are incorporated herein by reference.
Example External Interfaces
The external interface 1100 in the example embodiment was chosen based on current support by several manufacturers (e.g., Macronix) for the EXI interface on Macronix's CMOS serial flash EEPROM parts. The implemented EXI protocol is based on and compatible with MXIC's MX25L4004 EXI interface. The preferred embodiment example external interface 1100 includes five separate chip select signals to control five different devices (e.g., ROM/RTC 134, flash memory 140, expansion modem 136, expansion backup memory card 144, etc.). Different implementations could provide different numbers of chip selects. The example embodiment external interface 1100 includes three maskable external interrupts (one for each expansion port/channel 1102) that are used to signal EXI transfer complete for each channel. An additional pair of maskable interrupts provided by channels 1102(0) and 1102(1) is used to provide hot-plug status for peripheral insertion and removal. Each of channels 1102 support general DMA (direct memory access) transfers in the example embodiment.
Referring to
Block diagrams for the example external channel one interface 1100(1) and example external channel two interface 1100(2) are shown in
The following table sets forth the various signal descriptions for the signals provided to/from example external interface ports 1102:
Serial Peripheral Interface
In one embodiment, main processor 110 can set the clock rates of these EXI channels to 32 MHz, 16 Mhz, 8 MHz, 4 MHz, 2 MHz and 1 MHz and these clocks rates may be set independently for the different channels. Chip select registers are used to identify the device to which the EXI bus is connected. For the example EXI0, CS0 (Chip Select 0) is set for a connection to an internal real time clock, CS1 is set for a connection to an internal IPL_ROM, and CS2 is set for an external device (modem, voice recognition system and the like). For the example EXI1, CS0 is set for a connection to an internal flash ROM and CS1 is set for an external device (modem, voice recognition system, and the like). Other configurations are possible.
Small size data as command is transferred between CPU registers immediately and large size data is transferred between main memory by direct memory access (DMA).
Example Audio Interfaces
The example embodiment audio interfaces 1300 provide support for external 16-bit stereo digital-to-analog converter interfaces running at a fixed 48 kHz sampling rate. The disk serial interface 1302 provides an optical disk streaming audio input interface providing 16-bit serial interface running at 32 kHz or 48 kHz sampling rate. This allows audio mixer 160 to mix the streaming audio input at programmable audio volume control. Disk serial interface 1302 provides sample rate conversion “on the fly” to, for example, change from a 32 kHz sampling rate provided by the mass storage access device 106 to a 48 kHz sampling rate.
The following are example signal definitions for the various signals shown in
Example Video Interface
Video interface 164 in the example embodiment reads color information stored in main memory 112 and sends it to display 56. In more detail, the example video interface 164 has the following functions:
Main processor 110 can write instructions to video interface 164 via a register interface. Video interface 164 can access main memory external frame buffer 113 via the graphics memory request arbitration 130. Additionally, video interface 164 provides an output to an external video encoder comprising three sets of signals:
Because the example embodiment clamps Y to 0×10 during active display, Y is set to 0×00 during the vertical blanking interval. During that time, CbCr are used for outputting video timing signals that may be encoded as follows:
Because the timing signals are output in the Cb and Cr data only in the example embodiment, they should be expanded back to 13.5 MHz inside of the video encoder. As a result, horizontal sync and burst may be shifted by one pixel. An example timing diagram is shown in
In the example embodiment, vertical blanking can end on an even pixel (HBE is even), or it can end on an odd pixel (HBE is odd). In cases where HBE is even, the first chroma sample will be Cb followed by Cr, etc. In cases where HBE is odd, the first chroma sample will be Cr followed by Cb, etc. The diagram of
The video interface 164 also includes a gun trigger interface consisting of two pins. Each pin detects the instance of a screen flash when a light gun trigger is pulled. Latch circuitry is used to mark the value of a screen timer when a screen flash is registered.
In the example embodiment, in order to simplify the external video encoder, the video interface 164 generates most of the video timing required by the encoder. Video interface 164 supports the timing of NTSC, PAL and M-PAL. In the example embodiment, video interface 164 displays the top field only in a non-interlace mode. Video interface 164 includes a timing generator responsible for generating video timing, control signals and interrupts. Basically this timing generator consists of two counters: a vertical line counter and a horizontal pixel counter. Once enabled, these counters run continuously at a pixel clock rate of, e.g., 27 MHz. A programmable decoder decodes the outputs of these counters. The decoder operates in four modes: NTSC, PAL, M-PAL, and debug mode. The debug mode is used for testing and simulation.
Video interface 164 generates addresses required to access pixel data from external frame buffer 113. It supports various addressing features including programmable picture size, windowing and pixel resolution pan and scan.
Video interface 164 also supports horizontal scaling such that a smaller frame buffer can be stretched horizontally to the desired display size. This is achieved by using a 6-tap sampling filter. Each filter tap has eight phases and a zero tap is added to have a total of forty-nine taps in the example embodiment. An output pixel is sampled to a 1/256 sub-pixel grid and is rounded to the nearest ⅛ sub-pixel in the example embodiment. This results in scan line being sampled up to eight times before it is down sampled to a target frequency. See example
The Y, Cr and Cb components are buffered in three separate shift registers in the example embodiment. Each register is responsible for replicating the first and last pixels for filtering at the boundaries. To ease implementation, Cb and Cr pixels are averaged to 4:4:4 before filtering. This prevents chroma words from reading ahead of luma words. It also allows luma and chroma to share the same control logic.
An internal stepper controls new sample position. The stepper is incremented by a step size every output pixel. The lowest eight bits of the stepper in the example embodiment are rounded to three bits for determining the phase of the filter. Only one bit to the left of the binary pointer is kept. If that bit is toggled, a new pixel is shifted into the pixel registers. The step size in the example embodiment for the stepper is determined by:
step size=floor (256×destination size/source size)/256.
The step size and the filter coefficients are set up through the video interface 164 register interface in the example embodiment. The filter can be programmed to have different cut off frequencies, passband ripple and stopband attenuation. As the filter is symmetrical, only half of it is programmed. To conserve hardware in the filter, the filter coefficients are enveloped so that the center sixteen coefficients are in the range [0,2.0]. The outer 32 coefficients are in the range [−0.125, 0.125]. Eight times up-sampling is equivalent to a 0.5 Hz lowpass filter at an 8 Hz sampling rate. A conventional SINC filtering function can be used for windowing in the example embodiment.
Video interface 164 can support a 3D liquid crystal display by merging two frame buffer images (left and right) into a single stream of video. The output interleaves between the left and right pictures every two pixels.
The example embodiment video interface 164 provides a gun trigger control supporting three sampling modes: 1-field (gun trigger is sampled for one field), 2-field (gun trigger is sampled for two fields), and continuous. In the ½-field mode, the detection mechanism includes the event sequence shown in
In the example embodiment, the first gun trigger in a field latches the value of the display counters and gun triggers occurring in the remainder of the field are ignored.
The following tables describe various control registers within example video interface 164. The fourth column in each table shows the power-up reset values.
Display Configuration Register (R/W)
This register set ups and enables VI. Generally, VI should be reset before enabling it. This resets the states into some known values.
Horizontal Timing 0 Register (R/W)
This register setups the horizontal timing.
Horizontal Timing 1 Register (R/W)
This register setups the horizontal timing.
Vertical Timing Register (R/W)
This register setups the vertical timing. The value ACV is double buffered
Odd Field Vertical Timing Register (R/W)
This register sets up the pre-blanking and post-blanking intervals of odd fields. The values PRB and PSB are double buffered.
Even Field Vertical Timing Register (R/W)
This register sets up the pre-blanking and post-blanking intervals of even fields. The values PRB and PSB are double buffered.
Odd Field Burst Blanking Interval Register (R/W)
This register sets up the burst blanking interval of odd fields.
Even Field Burst Blanking Interval Register (R/W)
This register sets up the burst-blanking interval of even fields.
Top Field Base Register L (R/W)
This register specifies the display origin of the top field of a picture in 2D display mode or for the left picture in 3D display mode.
Top Field Base Register R (R/W)
This register specifies the base address of the top field for the right picture in the 3D display mode. It is not used in 2D display mode.
Bottom Field Base Register L (R/W)
This register specifies the display origin of the bottom field of a picture in 2D display mode or for the left picture in 3D display mode.
Bottom Field Base Register R(R/W)
This register specifies the base address of the bottom field for the right picture in the 3D display mode. It is not used in 2D display mode.
Picture Configuration Register (R/W)
This register specifies the picture configuration.
Display Position Register (R)
This register contains the current raster position.
The Horizontal Count is in pixels and runs from 1 to # pixels per line. It is reset to 1 at the beginning of every line.
The Vertical Count is in lines (on a frame basis) and runs from 1 to # lines per frame. It is 1 at the beginning of pre-equalization. This is a frame line count. So for example: for NTSC vcount=264 is the first (full) line in the second field and vcount=525 is the last line in the frame (fields being numbered 1–4). For non-interlaced modes vcount is on a field-by-field basis (for NTSC vcount ranges from 1–263).
This counting scheme applies the Display Postion, Display Interrupt, and Display Latch registers.
Display Interrupt Register 0 (R/W)
There are a total of four display interrupt registers (0–3). They are used to generate interrupts to the main processor at different positions within a field. Each register has a separate enable bit. The interrupt is cleared by writing a zero to the status flag (INT).
Display Interrupt Register 1 (R/W)
See the description of Display Interrupt Register 0.
Display Interrupt Register 2 (R/W)
See the description of Display Interrupt Register 0.
Display Interrupt Register 3 (R/W)
See the description of Display Interrupt Register 0.
Display Latch Register 0 (R/W)
The Display Latch Register 0 latches the value of the Display Position Register at the rising edge of the gt0 signal. The trigger flag is set if a gun trigger is detected. Writing a zero to the register clear the trigger flag.
Display Latch Register 1 (R/W)
See the description of Display Latch Register 0. This register is latched on the rising edge of the gt1 signal.
Output Polarity Register (R/W)
This register sets up the polarity of the out going control signals
Horizontal Scale Register (R/W)
This register sets up the step size of the horizontal stepper.
Scaling Width Register (R/W)
This register is the number of source pixels to be scaled. This is only used when the Horizontal Scaler is enabled. For example, if the image is to be scaled from 320×240 to 640×240, 320 would be written into this register.
Border HBE (R/W)
This register (in conjunction with the border HBS) sets up a black border around the actual active pixels in debug mode. This was done in order to accommodate certain encoders that only support 720 active pixels. The border HBE and HBS can be programmed for 720 active pixels while the regular HBE and HBS can be programmed to the actual active width. This allows the frame buffer to be of any width without having to manually set up a border in memory. These registers will only take effect if enabled and in debug mode.
Border HBS (R/W)
Filter Coefficient Table 0 (R/W)
This register sets up part of the low pass filter. Taps 0 to 9 are in the reange [0.0, 2.0).
Filter Coefficient Table 1 (R/W)
This register sets up part of the low pass filter.
Filter Coefficient Table 2 (R/W)
This regisster sets up part of the low pass filter.
Filter Coefficient Table 3 (R/W)
This register sets up part of the low pass filter. Taps 9 to tap 24 are in the range [−0.125, 0.125).
Filter Coefficient Table 4 (R/W)
This register sets up part of the low pass filter.
Filter Coefficient Table 5 (R/W)
This register sets up part of the low pass filter.
Filter Coefficient Table 6 (R/W)
This register sets up part of the low pass filter.
VI Clock Select Register (R/W)
This register selects whether the VI will receive a 27 Mhz or a 54 Mhz clock. The 54 Mhz clock is used only with the progressive display modes.
VI DTV Status Register (R)
This register allows software to read the status of two I/O pins.
Example Detailed Overall System Embodiment/Implementation
In the example shown, each of connectors 1510, 1514, 1516, 1518, 1520, 1523a–1523d, 1549, 1550, 1552, 1521 comprises a mating male and female multi-pin connector that allows connections to be made, broken and remade without destructive or permanent processes such as soldering or permanent (non-deformable) crimping. Use of such connectors allows simple and easy connection and disconnection between different modular portions of system 50 to provide an east-to-manufacture system that can also be expanded, extended and reconfigured in the field without special equipment and involved processes.
Skipping ahead to
Referring now more particularly to
Referring to
Referring to
Any of the various connectors described herein can be located in the various connector positions shown in
Example Detailed Connection Diagram
As also shown in
As shown in
Example Detailed Serial (Joybus) Hand Controller Connections
b show an example detailed implementation of a connection between an example serial connector 1510 and the graphics and audio processor 114, and
Example External Interface Connections
The connector arrangements shown in
Example Modem Connection
In the example embodiment, system 50 further includes a modem connector 1514 intended to be coupled directly to an internal and/or external modem of conventional design. In the example embodiment, an additional (fourth) external interface bus and associated external interface is provided by graphics and audio processor 114 for communicating with a modem via connector 1514. Devices other than a modem may also be coupled to the modem connector 1514. In the example embodiment, this modem bus is bidirectional with three lines (EXID00, EXI0CLK0 and EXICSB2) being uni-directionally buffered as outputs to the modem connector 1514 and a further line EXI0D10 being uni-directionally buffered as an input to the graphics and audio processor 114. In the example embodiment, the uni-directional buffer provided on the EXID10 line is controlled by the graphics and audio processor 114 via the EXI0CSB2 line (the latter line of which is also passed on as a signal to connector 1514). The other buffers in the example embodiment are controlled by an EXTIN signal asserted by a device coupled to the modem connector 1514. Modem connector 1514 may provide the following example pin assignments for a 12-pin connector:
As shown in
Example External Digital Video/Audio Connections
The digital video/audio connector 1552 shown in
Example SDRAM Expansion
Example Disk Interface Connector
Example Power Supply Connector
In the example embodiment, system 50 may also include a power supply connector 1700 used to connect power to power all of the components within the system. An example power supply connector is shown in
In the example embodiment, a temperature compensation chip 1702 is connected to connector 17 pin 19.
Other Example Compatible Implementations
Certain of the above-described system components 50 could be implemented as other than the home video game console configuration described above. For example, one could run graphics application or other software written for system 50 on a platform with a different configuration that emulates system 50 or is otherwise compatible with it. If the other platform can successfully emulate, simulate and/or provide some or all of the hardware and software resources of system 50, then the other platform will be able to successfully execute the software.
As one example, an emulator may provide a hardware and/or software configuration (platform) that is different from the hardware and/or software configuration (platform) of system 50. The emulator system might include software and/or hardware components that emulate or simulate some or all of hardware and/or software components of the system for which the application software was written. For example, the emulator system could comprise a general purpose digital computer such as a personal computer, which executes a software emulator program that simulates the hardware and/or firmware of system 50.
Some general purpose digital computers (e.g., IBM or MacIntosh personal computers and compatibles) are now equipped with 3D graphics cards that provide 3D graphics pipelines compliant with DirectX or other standard 3D graphics command APIs. They may also be equipped with stereophonic sound cards that provide high quality stereophonic sound based on a standard set of sound commands. Such multimedia-hardware-equipped personal computers running emulator software may have sufficient performance to approximate the graphics and sound performance of system 50. Emulator software controls the hardware resources on the personal computer platform to simulate the processing, 3D graphics, sound, peripheral and other capabilities of the home video game console platform for which the game programmer wrote the game software.
As one example, in the case where the software is written for execution on a platform using an IBM PowerPC or other specific processor and the host 1201 is a personal computer using a different (e.g., Intel) processor, emulator 1203 fetches one or a sequence of binary-image program instructions from storage medium 1305 and converts these program instructions to one or more equivalent Intel binary-image program instructions. The emulator 1203 also fetches and/or generates graphics commands and audio commands intended for processing by the graphics and audio processor 114, and converts these commands into a format or formats that can be processed by hardware and/or software graphics and audio processing resources available on host 1201. As one example, emulator 1303 may convert these commands into commands that can be processed by specific graphics and/or or sound hardware of the host 1201 (e.g., using standard DirectX, OpenGL and/or sound APIs).
An emulator 1303 used to provide some or all of the features of the video game system described above may also be provided with a graphic user interface (GUI) that simplifies or automates the selection of various options and screen modes for games run using the emulator. In one example, such an emulator 1303 may further include enhanced functionality as compared with the host platform for which the software was originally intended.
A number of program modules including emulator 1303 may be stored on the hard disk 1211, removable magnetic disk 1215, optical disk 1219 and/or the ROM 1252 and/or the RAM 1254 of system memory 1205. Such program modules may include an operating system providing graphics and sound APIs, one or more application programs, other program modules, program data and game data. A user may enter commands and information into personal computer system 1201 through input devices such as a keyboard 1227, pointing device 1229, microphones, joysticks, game controllers, satellite dishes, scanners, or the like. These and other input devices can be connected to processing unit 1203 through a serial port interface 1231 that is coupled to system bus 1207, but may be connected by other interfaces, such as a parallel port, game port Fire wire bus or a universal serial bus (USB). A monitor 1233 or other type of display device is also connected to system bus 1207 via an interface, such as a video adapter 1235.
System 1201 may also include a modem 1154 or other network interface means for establishing communications over a network 1152 such as the Internet. Modem 1154, which may be internal or external, is connected to system bus 123 via serial port interface 1231. A network interface 1156 may also be provided for allowing system 1201 to communicate with a remote computing device 1150 (e.g., another system 1201) via a local area network 1158 (or such communication may be via wide area network 1152 or other communications path such as dial-up or other communications means). System 1201 will typically include other peripheral output devices, such as printers and other standard peripheral devices.
In one example, video adapter 1235 may include a 3D graphics pipeline chip set providing fast 3D graphics rendering in response to 3D graphics commands issued based on a standard 3D graphics application programmer interface such as Microsoft's DirectX 7.0 or other version. A set of stereo loudspeakers 1237 is also connected to system bus 1207 via a sound generating interface such as a conventional “sound card” providing hardware and embedded software support for generating high quality stereophonic sound based on sound commands provided by bus 1207. These hardware capabilities allow system 1201 to provide sufficient graphics and sound speed performance to play software stored in storage medium 1305.
While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements.
This application is a continuation of application Ser. No. 09/723,335, filed Nov. 28, 2000, now U.S. Pat. No. 6,609,977 which claims the benefit of provisional Application No. 60/226,884, filed Aug. 23, 2000. This application is related to the following applications identified below, each of which is hereby incorporated herein by reference: U.S. application Ser. No. 09/722,664 filed Nov. 28, 2000 of Shimuzu et al., entitled “Controller Interface For A Graphics System” which claims priority from provisional application No. 60/226,885 filed Aug. 23, 2000;U.S. application Ser. No. 09/723,336 filed Nov. 28, 2000 of Parikh et al. entitled “Application Program Interface for a Graphics System”, now U.S. Pat. No. 6,452,600; andDesign application Serial No. 29/128,262 filed Jul. 31, 2000 of Ashida entitled “Video Game Machine”, now D453,800.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3369177 | Graham et al. | Feb 1968 | A |
| 4167019 | Shepperd | Sep 1979 | A |
| 4278972 | Wozniak | Jul 1981 | A |
| 4296476 | Mayer et al. | Oct 1981 | A |
| 4324401 | Stubben et al. | Apr 1982 | A |
| 4388620 | Sherman | Jun 1983 | A |
| 4407298 | Lentz et al. | Oct 1983 | A |
| 4425559 | Sherman | Jan 1984 | A |
| 4454594 | Heffron et al. | Jun 1984 | A |
| 4462076 | Smith, III | Jul 1984 | A |
| 4562308 | Kopetzky et al. | Dec 1985 | A |
| 4567516 | Scherer et al. | Jan 1986 | A |
| 4570233 | Yan et al. | Feb 1986 | A |
| 4589089 | Frederiksen | May 1986 | A |
| 4592012 | Braun | May 1986 | A |
| 4658247 | Gharachorloo | Apr 1987 | A |
| 4725831 | Coleman | Feb 1988 | A |
| 4799635 | Nakagawa | Jan 1989 | A |
| 4829295 | Hiroyuki | May 1989 | A |
| 4837488 | Donahue | Jun 1989 | A |
| 4850591 | Takezawa et al. | Jul 1989 | A |
| 4862392 | Steiner | Aug 1989 | A |
| 4866637 | Gonzalez-Lopez et al. | Sep 1989 | A |
| 4901064 | Deering | Feb 1990 | A |
| 4914729 | Omori et al. | Apr 1990 | A |
| 4945500 | Deering | Jul 1990 | A |
| 4972470 | Farago | Nov 1990 | A |
| 4976429 | Nagel | Dec 1990 | A |
| 5004232 | Wong et al. | Apr 1991 | A |
| 5049863 | Oka | Sep 1991 | A |
| 5050041 | Shafi | Sep 1991 | A |
| 5091832 | Tortola et al. | Feb 1992 | A |
| 5136664 | Bersack et al. | Aug 1992 | A |
| 5155768 | Matsuhara | Oct 1992 | A |
| 5170468 | Shah et al. | Dec 1992 | A |
| RE34161 | Nakagawa et al. | Jan 1993 | E |
| 5213327 | Kitaue | May 1993 | A |
| 5230059 | Nielsen et al. | Jul 1993 | A |
| 5239540 | Rovira et al. | Aug 1993 | A |
| 5245320 | Bouton | Sep 1993 | A |
| 5268669 | Roskowski | Dec 1993 | A |
| 5389006 | Noschese | Feb 1995 | A |
| 5392385 | Evangelisti et al. | Feb 1995 | A |
| 5392393 | Deering | Feb 1995 | A |
| 5421028 | Swanson | May 1995 | A |
| 5421590 | Robbins | Jun 1995 | A |
| 5428355 | Jondrow et al. | Jun 1995 | A |
| 5457775 | Johnson, Jr. et al. | Oct 1995 | A |
| 5504917 | Austin | Apr 1996 | A |
| 5509811 | Homic | Apr 1996 | A |
| 5513302 | Tsai | Apr 1996 | A |
| 5546050 | Florian et al. | Aug 1996 | A |
| 5549487 | Nortier | Aug 1996 | A |
| 5593350 | Bouton et al. | Jan 1997 | A |
| 5594854 | Baldwin et al. | Jan 1997 | A |
| 5599231 | Hibino et al. | Feb 1997 | A |
| 5599232 | Darling | Feb 1997 | A |
| 5607157 | Nagashima | Mar 1997 | A |
| 5608424 | Takahashi et al. | Mar 1997 | A |
| 5615344 | Corder | Mar 1997 | A |
| 5628686 | Svancarek et al. | May 1997 | A |
| 5630170 | Koizumi et al. | May 1997 | A |
| 5630174 | Stone, III et al. | May 1997 | A |
| 5644790 | Li et al. | Jul 1997 | A |
| 5645277 | Cheng | Jul 1997 | A |
| 5655966 | Werdin, Jr. et al. | Aug 1997 | A |
| 5680534 | Yamato et al. | Oct 1997 | A |
| 5687357 | Priem | Nov 1997 | A |
| 5696912 | Bicevskis et al. | Dec 1997 | A |
| 5701444 | Baldwin | Dec 1997 | A |
| 5708799 | Gafken et al. | Jan 1998 | A |
| 5717428 | Barrus et al. | Feb 1998 | A |
| 5721947 | Priem et al. | Feb 1998 | A |
| 5727192 | Baldwin | Mar 1998 | A |
| 5748756 | Leal et al. | May 1998 | A |
| 5754890 | Holmdahl et al. | May 1998 | A |
| 5758182 | Rosenthal et al. | May 1998 | A |
| 5764243 | Baldwin | Jun 1998 | A |
| 5768626 | Munson et al. | Jun 1998 | A |
| 5768629 | Wise et al. | Jun 1998 | A |
| 5774133 | Neave et al. | Jun 1998 | A |
| 5777629 | Baldwin | Jul 1998 | A |
| 5784064 | Penna et al. | Jul 1998 | A |
| 5798770 | Baldwin | Aug 1998 | A |
| 5801706 | Fujita et al. | Sep 1998 | A |
| 5801716 | Silverbrook | Sep 1998 | A |
| 5805868 | Murphy | Sep 1998 | A |
| 5815166 | Baldwin | Sep 1998 | A |
| 5816921 | Hosokawa | Oct 1998 | A |
| 5821949 | Deering | Oct 1998 | A |
| 5832244 | Jolley et al. | Nov 1998 | A |
| 5867166 | Myhrvold et al. | Feb 1999 | A |
| 5870027 | Ho | Feb 1999 | A |
| 5872999 | Koizumi et al. | Feb 1999 | A |
| 5874969 | Storm et al. | Feb 1999 | A |
| 5886686 | Chen | Mar 1999 | A |
| 5892974 | Koizumi et al. | Apr 1999 | A |
| 5917496 | Fujita et al. | Jun 1999 | A |
| 5920326 | Rentschler et al. | Jul 1999 | A |
| 5935224 | Svancarek et al. | Aug 1999 | A |
| 5940086 | Rentschler et al. | Aug 1999 | A |
| 5949424 | Cabral et al. | Sep 1999 | A |
| 5949440 | Krech, Jr. et al. | Sep 1999 | A |
| 5969726 | Rentschler et al. | Oct 1999 | A |
| 5991546 | Chan et al. | Nov 1999 | A |
| 5996033 | Chiu-Hao | Nov 1999 | A |
| 5999196 | Storm et al. | Dec 1999 | A |
| 6002409 | Harkin | Dec 1999 | A |
| 6006295 | Jones et al. | Dec 1999 | A |
| 6018765 | Durana et al. | Jan 2000 | A |
| 6023738 | Priem et al. | Feb 2000 | A |
| 6025853 | Baldwin | Feb 2000 | A |
| 6028611 | Anderson et al. | Feb 2000 | A |
| 6033309 | Couch et al. | Mar 2000 | A |
| 6037949 | DeRose et al. | Mar 2000 | A |
| 6057852 | Krech, Jr. | May 2000 | A |
| 6067411 | Poimboeuf et al. | May 2000 | A |
| 6071191 | Takeda et al. | Jun 2000 | A |
| 6076119 | Maemura et al. | Jun 2000 | A |
| 6092124 | Priem et al. | Jul 2000 | A |
| 6098130 | Wang | Aug 2000 | A |
| 6101560 | Gulick | Aug 2000 | A |
| 6131134 | Huang et al. | Oct 2000 | A |
| 6147673 | Zarek | Nov 2000 | A |
| 6166748 | Van Hook et al. | Dec 2000 | A |
| 6171190 | Thanasack et al. | Jan 2001 | B1 |
| 6173367 | Aleksic et al. | Jan 2001 | B1 |
| 6181352 | Kirk et al. | Jan 2001 | B1 |
| 6190257 | Takeda et al. | Feb 2001 | B1 |
| 6193609 | D'Achard Van Enschut | Feb 2001 | B1 |
| 6198488 | Lindholm et al. | Mar 2001 | B1 |
| 6200253 | Nishiumi et al. | Mar 2001 | B1 |
| 6213878 | Setsumasa et al. | Apr 2001 | B1 |
| 6217351 | Fung et al. | Apr 2001 | B1 |
| 6226012 | Priem et al. | May 2001 | B1 |
| 6230232 | Nishiumi et al. | May 2001 | B1 |
| 6238291 | Fujimoto et al. | May 2001 | B1 |
| 6247075 | Wang et al. | Jun 2001 | B1 |
| 6263392 | McCauley | Jul 2001 | B1 |
| 6264558 | Nishiumi et al. | Jul 2001 | B1 |
| 6279906 | Sanderson et al. | Aug 2001 | B1 |
| 6307880 | Evans et al. | Oct 2001 | B1 |
| 6334160 | Emmert et al. | Dec 2001 | B1 |
| 6609977 | Shimizu et al. | Aug 2003 | B1 |
| 6615301 | Lee et al. | Sep 2003 | B1 |
| 20010006391 | Sawano et al. | Jul 2001 | A1 |
| 20010008847 | Miyamoto et al. | Jul 2001 | A1 |
| Number | Date | Country |
|---|---|---|
| 2070934 | Dec 1993 | CA |
| 0780771 | Jun 1997 | EP |
| 1 074 945 | Feb 2001 | EP |
| 1 075 146 | Feb 2001 | EP |
| 1 081 649 | Mar 2001 | EP |
| 11053580 | Feb 1999 | JP |
| 11076614 | Mar 1999 | JP |
| 11161819 | Jun 1999 | JP |
| 11203500 | Jul 1999 | JP |
| 11226257 | Aug 1999 | JP |
| 11259671 | Sep 1999 | JP |
| 11259678 | Sep 1999 | JP |
| 2000-66985 | Mar 2000 | JP |
| 2000-92390 | Mar 2000 | JP |
| 2000-132704 | May 2000 | JP |
| 2000-132706 | May 2000 | JP |
| 2000-149053 | May 2000 | JP |
| 2000-156875 | Jun 2000 | JP |
| 2000-182077 | Jun 2000 | JP |
| 2000-207582 | Jul 2000 | JP |
| 2000-215325 | Aug 2000 | JP |
| 8809573 | Jun 1990 | WO |
| WO 9410641 | May 1994 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 60226884 | Aug 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09723335 | Nov 2000 | US |
| Child | 10600585 | US |
