Programmable interrupt controller with interrupt set/reset register and dynamically alterable interrupt mask for a single interrupt processor

[0002] The present application is a continuation of application Ser. No. 08/962,514 filed Oct. 31, 1997 entitled “Integrated Audio/Video Decoder Circuitry,” which is currently pending. Application Ser. No. 08/962,514 claims priority under 35 USC §119(e) (1) of Provisional Application Nos.: Ser. Nos. 60/030,107, 60/030,106, 60/030,105, 60/030,104, 60/030,108 and 60/029,923, all filed Nov. 1, 1996.

[0003] (C) Copyright 1996 Texas Instruments Incorporated. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

[0004] This invention relates generally to the field of computer processors, and more particularly to a programmable interrupt controller for a single interrupt processor.

[0005] Currently, digital television DSS/DVB signals are transmitted in an MPEG format. In the MPEG format, the signals are transmitted in the form of data packets, with each packet including a useful signal or data and a header signal or data containing information about the contents of the useful signal or data.

[0006] Such a digital signal generally consists of packets of various types, such as audio data packets, video data packets and packets containing information pertaining to the program transmitted.

[0007] In general, the decoding of such digital signals takes place in a decoder in a reception station, which identifies and selects, in the incoming signals, desired audio and video data packets and then decodes these packets to form data trains, of the audio and video types, respectively. The audio data trains are decoded by means of an audio decoder for forming an analog acoustic signal. Similarly, the video data trains are used to form an image as well as chrominance and luminance signals.

[0008] There are known devices for the identification of packets. These devices extract a piece of data from each header signal, which is representative of the type of the corresponding useful signal. They include a means for storing reference data in a memory, at addresses each corresponding to one packet type, and a means for comparing the piece of data extracted from each header signal with said reference data (stored in the memory) then delivering to a data processing unit for further processing, an address signal indicating the nature of the corresponding packet. The processing unit then selects the identified packets for decoding and for forming corresponding data trains.

[0009] For this type of identification device, the comparison between the piece of data extracted from the header signal and the reference data stored in memory is conducted successively; that is, at a transition of a synchronization clock, an extracted piece of data is compared to a reference piece of data.

[0010] However, since the transmission rate of the packets is very high, the packet being identified must be stored, for example, in a memory of the FIFO type, associated with a piloting circuit and then further processed by the data processing unit.

[0011] Consequently, this type of identification device is relatively slow, requires a large number of components, and requires a large amount of memory and/or local storage buffers.

[0012] International standardization committees have been working on the specification of the coding methods and transmission formats for several compression algorithms to facilitate world wide interchange of digitally encoded audiovisual data. The Joint Photographic experts Group (JPEG) of the International Standards Organization (ISO) specified an algorithm for compression of still images. The ITU (formerly CCITT) proposed the H.261 standard for video telephony and video conference. The Motion Pictures Experts Group (MPEG) of ISO specified a first standard, MPEG-1, which is used for interactive video and provides a picture quality comparable to VCR quality. MPEG has also specified a second standard, MPEG-2, which provides audiovisual quality of both broadcast TV and HDTV. Because of the wide field of applications MPEG-2 is a family of standards with different profiles and levels.

[0013] The JPEG coding scheme could be in principal also used for coding of images sequences, sometimes described as motion JPEG. However, this intraframe coding is not very efficient because the redundancy between successive frames is not exploited. The redundancy between succeeding frames can be reduced by predictive coding. The simplest predictive coding is differential interframe coding where the difference between a current pixel of the present frame and the corresponding pixel of the previous frame is quantized, coded and transmitted. To perform such interframe prediction a frame memory for storing one or more frames is required to allow for this pixel by pixel comparison. Higher efficiency than the simple differential interframe coding can be achieved by a combination of discrete cosine transform (DCT) and interframe prediction. For so-called hybrid coding the interframe difference, which is similar to JPEG, is obtained, DCT coded and then transmitted. In order to have the same prediction at both the receiver and transmitter the decoder is incorporated into the coder. This results in a special feedback structure at the transmitter which avoids coder-decoder divergence.

[0014] Variable word length coding results in a variable bit rate which depends on image content, sequence change, etc. Transmission of the coded information over a constant rate channel requires a FIFO buffer at the output to smooth the data rate. The average video rate has to be adjusted to the constant channel rate. This is performed by controlling the quantizer according to the buffer content. If the buffer is nearly full, the quantization is made more severe and thus the coded bitrate is reduced. Conversely, if the buffer is nearly empty, the quantization is relaxed.

[0015] In general, the MPEG coding use a special predictive coding strategy. The coding starts with a frame which is not differentially coded; it is called an Intraframe (I). Then prediction is performed for coding one frame out of every M frames. This allows computation of a series of predicted frames (P), while “skipping” M−1 frames between coded frames. Finally, the “skipped” frames are coded in either a forward prediction mode, backward prediction mode, or bi-directional prediction mode. These frames are called bi-directionally interpolated (B) frames. The most efficient prediction mode, in terms of bitrate, is determined by the encoder and its selected mode is associated with the coded data. Thus the decoder can perform the necessary operations in order to reconstruct the image sequence. A main difference between MPEG-1 and MPEG-2 is that MPEG-1 has been optimized for non-interlaced (progressive) format while MPEG-2 is a generic standard for both interlaced and progressive formats. Thus, MPEG-2 includes more sophisticated prediction schemes.

[0016] In more detail, motion pictures are provided at thirty frames per second to create the illusion of continuous motion. Since each picture is made up of thousands of pixels, the amount of storage necessary for storing even a short motion sequence is enormous. As higher and higher definitions are desired, the number of pixels in each picture grows also. This means that the frame memory used to store each picture for interframe prediction also grows; current MPEG systems use about 16 megabits (MB) of reference memory for this function. Fortunately, lossy compression techniques have been developed to achieve very high data compression without loss of perceived picture quality by taking advantage of special properties of the human visual system. (A lossy compression technique involves discarding information not essential to achieve the target picture quality to the human visual system). An MPEG decoder is then required to reconstruct in real time or nearly real time every pixel of the stored motion sequence; current MPEG decoders use at least about 16 MB of frame memory for reconstruction of frames using the encoded interframe prediction data.

[0017] The MPEG standard specifies both the coded digital representation of video signal for the storage media, and the method for decoding to achieve compatibility between compression and decompression equipment. The standard supports normal speed playback, as well as other play modes of color motion pictures, and reproduction of still pictures. The standard covers the common 525- and 625-line television, personal computer and workstation display formats. The MPEG-1 standard is intended for equipment supporting continuous transfer rate of up to 1.5 Mbits per second, such as compact disks, digital audio tapes, or magnetic hard disks. The MPEG-2 standard supports bit rates from 4 Mbits/sec (Mbits) to 15 Mbits and is targeted for equipment that complies with the International Radio Consultative Committee (CCIR) recommendation 601 (CCIR-601). The MPEG standard is intended to support picture frames at a rate between 24 Hz and 30 Hz. ISO-11171 entitled Coding for Moving Pictures and Associated Audio for digital storage medium at 1.5 Mbit/s, provides the details of the MPEG-1 standard. ISO-13838 entitled Generic Coding of Moving Pictures and Associated Audio provides the details of the MPEG-2 standard.

[0018] Under the MPEG standard, the picture frame is divided into a series of “Macroblock slices” (MBS), each MBS containing a number of picture areas (called “macroblocks”) each covering an area of 16×16 pixels. Each of these picture areas is represented by one or more 8×8 matrices which elements are the spatial luminance and chrominance values. In one representation (4:2:2) of the macroblock, a luminance value (Y type) is provided for every pixel in the 16×16 pixels picture area (in four 8×8 “Y” matrices), and chrominance values of the U and V (i.e., blue and red chrominance) types, each covering the same 16×16 picture area, are respectively provided in two 8×8 “U” and two 8×8 “V” matrices. That is, each 8×8 U or V matrix covers an area of 8×16 pixels. In another representation (4:2:0), a luminance value is provided for every pixel in the 16×16 pixels picture area, and one 8×8 matrix for each of the U and V types is provided to represent the chrominance values of the 16×16 pixels picture area. A group of four continuous pixels in a 2×2 configuration is called a “quad pixel”; hence, the macroblock can also be thought of as comprising 64 quad pixels in an 8×8 configuration.

[0019] The MPEG standard adopts a model of compression and decompression. Initially, interframe redundancy is first removed from the color motion picture frames. To achieve interframe redundancy removal, each frame is designated either “intra” “predicted” or “interpolated” for coding purpose. Intraframes are least frequently provided, the predicted frames are provided more frequently than the intraframes, and all the remaining frames are interpolated frames. The values of every pixel in an intraframe (“I-picture”) is independently provided. In a prediction frame (“P-picture”), only the incremental changes in pixel values from the last I-picture or P-picture are coded. In an interpolation frame (“B-picture”), the pixel values are coded with respect to both an earlier frame and a later frame. Again, large (16 MB) frame or reference memories are required to store frames of video to allow for this type of coding.

[0020] The MPEG standard does not require frames to be stored in strict time sequence, so that the intraframe from which a predicted frame is coded can be provided in the picture sequence either earlier or later in time from the predicted frame. By coding frames incrementally, using predicted and interpolated frames, much interframe redundancy can be eliminated which results in tremendous savings in storage requirements. Further, motion of an entire macroblock can be coded by a motion vector, rather than at the pixel level, thereby providing further data compression.

[0021] The next steps in compression under the MPEG standard remove intraframe redundancy. In the first step, a 2-dimensional discrete cosine transform (DCT) is performed on each of the 8×8 values matrices to map the spatial luminance or chrominance values into the frequency domain.

[0022] Next, a process called “quantization” weights each element of the 8×8 matrix in accordance with its chrominance or luminance type and its frequency. In an I-picture, the quantization weights are intended to reduce to one many high frequency components to which the human eye is not sensitive. In P- and B-pictures, which contain mostly higher frequency components, the weights are not related to visual perception. Having created many zero elements in the 8×8 matrix, each matrix can now be represented without information loss as an ordered list of a “DC” value, and alternating pairs of a non-zero “AC” value and a length of zero elements following the non-zero value. The list is ordered such that the elements of the matrix are presented as if the matrix is read in a zigzag manner (i.e., the elements of a matrix A are read in the order A00, A01, A10, A20, A11, A02, etc.). The representation is space efficient because zero elements are not represented individually.

[0023] Finally, an entropy encoding scheme is used to further compress the representations of the DC block coefficients and the AC value-run length pairs using variable length codes. Under the entropy encoding scheme, the more frequently occurring symbols are represented by shorter codes. Further efficiency in storage is thereby achieved.

[0024] In decompression, under MPEG, the processes of entropy encoding, quantization and DCT are reversed. The final step, called “absolute pixel generation”, provides the actual pixels for reproduction, in accordance to the play mode (forward, reverse, slow motion e.g.), and the physical dimensions and attributes of the display used. Again, large (16 MB) frame or reference memories are required to store frames of video to allow for this type of reproduction.

[0025] Since the steps involved in compression (coding) and decompression (decoding), such as illustrated for the MPEG standard discussed above, are very computationally intensive and require large amounts of memory, for such a compression scheme to be practical and widely accepted, the decompression processor must be designed to provide decompression in real time, and allow economical implementation using today's computer or integrated circuit technology.

[0026] The purpose of the present invention is to overcome these short-comings and drawbacks. Improvements in circuits, integrated circuit devices, computer systems of all types, and methods to address all the just-mentioned challenges, among others, are desirable, as described herein.

[0027] The present invention provides a programmable interrupt controller that substantially reduces or eliminates disadvantages and problems associated with prior systems and methods. The programmable interrupt controller is best shown by FIGS. 22B-E. In particular, the present invention uses a programmable interrupt mask and a programmable vector table in combination with an interrupt multiplexer to prioritize and process interrupts from a plurality of sources in a single interrupt architecture processor.

[0028] In accordance with one embodiment of the present invention, a programmable interrupt controller for a single interrupt architecture processor includes a plurality of interrupt sources each operable to generate an interrupt. A dynamically alterable interrupt mask selectively blocks interrupt signals for the interrupt sources. Interrupts permitted by the dynamically alterable interrupt mask are processed by an interrupt handler for the single interrupt architecture processor in order of priority. In addition, processing for a lower priority interrupt is interrupted in order to process a later received higher priority interrupt permitted by the dynamically alterable interrupt mask.

[0029] In accordance with a particular embodiment of the present invention, a vector table is provided to associate each interrupt signal permitted by the interrupt mask with an interrupt service routine. In this embodiment, the interrupt handler processes the interrupt signal by executing an interrupt service routine associated with the interrupt in the vector table. The interrupt service routine may reprogram the interrupt mask and the vector table during its execution. In addition, the interrupt service routine may alter the state of an interrupt.

[0030] Technical advantages of the present invention include providing a programmable interrupt controller for a single interrupt architecture processor. In particular, a programmable interrupt mask and a programmable vector table are provided to allow multiple interrupts to be dynamically prioritized and processed in order of their priority. In addition, interrupt processing may be nested to allow higher priority interrupts to interrupt processing of lower priority interrupts.

[0031] Other technical advantages of the present invention will be readily apparent to one skilled in the art from the following figures, description, and claims.

[0032] The invention may be understood by referring to the detailed description which follows, read in conjunction with the accompanying drawings in which:

[0033] FIG. 1A depicts a communication system of the present invention;

[0034] FIG. 1B depicts a high level functional block diagram of a circuit that forms a portion of the communications system of the present invention;

[0035] FIG. 2 depicts a portion of FIG. 1B and data flow between these portions;

[0036] FIG. 3 shows the input timing for the circuit of FIG. 1B;

[0037] FIG. 4 shows the timing of the VARIS output for the circuit of FIG. 1B;

[0038] FIG. 5 shows the timing of 4:2:2 and 4:4:4 digital video output for the circuit of FIG. 1B;

[0039] FIG. 6 depicts the data output of PCMOUT alternates between the two channels, as designated by LRCLK for the circuit of FIG. 1B;

[0040] FIG. 7 shows an example circuit where maximum clock jitter will not exceed 200 ps RMS for the circuit of FIG. 1B;

[0041] FIG. 8 (read) and FIG. 9 (write) show extension bus read and write timing, both with two programmable wait states for the circuit of FIG. 1B;

[0042] FIG. 10 shows the timing diagram of a read with EXTWAIT signal on for the circuit of FIG. 1B;

[0043] FIG. 11 depicts the connection between circuitry of the present invention, an external packetizer, Link layer, and Physical layer devices;

[0044] FIG. 12 shows a functional block diagram of the data flow between the TPP, DES, and 1394 interface;

[0045] FIG. 13 and FIG. 14 depict the read and write timing relationships on the 1394 interface for the circuit of FIG. 1B;

[0046] FIG. 15 shows the data path of ARM processor core for the circuit of FIG. 1B;

[0047] FIG. 16A depicts the data flow managed by the traffic controller for the circuit of FIG. 1B;

[0048] FIGS. 16B through 16Q depict details of the traffic controller of FIG. 1B;

[0049] FIGS. 16R and 16S illustrate details of the arbiter block 313-12 of FIG. 16N;

[0050] FIG. 16T illustrates timings;

[0051] FIG. 17A is an example circuit for the external VCXO for the circuit of FIG. 1B;

[0052] FIG. 17B depicts details of a transport packet containing 188 bytes;

[0053] FIG. 17C depicts a system where the video and audio decoders are in a separate device;

[0054] FIG. 17D depicts how header information is processed by the circuit of FIG. 1B;

[0055] FIG. 17E depicts the contents of a packet analyzer control register;

[0056] FIG. 17F depicts a block diagram for processing packet header information;

[0057] FIG. 17G is the flow diagram used to analyze a packet header;

[0058] FIG. 17H describes the structure of the PES packet;

[0059] FIGS. 17I-17P depicts the details of a presently preferred embodiment of the TPP of FIG. 1B;

[0060] FIGS. 18A to 18Y depict details of the OSD module;

[0061] FIGS. 18Z to 18AR depict details of OSD portions of the presently preferred OSD block of FIG. 1B;

[0062] FIGS. 18AS to 18BA depict details of BitBLT portions of the presently preferred OSD block of FIG. 1B;

[0063] FIG. 19 shows example displays of two OSD output channels for the circuit of FIG. 1B;

[0064] FIG. 20 show an example of the IR input bitstream for the circuit of FIG. 1B;

[0065] FIG. 21 shows a model of the hardware interface for the circuit of FIG. 1B; and

[0066] FIGS. 22A-22S depict details associated with software utilized on or with the circuit of FIG. 1B with FIGS. 22B-E best showing details of the programmable interrupt controller.

[0067] Corresponding numerals and symbols in the different Figures refer to corresponding parts unless otherwise indicated.

[0068] The present invention provides an improved communications system 100. FIG. 1A depicts an improved communications system 100 of the present invention. More particularly, there may be seen a satellite reception dish that receives signals from a satellite and provides them to a low noise amplifier 10. The low noise amplifier provides its signals to a tuner 20. The tuner 20 is employed to select the signals a user wishes to watch. The tuner 20 is connected to a quadrature phase-shift keying (QPSK) circuit 30 that recovers the digital data in the selected signal. This data is then error corrected by a forward error correction (FEC) circuit 40 using Viterbi, Reed-Solomon, or other techniques to compensate for data errors. The corrected received data is then passed to the circuit 200 of the present invention. The circuit 200 parses the packets of data and converts the data to video, audio and OSD, which may be appropriately displayed on an audio/visual display 130 or after RF modulation 110, on an NTSC/PAL TV 150. Alternatively, the digital video output may be converted, via a converter 90 and displayed on other types of TV's 110, for example, a French TV.

[0069] The audio output is converted to an analogue signal by DAC 120. The circuit 200 is also shown connected to a memory 70, an infrared (IR) receiver 50, a modem 60 and a voltage controlled oscillator (VCXO) 80 that provides circuit 200 with a precise but adjustable clock. The clock is adjusted to be synchronized with the clock signals found in the received digital data.

[0070] Referring now to FIG. 1B, there may be seen a high level functional block diagram of a circuit 200 that forms a portion of a communications system 100 of the present invention and its interfaces with off-chip devices and/or circuitry. More particularly, there may be seen the high level architecture of a circuit, including on-chip interconnections, that is preferably implemented on a single chip as depicted by the dashed line portion of FIG. 1B.

[0071] As depicted inside the dashed line portion of FIG. 1B, this circuit consists of a transport packet parser (TPP) block or module 210 that includes a bitstream decoder or descrambler 212 and clock recovery circuitry 214, an ARM CPU block 220, a data ROM block 230, a data RAM block 240, an audio/video (A/V) core block 250 that includes an MPEG-2 audio decoder 254 and an MPEG-2 video decoder 252, an NTSC/PAL video encoder block 260, an on screen display (OSD) controller block 270 to mix graphics and video that includes a bitblt hardware (H/W) accelerator 272, a communication co-processors (CCP) block 280 that includes connections for two UART serial data interfaces 280-4, 280-5, infrared (IR) and radio frequency (RF) inputs 280-2, SIRCS input and output 280-7, an I2C port 280-3 and a Smart Card interface 280-1, a P1394 interface (I/F) block 290 for connection to an external 1394 device, an extension bus interface (I/F) block 300 to connect peripherals such as additional RS232 ports 300-6, display and control panels 300-4, 300-5, external ROM, DRAM 300-1, or EEPROM memory 300-2, a modem 300-3 and an extra peripheral 300-7, and a traffic controller (TC) block 310 that includes an SRAM/ARM (on-chip memory (CPU)) interface (I/F) 311 and a (memory) DRAM I/F 313.

[0072] There may also be seen an internal 32 bit address bus 320 that interconnects the blocks and an internal 32 bit data bus 330 that interconnects the blocks. The TPP receives a high speed bit stream of transport data that requires it to analyze the bit stream and direct the data to the right destination. The TPP discards packets not selected by an application and routes as many packets as possible without real-time help from either the ARM CPU 220 or software running on the ARM CPU. External program and data memory expansion 310-2, 300-1, 300-2, allows the circuit to support a wide range of audio/video systems, especially, for example, but not limited to, set-top boxes, from low end to high end.

[0073] The consolidation of all these functions onto a single chip with a large number of inputs and outputs allows for removal of excess circuitry and/or logic needed for control and/or communications when these functions are distributed among several chips and allows for simplification of the circuitry remaining after consolidation onto a single chip. More particularly, this consolidation results in the elimination of the need for an external CPU to control, or coordinate control, of all these functions. This results in a simpler and cost-reduced single chip implementation of the functionality currently available only by combining many different chips and/or by using special chipsets. However, this circuit, by its very function, requires a large number of inputs and outputs, entailing a high number of pins for the chip.

[0074] In addition, a JTAG block 280-6 is depicted that allows for testing of this circuit using a standard JTAG interface that is interconnected with this JTAG block.

[0075] In addition, FIG. 1B depicts that the circuit is interconnected to a plurality of other external blocks. More particularly, FIG. 1B depicts a set of external memory blocks. Preferably, the external memory is SDRAM 312, although clearly, other types of RAM may be so employed. The external memory 312 is described more fully later herein. The incorporation of any or all of these external blocks and/or all or portions of the external memories onto the chip is contemplated by and within the scope of the present invention.

[0076] Referring now to FIG. 2, there may be seen a portion of the components of FIG. 1B. The components depicted in FIG. 2, serve as the basis for an initial discussion of data flows between the components to help understand the functionality provided by each block or module and the overall circuit 200. Continuing to refer to FIG. 2, it may be seen how the circuit 200 accepts a transport bitstream from the output of a forward error correction (FEC) device (not depicted) with a maximum throughput of 40 Mbits/s or 7.5 Mbytes/s. The Transport Packet Parser (TPP) 210 in the circuit 200 processes the header of each packet and determines whether the packet should be discarded, further processed by ARM CPU 220, or if the packet contains relevant data and may be stored without any intervention from the ARM 220. The TPP 210 sends all packets requiring further processing or containing relevant data to the internal RAM 240 via the traffic controller (TC) 310. The TPP 210 also activates or deactivates the decryption engine (DES) 212 based on the content of an individual packet. Conditional access keys for decryption (or encryption) are stored in RAM 240 or off-chip memory locations, such as, for example, a smart-card,and managed by special firmware running on the ARM CPU 220. The data transfer from TPP 210 to SDRAM 312 is done via DMA set up by the traffic controller (TC) 310.

[0077] Further processing on the packet is done by the ARM firmware, which is activated by an interrupt from the TPP 210 after the completion of the packet data transfer. Two types of transport packets are stored in the RAM 240 which is managed as a first-in first-out buffer (FIFO). One type is for pure data which will be routed to SDRAM 312 without intervention from the ARM 220, and the other type is for packets that need further processing by the ARM 220. Within the interrupt service routine, the ARM 220 checks the FIFO for packets that need further processing, performs necessary parsing, removes the header portion, and establishes DMA for transferring payload data from RAM 240 to SDRAM 312. The traffic controller 310 repacks the data and gets rid of the voids created by any header removal.

[0078] Together with the ARM 220, the TPP 210 also handles System Clock Reference (SCR) recovery with an external VCXO 80. The TPP 210 will latch and transfer to the ARM 220 its internal system clock upon the arrival of any packet which may contain system clock information. After further processing on the packet and identifying the system clock, the ARM 220 calculates the difference between the system clock from a bitstream and the actual system clock at the time the packet arrives. Then, the ARM 220 filters the difference and sends it through a Sigma-Delta DAC 216 in the TPP 210 to control the external voltage controlled oscillator (VCXO) 80. During start-up when there is no incoming SCR, the ARM will drive the VCXO 80 to its center frequency.

[0079] The TPP 210 will also detect packets lost from the transport stream. With error concealment by the audio/video decoder and the redundant header from DSS bitstream, the circuit 200 minimizes the effect of lost data.

[0080] After removing packet headers and other system related information, both audio and video data is stored in external SDRAM 312. The video 252 and audio 254 decoders then read the bitstream from SDRAM 312 and process it according to the ISO standards. The circuit 200 decodes MPEG-1 and MPEG-2 main profile at main level for video and Layer I and II MPEG-1 and MPEG-2 for audio. Both video 252 and audio 254 decoders synchronize their presentation using the transmitted Presentation Time Stamps (PTS). In a Digital Satellite System (DSS), the PTS is transmitted as picture user data in the video bitstream and an MPEG-1 system packet bitstream for audio. Dedicated hardware decodes the PTS if it is in the MPEG-1 system packet and forwards it to the audio decoder 254. The video decoder 252 decodes PTS from picture user data. Both video 252 and audio 254 decoders compare PTS to the local system clock in order to synchronize presentation of the reconstructed data. The local system clock is continuously updated by the ARM 220. That is, every time the System Clock Reference (SCR) of a selected SCID is received and processed, the ARM 220 will update the decoder system clock.

[0081] The video decoder 252 is capable of producing decimated pictures using ½ or ¼ decimation per dimension, which results in reduced areas of ¼ or {fraction (1/16)}. The decimated picture can be viewed in real time. Decimation is achieved by using field data out of a frame, skipping lines, and performing vertical filtering to smooth out the decimated image.

[0082] When decoding a picture from a digital recorder, the decoder can handle trick modes (decode and display I frame only), with the limitation that the data has to be a whole picture instead of several intra slices. Random bits are allowed in between trick mode pictures. However, if the random bits emulate any start code, it will cause unpredictable decoding and display errors.

[0083] Closed Caption (CC) and Extended Data Services (EDS) are transmitted as picture layer user data. The video decoder 252 extracts the CC and EDS information from the video bitstream and sends it to the NTSC/PAL encoder module 260.

[0084] The video decoder 252 also extracts the aspect ratio from the bitstream and sends it to the ARM 220 which prepares data according to the Video Aspect Ratio Identification Signal (VARIS) standard, EIAJ CPX—1204. The ARM 220 then sends it to the NTSC/PAL encoder 260 and OSD module 270.

[0085] The OSD data may come from the user data in the bitstream or may be generated by an application executed on the ARM 220. Regardless of the source, the OSD data will be stored in the SDRAM 312 and managed by the ARM 220. However, there may be limited space in the SDRAM 312 for OSD. Applications that require large quantities of OSD data preferably store them in an external memory attached to the extension bus 300. Based on a request from a user application, the ARM 220 will turn the OSD function on and specify how and where the OSD will be mixed and displayed along with the normal video sequence. The OSD data can be represented in one of the following forms: bitmap, graphics 4:4:4 component, CCIR 601 4:2:2 component, or just background color. A special, dedicated bitBLT hardware 272 expedites memory block moves between different windows.

[0086] DES 212 processing is signaled by the arrival of a control word packet. That is, a conditional access is triggered by the arrival of a control word packet (CWP). The ARM firmware recognizes a CWP has been received and hands it to the Verifier, which is NewsDataCom (NDC) application software running on the ARM 220. The Verifier reads the CWP and communicates with an external Smart Card through a Smart Card I/O interface in communication coprocessor 280. After verification, it passes the pointer to an 8 byte key back to the firmware, which then loads the key for the DES 212 to decrypt succeeding packets.

[0087] The ARM 220 is a 32-bit processor running at 40.5 MHz and with its associated firmware provide the following: initialization and management of all hardware modules; service for selected interrupts generated by hardware modules and I/O ports; and application program interface (API) for users to develop their own applications.

[0088] The ARM firmware is stored in the on-chip ROM 230, except for OSD graphics and some generic run time support code. The ROM 230 is preferably 12K bytes, but other sizes may be so employed. The on-chip RAM 240 provides the space necessary for the circuit 200 to properly decode transport bitstreams without losing any packets. The RAM 240 is preferably 4.5K bytes, but other sizes may be so employed. The run-time support library (RTSL) and all user application software is presently preferred to be located in memory outside the circuit 200. Details of the firmware and RTSL are provided later herein.

[0089] There are two physical DMA channels managed by the traffic controller 310 to facilitate large block transfers between memories and buffers. That is, as long as there is no collision in the source and destination, it is possible to have two concurrent DMA transfers. A more detailed description of these DMA functions is provided later herein in subsequent discussions of the details of the traffic controller 310.

[0090] The circuit 200 accepts DSS transport packet data from a front end such as a forward error correction (FEC) unit. The data is input 8 bits at a time, using a byte clock, DCLK. PACCLK high signals valid packet data. DERROR is used to indicate a packet that has data errors. The timing diagram in FIG. 3 shows the input timings for such data.

[0091] As part of the communication coprocessor 280, the circuit 200 includes an interface to the Smart Card access control system. The interface consists of a high speed UART and logic to comply with the News Datacom specification (Document # HU-T052, Release E dated November 1994, and Release F dated January 1996) Directv Project: Decoder-Smart Card Interface Requirements. Applicable software drivers that control the interface are also included, and are described later herein.

[0092] It should be noted that the circuit 200 is preferably a 3.3 volt device, while the Smart Card requires a 5 volt interface. The circuit 200 will output control signals to turn the card's VCC and VPP on and off as required, but external switching will be required. It is also possible that external level shifters may be needed on some of the logic signals.

[0093] A NTSC/PAL pin selects between an NTSC or a PAL output from encoder 260. Changing between NTSC and PAL mode requires a hardware reset of the device 200.

[0094] The circuit 200 produces an analog S-video signal on two separate channels, the luminance (Y) and the chrominance (C). It also outputs the analog composite (Comp) signal. All three outputs conform to the RS170A standard.

[0095] The circuit 200 also supports Closed Caption and Extended Data Services. The analog output transmits CC data as ASCII code during the twenty-first video line. The NTSC/PAL encoder module inserts VARIS codes into the 20th video line for NTSC and 23rd line for PAL.

[0096] The digital output provides video in either 4:4:4 or 4:2:2 component format, plus the aspect ratio VARIS code at the beginning of each video frame. The video output format is programmable by the user but defaults to 4:2:2. The content of the video could be either pure video or the blended combination of video and OSD.

[0097] The pin assignments for the digital video output signals are:

[0098] YCOUT(8) 8-bit Cb/Y/Cr/Y and VARIS multiplexed data output

[0099] YCCLK(1) 27 MHz or 40.5 MHz clock output

[0100] YCCTRL(2) 2-bit control signals to distinguish between Y/Cb/Cr components and VARIS code

[0101] The interpretation of YCCTRL is defined in the following table.

[0102] The aspect ratio VARIS code includes 14 bits of data plus a 6-bit CRC, to make a total of 20 bits. In NTSC the 14-bit data is specified as shown in Table 2.

[0103] The 6-bit CRC is calculated, with the preset value to be all 1, based on the equation G(X)=X⁶+X+1.

[0104] The 20-bit code is further packaged into 3 bytes according to the following format illustrated in Table 3.

[0105] The three byte VARIS code is constructed by the ARM 220 as part of the initialization process. The ARM 220 calculates two VARIS codes corresponding to the two possible aspect ratios. The proper code is selected based on the aspect ratio from the bitstream extracted by the video decoder 252. The user can set VID_EN to signal the NTSC/PAL encoder to enable (1) or disable (0) the VARIS code. The transmission order is the 1st byte first and it is transmitted during the non-active video line and before the transmission of video data.

[0106] The timing of the VARIS output is shown in the following FIG. 4. The timing of 4:2:2 and 4:4:4 digital video output is shown in FIG. 5.

[0107] The PCM audio output from the audio decoder 254 is a serial PCM data line, with associated bit and left/right clocks.

[0108] PCM data is output serially on PCMOUT using the serial clock ASCLK. ASCLK is derived from the PCM clock, PCMCLK, according to the PCM Select bits in the control register. PCM clock must be the proper multiple of the sampling frequency of the bitstream. The PCMCLK may be input to the device or internally derived from an 18.432 MHz clock, depending on the state of the PCM_SRC pin. The data output of PCMOUT alternates between the two channels, as designated by LRCLK as depicted in FIG. 6. The data is output most significant bit first. In the case of 18-bit output, the PCM word size is 24 bits. The first six bits are zero, followed by the 18-bit PCM value.

[0109] The SPDIF output conforms to a subset of the AES3 standard for serial transmission of digital audio data. The SPDIF format is a subset of the minimum implementation of AES3.

[0110] When the PCM_SRC pin is low, the circuit 200 generates the necessary output clocks for the audio data, phase locked to the input bitstream. However, the clock generator requires an additional 18.432 MHz external VCXO 254-1 and outputs a control voltage that can be applied to the external loop filter and VCXO to produce the required input. The clock generator derives the correct output clocks, based on the contents of the audio control register bits PCMSEL1-0, as shown in the following table.

[0111] Maximum clock jitter will not exceed 200 ps RMS. A representative VCXO circuit is shown in FIG. 7.

[0112] When PCM_SRC is high, the circuit 200 expects the correct PCM oversampling clock frequency to be input on PCMCLK.

[0113] The SDRAM 312 is preferably 16-bit wide SDRAM. The DRAM I/F 313 of the TC 310 is presently preferably configured for this type of bit width; clearly other widths may be selected and so employed. The circuit 200 provides control signals for up to two SDRAMs. Any combination of 4, 8, or 16 Mbit SDRAMs may be used, provided they total at least 16 Mbits. The SDRAM must operate at an 81 MHz clock frequency and have the timing parameters described later herein.

[0114] The extension. bus interface 300 is a 16-bit bi-directional data bus with a 25-bit address for byte access. It also provides 3 external interrupts, each with it's own acknowledge signal, and a wait line. All the external memories or I/O devices are mapped to the 32-bit address space of the ARM. There are seven internally generated Chip Selects (CSx) for EEPROM memory 300-2, DRAM 300-1, modem 300-3, front panel 300-4, front end control 300-5, parallel output port 300-6, and extra peripheral 300-7. Each CS has its own defined memory space and a programmable wait state register which has a default value 1. The number of wait states depends on the content of the register, with a minimum of one wait state. The EXTWAIT signal can also be used to lengthen the access time if a slower device exists in that memory space.

[0115] The extension bus 300 supports the connection of 7 devices using the pre-defined chip selects. Additional devices may be used by externally decoding the address bus. The following table shows the name of the device, its chip select, address range, and programmable wait state. Every device is required to have tri-stated data outputs within 1 clock cycle following the removal of its chip-select (CS).

[0116] CS1 is intended for ARM 220 application code, but writes will not be prevented.

[0117] CS2 is read/write accessible by the ARM 220. It is also accessed by the TC 310 for TPP 210 and bitBLT 272 DMA transfers.

[0118] CS3, CS4, CS5, and CS6 all have the same characteristics. The ARM 220 performs reads and writes to these devices through the extension bus.

[0119] CS7 is read and write accessible by the ARM 220. It is also accessed by the TC 310 for TPP 210 DMAs, and it is write only. The parallel port is one byte wide and it is accessed via the least significant byte.

[0120] The extension bus 300 supports connection to external EEPROM, SRAM, or ROM 300-2 memory and DRAM 300-1 with its 16-bit data and 25-bit address. The extension bus 300 supports access to 70 ns DRAM with 2 wait states. The DRAM must have a column address that is 8-bits, 9-bits, or 10-bits wide. The DRAM preferably has a data width of 8 or 16 bits. Byte access is allowed even when the DPAM has a 16 bit data width. The system default DRAM configuration is 9-bit column address and 16-bit data width. The firmware will verify the configuration of DRAM during start up. The extension bus 300 also supports DMA transfers to/from the extension bus. DMA transfers within the extension bus are not supported. However, they may be accomplished by DMA to the SRAM, followed by DMA to the extension bus. Extension bus read and write timing are shown in FIG. 8 (read) and FIG. 9 (write), both with two programmable wait states. The number of wait states may be calculated by the following formula:

[0121] # of wait states=round_up[((CS_delay+device_cycle_time)/24)−1]

[0122] For example, the CS_delay on the chip is 20 nsec. A device with 80 nsec read timing will need 4 wait states.

[0123] There are three interrupt lines and three interrupt acknowledges in the circuit 200. These interrupts and interrupts from other modules are handled by a centralized interrupt handler. The interrupt mask and priority are managed by the firmware. The three extension bus interrupts are connected to three different IRQs. When the interrupt handler on the ARM 220 begins servicing one of these IRQs, it should first issue the corresponding EXTACK signal. At the completion of the IRQ, the ARM 220 should reset the EXTACK signal.

[0124] The EXTWAIT signal is an alternative way for the ARM 220 to communicate with slower devices. It can be used together with the programmable wait state, but it has to become active before the programmable wait cycle expires. The total amount of wait states should not exceed the maximum allowed from Table 5. If the combined total wait states exceeds its maximum, the decoder is not guaranteed to function properly. When a device needs to use the EXTWAIT signal, it should set the programmable wait state to at least 2. Since the EXTWAIT signal has the potential to stall the whole decoding process, the ARM 220 will cap its waiting to 490 nanoseconds. Afterwards, the ARM 220 assumes the device that generated the EXTWAIT has failed and will ignore EXTWAIT from then on. Only a software or hardware reset can activate the EXTWAIT signal again. The timing diagram of a read with EXTWAIT signal on is shown in the FIG. 10.

[0125] The circuit 200 includes an Inter Integrated Circuit (I²C) serial bus interface that can act as either a master (default) or slave. Only the ‘standard mode’ (100 kbit/s) I²C-bus system is implemented; ‘fast mode’ is not supported. The interface uses 7-bit addressing. When in slave mode, the address of the circuit 200 is programmed by the API.

[0126] Timing for this interface matches the standard timing definition of the I²C bus.

[0127] The circuit 200 includes two general purpose 2-wire UARTs that are memory mapped and fully accessible by application programs. The UARTs operate in asynchronous mode only and support baud rates of 1200, 2400, 4800, 9600, 14400, 19200 and 28800 kbps. The outputs of the UARTs are digital and require external level shifters for RS232 compliance.

[0128] The IR, RF, and SIRCSI ports require a square wave input with no false transitions; therefore, the signal must be thresholded prior to being applied to the pins. The interface will accept an IR, RF, or SIRCSI data stream up to a frequency of 1.3 KHz. Although more than one may be active at any given time, only one IR, RF, or SIRCSI input will be decoded. Decoding of the IR, RF, and SIRCSI signals will be done by a combination of hardware and software. A more detailed description of these IR, RF functions is provided later herein in subsequent discussions of the details of the module 280.

[0129] SIRCSO outputs the SIRCSI or IR input or application-generated SIRCSO codes.

[0130] The circuit 200 provides a dedicated data interface for 1394290. To complete the implementation, the circuit 200 requires an external packetizer 290-1, Link layer 290-2, and Physical layer 290-3 devices. FIG. 11 depicts the inter-connection of these components.

[0131] The control/command to the packetizer or the Link layer interface device is transmitted via the extension bus 300. The 1394 data is transferred via the 1394 interface which has the following 14 signals:

[0132] In recording mode, the circuit 200 will send either encrypted or clean packets to the 1394 interface 290. The packet is transferred as it comes in. When recording encrypted data, the TPP 210 will send each byte directly to the 1394290 interface and bypass the DES module 212. In the case of recording decrypted data, the TPP 210 will send the packet payload to the DES module 290, then forward a block of packets to the 1394 interface 290. The interface 290 sends the block of packets out byte by byte. No processing will be done to the packet during recording, except setting the encrypt bit to the proper state. In particular, the TPP 210 will not remove CWP from the Auxiliary packet. During playback mode, the packet coming from the interface will go directly into the TPP 210 module. FIG. 12 shows the functional block diagram of the data flow between the TPP 210, DES 212, and 1394 interface 290, via muxes 218 and 219. The packet coming out from TPP 210 can go either to the 1394 interface 290 or to the RAM 240 through traffic controller TC, or to both places at the same time. This allows the circuit 200 to decode one program while recording from 1 to all 32 possible services from a transponder.

[0133] FIG. 13 and FIG. 14 depict the read and write timing relationships on the 1394 interface 290. In FIG. 13, CLK40 is 40.5 MHz. When PPACEN is high, circuit 200 toggles PWRITE as needed to output data. There should preferably be at least one cycle between the time that PDATA is valid to the time PWRITE goes high. The duration of PWRITE is one cycle, 25 ns. In FIG. 14, PREADREQ can go high at any time before or coincident with the next packet and it should remain high at least one cycle. PPACEN goes high when PDATA ready and both are synchronized to CLK40. PREAD toggles for one cycle when PDATA will change.

[0134] During recording, if the DERROR signal from the front end interface goes high in the middle of a packet, it is forwarded to the PERROR pin. If DERROR becomes active in between packets, then a PERROR signal will be generated during the transfer of the next packet for at least one PDATA cycle.

[0135] During playback mode, the external 1394 device can only raise the PERROR signal when the PPACEN is active to indicate either error(s) in the current packet or that there are missing packet(s) prior to the current one. PERROR is ignored unless the PPACEN is active. The PERROR signal should stay high for at least two PCLK cycles. There should be at most one PERROR signal per packet.

[0136] The circuit 200 requires a hardware reset on power up. Reset of the device is initiated by pulling the RESET pin low, while the clock is running, for at least 100 ns. The following actions will then occur: input data on all ports will be ignored; external memory is sized; data pointers are reset; all modules are initialized and set to a default state: the TPP tables are initialized; the audio decoder is set for 16 bit output with 256× oversampling; the OSD background color is set to blue and video data is selected for both the analog and digital outputs; MacroVision is disabled; and the I²C port is set to master mode.

[0137] When the reset sequence is finished, the device will begin to accept data. All data input prior to the end of the reset sequence will be ignored.

[0138] JTAG boundary scan is included in the circuit 200. Five pins (including a test reset) are used to implement the IEEE 1149.1 (JTAG) specification. The port includes an 8-bit instruction register used to select the instruction. This register is loaded serially via the TDI input. Four instructions (Bypass; Extest; Intest and Sample) are supported, all others are ignored. Timing for this interface conforms to the IEEE 1149.1 specification.

[0139] The ARM/CPU module runs at 40.5 MHz and supports byte (8-bit), half-word (16-bit), and word (32-bit) data types. It reads instructions from on-chip ROM or from the extension bus. It can switch between ARM (32-bit) or Thumb (16-bit) instruction mode and has a 32-bit data and 32-bit address lines. It has 7 processing modes and two interrupts, FIQ and IRQ.

[0140] Preferably, the CPU 220 in the circuit 200 is a 32 bit RISC processor, the ARM7TDMI/Thumb, which has the capability to execute instructions in 16 or 32 bit format at a clock frequency of 40.5 MHz. Other RISC processors may be employed. The regular ARM instructions are exactly one word (32-bit) long, and the data operations are only performed on word quantities. However, LOAD and STORE instructions can transfer either byte or word quantities.

[0141] The Thumb uses the same 32 bit architecture with an 16-bit instruction set. That is, it retains the 32-bit performance but reduces the code size with 16-bit instructions. With 16-bit instructions, the Thumb still gives 70-80% of the performance of the ARM when running ARM instructions from 32-bit memory. ARM and Thumb are used interchangeably herein.

[0142] ARM uses a LOAD and STORE architecture, i.e. all operations are on the registers 221. ARM has 7 different processing modes, with 16 32-bit registers visible in user mode. In the Thumb state, there are only 8 registers available in user mode. However, the high registers may be accessed through special instructions. The instruction pipeline is three stage, fetch→decode→execute, and most instructions only take one cycle to execute. FIG. 15 shows the basic data path of ARM processor core.

[0143] The ARM CPU 220 is responsible for managing all the hardware and software resources in the circuit 200. At power up the ARM will verify the size of external memory. Following that, it will initialize all the hardware modules by setting up control registers, tables, and reset data pointers. It then executes the default firmware from internal ROM. A set of run-time library routines provides the access to the firmware and hardware for user application programs. The application programs are stored in external memory attached to the extension bus 300.

[0144] During normal operation the ARM constantly responds, based on a programmable priority, to interrupt requests from any of the hardware modules and devices on the extension bus. The kind of interrupt services include transport packet parsing, program clock recovery, traffic controller and OSD service requests, service or data transfer requests from the extension bus and Communication Co-Processor, and service requests from the audio/video decoders.

[0145] The traffic controller module 310 manages interrupt requests and authorizes and manages DMA transfers. It provides SDRAM interface and manages the extension bus 300. It provides memory access protection and manages the data flow between processors and memories such as: TPP/DES to/from internal Data RAM; Data RAM to/from extension bus; SDRAM to OSD; OSD to/from Data RAM; audio/video decoder to/from SDRAM; and SDRAM to/from Data RAM. It also generates chip selects (CS) for all the internal modules and devices on the extension bus 300 and generates programmable wait states for devices on the extension bus. It also provides 3 breakpoint registers and 64 32-bit patch RAM.

[0146] FIG. 16A depicts the various data flows managed by the traffic controller 310.

[0147] The SDRAM interface 313 supports 12 nanoseconds 16-bit data width SDRAM 312. It has two chip selects that allow connections to a maximum of two SDRAM chips. The minimum SDRAM size required for a fully functional video decoder is 16 Mbit. Other supported sizes and configurations are:

[0148] 16 Mbit→one 16 Mbit SDRAM

[0149] 20 Mbit→one 16 Mbit and one 4 Mbit SDRAM

[0150] 24 Mbit→one 16 Mbit and one 8 Mbit SDRAM

[0151] 32 Mbit→two 16 Mbit SDRAM

[0152] The access to the SDRAM can be by byte, half word, single word, continuous block, video line block, or 2D macroblock. The interface also supports decrement mode for bitBLT block transfer.

[0153] The two chip selects correspond to the following address ranges:

[0154] SCS1→0xFE00 0000−0xFE1F FFFF

[0155] SCS2→0xFE20 0000−0xFE3F FFFF

[0156] During decoding, the circuit 200 allocates the 16 Mbit SDRAM for NTSC mode according to Table 7.

[0157] However, it is also within the scope of the present invention to put the VBV buffer in optional memory on the extension bus 300 and thereby free up the SDRAM memory by the amount of the VBV buffer. This means that the SDRAM is allocated in a different manner than that of Table 7; that is the OSD memory size may be expanded or any of the other blocks expanded.

[0158] Interrupt requests are generated from internal modules like the TPP, OSD, A/V decoder and Communication Processor, and devices on the extension bus. Some of the requests are for data transfers to internal RAM, while others are true interrupts to the ARM CPU. The traffic controller handles data transfers, and the ARM provides services for true interrupts. The interrupts are grouped into FIQ and IRQ. The system software uses FIQ, while the application software uses IRQ. The priorities for FIQs and IRQs are managed by the firmware.

[0159] As noted in Table 7, the SDRAM 312 is used to store system level tables, video and audio bitstreams, reconstructed video images, OSD data, and video decoding codes, tables, and FIFOs. The internal Data RAM 240 stores temporary buffers, OSD window attributes, keys for conditional access, and other tables and buffers for firmware. The TC 310 manages two physical DMA channels, but only one of them, the General Purpose DMA, is visible to the user. The user has no knowledge of the DMAs initiated by the TPP, the video and audio decoders, and the OSD module. The General Purpose DMA includes ARM-generated and bitBLT-generated DMAs. The TC 310 can accept up to 4 general DMAs at any given time. Table 8 describes the allowable General Purpose DMA transfers.

[0160] Note that there is no direct DMA transfer to/from the extension bus memories from/to the SDRAM. However, the user can use the bitBLT hardware which uses Data RAM 240 as intermediate step for this purpose. The only constraint is the block being transferred has to start at a 32-bit word boundary.

[0161] FIG. 16B depicts the two interior blocks of the SRAM/ARM I/F block 311 of TC 310. More particularly, FIG. 16B depicts the SRAM hardware control block 311-1 and the ARM I/F block 311-2. FIG. 16C provides the details of block 311-2. Similarly, FIG. 16D provides the details of block 311-1.

[0162] As may be seen from FIG. 16C, the ARM I/F 311-2 includes a privilege decoder block 311-20 connected to a protection block 311-22. The protection block implements three levels of protection for the memory space of the ARM CPU 220. That is, firmware is allowed access to any memory, while the OS is allowed access to most memory; the application software (user mode) is only allowed access to restricted portions of the DRAM 312 and SRAM 240, but is allowed access to all other external memory. The chip select decoder block 311-24 determines from the ARM bus address the module, register, device or memory that is being addressed and generates a chip select (CS) for that address. In a similar manner, an interrupt control block handle interrupts from the modules or blocks in circuit 200.

[0163] A patch logic block 311-28 provides a way to load preselected values onto the bus when a certain address is selected. That is, this circuitry provides a patch from a portion of memory to a different locations, e.g. a patch RAM.

[0164] An SDRAM finite state machine 311-30 controls accesses to the SRAM 240. If the ARM tries to access the SRAM while it is busy, the ARM wait state generator 311-32 generates a signal to the ARM that essentially turns off its internal clock signal until the SRAM is available.

[0165] The remaining block 311-34 handles byte control for the SRAM. That is, it evaluates an ARM request to determine if the ARM is reading or writing a word, a half word (upper or lower) or a byte of data. It does this by evaluating the ARM control signals and selected ARM address positions.

[0166] FIG. 16D depicts the SRAM control block 311-1 and it includes a state machine 311-40 that interfaces with an extension bus interface (I/F) 311-42, a TCDRAM I/F 311-44, a TPP I/F 311-46 and a BitBLT I/F 311-48. It has available to it a TPP DMA table stored in a register 311-50 and a GEN DMA table stored in register 311-52.

[0167] The various states for the state machine 311-40 are depicted in FIGS. 16E-16M.

[0168] FIG. 16N depicts the interior blocks of the DRAM I/F 313 of the TC 310. More particularly, it may be seen that the DRAM I/F 313 includes an audio/visual I/F 313-10, an arbitration block 313-12, a data path control block 313-14, a data path block 313-10 and a DRAM I/F 313-16. FIG. 160 depicts the details of the A/V block 313-10. It depicts the video buffer and audio buffer management blocks, 313-30 and 313-32, respectively. The audio buffer is managed by the TC 310 hardware, while the video buffer is managed by the TC 310 hardware and video decoder 252 software. The video register file 313-34 allows the circuit 200 access to the video decoder busses and vice-versa. There is also depicted a video bus control state machine 313-36, that allows for single reads and writes and allows the video decoder 252 to cycle steal on the video decoder bus.

[0169] FIG. 16P depicts the various state machines in the DRAM I/F 313-16 of FIG. 16N that implement the various commands, line increment (lininc), line decrement (lindec) motion compensation (mc), video scan (vidscan) and refresh (refresh). These state machines generate the appropriate address and control signals to control the SDRAM 312.

[0170] FIG. 16Q depicts the data path block 313-18 of FIG. 16N. It provides the details of how data is passed to and from the SDRAM.

[0171] FIG. 16R depicts a block diagram illustrating additional details about arbiter block 313-12 of FIG. 16N. FIG. 16S depicts the state machine states for the state machine of this block. FIG. 16T illustrates timings for data path control (313-18) read and writes.

[0172] The TPP Module 210 parses transport bitstreams and accepts bitstreams either from the front end device or from the 1394 interface. It performs System Clock Reference (SCR) recovery and supports transport streams up to 40 Mbits-per-second. It accepts 8-bit parallel input data and supports storage of 32 PID/SCIDs. It provides lost-packet detection and provides decrypted or encrypted packets directly to the 1394 interface. It also provides an internal descrambler 212 for DSS with the Data Encryption Standard (DES) implemented in hardware.

[0173] The TPP 210 accepts packets on a byte by byte basis. Each packet contains a unique ID, PID/SCID, and the TPP extracts those packets containing the designated ID numbers. It processes the headers of transport packets and transfers the payload or auxiliary packets to the internal RAM 240 via the DES 212 hardware, if required. Special firmware running on the ARM 220 handles DES key extraction and activates DES operation. The ARM/CPU 220 performs further parsing on auxiliary packets stored in the internal RAM 240. The ARM 220 and TPP 210 together also perform SCR clock recovery. FIG. 17A is an example circuit for the external VCXO 80. The output from the circuit 200 is a digital pulse with 256 levels.

[0174] The conditional access and DES block 212 is part of the packet header parsing function. A CF bit in the header indicates whether the packet is clean or has been encrypted. The clean packet can be forwarded to the internal RAM 240 directly, while the encrypted one needs to go through the DES block 212 for decryption. The authorization and decryption key information are transmitted via control word packet (CWP). An external Smart Card 280-1 guards this information and provides the proper key for the DES 212 to work.

[0175] The 1394 interface 290 is directly connected to the TPP/DES module 210. At the command of the a program, the TPP/DES can send either clean or encrypted packets to the 1394 interface 290. The user can select up to 32 services to record. If the material is encrypted, the user also needs to specify whether to record clean or encrypted video. In a recording mode, the TPP 210 will appropriately modify the packet header if decrypted mode is selected; in encrypted mode, the packet headers will not be modified. During the playback mode, the 1394 interface 290 forwards each byte as it comes in to the TPP 210. The TPP 210 parses the bitstream the same way it does data from the front end.

[0176] The MPEG2 transport stream parser (TPP) receives the MPEG transport stream and selects video, audio or services information packets. After decoding, the packets are stored to memory buffers to form a data stream. The audio decoder 254 processes the MPEG audio stream and produces an analog audio signal. The video decoder 252 decompresses the MPEG video and generates a video sequence.

[0177] As depicted in FIG. 17B, a transport packet (A) contains 188 bytes. The packet is divided in two parts, a 32-bit header and 184 bytes of payload. The transport header contains different fields (PID, payload unit start indicator, adaptation field flags, continuity counter index) that will allow the transport packet parser to do a coarse filter. After the transport header, the packet can contain an adaptation field of variable length for a payload. Some of these payloads will themselves start with a header (PES header) B which has also a variable length. The PES header in MPEG2 standard can be bigger than a packet (overflow on the next packet).

[0178] The current state of the art for MPEG2 transport stream system analyzer consists of chip set solution including a complete transport stream hardware analyzer and an associated micro-processor and memory. The video and audio decoder are separate devices, as shown in the FIG. 17C. The transport stream parser is in charge of the transport stream full analysis with the current approach leaving to the CPU the tasks of directing the data towards the right destination and controlling the different modules. Another solution would be to implement all the transport analysis in software; however, this solution would require much higher CPU processing power.

[0179] The approach for the transport stream parser of the present invention splits the load of the transport stream and MPEG2 analysis between hardware and software to make the analysis more effective. Hardware filtering allows an early decision to be taken based on PIDs recognition; it reduces the data stream very efficiently allowing the firmware to execute much more complex filtering algorithms on the reduced data stream. This approach optimizes the resources. The hardware stays simple while the firmware needs less CPU power because the bit rate it receives has been pre-processed by the hardware.

[0180] The parsing and routing of the packets are done with a PID recognition mechanism coupled with a set of attributes stored in a local memory for each PID. These attributes complete the information received from the different headers.

[0181] The transport parser module immediately discards all packets which are not selected by the application, and routes as many packets as possible without “real time” help from the firmware.

[0182] Once a packet with a valid PID has been detected, the parser checks the condition set which determines if the packet needs further processing by the CPU 220 (see description of EOP interrupt generation later herein). If one of these conditions is met, the packet is sent to a temporary buffer with an attached flag (indicating that further processing is required) and an interrupt EOP is sent to the CPU to indicate that a new packet has been received. Data stored in this temporary buffer is then processed by the firmware before it can be routed or discarded as shown in path (2) of FIG. 17D. Once the data have been processed, the CPU 220 transfers the data itself or initiates DMA transfers to the system buffer in memory 240. The software is also going to modify in some cases some of the PID attributes (ex: stream-id filter) to modify the routing of the following packet (e.g. one with the same PID). If none of the conditions are met, the attached flag indicates that no additional processing is required. The packet can then be automatically forwarded (via path (1) in FIG. 17D) to its final destination via automatic DMA transfers (e.g.: packets containing compressed video information can be sent directly to the system video buffer, . . . ). In this case, no EOP interrupt is sent to the CPU 220 and the packet transfer to the final destination does not require any CPU resource.

[0183] FIG. 17D shows the two different data flows; one with CPU intervention, path (2), and one with no intervention, path (1).

[0184] FIG. 17D is the key for the trade-off between hardware and software. The transport stream parser can very easily route the packets and let the CPU do more complex analysis on some parts of the bit stream.

[0185] Again, this selection is done by analyzing the header (PID, AF flag, PES/PSI start flag [payload unit start indicator], transport error flag, counter continuity index), and the PID attributes because the choice can not always be done by extracting information from the packet itself as depicted in FIG. 17E. Sometimes, the nature of the previous packet (same PID) will determine if the packet needs additional processing (PES header split between two packets). Sometimes, it is linked to the PID number. If a PID contains table information for instance that always require CPU processing then the attribute Spei is set (means that packets with this PID will always be sent to the CPU). The list of information used to generate the EOP interrupt is summarized in FIG. 17E and described below.

[0186] FIG. 17E shows where the information comes from. The conditions to generate the EOP are described later herein.

[0187] The following is a description of the bits in Packet Analyzer Control Register.

[0188] Valid PID: This bit is the result of the PID recognition function. The PID number is the packet identification number received in the transport stream header of each packet. It determines if a packet must be transmitted to the system or not. If the PID number has been selected, the Valid_PID bit goes active ‘1’ when a packet with this PID number is received. It is the first level of packet filtering and the necessary condition for the other analysis steps.

[0189] Te (transport error indicator): This is retrieved from the Transport Stream packet header. The transport error indicator bit is active when the packet received contains some errors.

[0190] Pes/Psi start flag (transport stream payload start-unit-indicator): This is retrieved from the Transport Stream packet header.

[0191] When the payload of the Transport stream contains a PES packet data. A ‘1’ indicates that the payload of this Transport stream packet will commence with the first byte of the PES packet (PES header) and a ‘0’ indicates that no PES packet starts in this Transport Stream Packet.

[0192] When the payload of the Transport Stream packet contains PSI data. A ‘1’ means that the payload carries at least one beginning of a PSI section and a ‘0’ if no start of a PSI section is carried is this Transport Stream packet.

[0193] AF flag (transport stream adaptation field): This two bit field of the Transport Stream header indicates whether the Transport Stream header is followed by an adaptation field or not.

[0194] CC-error: This bit is the result of the hardware discontinuity counter detection function on the continuity counter (CC). The detection is done with a comparison between the CC (4-bits contained in the Transport Stream header) called the Current_CC and the CC from the previous packet of the same PID (called Previous_CC). The Previous_CC is an attribute modified by the hardware. Once the comparison is done, the hardware overwrites the Previous_CC with the Current_CC for the reception of the next packet and so on. If the comparison does not match Current_CC=Previous_CC or Current_CC=Previous_CC+1, the CC_error bit goes active.

[0195] Duplicate-packet flag: If the comparison indicates that Current_CC=Previous_CC the Duplicate-packet goes active.

[0196] Hpei (Hardware End of packet enable interrupt): This is an attribute bit set by Hardware. At reception of a new packet (when packet unit start indicator is active and when it is not a packet with-program service information PSI) the Hpei goes active and is reset on the following packet of the same PID. It forces the packet following a packet with a PES header to be temporarily stored in a buffer for further analysis in case the PES header would be split between two packets. This bit is necessary when the bit rate of the incoming bit stream is two high to fit within the EOP service routine latency.

[0197] Spei (Software End of packet enable interrupt): This attribute bit is set by software and covers two different purposes. First, the bit is set at initialization for PID which always requires CPU processing (PID with table information for instance). It is simply used in that case to force all the packets of this PID to be analyzed by the CPU.

[0198] The second usage is for audio and video packets whose PES header would be split between two packets. This is only valid for some given system, once the software has determined that its latency response is compatible with the bit stream rate. In that case the software sets the Spei as soon as it receives the EOP interrupt of a packet containing a PES header. It determines afterwards if the PES header overflows on the next packet. If it does not, it resets the Spei attribute bit. In this case the Spei can replace the Hpei which is disabled to gain in efficiency (see En_Hpei).

[0199] PSI (program service information packet flag): In MPEG2 transport stream, one flag in the transport stream header (payload unit start indicator) indicates the start of a new PES packet or the start of a section of a program service information. In order to differentiate these two types of data another attribute is needed (PSI). This attribute is set by the firmware at initialization for PIDs containing program service information(PSI).

[0200] It is used to generate Hpei and for the detection of the boundary between encrypted/clean bytes. Without this information tightly coupled with the PIDs, the controller could not timely find the encryption flags nor the boundary between encrypted/clean byte without some significant input buffers on the bit stream interface.

[0201] Stream-id-filter: This software attribute bit is set by software when it receives a packet containing a PES header with a non selected stream-id. Once this attribute is set, the hardware discards all the packets of this PID containing only payload (AF=“1x”) until it reaches a new PES header. The packet is sent to the CPU which analyzes the PES header and determines if the new stream-id is valid. If it is, it resets the stream-id-filter for the following packets.

[0202] En Hpei: This is a global control bit. The Hpei mechanism can be switched off/on depending on the constraint of the system. If the software determines that it has enough time to react and modify the Spei attribute bit before the reception of the next packet, it can disable the Hpei attribute. The bit stream parsing is more efficient in that case because the packet following a packet with a PES header is only sent to the CPU for further analysis when the PES header is not fully contained in one packet.

[0203] En erroneous p: This global control bit enables transmission of erroneous packets to the temporary buffer. This is mainly to add some flexibility in case some new error concealment is found in the future.

[0204] En duplicate p: This global control bit enables transmission of duplicate packet containing only payload. It is only used for test purposes.

[0205] FIG. 17F shows the hardware implementation based on PID recognition. The PID from the Transport packet header 210-5 is compared in parallel with a set of PIDs (32) located in an associative memory 210-10. If the PID in the header corresponds to a PID stored in the associative memory, the CAM encoder outputs a “match” signal (Valid-PID) 210-12 and a CAM address (cam-ad) 210-14 in a single system clock period. The valid-PID is used to initiate the transport stream packet analysis and it enables the process to load the others bits coming from the transport stream headers: AF-load (transport-error, payload-unit-start-indicator, adaptation field flag, continuity counter index and other like encryption flags reserved for the control of the decryption module).

[0206] As soon as a valid PID is detected, the cam-ad 210-14 is used to look for the associated attributes. The sequencer 210-16 generates Read-SRAM-attributes to start the state machine controlling the SRAM address generator. The state machine creates the SRAM 240 address from the cam-ad, it reads the SRAM two times, once to retrieve the hardware attributes and a second time to read the software attributes (splitting hardware modified attributes and software modified attributes avoids the use of a complex protection mechanisms).

[0207] From both attributes and bit-stream information (bits from headers), the conditions required to generate a EOP interrupt are evaluated. The hardware attributes are then updated for the reception of the next packet (same PID). The software attributes can be updated as part of the EOP interrupt service routine but only for some very precise function (like stream-id-filter). If the attributes need to be modified before the start of the next packet, then the bit rate, the gap between packets and the interrupt routine service latency must respect some constraints to allow this to occur.

[0208] Depending on the Packet analyzer control bits (FIG. 17E), the packet is going to be discarded, automatically transmitted to its final destination or processed by the firmware. When one of these conditions to generate an EOP interrupt is met, the bit controlling the interrupt goes active and is reset on the first byte of the following packet. EOP interrupt enable controls the position of the interrupt relative to the end of the packet. The different conditions generating the EOP interrupt 210-20 (FIG. 17E: logic block) are described below.

[0209] Note that all these conditions evaluated sequentially by the foregoing are in fact computed in parallel by the hardware.

[0210] Once the EOP interrupt conditions are met the CPU 220 takes on the analysis task. The microprocessor 220 can perform a more complex analysis than the Transport Packet Parser hardware module and will complete the hardware pre-processing. In addition, the processing can differ according on the type of data that corresponds to the packet; in fact, it is very easy to define a software table, based on the PID values, that associates the packet with the particular processing to be used.

[0211] The software processing of the transport packet is driven by interrupts; once an EOP interrupt is issued, the process that analyzes the packet is started. Two different methods of processing can be selected, according to the CPU latency response and the bit stream rate.

[0212] In first case the software sets the Spei flag in the TPP hardware module as soon as it receives the EOP interrupt of a packet containing a PES header. After processing the packet, the software can detect whether the PES header continues in the following transport packet or not; if the PES header ends in the current packet, the CPU resets the Spei bit in the Packet Analyzer Control Register, since it does not need to analyze the following packet. Otherwise the Spei bit is left unchanged. This method can be used only if the CPU latency, compared with the input bit rate, allows the Spei to be set before the arrival of the following packet.

[0213] The second method can be used in any case: If the En_Hpei bit is set in the Packet Analyzer Control Register, the CPU does not have to set the Spei bit after each PES header, because the TPP hardware already provides for sending to the ARM processor the packet including the PES header continuation.

[0214] Afterwards the reason of the interrupt is found by reading the flags in the registers of the TPP hardware module; if the adaptation field is present, it is processed.

[0215] After the adaptation field analysis the packet can be discarded if there is no payload or the payload is duplicated from the previous packet.

[0216] At this point the execution of the software process branches into separate routines, according on the packet type (audio, video, private data, service information, . . . ). Then the data are transferred via a DMA channel to a specific buffer.

[0217] FIG. 17G depicts a flowchart that can be used to analyze the packet. The first point in the following list (check of the Pes/Psi start flag and setting of the Spei flag) is optional.

[0218] In fact, as mentioned before, if the software latency is short enough to allow the Spei bit to be set before the TPP hardware module analyzes the following transport packet, this operation will minimize the CPU intervention; an EOP interrupt will be sent to the microprocessor only if the packet following a PES header start has to be processed indeed.

[0219] Otherwise, if the bit rate of the incoming stream and the CPU latency are too high, the Hpei mechanism can be enabled (En_Hpei=1); the next packet with the same PID following a PES header starting point will be always transmitted to the CPU.

[0220] Check if a PES header starts 17-1 in the current transport packet by reading the Pes/Psi start flag in the Packet Analyzer Control Register (Packet Status Word).

[0221] If a PES header starts in the current transport packet, the Spei bit 17-2 in the Packet Analyzer Control Register has to be set by the CPU in order to intercept the next packet with the same PID; further, the PES header could continue in the following transport packet.

[0222] Check the presence of the adaptation field 17-3 by reading the AF flag in the Packet Analyzer Control Register: Packet Status Word.

[0223] If the adaptation field is transmitted into the packet, the associated data have to be processed. In particular, the PCR has to be extracted and filtered in order to control the reconstruction of the reference clock. Another important part consists of the analysis of the discontinuity status 17-4; if the discontinuity status bit in the adaptation field is set, a discontinuity in the continuity counter value does not correspond to a missing packet. If the discontinuity status is set, the local clock has to be re-initialized 17-5 to the PCR value, if present.

[0224] Check if the packet is duplicated by reading the duplicate packet flag 17-6 in the Packet Analyzer Control Register.

[0225] If the packet is duplicated, it is discarded 17-7; since no other processing is required. If the Spei bit has been modified at the beginning of the packet 17-8 because there is a PES header and the Hpei method is not used, the Spei bit has to be cleared 17-9 before the end of the process.

[0226] Check if the packet contains a transport payload by reading the AF flag 17-10 in the Packet Analyzer Control Register.

[0227] If there is no payload (adaptation field only) the packet is discarded, since no other processing is required.

[0228] This “check the packet” part of the flow diagram is based on a table that associates each selected PID to a particular type of processing to be performed; in this way, the packet is processed by the related routine. The table contains 32 entries, one for each possible selected PID: each entry allows identification of the packet type (i.e. audio packet, video packet, PES private date, PSI, etc.) and the memory address where the data is to be stored. In particular, if the packet type corresponds to a video stream or to an audio stream (in general to an automatic DMA transfer) and the Hpei mechanism is not used, after the packet processing the Spei bit has to be cleared 17-13 if the PES header 17-12 is finished. The data after processing are finally transmitted, via DMA 17-20, to the specific memory buffer.

[0229] For the complete flow chart shown in FIG. 17G; the black modules correspond to the logical blocks of the flow chart that are executed only if the Hpei mechanism is disabled.

[0230] For example, if the transport stream for a video decoder does not analyze the PES syntax.

[0231] In this case only the video elementary stream is sent to the video decoder; the PTS value is extracted and written into a register of the video decoder. All the other fields that could be included in the PES header are not considered, as it is allowed by the DVB recommendations. FIG. 17H describes the structure of the PES packet.

[0232] The following steps are used to process the PES packet. The first part of the PES header is stored in a temporary buffer in order to process the interesting fields: if the header is split among different packets, the process continues after the second packet is received and the first bytes of the header have to be written into the temporary buffer.

[0233] This example explains only the part related to the PES analysis. For the other part of the CPU processing, the process described earlier herein applies.

[0234] Before enabling the PID selection of the TPP hardware module the flags of the TPP control register are initialized as follow:

[0235] The process can also be explained by the following pseudo-code.

[0236] PesStatus indicates the status of the PES header processing of the previous status (0=the PES header is finished; 1=the PES header continues from the previous packet and it has not been analyzed yet; 2=the PES header continues from the previous packet and all the useful fields have already been analyzed).

[0237] PreviousSize indicates the length of the PES header that has been analyzed in the previous packet and, after the update, the size of the PES packet that has been analyzed in the previous packet plus the size of the PES packet included in the current transport packet.

[0238] In this case the packet is sent to the CPU only when the PES header is present: the occurrence can be easily found by checking the value of the PUS indicator in the transport packet header.

[0239] Suppose that the video stream is coded in frames with a bit rate of 15 Mbps, if the CPU has to process each packet, it will be interrupted about every 100 μsec.

[0240] On the contrary, by using the preliminary filter and routing performed by the TPP hardware, the CPU is interrupted only for each PES packet; if the PES packet length is equivalent at least to the frame size, the interrupts are generated, in the worst case, each 40 ms.

[0241] For example, the transport stream for an audio decoder analyzes the PES syntax and a filter on the stream-id field is performed. In this example, the audio decoder can analyze the PES packet but the CPU has to filter all the PES packet with a stream-id different from a specific value, if the stream-id is identical.

[0242] The general flow shown in FIG. 17G and described previously herein is used; the following part describes only the specific part of the processing related to the audio PES packet. In particular, the Hpei mechanism is disabled, so the CPU sets the Spei flag every time a transport packet containing the starting point of a PES header is received.

[0243] Before enabling the PID selection of the TPP hardware module the flags of the TPP control register are initialized as follow:

[0244] After the initialization, the TPP hardware module discards all the packets until the first PES header is received. At this point an EOP interrupt is issued and the CPU analyze the packet.

[0245] If the stream-id value matches a specific pattern, all the PES packet has to be sent to the audio decoder; as a consequence the CPU 220 clears the stream-id filter flag in the Packet Analyzer Control Register and all the transport packets are automatically transmitted to the audio decoder 254. When another PES header is found by the TPP hardware (the packet unit start indicator in the transport header is set), an interrupt is generated and the CPU can perform another filter operation on the stream-id value of the new PES packet.

[0246] If the stream-id value does not match the specified pattern, the CPU sets the stream-id flag in the TPP module and all the following transport packets with the same PID are automatically discarded by the hardware until the next PES header.

[0247] The process can also be explained by the following pseudo-code. The CPU does not analyze all the PES header, but only the stream-id field.

[0248] PesStatus indicates the status of the PES header processing of the previous status (0=the PES header is finished or the PES header continues from the previous packet but the stream-id value has been already filtered; 1=the PES header continues from the previous packet and the stream-id value has not been filtered yet).

[0249] PreviousSize indicates the length of the PES header that has been read in the previous packet.

[0250] At this point the Spei bit is cleared only if PesStatus is equal to zero, since the considered part of the PES header has been already processed.

[0251] In this case an interrupt is sent to the CPU only when the PES header is present in order to filter the stream-id value. If the stream-id matches the selected value, the following packets are automatically transmitted to the destination buffer; on the contrary, if the stream-id does not match the selected value all the following packets are discarded by the TPP hardware module until the next PES header.

[0252] Without this mechanism, the CPU would be forced to receive an interrupt to discard all the transport packets that are included in a PES packet with an unwanted value of stream-id.

[0253] FIG. 17I depicts a high-level block diagram of the presently preferred details of the TPP 210 of FIG. 1B. More particularly, it may be seen that the TPP 210 includes the TPP functional block 210-15, a DES functional block 210-25, a DVCR/1934 block 210-30, a DAC 210-40 and a CPU interface 210-50. The TPP block 210-15 performs the functions noted earlier herein. The DES block 210-25 performs any needed decryption. The DVCR/1394 block 210-30 provides data streams to the 1294 connections and/or a digital VCR. The DAC 210-40 is for controlling the VCXO.

[0254] FIG. 17J depicts various DSS bitstream packets and their contents.

[0255] FIG. 17K depicts preferred circuit for implementing portions of the blocks depicted in FIG. 17I. More particularly, it may be seen how input multiplexors may be employed to switch the input between a DVB or DSS signal. It further illustrates how the header information/data may be temporarily stored in registers and shifted out to perform the header analysis described earlier herein. In addition, it may be seen how incoming data may be buffered in small registers before being sent out as valid data in “bursts” during and following the header analysis; this assumes the header analysis indicates the data is to be stored for subsequent processing.

[0256] FIGS. 17L and 17M depict state machines that control the operations of the TPP block. More particularly, FIG. 17L depicts two basic operations; it depicts a “clean” packet to the TC in the upper right portion and an encrypted packet to the IT in the lower left portion. State S20 is the “idle” state of the state machine. In FIG. 17L, “muxheaderdata” controls the multiplexor between the TPP header and the first data word. FIG. 17M depicts an attribute request and writeback series of states that are in the upper left and start with S10. The remainder of FIG. 17M details other transfers.

[0257] FIG. 17N depicts the details of the DAC block 210-40 of FIG. 17I.

[0258] FIG. 17O depicts the various signals associated with the TPP and its interface with the CPU 220.

[0259] FIG. 17P depicts more details of the block 210-30 of FIG. 17I. More particularly, it illustrates the presence of a record and play state machine and registers that a VCR may write to.

[0260] The video decoder module 252 provides real-time video decoding of MPEG-2 Main Profile Main level and MPEG-1, error detection and concealment, an internal 90 KHz/27 MHz System Time Clock and a sustained input rate of 16 Mbps. It supports Trick Mode with full trick mode picture and provides ¼ and {fraction (1/16)} decimated size picture. It extracts Closed Caption and other picture user data from the bitstream, has 3:2 pulldown in NTSC mode, and supports the display formats in Table 10 with polyphase horizontal resampling and vertical chrominance filtering.

[0261] Pan-and-scan for 16:9 source material according to both DSS and MPEG syntax; high level command interface; and synchronization using Presentation Time Stamps (PTS).

[0262] The video decoder module 252 receives a video bitstream from SDRAM 312. It also uses SDRAM as its working memory to store tables, buffers, and reconstructed images. The decoding process is controlled by an internal RISC processor which accepts high level commands from the ARM. A more detailed description of the decoder 252 is found in U.S. Pat. No. 5,379,356, which is incorporated herein by reference. In this fashion, the ARM is acting as an external host to initialize and control video decoder module. The output video is sent to the OSD module for further blending with OSD data. Exemplary video decoders are disclosed in U.S. Pat. Nos. 5,608,459, 5,270,832, 5,253,078, 5,196,946 and 5,191,548, which are incorporated by reference herein.

[0263] Besides normal bitstream decoding, the video decoder 252 also extracts from the picture layer user data the Closed Caption (CC), the Extended Data Services (EDS), the Presentation Time Stamps (PTS) and Decode Time Stamps, the pan_and_scan, the fields display flags, and the no_burst flag. These data fields are specified by the DSS. The CC and EDS are forwarded to the NTSC/PAL encoder module 260 and the PTS is used for presentation synchronization. The other data fields form a DSS-specific constraints on the normal MPEG bitstream, and they are used to update information obtained from the bitstream.

[0264] When the PTS and SCR (System Clock Reference) do not match within tolerance, the video decoder 252 will either redisplay or skip a frame. At that time, the CC/EDS will be handled as follows: if redisplaying a frame, the second display will not contain CC/EDS; if skipping a frame, the corresponding CC/EDS will also be skipped. During trick mode decoding, the video decoder repeats the following steps: searches for a sequence header followed by an I picture; ignores the video buffer underflow error; and continuously displays the decoded I frame.

[0265] Note that trick mode I frame data has to contain the whole frame instead of only several intra slices.

[0266] The video decoder 252 accepts the high level commands listed in Table 11.

[0267] Table 12 shows the aspect ratio conversions that are presently preferred.

[0268] The Pan-Scan method is applied when displaying a 16:9 source video on a 4:3 device. The Pan-Scan location specifies the 1, ½, or ¼ sample if the source video has the full size, 720/704×480. If the sample size is smaller than full then the Pan-Scan location only specifies to an exact integer sample. Note that the default display format output from circuit 200 is 4:3. Outputting 16:9 video is only available when the image size is 720/704×480. A reset is also required when switching between a 4:3 display device and a 16:9 one.

[0269] The ½ and ¼ decimation, in each dimension, is supported for various size images in 4:3 or 16:9 format. Table 13 provides the details for the decimation modes.

[0270] The audio decoder module 254 decodes MPEG audio layers 1 and 2 and supports all MPEG-1 and MPEG-2 data rates and sampling frequencies, except half frequency. It provides automatic audio synchronization and supports 16- and 18-bit PCM data. It outputs in both PCM and SPDIF formats and generates the PCM clock or accepts an external source. It provides error concealment (by muting) for synchronization or bit errors and provides frame-by-frame status information.

[0271] The audio module 254 receives MPEG compressed audio data from the traffic controller 310, decodes it, and outputs audio samples in PCM format. The ARM CPU 220 initializes/controls the audio decoder 254 via a control register and can read status information from the decoder's status register.

[0272] Audio frame data and PTS information are stored in the SDRAM 312 in packet form. The audio module 254 will decode the packet to extract the PTS and audio data. The details of the audio decoder may be found in co-pending and commonly-owned U.S. Pat. No. 5,644,310, U.S. patent application Ser. No. 08/475,251, filed Jun. 7, 1995, a continuation of U.S. patent application Ser. No. 08/021,007, filed Feb. 22, 1993 and now abandoned; U.S. Pat. No. 5,729,556, U.S. patent application Ser. No. 08/054,127, filed Apr. 26, 1993; U.S. Pat. No. 5,642,437, U.S. patent application Ser. No. 08/054,126, filed Apr. 26, 1993; U.S. Pat. No. 5,608,459, U.S. patent application Ser. No. 08/107,098, filed Aug. 13, 1993; U.S. Pat. No. 5,657,423, U.S. patent application Ser. No. 08/054,768, filed Apr. 26, 1993; U.S. Pat. No. 5,845,239, U.S. patent application Ser. No. 08/964,092, filed Nov. 4, 1997, a continuation of U.S. patent application Ser. No. 08/100,591, filed Jul. 30, 1993 and now abandoned; and U.S. Pat. No. 5,425,061, filed Jun. 7, 1993.

[0273] The ARM 220 can control the operation of the audio module via a 32-bit control register. The ARM may reset or mute the audio decoder, select the output precision and oversampling ratio, and choose the output format for dual channel mode. The ARM will also be able to read status information from the audio module. One (32-bit) register provides the MPEG header information and sync, CRC, and PCM status. Exemplary audio decoders are disclosed in U.S. Pat. Nos. 5,657,454 and 5,644,310, which are incorporated by reference herein.

[0274] The audio module has two registers: a read/write control register and a read-only status register. The registers are defined in Table 14 below.

[0275] The OSD module 270 supports up to 8 hardware windows, one of which can be used for a cursor and all the non-overlapped windows can be displayed simultaneously. The overlapped windows may be displayed obstructively with the highest priority window on top. The OSD provides a hardware window-based rectangle cursor with programmable size and blinking frequency and provides a programmable background color, which defaults to blue. It supports 4 window formats (empty window for decimated video; bitmap; YCrCb 4:4:4 graphics component; and YCrCb 4:2:2 CCIR 601 component) and supports blending of bitmap, YCrCb 4:4:4, or YCrCb 4:2:2 with motion video and with an empty window. It supports window mode and color mode blending and provides a programmable 256 entries color look up table. It outputs motion video or mixture with OSD in a programmable 422 or 444 digital component format and provides motion video or mixture with OSD to the on-chip NTSC/PAL encoder 260 and provides graphics acceleration capability with bitBLT hardware 272.

[0276] Each hardware window has the following attributes: window position (any even pixel horizontal position on screen; windows with decimated video have to start from an even numbered video line also); window size: from 2 to 720 pixel wide (even values only) and 1 to 576 lines; window base address; data format (bitmap, YCrCb 4:4:4, YCrCb 4:2:2, and empty); bitmap resolution (1, 2, 4, and 8 bits per pixel); full or half resolution for bitmap and YCrCb 4:4:4 windows; bitmap color palette base address; blend enable flag; 4 or 16 levels of blending; transparency enable flag for YCrCb 4:4:4 and YCrCb 4:2:2; and output channel control.

[0277] The OSD module 270 is responsible for managing OSD data from different OSD windows and blending them with the video. It accepts video from the video decoder 252, reads OSD data from SDRAM 312, and produces one set of video output to the on-chip NTSC/PAL encoder 260 and another set to the digital output that goes off-chip. The OSD module 270 defaults to standby mode, in which it simply sends video from the video decoder 252 to both outputs. After being activated by the ARM CPU 220, the OSD module 270, following the window attributes set up by the ARM, reads OSD data and mixes it with the video output. The ARM CPU 220 is responsible for turning on and off OSD operations. The bitBLT hardware 272 which is part of the OSD module 270 provides acceleration to memory block moves and graphics operations. FIG. 18 shows the block diagram of the OSD module. The various functions of the OSD module 270 are described later herein.

[0278] OSD data has a variable size. In the bitmap mode, each pixel can be 1, 2, 4, or 8 bits wide. In the graphics YCrCb 4:4:4 or CCIR 601 YCrCb 4:2:2 modes, it takes 8-bits per component, and the components are arranged according to 4:4:4 (Cb/Y/Cr/Cb/Y/Cr) or 4:2:2 (Cb/Y/Cr/Y) format. In the case where RGB graphics data needs to be used as OSD, the application should perform software conversion to Y/Cr/Cb before storing it. The OSD data is always packed into 32-bit words and left justified. Starting from the upper left corner of the OSD window, all data will be packed into adjacent 32-bit words. The dedicated bitBLT hardware 272 expedites the packing and unpacking of OSD data for the ARM to access individual pixels, and the OSD module 270 has an internal shifter that provides pixel access.

[0279] In NTSC mode, the available SDRAM 312 is able to store one of the following OSD windows with the size listed in Table 15, with the current and proposed VBV buffer size for DSS. Although as noted earlier herein, the VBV buffer may be placed in optional memory on the external bus 300, which provides more OSD room in the SDRAM 312.

[0280] An OSD window is defined by its attributes. Besides storing OSD data for a window in SDRAM 312, the application program also needs to update window attributes and other setups in the OSD module 270 as described below.

[0281] The CAM memory 270-40 contains X and Y locations of the upper left and lower right corners of each window. The application program needs to set up the CAM and enable selected OSD windows. The priority of each window is determined by its location in the CAM. That is, the lower address window always has higher priority. In order to swap the priority of windows, the ARM has to exchange the locations within the CAM.

[0282] The OSD module keeps a local copy of window attributes 270-110. These attributes allow the OSD module to calculate the address for the OSD data, extract pixels of the proper size, control the blending factor, and select the output channel.

[0283] Before using bitmap OSD the application program has to initialize the 256 entry color look up table (CLUT) 270-110. The CLUT is mainly used to convert bitmap data into Y/Cr/Cb components. Since bitmap pixels can have either 1, 2, 4, or 8 bits, the whole CLUT can also be programmed to contain segments of smaller size tables, such as sixteen separate, 16-entry CLUTs.

[0284] There are two blending modes. The window blending mode applies to the type of OSD window, e.g., YCrCb 4:4:4, and YCrCb 4:2:2. The color blending mode is pixel by pixel and is preferably only allowed for the bitmap OSD. Blending always blends OSD windows with real time motion video. That is, there is no blending among OSD windows except the empty window that contains decimated motion video. In case of overlapping OSD windows the blending only occurs between the top OSD window and the video. The blending is controlled by the window attributes, Blend_En (2-bit), Blend Level (4-bit), and Trans_En (1-bit). Blend_En activates blending as shown in Table 16.

[0285] In window mode all pixels are mixed with the video data based on the level defined by the attributes Blend Level. In the color mode the blending level is provided in the CLUT. That is, the least significant bit of Cb and Cr provides the 4 level blending, while the last two bits from Cb and Cr provide the 16 level blending. Transparency level, no OSD but only video, is achieved with the Trans_En bit on and the OSD pixel containing all Os.

[0286] A rectangular blinking cursor is provided using hardware window 0. With window 0, the cursor always appears on top of other OSD Windows. The user can specify the size of the cursor via a window attribute. The activation of the cursor, its color, and blinking frequency are programmable via control registers. When hardware window 0 is designated as the cursor, only seven windows are available for an application. If the hardware cursor is not used, then the application can use window 0 as a regular hardware window.

[0287] After the OSD windows are activated, each of them has an attribute, Disp_Ch_Cntl[1,0], that defines the contents of the two output channels (the analog and digital video outputs) when the position of that window is currently being displayed. Table 17 shows the controls for the output channels.

[0288] Example displays of these two output channels are shown in FIG. 19.

[0289] The bitBLT hardware 272 provides a faster way to move a block of memory from one space to the other. It reads data from a source location, performs shift/mask/merge/expand operations on the data, and finally writes it to a destination location. This hardware enables the following graphics functions: Set/Get Pixel; Horizontal/Vertical Line Drawing; Block Fill; Font BitBLTing; Bitmap/graphic BitBLTing; and Transparency.

[0290] The allowable source and destination memories for bitBLT 272 are listed in Table 18.

[0291] The types of source and destination OSD windows supported by the bitBLT 272 are the given in the following table (“HR” stands for half resolution).

[0292] Since the bitmap allows resolutions of 1, 2, 4, or 8 bits per pixel, the bitBLT will drop the MSB bits or pad it with 0s when swapping between windows of different resolution. For half-resolution OSD, the horizontal pixel dimension must be even numbers. For YCrCb 4:2:2 data, the drawing operation is always on 32-bit words and two adjacent pixels that align with the word boundary.

[0293] In a block move operation, the block of data may also be transparent to allow text or graphic overlay. The pixels of the source data will be combined with the pixels of the destination data. When transparency is turned on and the value of the source pixel is non-zero, the pixel will be written to the destination. When the value of the pixel is zero, the destination pixel will remain unchanged. Transparency is only allowed from bitmap to bitmap, and from bitmap to YCrCb 4:4:4.

[0294] The following describes how the OSD 270 may be employed to provide OSD with variable resolution. FIG. 18B shows the global flow to decode and display an OSD picture. The PSI buffer 312acontain the coded picture, for example: a Teletext data to be displayed within an OSD picture. The CPU 220 decodes (1) the Teletext data and build (2) the OSD picture using the Bitblt hardware 272 accelerator. The OSD controller 270 reads (3) the OSD buffer 312band generates the OSD video that is mixed with MPEG video (4).

[0295] Different modes are displayed simultaneously on the screen: a bit map-window 1000 with 2 colors, a still video picture 1010, a 256 colors graphic window 1020, a decimated motion video picture 1030 and a Logo 1040 in true color. The OSD controller 270 minimizes the memory required to display service information. The OSD uses a new hardware windowing technique to mix different mode of display such as: Bit map with variable resolution, graphic plane, still video picture and decimated motion video.

[0296] FIG. 18C shows the various modes of display that circuit 200 may employ.

[0297] In a bit map mode 1050, the frame buffer contains the code of the color of each pixel to be displayed. The number of bit per pixel defines the number of the colors that can be displayed on screen. Two colors require 1-bit per pixel and 256 colors require 8-bit per pixel. This mode is used to display graphic and text. The code of the color addresses the color look up table that contain the three color components with 8-bits each.

[0298] Graphic plane, 4:4:4 mode 1060, uses 8_bit per pixel for each color component R,G,B or Y,Cr,Cb. Each pixel requires24-bit (16 million colors per pixel).

[0299] With the 4:2:2 mode 1070 the resolution of the chroma is divided horizontally by two. Each pixel has a luminance component Y and alternately a chrominance component Cr or Cb. This mode is used for video still or motion picture. Each pixel requires 16-bit.

[0300] With the 4:2:0 mode 1080 the resolution of the chroma is divided by two horizontally and vertically. Each pixel has a luminance component Y and a chrominance component Cr and Cb for 4 pixels. This mode is used by the MPEG video decoder to the size of the memory required to store a video motion picture. Each pixel requires 12-bit. The chroma interpolator generates the 4:2:2 output format.

[0301] Table 20 shows the number of bytes required to store .a full screen picture 720 pixels ×576 lines in different display modes for an OSD system that does not allows to mix several modes of display in real time on same screen. When one part of the screen requires 256 colors, the full screen must be 256 colors even if a part of the screen requires only 2 colors.

[0302] The OSD controller 270 can display several modes described above simultaneously on the same screen. Each part of the screen with different display modes uses a windows fully programmable in size, in position and priority level. The windows can be overlapped without limitations. The characteristic of each window is defined by a set of attributes stored in SRAM 240. Those attributes are used to calculate the memory address in real time during display and to control the hardware display system.

[0303] FIG. 18D shows typical OSD pictures. The left screen is composed of 5 OSD windows with different characteristics displayed on a full screen background color 1110:

[0304] a bit-map window 1100 having 360 pixels by 288 lines with two colors that requires 1-bit per pixel,

[0305] a bit-map window 1102 having 360 pixels by 144 lines with 16 colors that requires 4-bit per pixel,

[0306] a graphic window 1104 having 90 pixels by 72 lines with 16 million colors that requires 24-bit per pixel,

[0307] a still video picture window 1106 having 180 pixels by 144 lines in 4:2:2 format using 24-bit per pixel,

[0308] an MPEG motion video window 1108 having 180 pixels by 144 lines in 4:2:0 format. The window size and position is generated by the OSD system. The MPEG video decoder generates the content of the window by decimation of the full screen picture.

[0309] This OSD picture requires 110 Kbytes memory. Without the OSD controller 270 the memory requirement could be up to 1.24 Meg bytes.

[0310] The right screen of FIG. 3 shows an other picture composed of 2 OSD windows displayed over full screen motion video 1120:

[0311] a bit-map window 1122 having 540 pixels by 504 lines with two colors that requires 1-bit per pixel. The background color is blended over motion video; and

[0312] a bit-map window 1124 having 360 pixels by 144 lines with 16 colors that requires 4-bit per pixel.

[0313] The memory size is 93 Kbytes using the OSD controller 270 compare to 207 Kbytes without it.

[0314] The following illustrates the memory needed for the examples in FIG. 18D.

[0315] As depicted in FIG. 18E, in frame mode the CPU 220 and frame use different memory areas. The CPU 220 builds the windows separately in the CPU memory 240 and each window has its own display attributes i.e. display mode, resolution . . . . The new display picture is created by the CPU, by copying sequentially each segment of the window 1 and 2 in such way that the OSD display controller 270 reads the frame memory 312 sequentially and displays line by line from the left upper corner to the right lower corner. The display area that does not contain any OSD data, such as background color or motion video, is not included in the frame memory. Each transition of window, each line, the controller synchronously change the attribute in order to display the window with the corresponding mode. The number of bits to display a pixel of window 1 and 2 can be different.

[0316] A block diagram of the OSD controller 270 is shown FIG. 18F:

[0317] The pixel and line counter 270-1 receives the pixel clock, generates X, Y that represent the pixel position on the screen and uses the synchronization signals Hsyn and Vsync to control screen display.

[0318] The windows controller 270-2 contains the position X and Y of each windows to be displayed on the screen. The controller 270-2 compares X, Y position and indicates to the display controller 270-4 each window transition and window number.

[0319] The address calculator 270-3 is not used in the frame mode.

[0320] For each new window transition the display controller 270-4 reads the new attribute from the attribute memory 270-5. It generates the address for the display memory 312 and loads the FIFO 270-7 with a new block of data. It then generates the attribute for the current window and sends it to the Decoder 270-6.

[0321] For each pixel, the decoder 270-6 extracts from the FIFO 270-7 the number of bits corresponding to the current pixel to be displayed. It transforms data bits into pixels.

[0322] The windows attributes are as follows:

[0323] Display modes: empty window for decimated video. Bitmap, YCrCb 4:4:4 graphics component, YCrCb 4:2:2 CCIR 601 component and background color

[0324] Supports blending of bitmap, YCrCb 4:4:4, or YCrCb 4:2:2 with motion video and with an empty window

[0325] Supports window mode and color mode blending

[0326] Provides a programmable 256 entries color look up table

[0327] Outputs motion video or mixture with OSD in a programmable 422 or 444 digital component format

[0328] Provides motion video or mixture with OSD to the on-chip NTSC/PAL encoder

[0329] Each hardware window has the following attributes:

[0330] window position: any even pixel horizontal position on screen; windows with decimated video have to start from an even numbered video line also

[0331] window size: from 2 to 720 pixel wide (even values only) and 1 to 576 lines

[0332] window base address

[0333] data format: bitmap, YCrCb 4:4:4, YCrCb 4:2:2, and empty

[0334] bitmap resolution: 1, 2, 4, and 8 bits per pixel full or half resolution for bitmap and YCrCb 4:4:4 windows

[0335] bitmap color palette base address blend enable flag 4 or 16 levels of blending transparency enable flag for YCrCb 4:4:4 and YCrCb 4:2:2

[0336] output channel control

[0337] FIG. 18G shows an example of display of two overlapped windows. Window 2 in back is a bit map with 16 colors per pixel. Each pixel require 4-bits into the frame memory to define the code of the color. The window 1 on top is a bit map with 2 colors per pixel. Each pixel require 1-bit in the frame memory 312 to define the code of the color. The position and dimension of the windows 1 is given by the attributes X_10, X_11, Y_10, Y_11. Horizontally the number of pixel is: X_11−X_10. Vertically the number of lines is: Y_11−Y_10. Same for window 2 with X_20, X_21, Y_20 and Y_21.

[0338] The display controller 270-4 access sequentially the display memory 312 (FIG. 7) from the first word containing the pixel X_20, X_21 to the last word containing the pixel X_11, Y_11. Details of the line 20 are shown FIG. 18H. The line begins with the pixels of the window 2, window 1 starts in X-10, Pa is the last pixel of window 2 with 4-bit per pixel and Pb is the first pixel of window 1 that uses 1-bit per pixel. Window 1 end on Pc and window 1 restarts in Pd until pixel position X_21.

[0339] The same word contain pixels of window 1 and 2. During display the window controller 270-4 detects the transition between Pa and Pb and controls the data processing after FIFO 270-7 access.

[0340] The pixel selector and multiplex 270-12 is the input of the decoder block 270-6 shown FIG. 18I. It receive the outputs of the FIFO 270-7 and the windows 270-5 attributes and control signals from the display controller 270-4. The basic function is to transform data stored in the frame memory 312 in pixel. In case of bit map display, the output, Pixel_Mux[7:0] 270-10 is the address of the CLUT (color look up table). For graphic or still video picture the output is one color component. Pixel_Mux[7:0]270-10 output is produced by bits coming from the FIFO and bits from attribute memory.

[0341] The pixel selector 270-12 receives 32-bit data from the FIFO outputs F[31:0]. The first stage 270-13 select one of the five bytes F[31:24], F23:16], F[15:8], F[7:0] and F[6:0] delayed by one clock sample. The second stage 270-14 is a half barrel shifter that allows shifting right a 15-bit input data by 0 to 7 bit positions. The output of the barrel shifter 270-14 positions the LSB of the code of the pixel to be displayed in Bs[0]. The pixel counter 270-20 provides the control signals for the multiplexer 270-13 and barrel shifter 270-14. Table 21a shows the effect of the control Mux_S[1:0] on the bytes selection and 21bshows the output of the barrel shifter in function of Bs_S[2:0]. Table 21c combines Tables 21a and 21b and shows the bits of the FIFO selected at the output of the barrel shifter as a function of the 5_bit pixel counter.

[0342] The multiplexer 270-18 receives data Bs[7:0] from the barrel shifter and Base[7:0] from the attribute register. It is controlled by 4 control bits coming from the attribute register 270-4, cursor and default signals from display controller 270-4 as shown Table 21d.

[0343] When active Pm[7:0] is equal to the 8-bit default color provided by the general control register of the display controller, no data is read from the FIFO.

[0344] When active Pm[7:0] is equal to the 8-bit cursor color provided by the general control register of the display controller, no data is read from the FIFO.

[0345] Bp[3:0]=0000 indicates that the current window is empty and contains 0_bit per pixel or color component. Pm[7:0] is equal to Base[7:0] stored into the attribute register 270-4. In bit-map mode, the Base[7:0] selects one of the256 colors of the CLUT as a background color.

[0346] Bp[3:0]=0001 indicates that the current window contains 1_bit per pixel or color component. Pm[7:0] is equal to Base[7:1] concatenated with Bs[0] from the barrel shifter. In bit-map mode, the Base[7:1] is the base address of a set of2_colors of the256 colors CLUT.

[0347] Bp[3:0]=0011 indicates that the current window contains 2_bit per pixel or color component. Pm[7:0] is equal to Base[7:2] concatenated with Bs[1:0] from the barrel shifter. In bit-map mode the Base[7:2] is the base address of a set of4_colors of the256 colors CLUT.

[0348] Bp[3:0]=0111 indicates that the current window contains 4_bit per pixel or color component. Pm[7:0] is equal to Base[7:4] concatenated with Bs[3:0] from the barrel shifter. In bit-map mode the Base[7:4] is the base address of a set of16_colors of the256 colors CLUT.

[0349] Bp[3:0]=1111 indicates that the current window contains 8_bit per pixel or color component. Pm[7:0] is equal to Bs[7:0] from the barrel shifter. In bit-map mode the256 colors in the CLUT are used.

[0350] The pixel counter 270-20 provides the control for the pixel selector 270-13 Mux_S[1:0] concatenated with Bs_S[2:0]. Each beginning of frame the pixel counter is reset. It is decremented by 0, 1, 2, 4 or 8 depending on the current window attribute. An address clock signal is generated when the counter hits zero.

[0351] The memory address generator 270-30 generates the read address for the FIFO 270-7. Each address clock signal generated by the pixel counter 270-20 a new 32-bit word F[31:0] is sent to the pixel selector 270-12.

[0352] The attribute memory and register 270-4 contains the attributes of the windows to be displayed during the current frame. The attributes that control the pixel selector and multiplex are:

[0353] Display mode: bit-map, graphic, still video or empty

[0354] Number of bit per pixel or color component: 0, 1, 2, 4 or 8 bits

[0355] The bit-map CLUT base address

[0356] The attribute register 270-4 contains the attribute of the current window. The attribute clock transfers the content of attribute memory 270-5 to the register 270-4 when the window changes.

[0357] As depicted in FIG. 18J, the windows controller 270-2 is composed of a content addressable memory CAM 270-40, flip flops 270-41, 270-42 and priority encoder 270-45. The CAM contain the attributes of position and size of the windows to be displayed in the current frame. FIG. 18J shows a 32-word CAM 270-40. Each window requires 4 words that indicate horizontally the coordinates of the first and last pixel and vertically the coordinates of the first and last line. A 32_word CAM supports8 windows. Other sizes of CAM may be employed.

[0358] The CAM 270-40 compares the value of the pixel and line counters respectively X and Y. When Y counter matches a value Yn0, a new window starts vertically, and the corresponding RS flip-flop is set Wn_Y=1. When the Y counter matches a value Yn1, the corresponding window ends vertically and RS flip-flop Wn_Y is reset. The process is the same horizontally. Wn_Y and Wn_X are combined to indicate that the X, Y counter is in an active window. The indices “n” indicate the window number. Since several windows can be overlapped, the priority encoder 270-45 indicates the display order on the screen. The indices “n=0” correspond to the cursor that must be always on top. Outputs of priority encoder are HIT and OSD_W; HIT generates the attribute clock and OSD_W generates the memory attribute address corresponding to the active window.

[0359] The details of a CAM cell is shown FIG. 18K. The cell contain 2 parts, a 6 Transistor RAM cell 270-41 and a 4 transistors comparator circuit 270-42. The CPU 220 loads the CAM with the attributes of position of the windows, memory mode is selected. During the display the associative mode is selected. The line counter Y and pixel counter X are compared to the contents of all Yn and Xn of the CAM. When X or Y is equal to one or several values the corresponding Match lines are active to set or reset a flip-flop as noted in FIG. 18J.

[0360] FIGS. 18L, 18M and 18N correspond to the generation of the display and frame memory represented FIGS. 18G and 18H.

[0361] In FIG. 18L, the pixel Px of the window 1 is selected in the 32_bit word “am”. The pixel counter is decrement by one each access. The pixel selector places Px at the output Bs[0]. The current window attribute select1_bit per pixel. The pixel multiplex selects Base[7:1] and concatenates with Px to form the output Pixel_Mux[7:0]. In bit-map mode Pixel_Mux[7:0] selects2 colors of the CLUT. Base[7:1] is the base address of the CLUT.

[0362] FIG. 18M shows the generation of a pixel Px for the window 2 that use 4_bits per pixel in bit-map mode. The pixel selector places Px at the output Bs[3:0]. The pixel multiplex selects Base[7:4] and concatenates with Bs[3:0] to form the output Pixel_Mux[7:0] that select one of the16 colors of the CLUT. Base[7:4] is the base address of the CLUT. 16 CLUT of 16 colors can be selected with the window attributes.

[0363] FIG. 18N shows a specific case of the window 2 where Pn+1 has its 2 msb bits into the word m+1 and 2 lsb into m+2. Word m+2 is currently selected at the output of the FIFO and the 7 lsb bits of word m+1 are maintained into the 7_bit register F-1[6:0]. Pixel selector take F-1[1:0] concatenated with F[31:30] to generate Bs[3:0]. The corresponding timing is shown FIG. 14b. At Pn+1 pixel counter equal 30. The barrel shifter output generate F-1 [5:0] concatenated with F[31:30]. The current FIFO address is word m+2 and the Pixel_Mux output is Base[7:4] & F-1 [1:0] & F[31:30]. Pixel Pn+2 the pixel counter is decrement by 4, the pixel selector select the next 4_bits of word m+2.

[0364] In FIG. 18G, the window 1 is on top of window 2. The CAM of the window controller is loaded with window 1 attributes position on top of window 2. The window displayed on top has the lower indices. Pixel Pa is last pixel for this portion of window 2 into the frame memory, the next bits contain the code of color of window 1, the first bit is Pb. During the same line window 1 end in Pc and window 2 restart in Pd. Each of this window transitions are detected by the window controller that generate the attribute clock to change the current display attribute stored in a register (see timing FIG. 180-1). For Pa-1 and Pa the Pixel counter is decrement by 4 each pixel and after attribute clock Bp[3:0]=1 (FIG. 18I) decrements the counter by 1 each pixel.

[0365] In bit-map mode the frame memory contains the code of the color, 1,2,4 or 8 bits per color depending of the attributes. The code of the color concatenated with the CLUT color base attribute selects a color from the CLUT. The CLUT contain 3 color components, one component for Luma and two components for Chroma.

[0366] When the current window is graphic, the CLUT is not used. For each pixel there are 3 identical accesses to the bit-map mode to extract the 3 color components from the frame memory. There are 3 accesses during a pixel.

[0367] In still video picture the CLUT is not used. Still video reduces Chroma bandwidth. For each pixel there are 2 accesses identical to the bit-map mode to extract one Luma components and chroma component Cr or Cb (alternately each pixel) from the frame memory.

[0368] When the picture is empty, the mode is bit-map with 0_bit per pixel. This mode is used to generate a window with a background color or a decimated motion video picture coming from the MPEG video decoder.

[0369] The pixel selector allows the hardware to mix different modes of display. The pixel selector and multiplex hardware, its control, the window controller, window attribute generation and the flow of data from the frame memory to the Pixel_Mux output the different display modes for different resolution.

[0370] The frame memory contains a description of the current displayed picture. The description is done sequentially starting from the first upper left corner of a window “n” to the last lower right corner of a window “m”. Only the active windows need to be described, not the full screen, background color or motion video.

[0371] The description is done pixel per pixel, the number of bits to describe one pixel can vary for each window. Each transition of a window is indicated by the attributes of position stored into the CAM. The window controller selects the attribute of the corresponding window in real time during display.

[0372] The pixel selector select the number of bits corresponding to the current pixel to be displayed. The complementary bits to form the 8_bit pixel output are obtained by concatenation of selected data bits from the frame and window attribute from the attribute memory.

[0373] When the current window is a bit-map, the Pixel_Mux output selects a color from the CLUT. The CLUT contains the 3 colors component.

[0374] When the current window is graphic, the CLUT is not used. For each pixel there are 3 accesses identical to the bit-map mode to extract the 3 colors components from the frame memory.

[0375] In still video picture the CLUT is not used. For each pixel there are 2 accesses identical to the bit-map mode to extract the 2 colors components from the frame memory. Luma is extracted each pixel and the chroma component Cr or Cb is alternately extracted for each pixel.

[0376] When the picture is empty the mode is bit-map with 0_bit per pixel. This mode is used to generate a window with a background color or a decimated motion video picture coming from the MPEG video decoder.

[0377] The following describes the use of the OSD 270 to provide a display flow with real-time address calculations. Most of the display system use a frame mode for OSD so that the CPU working space and display memory are separate. With a hardware windowing mode depicted in FIG. 18P; there is no duplication of memory space for the CPU 220 and OSD 270. Hardware windowing reduces memory transfer, power dissipation and system cost.

[0378] The CPU 220 builds each window separately in different portion of the SDRAM 312. Each window has its own display attributes, i.e. display mode, resolution and position; the number of bits to display a pixel of the window 1 and 2 can be different. The picture is composed directly by the hardware that reads the contents of the windows from the CPU memory space 312. The display controller 270 hardware reads only the data required to compose the current frame.

[0379] The OSD display controller 270 reads sequentially each segment of the window 1 and 2 line by line from the left upper corner to the right lower corner. Each new line the OSD controller 270 calculates the start address and block size for each segment of windows that make up the line. During display the OSD controller 270 transfers the contents of the windows from the CPU memory 312 segment by segment and changes the attribute of display for each transition of a window.

[0380] As depicted in FIG. 18Q, the OSD 270 and the CPU 220 communicate with the display memory (SDRAM) 312 via the memory controller 310. The OSD memory addresses are generated by the display controller 270-4. The FIFO 270-7 receive each segment of the windows to be displayed. The OSD controller 270 is composed of the following blocks:

[0381] The pixel counter 270-1 is incremented by the pixel clock and line counter when the pixel counter is at the end of the line. It generates X, Y, that represent the pixel position on the screen and synchronization signals Hsyn and Vsync to control screen display.

[0382] The windows controller 270-2 contains the position X and Y of each window to be displayed on the current screen. The controller compares X, Y to the position of the windows and indicates to the display controller 220-4 each window transition and the window number.

[0383] The address calculator 220-3 calculates the start address and block size of each segment of a window for each new line and pushes the values onto a stack in the attribute memory 270-5.

[0384] For each new window transition, the display controller 270-4 reads the new attribute from the attribute memory 270-5. The controller manages the FIFO 270-7. Each new line, the FIFO is loaded block by block with the segments of windows that make up the line. When the FIFO 270-7 is full, the controller 270-4 waits for the next access.

[0385] For each pixel, the decoder 270-6 extracts from the FIFO 270-7 the number of bits corresponding to the current pixel to be displayed. It transforms data bits in a pixel.

[0386] FIG. 18R shows an example of a display with two overlapped windows. Window 2, in back, is a bit map with 16 colors per pixel, so a pixel requires 4-bits in the frame memory to define the code of the color. Window 1 on top is a bit map with 2 colors per pixel, so a pixel requires 1-bit in the frame memory.

[0387] The position and dimension of the windows 1 is given by the attributes X_10, X_11, Y_10, Y_11. Horizontally the number of pixel is: X_11−X_10. Vertically the number of lines is: Y_11−Y_10. Same for window 2 with X_20, X_21, Y_20 and Y_21.

[0388] The line Y10 contain 3 segments. The first segment at the beginning of window 2, starts in position X20 and end in Pa. The segment 2, window 1, is displayed on top of window 2, starts in X10 and end in Pc. The third segment is the end of the window 2, start in Pd and end in X21. Segments 1 and 3 come from the memory space of window 2 and segment 2 from the memory space of window 1. The content of the window 2 memory between Pa and Pb are ignored and not transferred to the FIFO.

[0389] FIG. 18S details the process for this line and the flow from the memory to the FIFO. The CPU 220 has composed two windows in separate memory spaces. The windows are described line by line, each new line starts with a new 32-bit word. The first pixel of a line is aligned with the msb of the word. If the number of bits to describe the content of the line is not modulo 32, some bits of the word can be ignored. The window 2 has 4-bits per pixel, the first segment W2.1 contains 2 words but only 15 pixels. The last 4-bits are not used for display. The second segment W1.1 has 2 words, the window 1 has 1-bit per pixel and 62 pixels horizontally. The last 2-bits of the second word are ignored. The third segment W2.2 is not a beginning of a new line, the pixel Pc is not necessary aligned at the word boundary, in this example Pc is the second pixel of the first word of this segment, this position is referred by the segment offset W2.2.

[0390] FIG. 18T shows different blocks of OSD controller 270 described previously. The details of the blocks for the window controller, display controller and decoder are as follows.

[0391] The FIFO 270-7 is a 32-bit dual port memory. The data is received from the main memory SDRAM and used by the Pixel selector 270-12. The transfer requests and addresses generation are controlled by the FIFO memory controller. It generates write and read addresses and control signals to the FIFO and the memory address and control to the traffic controller that access the SDRAM. The OSD data is read by segment of windows in a burst. Each new segment the controller 270 accesses the attributes RAM to get a memory address and segment size.

[0392] FIG. 18U shows the FIFO management flow for the transfers from the SDRAM.

[0393] At the beginning of each new active line, the FIFO is empty the Read and Write pointer are equal.

[0394] The address calculator calculate the start address of each segment of the windows that compose the current line and store into the Attribute RAM.

[0395] The FIFO controller generate the Read segment request to the OSD Memory controller in order to read the first segment address Sa[23:0] and segment size Ss[8:0] stored previously into the attribute RAM.

[0396] If the segment is larger than the size of the FIFO the controller split the segment by burst. When the FIFO is full or cannot contain the block the FIFO controller is waiting.

[0397] When the full segment of window has been read the FIFO controller generate a request to access the next segment composing the current line. The pixel selector read the data word by word F[31:0]. The number of bit per pixel or pixel per word can vary for each segment of window so the time between two access to the FIFO is variable. A new segment start always with a new word. As shown FIG. 18R and 18S, window 1 overlaps window 2, Pa is the last pixel of window 2 for this segment. In this case a part of the word of the first segment of window 2 will not be used by the pixel selector to generate a pixel. Address clock signal is generated to access a new word into the FIFO.

[0398] For the pixel counter 220-20, there are two different cases (depicted in FIG. 18V): a new segment start or a new pixel clock. When a new segment of window starts the pixel counter logic generate the address clock signal to the FIFO controller in order to transfer the first word of this segment to the pixel selector.

[0399] The window controller generates the “Load” signal to indicate a window transition. The “Load” transfer the “Segment offset So[4:0] corresponding to this new segment of window to the pixel counter. There are two situations represented in FIG. 18S:

[0400] The segment W2.1 is the left border of the window, So[4:0]=0. Window 2 has 4-bits per pixel, the value of the pixel counter that generate Mux_S[1:0] concatenated with Bs_S[2:0] will be (So[4:0]−Bp[3:0])=28 to point to the first pixel of this word.

[0401] The segment W2.2 is overlapped partly with window 1. The first pixel of the first word is not displayed. So[4:0]=(0 −Bp[3:0])=28. The pixel counter will be So[4:0]−Bp[3:0]=24 to point to the second pixel of this word.

[0402] The “Pixel clock” decrements the Pixel counter by 0, 1, 2, 4 or 8 depending of the number of bits per pixel Bp[3:0] of the current window. An address clock signal is generated when the Pixel counter is equal to zero.

[0403] The pixel selector 270-12 receives the 32-bit data word from the FIFO outputs F[31:0]. It contains two parts, a byte multiplexer 270-13 and a barrel shifter 270-14. The byte multiplexer selects one of the four bytes F[31:24], F23:16], F[15:8] or F[7:0] as function of Mux_S[1:0] as shown Table 22a. The barrel shifter shift the byte to the right by 0 to 7 bit positions, as shown Table 22b.

[0404] The 5-bit pixel counter generates Mux_S[1:0]&Bs_S[2:]. Table 22c indicates the value of Bs[7:0] as function of the pixel counter value. This table combine Tables 22a and 22b.

[0405] The color multiplexer 270-18 receives data Bs[7:0] from the barrel shifter and Base[7:0] from the attribute register. It is controlled by number of bits per pixel Bp[3:0], coming from the attribute register. According to the Table 22d the multiplexer selects 0, 1, 2, 4 or 8 bits of the Base address color Base[7:0] and its complement in Bs[7:0] in order to form the outputs Pm[7:0].

[0406] When the cursor is detected by the window controller Base[7:0] is equal to the cursor color. When the display does not contain any OSD window or motion video, the default color is selected. During OSD window the Base[7:0] comes from the current window attribute register.

[0407] The output of the multiplexer generate Pixel_Mux[7:0] is used in the bit-map mode to select one of the 256 colors of the CLUT. In graphic mode or still video picture mode, Pixel_Mux[7:0] is one color component, Luma or Chroma. Graphic mode requires three color components per pixel, the Pixel_clock is 3 times faster than in bit-map. In still video picture, 2 color component are required during one pixel duration. The display output is three 8-bits words, Y, Cr and Cb.

[0408] The global attribute register 220-50 contains cursor and default color, these values are set by the CPU. The S window attribute register contains the attribute for the current window:

[0409] Display mode: bit-map, graphic, still video or empty.

[0410] Number of bit per pixel or color component: 0, 1, 2, 4 or

[0411] 8 bits.

[0412] The bit-map CLUT base address.

[0413] Blending . . . .

[0414] The attributes are located into the Attribute RAM. The window attributes change every window transition. The segment attribute are sent through this block to the FIFO controller or pixel counter.

[0415] The windows controller 270-2 contains a content addressable memory CAM, flip flop and priority encoder. The CAM contains the attributes of position and size of the windows to be displayed on the current frame. Each window require 4 words to indicate horizontally the coordinates of the first and last pixel and vertically the coordinates of the first and last line. A 32_words CAM supports8 windows.

[0416] The CAM compares the value of the pixel and line counters respectively X and Y. When Y counter match a value Yn0, a new window starts vertically and the corresponding RS flip-flop is set Wn_Y=1. When Y counter match a value Yn1, the corresponding window ends vertically and the RS flip-flop Wn_Y is reset. The process is the same horizontally. Wn_Y and Wn_X are combined to indicate that the X, Y counter crosses an active window. The indices “n” indicate the window number. Several windows can be overlapped, the priority encoder defines the display order on the screen. The indices “n=0” correspond to the cursor always on top. Outputs of the priority encoder are HIT and OSD_W; HIT generates the attribute clock and OSD_W select the memory attribute address corresponding to the active window. The HIT signal generates the access request to the attribute RAM at the address given by the priority encoder. The attributes are transferred to the window attribute register.

[0417] The CAM can be accessed by the CPU to set the position of the windows during initialization. The address calculator accesses the CAM each line for real time address calculation.

[0418] The memory controller 270-66 manages the access to the Attribute RAM and CAM. The access are:

[0419] CPU access:

[0420] CAM: The CPU program position and priority of the windows. This access is done during vertical blanking or when before OSD display.

[0421] Attribute RAM: to load the CLUT, windows attributes and Base address.

[0422] Address calculator access: During horizontal blanking to the CAM and Attribute RAM to calculate the segment address, size and offset.

[0423] FIFO controller access: When read segment request is generated, to the Attribute RAM to read the next segment address and size for data transfer between SDRAM and FIFO.

[0424] Window controller access: Each window transition to the Attribute RAM to read window attribute and segment offset.

[0425] The address calculator 270-70 is the key element of hardware windowing system. It calculates the attributes of each segments making up the current display line (first address, size in words and offset of the first pixel) and stores the values in the segments stack. The address calculator (AC) receives vertical and horizontal synchronization signals that indicate the beginning of a new frame or a line.

[0426] Each new frame the AC transfers the base address Ba0 to Ba7 to the corresponding line pointers “L0” to L7. The line pointers are located in the Attribute RAM. Ba(n) is the base address of the window in the SDRAM.

[0427] FIG. 18X shows 4 overlapped windows, the line Y cross horizontally all windows start and end. For each line of the active display area, the AC gets the active windows for the current line; the window controller return an 8-bit value. The “1” represent the active, first bit is window 0 and last bit window 7: WO_XY . . . . W7_XY=0,1,1,1,1,0,0,0

[0428] For each active window (Wn_XY=1), the AC reads the contents Xn0 and Xn1 of the CAM, and sorts window indices in the order of transitions from the left to the right. For the given example the sorted values are: X20, X40, X30, X10, X31, X21, X11, X41 (X20, is the lower value X41 the bigger)

[0429] From the left to the right when a window starts the AC selects in that window the values with lower indices. For example the first window starts in X20, the first selection is done by selecting only the values <X20 between X20, and X21, the values X40, X30, X31 are eliminated, X10 is maintained. The next window start is X10; there are no values between X10 and X11. There is no remaining window start after X11, so X41 is valid. The selected active transitions are:

[0430] X20, X10, X11, X41.

[0431] This line has 3 segments: S1 between X20 and X10; S2 between X10 and X11 and S3 between X11 and X41. S1 is window 2, S2 is window 1 and S3 window 4. The AC calculates the segment address. For each window start the segment address Sa[23:0] is equal to the line pointer Ln.

[0432] Example: S1: Sa[23:0] =L2; S2: Sa[23:0] =L1;

[0433] The last segment (S3) is the end of window 4. S3 starts in (X11) the AC calculates the number pixels and entire words from the beginning of window 4 to (X11). The number of pixels is (X11−X40). The number of words are (X11−X40)*K4/32, K4 is the number of bits per pixel for window 4 and 32 the number of bits per words. This value is added to the line pointer (L4) give the segment address S3: Sa[23:0].

[0434] The block size is the entire number of words between 2 transitions. The offset that points the first pixel is the remainder.

[0435] S1: (X10−X20)*K2/32=>Ss[8:0] and So[4:0]

[0436] S2: (X11−X10)*K1/32=>Ss[8:0] and So[4:0]

[0437] S3: (X41−X11)*K4/32=>Ss[8:0] and So[4:0]

[0438] The entire part of the equation gives the number of words Ss[8:0]. The decimal part the offset is So[4:0]. If So[4:0] >0 the number of words is Ss[8:0]+1.

[0439] In the last step, the line pointer is incremented by the number of entire words to describe a line of the active windows.

[0440] L1=L1+(X11−X10)*K1/32+1 if the number of bits divided by 32 is >0

[0441] L2=L2+(X21−X20)*K2/32+1 if the number of bits divided by 32 is >0

[0442] L3=L3+(X31−X30)*K3/32+1 if the number of bits divided by 32 is >0

[0443] L4=L4+(X41−X40)*K4/32+1 if the number of bits divided by 32 is >0

[0444] A flowchart of the address calculator steps is depicted in FIG. 18Y. Thus, the OSD system 270 simultaneously displays different kinds of pictures: bit-map, graphic, still video picture, motion video picture or background color. Each picture is in a different window that is managed by OSD hardware.

[0445] A display memory organized by windows is located in an SDRAM 312; the same memory space in the SDRAM 312 is used for both the display frame memory and for the CPU working area.

[0446] An address calculator calculates the attributes of each of the segments that make up the current display line (first address, size in word and offset of the first pixel) and stores these values in the segments stack.

[0447] The OSD data is read in a burst by window segment. For each new segment, the controller accesses the attributes RAM to get a memory address and segment size.

[0448] The OSD functionality of the OSD block 270 of FIG. 1B is presently preferred to be implemented as depicted in FIGS. 18Z and 18AA. FIG. 18AB depicts how the data size, address and control are generated for a window; it includes numbered steps for how this is accomplished.

[0449] FIGS. 18AC, 18AD, 18AE and 18AF depict the address generation circuitry, the instruction decoding, the state machine of the generation circuitry and a representative set of timing diagrams for this circuitry.

[0450] FIG. 18AG depicts how the window data is used by the TC to load the OSD FIFO and illustrates details of the OSD FIFO and its control.

[0451] FIG. 18AH illustrates how the OSD palette memory is organized and its interfaces.

[0452] FIG. 18AI illustrates how the window mode is determined.

[0453] FIG. 18AJ illustrates in more detail the CAM logic block of FIG. 18AI. It operates as described earlier herein.

[0454] FIG. 18AK illustrates a line pointer update flow diagram.

[0455] FIG. 18AL illustrates an OSD blending example.

[0456] FIG. 18AM illustrates the flow associated with FIG. 18AL.

[0457] FIG. 18AN illustrates timings for FIG. 18AM.

[0458] FIG. 18AO illustrates an OSD state machine and its states.

[0459] FIG. 18AP illustrates a state machine for FIFO request to the TC.

[0460] FIG. 18AQ illustrates a state machine for FIFO reads and control functions.

[0461] FIG. 18AR illustrates a representative timing diagram.

[0462] The BitBLT functionality 272 of the OSD block 270 of FIG. 1B is presently preferred to implemented as depicted in FIGS. 18AS and 18AT.

[0463] FIGS. 18AU illustrates an SDRAM to SDRAM transfer. FIG. 18AV illustrates this flow in more detail.

[0464] FIGS. 18AW and 18AX illustrate other transfers.

[0465] FIGS. 18AY, 18AZ and 18BA illustrate other BitBLT functions.

[0466] An appendix for the BitBLT module is attached as Appendix C hereto and incorporated by reference herein. It provides details on the operations of the BitBLT module.

[0467] The NTSC/PAL Encoder module 260 supports NTSC and PAL B, D, G/H, and I display formats and outputs Y, C, and Composite video with 9-bit DACs. It complies to the RS170A standard and supports the MacroVision Anti-taping function. It provides Closed Caption, Extended Data Services, and aspect ratio VARIS encoding. It also provides sync signals with an option to accept external sync signals.

[0468] This module 260 accepts from the OSD module 270 the video data that may have been blended with OSD data and converts it to Y, C, and Composite analog outputs. The Closed Caption and Extended Data Services data are provided by the video decoder 252 through a serial interface line. These data are latched into corresponding registers. The CC encoder sends out Closed Caption data at video line 21 and Extended Data Services at video line 284. The ARM initializes and controls this module via the ARM Interface block. It also sends VARIS code to the designated registers which is then being encoded into video line 20. The ARM also turns on and off MacroVision through the ARM Interface block. The default state of MacroVision is off.

[0469] The Communications Co-Processor module 280 provides two programmable timers, 3 UARTs—one for Smart Card and two for general use, accepts IR, SIRCSI and RF signals and provides a SIRCSO output. It also provides two general purpose I/Os and manages the I²C and JTAG interfaces.

[0470] This module 280 contains a collection of buffers, control registers, and control logic for various interfaces, such as UARTs, IR/RF, I²C, and JTAG. All the buffers and registers are memory mapped and individually managed by the ARM CPU 220. Interrupts are used to communicate between these interface modules and the ARM CPU.

[0471] The circuit 200 has two general purpose timers which are user programmable. Both timers contain 16 bit counters with 16 bit pre-scalers, allowing for timing intervals of 25 ns to 106 seconds. Each timer, timer0 and timer1, has an associated set of control and status registers. These registers are defined in Table 23.

[0472] The timers are count-down timers composed of 2 counters: the timer pre-scaler, psc, which is pre-loaded from tddr and counts down every sys_clock; and the timer counter, tim, (pre-loaded from prd). When psc=0, it pre-loads itself and decrements tim by one. This divides the sys_clock by the following values:

[0473] When tim=0 and psc=0, the timer will issue an interrupt if the corresponding tint_mask is not set. Then both counters are pre-loaded if soft=0. If soft is 1, the timer stops counting.

[0474] The timer control register (tcr) can override normal timer operations. The timer reload bit, trb, causes both counters to pre-load, while the timer stop bit, tss, causes both counters to stop.

[0475] The two general purpose 2-wire UARTs are asynchronous mode, full duplex, double buffered with 8 bytes FIFO UARTs that operate at up to 28.8 kbps. They transmit/receive 1 start bit, 7 or 8 data bits, optional parity, and 1 or 2 stop bits.

[0476] The UARTs are fully accessible to the API and can generate interrupts when data is received or the transmit buffer is empty. The ARM also has access to a status register for each UART that contains flags for such errors as data overrun and framing errors.

[0477] The IR/RF remote control interface is a means of transmitting user commands to the set top box. This interface consists of a custom hardware receiver implementing a bit frame-based communication protocol. A single bit frame represents a user command.

[0478] The bit frame is defined in three possible lengths of 12, 15 or 20 bits. The on/off values of the bits in the frame are represented by two different length pulse widths. A ‘one’ is represented by a pulse width of 1.2 ms and a ‘zero’ is represented by a 0.6 ms pulse width. The example in FIG. 20 shows the IR input bitstream. The bitstream is assumed to be free of any carrier (36-48 KHz typical) and represents a purely digital bitstream in return-to-zero format. The hardware portion of this interface is responsible for determining the bit value along with capturing the bit stream and placing the captured value into a read register for the software interface to access. Each value placed in the read register will generate an interrupt request.

[0479] Each user command is transmitted as a single bit frame and each frame is transmitted a minimum of three times. The hardware interface is responsible for recognizing frames and filtering out unwanted frames. For a bit frame to be recognized by the hardware interface it must pass the following steps: first it must match the expected frame size, 12, 15 or 20 bits; then two of the minimum three frames received must match in value. A frame match when detected by the hardware interface will generate only one interrupt request.

[0480] The IR/RF protocol has one receive interrupt, but it is generated to indicate two different conditions. The two different conditions are start and finish of a user command. The first type of receive interrupt (start) is generated when the hardware interface detects a new frame (remember 2 out of three frames must match). The second type of interrupt is generated when there has been no signal detected for the length of a hardware time out period (user command time out). Each frame, when transmitted, is considered to be continuous or repeated. So although there is a three frame minimum for a user command the protocol is that when a start interrupt is received the interface will assume that until a finish (time out) interrupt is generated the same frame is being received.

[0481] A typical example of the receive sequence is to assume that the interface has been dormant and the hardware interface detects a signal that is recognized as a frame. This is considered the start of a user command, and a start interrupt is issued by the hardware interface. The finish of a user command is considered to be when there has not been a signal detected by the hardware interface for a time out period of approximately 100 ms. The finish will be indicated by an interrupt from the hardware interface.

[0482] During a receive sequence it is possible to receive several start interrupts before receiving a finish interrupt. Several start interrupts maybe caused by the user entering several commands before the time out period has expired. Each of these commands entered by the user would be a different command. A new user command can be accepted before the previous command time out.

[0483] The IR, SIRCSI, and RF inputs share common decoding logic. FIG. 21 shows a theoretical model of the hardware interface. There are three possible inputs, SIRCSI, IR and RF, and one output, SIRCSO. The IR receiver receives its input from the remote control transmitter while the SIRCSI receives its input from another device's SIRCSO. Again, examining FIG. 21 shows that normal operation will have the IR connected to the SIRCSO and the decoder. The SIRCSI signal has priority over the IR and will override any IR signal in progress. If a SIRCSI signal is detected, the hardware interface will switch the input stream from IR to SIRCSI and the SIRCSI will be routed to the decoder and the SIRCSO.

[0484] There are two possible inputs for the IR frame type and one input for the RF frame type. A selection must be made by the user if the received frame type is going to be IR or RF. The IR/RF interface contains two 32-bit data registers, one for received data (IRRF Data Decode register) and one for data to be written out (IRRF Encode Data register). In both registers, bits 31-20 are not used and are set to 0.

[0485] The circuit 200 has two general purpose I/O pins (IO1 and IO2) which are user configurable. Each I/O port has its own 32-bit control/status register, iocsr1 or iocsr2.

[0486] If an I/O is configured as an input and the delta interrupt mask is cleared, an ARM interrupt is generated whenever an input changes state. If the delta interrupt mask is set, interrupts to the ARM are disabled. If no other device drives the I/O pin while it is configured as an input, it will be held high by an internal pull-up resistor.

[0487] If an I/O is configured as an output (by setting the cio bit in the corresponding control/status register), the value contained in the io_out bit of the control/status register is output. Interrupt generation is disabled when an I/O is configured as an output.

[0488] The definition of the control/status registers is given in Table 24.

[0489] The circuit 200 includes an I²C serial bus interface that can act as either a master or slave. (Master mode is the default). In master mode, the circuit 200 initiates and terminates transfers and generates clock signals.

[0490] To put the device in slave mode, the ARM must write to a control register in the block. The API must set the slave mode select and a 7-bit address for the circuit 200. It must also send a software reset to the I2C to complete the transition to slave mode.

[0491] In slave mode, when the programmable address bits match the applied address, the circuit 200 will respond accordingly. The circuit 200 will also respond to general call commands issued to address 0 (the general call address) that change the programmable part of the slave address. These commands are 0x04 and 0x06. No other general call commands will be acknowledged, and no action will be taken.

[0492] The circuitry is presently preferably packaged in a 240 pin PQFP. Table 25 is a list of pin signal names and their descriptions. Other pin outs may be employed to simplify the design of emulation, simulation, and/or software debugging platforms employing this circuitry.

[0493] Circuit 200's initialization is a three step process from a software perspective:

[0494] Power-on-reset (POR) of the on-chip hardware modules

[0495] Firmware controlled initialization

[0496] API controlled initialization

[0497] The sequencing of the above actions is determined by the POR sequence. The ARM software will not start execution until all the on-chip hardware resets are completed. This eliminates the need for firmware checking of POR status in each module.

[0498] Power ON Reset (POR)

[0499] At Power On Reset the ARM will branch automatically to the POR routine from the jump vector at ROM address 0x00000000. The ARM at reset is in supervisor mode and has the ability to reach all supervisor resources. The POR section will consist of four sub modules:

[0500] Diagnostics

[0501] ‘C’ Environment

[0502] Processor Environment Setup/Initialization

[0503] Kernel Setup

[0504] At the conclusion of POR the logic will branch to the User/OS for continued operation until firmware event processing takes place.

[0505] Initialization

[0506] The on chip firmware is responsible for initializing the FIQ mode stack. The SUPERVISOR, IRQ, ABORT, UNDEFINED and USER stacks must be initialized by the user application. At reset the initialization module will assume the ARM is in Supervisor mode. The initialization module will immediately switch to FIQ mode and not use any Supervisor mode resources. Both the FIQ and IRQ arm enable bits will be set in the CPSR to prevent any further interrupts.

[0507] Until the reason for the reset is determined, the initialization module will assume that a warm start had been issued. The OS application may have branched to the Reset vector intentionally. The IRQ and FIQ interrupts will be masked and the processor state will be assumed unknown.

[0508] Referring most specifically to FIGS. 22B-E, because the architecture enables nested FIQs, a context save area is established and initialized to allow the FIQ handler to save off the context of each successive FIQ. This area is reserved as a part of the normal FIQ stack area.

[0509] Defined within each FIQ ISR task will be a function responsible for hardware and system initialization for that ISR, at reset time this task will be executed by the system Initialization module.

[0510] The Initialization module will call tasks for the following after the C environment is initialized:

[0511] These initializations are accomplished “pre-data” to avoid pipeline delays once live data is present. The error code is a result that indicates a pass-fail status back to the initialization module. Each initialization routine will assume the ARM is in ARM state and FIQ mode. The stack will be the FIQ stack.

[0512] C Environment

[0513] The initialization module will initialize all memory required for the on-chip firmware. This consist of:

[0514] RAM area initialization

[0515] ROM pointers and data initialization

[0516] Diagnostics

[0517] At Reset the initialization module will check for the presence of and size of external RAM and SDRAM. A memory test will be executed to assure integrity of the external memory.

[0518] Warm/Cold Start

[0519] If a module receives an initialization call, the module will assume a restart is in place. This will force each module to reprogram the corresponding hardware to a known idle state. This action will be assumed regardless of previous User API programming.

[0520] Initialize FIQ Interrupt Logic

[0521] At reset, the FIQ interrupt logic is in an undetermined state. Initially, the FIQ handler 500 will reprogram all interrupt sources 502 as unmasked to enable all modules to interrupt with all logical interrupts at equal priority. Each interrupt will be reset to unpend any that may have occurred before a warm reset.

[0522] The FIQ context save area will be initialized along with the SRAM based vector table 504. This vector table 504 allows dynamic modification of the FIQ ISR entry points. All FIQ handlers 500 will have a defined set of initialization code pointers, as a default, loaded into the vector table 504 to allow reinitialization of the handler. The ISR 506 will then be responsible for reloading the appropriate state that follows initialization into the vector table 504 if required.

[0523] The FIQ handler 500 will then enable FIQ interrupts via the F bit in the ARM CPSR 508.

[0524] Initialization Completion

[0525] At completion of the initialization module, the state of the ARM firmware will be in IDLE. All FIQs will be enabled waiting on non-data FIQs for status information exchange or stream data FIQs after the User application enables the appropriate SCIDs.

[0526] System memory layout

[0527] The logical address space for the circuit 200 is generally defined in five areas:

[0528] The system memory defined for usage with the firmware is 4.5 Kbytes of SRAM, organized in two blocks, and 12 Kbytes of ROM. This SRAM is fully accessible by the ARM processor via the TC and has the highest TC priority level. The consequence of that is that any other TC function is delayed by the ARM access.

[0529] Firmware Kernel

[0530] The “Kernel” is the core module of the circuit 200 firmware system. It resides on chip and controls the flow of all FIQ-driven routines.

[0531] The purpose of for the Kernel is to control FIQ hardware vectors as well as the ARM Reset processor exception and initial processing of the ABORT exception vector. Rather than have a Kernel that has firmware based scheduling, pre-empting, and dispatching, a hardware and firmware driven Programmable Interrupt Controller (PIC) 510 based design will be used. All dispatching of run-time firmware tasks will be initiated by a FIQ. Some of these FIQs will be generated by hardware devices 512 and some by firmware 514. The FIQ is exclusively owned by the on-chip firmware and no other device, application software or module.

[0532] Each ISR 506 is attached to a hardware device in functionality. Because of the asynchronous nature of the circuit 200, each ISR 506 must have a priority assigned to it. This priority is a result of the design and architecture of the system and not from a run time decision. At run time it is simply a matter of deciding what new FIQs are capable of interrupting a current FIQ in progress, and completing the necessary systems housekeeping to allow that interruption. The purpose of this housekeeping is programming the PIC Mask Register 508 to enable/disable the appropriate FIQs.

[0533] The masks 508 on the PIC 510 become the priority scheduler for all FIQ generated requests. Each ISR 506 will know its relative priority in the system and mask the PIC 510 to allow other FIQs that are appropriate. The PIC hardware will present all active FIQs in the interrupt register 514. The firmware will interpret the generated FIQ and determine which of the FIQs should be processed. The FIQs will remain active until reset by writing to the PIC register 516, which serves as a reset/ack of that FIQ. In general, if two FIQs are outstanding at the same time, the FIQ with the lowest number assigned physically, will be processed. The priority of these FIQs go from 0→n with 0 the highest priority and n the lowest. The numbers are assigned based on their connection point to the PIQ, but can be logically reassigned in priority.

[0534] All of the Kernel execution is based on FIQs. There are no timer-based or other methods of scheduling tasks or execution of code.

[0535] Exception Handling

[0536] The ARM processor 518 handles interruptions to normal program flow through exception vectors. When an event occurs that requires exception processing, the ARM will branch to one of these exception vectors. At these vector locations exist branches to routines that will process the exception and then return to normal program flow. Each exception has a priority associated with it for arbitration purposes and a particular mode the ARM enters upon execution of the exception.

[0537] The Kernel will handle three exceptions directly. FIQs will be owned and processed totally by the Kernel. Reset will be handled initially by the Kernel with control passed to a user vector table via branch after firmware reset. Abort (data) will be preprocessed by the on-chip firmware to determine the type of abort. If it was a traffic controller SDRAM access abort, the on-chip firmware will handle the exception. If it was a true data abort, the firmware abort handler will vector off to the user abort exception vector. All other exceptions will pass directly to the user application via the same vector table. The base vector table address will be located at the memory mapped base location for the user application space as illustrated in Table 26.

[0538] Reset

[0539] This exception vector is normally used as the Power On Reset (POR) or user reset via the reset pin, or for a warm start the circuit 200 via a soft reset. Control of the soft reset will be in the USER domain. This soft reset will be accomplished by branching to the Reset Vector in Kernel defined space. After execution of the firmware reset code, execution will then proceed to the reset vector defined in the user vector table.

[0540] Undefined Instruction

[0541] This exceptions is generated by the ARM if the currently executed instruction is not recognized by the ARM. This error can be caused if a mistake is make in transitioning from THUMB→ARM state or from ARM→THUMB state. It could also be caused by code being overwritten in a RAM based code fetch.

[0542] If this exception occurs, the Kernel will allow the exception to branch directly to the User application via the user vector table.

[0543] Software Interrupts (SWI's)

[0544] ARM SWI's are general purpose exceptions generated by the API for interprocessor communications. The firmware will not use or generate SWI's. The SWI's are owned by the API, but the firmware will handle the initial SWI vector.

[0545] If this exception occurs, the Kernel will allow the exception to branch directly to the User application via the user vector table.

[0546] Prefetch Aborts

[0547] This exceptions is generated by the ARM if an attempt is made to execute an instruction that has been prefetched from an illegal address. It could be caused by code being overwritten in a RAM based code fetch causing an erroneous value or an actual MMU fault based on program logic. In this design, memory protection violations will generate this exception. Any access by the USER application outside of the range programmed by the USER OS will cause this exception. See Memory Protection for the detailed description of Memory Protection.

[0548] If this exception occurs, the Kernel will allow the exception to branch directly to the User/OS application via the user vector table.

[0549] Data Aborts

[0550] This exception is generated by the ARM if an attempt is made to transfer data to or from an illegal address, or if ARM access to the SDRAM is temporarily held off by the traffic controller. It could be caused by code being overwritten or an actual MMU fault based on program logic.

[0551] In this design, memory protection violations will generate this exception. Any access by the USER application outside of the range programmed by the USER OS will cause this exception. See Memory Protection for the detailed description of Memory Protection.

[0552] If this exception occurs as a result of the above violation, the Kernel will allow the exception to branch directly to the User/OS application via the user vector table. If the exception occurs as a result of an access hold-off to the SDRAM by the traffic controller, the firmware will completely process the exception and not vector to user space.

[0553] IRQ

[0554] Under normal circumstances, the IRQ logic is under direct control of the User software. To expedite transferring of data from the firmware to the User software, the firmware 550 will have the ability to generate IRQs as if from a hardware device 552.

[0555] During firmware FIQ task time, IRQs will be masked with the IRQ disable bit in the CPSR 554. This is necessary to prevent masking the IRQ PIC at FIQ exception time. Using the CPSR 554 instead of having the hardware mask the IRQs prevents the FIQ handler 500 from having to manage the context of the IRQ PIC. Upon return from the FIQ, the CPSR 554 will be restored to the original IRQ disable status.

[0556] The firmware 550 will appear as a hardware device to the IRQ handler in USER space. To communicate with the USER app, the firmware will generate an IRQ by writing the corresponding IRQ output bit in the IRQ FW register.

[0557] If an IRQ exception occurs, the Kernel will allow the exception to branch directly to the User application via the user vector table.

[0558] The table below describes the IRQ inputs. Those inputs identified as firmware are generated by the on chip firmware simulating a hardware device if needed. Each firmware IRQ has an associated structure element to further define data passing upon execution of these IRQs. Those IRQs that do not specify Firmware are actual hardware inputs.

[0559] To support the demands of the design, the OS will need hardware capable of supporting 32 IRQs. The hardware as pictured in FIG. 22C has four registers visible (Table 29: FIQ Interrupt Map) to the Firmware used for programming and reading the active interrupt.

[0560] After an interrupt is generated and processed, the IRQ handler 556 will reset the interrupt by writing a ‘1’ to the corresponding bit to the IRQ Interrupt Reset logic 558.

[0561] To generate IRQs from the firmware or OS, the firmware or OS may write to the IRQ Interrupt Set logic 558. Writing a 1 to the corresponding bit in the IRQ Interrupt Set register 558 will generate a IRQ for that position in the next cycle.

[0562] Table 29 lists those interrupts that are defined. Software generated interrupts can be generated in any of the interrupt register bits. This allows the Operating System to generate simulated hardware interrupts in those bit positions that are physically connected to hardware devices.

[0563] FIQ

[0564] All hardware on the circuit 200 notifies the firmware of a need for processing or intervention via an FIQ interrupt to the ARM. Since the ARM 518 supports a single FIQ 520, they are virtualized using the hardware pictured in FIG. 22D.

[0565] Each hardware device expects “real-time” processing of their respective FIQs. Because of this, the FIQ Handler (FIQH) 500 will trap the FIQ, identify it, and make a data processing decision. The FIQH 500 will then process the appropriate ISR 506.

[0566] Besides hardware generated FIQs, the Kernel will also process firmware generated FIQs. Firmware FIQs are necessary for algorithms that need real time posting or processing of events, or to delay processing of a process. It is expected that the OSD module will be the leading user of this feature.

[0567] Hardware support

[0568] To support the demands of the design, the Kernel firmware has a PIC capable of supporting 32 FIQs. The PIC has four registers visible (Table 29: FIQ Interrupt Map) to the Firmware used for programming and reading the active interrupt.

[0569] Table 30 describes a memory mapped 32 bit R/W register. This register represents the bit mapped position of the FIQ capable interrupts.

[0570] After an interrupt is generated and processed, the firmware will reset the interrupt by writing a ‘1’ to the corresponding bit in the FIQ Interrupt Reset register 516.

[0571] To generate FIQs from the firmware 514, the firmware 514 may write to the FIQ Interrupt Set register 516. Writing a 1 to the corresponding bit in the FIQ Interrupt Set register 516 will generate a FIQ for that position in the next cycle.

[0572] When an otherwise active FIQ is unmasked it will generate a FIQ. An interrupt line may be masked and unmasked several times. It will remain active until serviced by the firmware due to its priority.

[0573] In the case of a tie for multiple incoming unmasked FIQs, the firmware logic will use the lowest numbered FIQ as the highest priority. If a higher priority unmasked interrupt again comes in before the previous lower FIQ is serviced, then the lower priority FIQ will again be held off.

[0574] It is important to note this has the potential for lower priority FIQs to never be serviced.

[0575] All register manipulations in the PIC 510 must be atomic in nature. Once a read/modify/write sequence begins on a PIC register, the associated hardware or firmware must not update that register until after completion of the modification cycle.

[0576] Also note the interleaving of hardware and firmware FIQs. This will further enable the firmware to manage FIQ priorities by setting a firmware generated FIQ as a higher priority than hardware.

[0577] To manage these firmware priorities, the firmware will maintain an internal table in RAM of vector addresses for those firmware based FIQs. This will allow run-time manipulation of ISR priorities. Each firmware FIQ can be placed in the vector position associated with the priority of that vector as viewed by the PIC 510.

[0578] This will also allow dynamic modification of routines that are executed. An example of this would be pointing to initialization routines at startup and modifying the vectors to point at main code of the associated FIQ after startup.

[0579] FIQ Handler

[0580] The FIQ handler (FIQH) 500 is the actual ISR routine for all ARM FIQS. It is the responsibility of the FIQH 500 to accept the FIQ vector branch, decide the proper pseudo ISR routine to execute, enter the proper ARM mode and branch to the ISR 506. At the completion of the ISR 506 it will logically return to the FIQH 500 which will then return to the USER API interrupted program flow. Note the “logical return” to the FIQH. It is anticipated that proper stack management will allow a direct return to the interrupted program flow.

[0581] FIQ ISR

[0582] The firmware FIQ ISR 560 will perform the necessary setup to save the present context it will destroy. It will then program the IRM register to allow interrupts of a higher priority FIQs. It will then process the logic necessary to execute its intended function. At completion it will restore the context saved and branch as a normal return.

[0583] IRQ/FIQ Interface

[0584] The following routines specify the interface to the IRQs and FIQS.

[0585] irqInit( )

[0586] Syntax

[0587] FERROR ferror=irqInit(void);

[0588] where:

[0589] no parameters

[0590] Returns

[0591] fError=0, No Errors

[0592] Mode

[0593] Supervisor Privileged (Access Bit Enabled)

[0594] ARM 16 (THUMB)

[0595] Description

[0596] This function initializes the irq handler and resource table to defaults. This function is written in assembler and may be called from ‘C’.

[0597] This function must be called before any irqs are asserted in the system if the T.I. supplied irq handler is implemented.

[0598] Example

[0599] FERROR ferror;

[0600] ferror=irqInit;

[0601] See Also

[0602] irqHandler( )

[0603] irqHook( )

[0604] irqHandler( )

[0605] Syntax

[0606] irqHandler(void);

[0607] where:

[0608] no parameters

[0609] Returns

[0610] fError=0, No Errors

[0611] Mode

[0612] IRQ (Interrupt Handler)

[0613] ARM 16 (THUMB)

[0614] Description

[0615] This function when installed, will dispatch the function ISRs based on the ARM IRQ.

[0616] Using the function irqHook( ), function addresses may be programmed into the IRQ vector table 562. When an IRQ occurs, irqHandler will dispatch the appropriate ISR based on the IRQ_STATUS_REG. This register has predefined hardware devices from bit 0-1F. This function uses the bit offset of 0-1F to dispatch the associated function from the IRQ vector table.

[0617] The dispatched function executes in IRQ mode. The stack is assumed and all registers are saved before entry to the dispatched function. IRQs are disabled and the IRQ mask register is saved. The dispatched function is NOT declared with the INTERRUPT type but as a normal function. It is up to the dispatched function to re-enable IRQs through the CPSR 554 and reprogramming of the IRQ_MASK_REG if needed. The irqHandler will reset the cause of the IRQ and save/restore the IRQ_MASK_REG upon entry/exit of the dispatched function.

[0618] Note this handler allows re-entrant IRQs and handles the necessary housekeeping for this to occur.

[0619] The function irqInit should be called before this handler is allowed to run.

[0620] Example

[0621] This function is not callable, but should be vectored from USER_ROM_BASE+0x0c.

[0622] See Also

[0623] irqHook( )

[0624] irqInit( )

[0625] irqHook( )

[0626] Syntax

[0627] FERROR ferror=irqHook(long irq_num, long addr)

[0628] where:

[0629] irq_num The number of the irq vector to be replaced

[0630] addr The address of the routine to be vectored to.

[0631] Returns

[0632] fError=0, No Errors

[0633] Mode

[0634] ARM 16 (THUMB)

[0635] Description

[0636] This function is used to install IRQ handlers. Based on the input parameter ‘irq_num’. The associated address vector in ‘addr’ will be programmed into the IRQ vector table. ‘irq_num’ is valid from 0 to the maximum number of IRQs.

[0637] The dispatched function executes in IRQ mode. The stack is assumed and all registers are saved before entry to the dispatched function. IRQs are disabled and the IRQ mask register 554 is saved. The dispatched function is NOT declared with the INTERRUPT type but as a normal function. It is up to the dispatched function to re-enable IRQs through the CPSR and reprogramming of the IRQ_MASK_REG if needed. The irqHandler will reset the cause of the IRQ and save/restore the IRQ_MASK_REG upon entry/exit of the dispatched function.

[0638] Note the irqHandler allows re-entrant IRQs and handles the necessary housekeeping for this to occur.

[0639] The function irqInit should be called before this handler is allowed to run.

[0640] See Also

[0641] irqInit( )

[0642] fiqGen( )

[0643] Syntax

[0644] fiqGen(ulong fiq);

[0645] where

[0646] fiq Bit mapped long representing the fiqs to generate

[0647] Returns

[0648] no return

[0649] Description

[0650] fiqGen is used to generate software fiqs. It can also be used to simulate hardware fiqs by setting the bit in the word associated with that fiq input. Setting bit zero will generate the fiq that is assigned to bit zero. Multiple bits may be set at the same time. Note the fiq handler will process the bits from 0-31 in priority.

[0651] Example

[0652] #define fwFIQ06 (unsigned long) 0x06

[0653] fiqGen(fwFIQ06);

[0654] See Also

[0655] irqGen( )

[0656] irqGen( )

[0657] Syntax

[0658] irqGen(ulong irq);

[0659] where

[0660] irq Bit mapped long representing the irqs to generate

[0661] Returns

[0662] no return

[0663] Description

[0664] irqGen is used to generate software irqs. It can also be used to simulate hardware irqs by setting the bit in the word associated with that irq input. Setting bit zero will generate the irq that is assigned to bit zero. Multiple bits may be set at the same time. Note the irq handler will process the bits from 0-31 in priority.

[0665] Example

[0666] #define fwIRQ06 (unsigned long)0x06

[0667] irqGen(fwIRQ06);

[0668] See Also

[0669] fiqGen( )

[0670] Memory Management/Protection

[0671] For memory protection purposes, the system memory map is divided into three areas of protection.

[0672] Memory protection level 1 can only write to level 1 data space.

[0673] Memory protection level 2 can write to level 1 and 2 data space.

[0674] Memory protection level 3 can write to level 1, 2 and 3 data space.

[0675] This memory protection is necessary to prevent user applications or OS functions to write directly into firmware data space corrupting the on chip hardware. A second level of protection is also provided to prevent the user application from writing into OS data space. A programmable register allows the user to define which part of the extension bus DRAM is OS protected.

[0676] The monitoring of data writes is managed by the traffic controller (TC), which checks that the write is in a valid range.

[0677] The OS software can temporarily assume the firmware level protection by manipulating the so-called “protection bit.” This is supplied via a traffic controller hardware register and is only accessible from OS or firmware data.

[0678] Violations of the programmed memory ranges will cause the TC to assert the DATA ABORT ARM processor exception. This exception is handled by the previously defined section on data aborts.

[0679] RTSL/USER/OS to Firmware Communications

[0680] The RTSL (Run Time Support Library) is the top level name for all TI supplied libraries that support the circuit 200. The firmware has established through IRQs a way to manage passing run time data to the USER applications. Using the RTSL the USER application can communicate with the firmware.

[0681] The USER API will execute an RTSL function that uses the passed parameter to determine what on-chip function to perform. The passed parameter can be a function identifier that maps to a set of functions on chip or further embedded in the RTSL. All logical programming and status determination of on-chip hardware will be isolated from the USER/OS through this RTSL. This does not prohibit the User OS from accessing the hardware directly, using the protection bit whenever necessary.

[0682] The RTSL routines can access/share on-chip variables via the Common Reference Table (CRT). The CRT allows resolution of on-chip variables in the separate off-chip application software. There are two CRTs, one on-chip and one in the application software. The on-chip CRT pointer is located at a 0x20 offset from the on-chip ROM. The CRT pointer in the application software is located at a 0x20 offset from the user EPROM base. At start-up/reset, the respective software modules (on-chip firmware and off-chip application software) initialize their CRTs.

[0683] Common Reference Table

[0684] The on-chip firmware needs the ability to communicate with off chip functions, memory tables and processes. The off-chip RTSL or Run Time Support Library also needs the ability to make calls and/or manipulate data and pass parameters from the library to the on-chip functions. This communication needs to be standardized such that future releases of the chip or RTSL will not necessarily be dependent on each other. Also, this allows the code for each module, RTSL and on-chip firmware, to be built independently and not compiled, linked and loaded together.

[0685] To accomplish a common communication path between the two, a structure is defined with a known location on chip that will allow the process to communicate. This structure is defined and referred to as the CRT or Common Reference Table. Below is a list of the locations and features of each element of the CRT.

[0686] The table is referenced by a pointer hard coded at location 0x20. This location is one word address above the exceptions vectors and is a permanent location for this definition. The complete definition of the CRT is referenced in a common file called def.h. The structure typedef CRTFW defines the on-chip CRT and is updated as needed.

[0687] In addition to on-chip resources that need to be shared, the RTSL or User environment must make available certain data tables and functions for on-chip use. An example of this is the video decoder loader data table. This data is used entirely on chip, but due to size constraints is held off chip in the RTSL library. Because of these needs there is an associated off-chip CRT termed CRTOC for Common Reference Table Off Chip. A pointer to this table is expected at the base of user code+0x20 or 0x2000020. This table must be ROM'd. The values and pointers must be available before the user reset vector is executed. Some of the data will be referenced as the circuit 200 executes a hardware reset.

[0688] Transport Packet Parser

[0689] The Transport Packet Parser (TPP) in the circuit 200 processes the header of each packet and decides whether the packet should be discarded, further processed, or stored without intervention from software. Further processing on the packet is done by the TPP software module, which is activated by interrupt from the TPP hardware after the completion of the packet data transfer. TPP Interface

[0690] The following routines specify the interface to the transport packet parser (TPP) related functionality.

[0691] tppInit( )

[0692] Syntax

[0693] void tppInit(void);

[0694] Returns

[0695] This function returns no error code.

[0696] Description

[0697] The function initializes the Transport Packet Parser hardware. It will reinitialize all related tables, structures and hardware locations. This function should only be called if a total re-initialization of the hardware bitstream demultiplexer is required.

[0698] Example

[0699] Protection level

[0700] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0701] See Also

[0702] tcInit( )

[0703] tppEnableScid( )

[0704] Syntax

[0705] void tppEnableScid(uchar logical_channel, ushort scid, uchar flag, uchar device);

[0706] where:

[0707] Note: It is the responsibility of the application programmer to enable ONLY 1 channel as SCR_CHAN. To disable an existing SCR_CHAN, repeat the call to tppEnableScid without OR-ring SCR_CHAN in the flag

[0708] Returns

[0709] The function does not return an error code.

[0710] Description

[0711] This function enables the demultiplexing of data from and the incoming DSS stream for the given SCID and enables the logical channel (0-31) for output. In case of virtual device mapping, the output will automatically be routed to the appropriate on-chip resource. The channel can be used for SCR extraction, if so indicated by the SCR_CHAN in the flag parameter.

[0712] Checking of the Continuity Counter for the channel is enabled or disabled by resp. CC_ENABLE or CC_DISABLE in the flag parameter.

[0713] To disable a channel, the SCID parameter passed needs to have the value SCID_DISABLE. The software will ignore all other parameters and disable the logical channel. All old channel parameters will be overwritten during the next tppEnableScid call for this same logical channel.

[0714] Example

[0715] Protection level

[0716] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0717] tppSetChannelOutl( )

[0718] Syntax

[0719] void tppSetChannelout(uchar logical_channel, uchar enable, ushort out, ushort decrypt);

[0720] where:

[0721] Returns

[0722] This function does not return an error code.

[0723] Description

[0724] The function enables/disables and directs the output from the demultiplexer to the appropriate resource. It also allows the caller to specify which one of the output directions will be decrypted. If the input parameter specifies DISABLE_ALL_CHAN, the additional parameters are not considered anymore. In case ENABLE_ALL is specified, all logical channels (0-31) are enables with the given output and decryption characteristics as well as the decryption specified in the input parameters.

[0725] Example

[0726] Protection level

[0727] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0728] tppGetData( )

[0729] Syntax

[0730] void tppGetData(uchar logical_channel, uchar *buf, long size, uchar irq, Get_data_s *ret, uchar transfer_type, Filt_s *filter);

[0731] where:

[0732] Returns

[0733] The function does not return an error code.

[0734] Description

[0735] The function transfers “size” bytes from the given logical channel stream to the destination buffer address as specified. The type of transfer determines the way the destination is calculated. In case of CAP the transfer always takes place in 127 byte increments to whatever free buffer is found in the CAP buffer array. The firmware will do the management of busy/free CAP-buffers.

[0736] The irq parameter specifies the IRQ to activate when the transfer is completed or aborted. The reason for the IRQ as well as the buffer address (CAP) and/or the logical channel that caused the IRQ are all located in the “ret” structure. The format of the Get_data_s structure is as follows:

[0737] Filtering of the data is determined by the “filter” parameter. If no filtering is to be performed, the caller should pass a NULL. If filtering is to be done, the Filt_s structure needs to be loaded with the appropriate parameters as shown in “syntax”.

[0738] Example

[0739] Protection Level

[0740] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0741] tppAbortGetData( )

[0742] Syntax

[0743] void tppAbortGetData(uchar logical_channel);

[0744] where:

[0745] logical_channel=channel to use

[0746] Returns

[0747] The function does not return an error code.

[0748] Description

[0749] The function terminates any tppGetData request that is in progress on the given logical channel. Since the possibility exists that the transfer to be aborted is finishing while the application call is being made, the application program should be able to handle a tppGetData termination IRQ even after this tppAbortGetData call is completed. This is due to the asynchronous nature of the API and the firmware on-chip.

[0750] Example

[0751] Protection level

[0752] This routine needs to run with protection ON, as it accesses the on-chip protected resources. tppDeliverControlWord( )

[0753] Syntax

[0754] void tppDeliverControlWord(uchar cw_index, uchar *cwp_buf);

[0755] where:

[0756] Returns

[0757] The function does not return an error code.

[0758] Description

[0759] The function will compact the 8 byte CWP data from the cwp_buf locations into a 7 byte compacted Control word as follows:

[0760] The resulting control word will be stored in the control word key table at the given index for the decryption engine to access at the appropriate time.

[0761] Example

[0762] Protection level

[0763] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0764] tppCwpAcqEnable( )

[0765] Syntax

[0766] void tppCwpAcqEnable(uchar irq, uchar *buf, Cwp_s *parms, char enable);

[0767] where:

[0768] Returns

[0769] The function does not return an error code.

[0770] Description

[0771] In case of ENABLE, the CWP acquisition will be enabled for those logical channels that are ‘1’ in “map” for DISABLE; the CWP acquisition will be disabled for those logical channels that are ‘1’ in the map parameter. The process of ENABLE/DISABLE is accumulative; the logical channels that were previously enabled/disabled are not changed, unless specified in “map”.

[0772] The acquisition of the CWP automatically selects the appropriate CWP buffer from the buffer pool pointed to with buf. CWP buffer management is done by the firmware. It will ‘in-use’ the buffer when the CWP is written into it, and ‘free’ it when the tppDeliverControlWord call is executed for that CWP buffer. When a CWP is acquired, but the buffer is “in-use”, the CWP will be discarded. Otherwise, the CWP will be transferred to the appropriate CWP buffer and upon completion of the transfer, the IRQ will be activated that was specified in the irq passing parameter. The logical channel of which acquisition was completed is returned in the Cwp_s return structure logical_channel member.

[0773] When DISABLE is specified in the enable flag, irq, buf and parms are not used. The appropriate logical channel's CWP acquisition will be disabled, no response is generated to the caller.

[0774] Note: The Cwp_s→logical_chan upon return is an lvalue, not bitmapped as it is upon call.

[0775] Example

[0776] Protection level

[0777] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0778] tppCapAcqEnable( )

[0779] Syntax

[0780] void tppCapAcqEnable(ulong map, uchar flag);

[0781] where:

[0782] map=bitmapped logical channel(s) to enable/disable

[0783] flag=flag to indicate ENABLE/DISABLE this (these)

[0784] logical channel(s)

[0785] Returns

[0786] The function does not return an error code.

[0787] Description

[0788] This function allows the caller to enable/disable CAP buffers in the CAP buffer pool. The function will set/reset the buf-free flag for the appropriate index.

[0789] Each logical channel that needs to be enables/disabled is represented by a ‘1’ in the bitmap.

[0790] Example

[0791] Protection level

[0792] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0793] vcrcommand( )

[0794] Syntax

[0795] void vcrCommand(char command);

[0796] where:

[0797] command=VCR control command(s) as described below

[0798] Returns

[0799] The function does not return any error code.

[0800] Description

[0801] The function can be used to control the digital VCR processing function on the chip. The command consists of the OR'd command functions as follows:

[0802] VCR_PLAY/RECORD and VCR_FULL_PACK/PAYL_ONLY functions are only changed when either the VCR_ON function is included in the command or the VCR_ON command was executed in a previous vcrCommand call (see example).

[0803] Notes: When the command contains the VCR_OFF function, all other OR'd functions will be ignored, thus vcrCommand(VCR_OFF |VCR_RECORD |VCR_PAYL_ONLY) will NOT change the settings of the PLAY/RECORD or the FULL/PAYLOAD ONLY functions on the chip.

[0804] Example

[0805] Protection Level

[0806] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[0807] Infrared Control and RF control Initialization

[0808] At power-up there is required initialization by the application software. The application software will have to perform one step to initialize the interface. The user should call the irrfInitIntrfc routine to initialize the internal firmware variables.

[0809] Module Description

[0810] The IR/RF remote control interface is a means of transmitting user commands to the set top box. This interface consists of a custom hardware receiver implementing a bit frame based communication protocol. A single bit frame represents a user command.

[0811] The bit frame is defined in three possible lengths of 12, 15 or 20 bits. The hardware portion of this interface is responsible for determining the bit value along with capturing the bit stream and placing the captured value into a read register for the software interface to access. Each value placed in the read register will generate an interrupt request.

[0812] Each user command is transmitted as a single bit frame and each frame is transmitted a minimum of three times. The hardware interface is responsible for recognizing frames and filtering out unwanted frames. A frame match when detected by the hardware interface will generate only one interrupt request.

[0813] The IR/RF protocol has one receive interrupt, but it is generated to indicate two different conditions. The two different conditions are start and finish of a user command. The first type of receive interrupt (start) is generated when the hardware interface detects a new frame. The second type of interrupt is generated when there has been no signal detected for the length of a hardware time out period (user command time out). Each frame, when transmitted, is considered to be continuous or repeated. So although there is a three frame minimum for a user command, the protocol is that when a start interrupt is received the interface will assume that until a finish (time out) interrupt is generated the same frame is being received.

[0814] During a receive sequence it is possible to receive several start interrupts before receiving a finish interrupt. Several start interrupts maybe caused by the user entering several commands before the time out period has expired. Each of these commands entered by the user would be a different command. A new user command can be accepted before the previous command time out.

[0815] There are two possible inputs for the IR frame type and one input for the RF frame type. A selection must be made by the user if the received frame type is going to be IR or RF.

[0816] The IR/RF interface will provide information to the user application through a status mailbox. New information in the mailbox will be indicated by an IRQ from the IR/RF driver. There are two interrupts (decode and encode) from the hardware interface that could invoke either RTSL supplied routines or invoke user supplied routines. These parameters are provided by the user and setup by an RTSL initialization routine.

[0817] An initialization routine will setup the pointers to the IRQ vectors for the decode and encode handlers and a pointer to the status mailbox. There are basic encode and decode handlers supplied in the RTSL; however, the user can also decide to use encode and decode handlers other than the ones supplied.

[0818] There are two required IRQ numbers that must be supplied to the interface, which is user notification that an encode operation has completed or that a decode operation has completed.

[0819] IR/RF Interface

[0820] The following routines specify the interface to the IR/RF ports.

[0821] irrfInitIntrfc( )

[0822] Syntax

[0823] Returns

[0824] Nothing

[0825] Description

[0826] This routine will initialize the IR/RF interface. IrrfInitIntrfc will initialize the user's notification IRQ, the vectors in the IRQ table for the encode and decode handlers, hardware registers and initialize a global interface structure. The user is required to allocate the memory required for both status mailboxes (dec_sts and enc_sts). This routine should be called by the user at power up to initialize the interface parameters. If the pointers passed for the interrupt handlers are NULL, then the RTSL supplied routines for the IRRF interface will be loaded into the IRQ vector table. If there are addresses supplied for the Decode and Encode handlers then the values for the other parameters of usr_irq, dec_sts and enc_sts should be NULL.

[0827] irrfEncIsr( )

[0828] Syntax

[0829] interrupt void irrfEncIsr( )

[0830] Returns

[0831] Normal return from interrupt

[0832] Description

[0833] This routine will handle interrupts from the encode function for the SIRCSO of the IRRF interface. The functions performed by this routine will be to place the value of the command in the encode status mailbox as an indicator that the SIRCSo function has completed. An IRQ is then issued to the user through the IRQ that the user specified for the encode IRQ in the initialization routine. The encode command bit is cleared to indicate to the software interface that an encode operation is no longer in service.

[0834] irrfDecIsr( )

[0835] Syntax

[0836] interrupt void irrfDecIsr( )

[0837] Returns

[0838] Normal return from interrupt

[0839] Description

[0840] This routine will handle the interrupts from the decode function of the IR/RF interface. There are two different types of interrupts associated with the decode interrupt. If the time out bit is not set in the decode register of the interface this interrupt indicates a new bit frame has been identified. If the time out bit is set then it means this interrupt indicates that there has not been a bit stream for the period of the hardware time out. If a new bit frame has been identified the bit frame value is place in the status mailbox (dec_sts) and the user is notified through an IRQ that was specified by the user in the initialization routine. The read will take whatever size command that is in the decode register (12,15 or 20 bit), it up to the user to know what size of command to expect.

[0841] irrfIntrfcWr

[0842] Syntax

[0843] unsigned char irrfIntrfcWr(unsigned int cmd)

[0844] Returns

[0845] 1 if SIRCSo command was successfully written to the encode register

[0846] 0 if SIRCSo command is already in progress, command was not written

[0847] Description

[0848] This is the write routine for the SCIRCSo for the IR/RF interface. Normally the SCIRSo will receive the input signal from the SCIRSi and output it. When this routine is called the cmd (command) that is passed in the argument list will be written to the encode register for the IR/RF interface.

[0849] For the command to be transmitted on the SCIRSo the encode bit must set in the command before it is written to the encode register.

[0850] irrfDecRfSel( )

[0851] Syntax

[0852] void irrfDecRfSel(unsigned char select)

[0853] where:

[0854] unsigned char select; 0=IR selected/1=RF selected

[0855] Returns

[0856] Nothing

[0857] Description

[0858] This routine will select what the frame format for the decode function of the IRRF interface, 15 or 20 bits.

[0859] irrfEncRfSel( )

[0860] Syntax

[0861] void irrfEncRfSel(unsigned char select)

[0862] where:

[0863] unsigned char select; 0=IR selected/1=RF selected

[0864] Returns

[0865] Nothing

[0866] Description

[0867] This routine will select what the frame format for the encode function of the IRRF interface, 15 or 20 bits.

[0868] Smart Card Communication Control

[0869] The circuit 200 interface to the NDC Smart Card is based on the ISO-7816-3 specification, which defines electronic signals and transmission protocols. Only the portions of the specification that pertain to a asynchronous type of interface are used. The interface itself is the Smart Card and a specific UART inside the circuit 200. In this section, the Smart Card will be referred to as the card and the circuit 200 will be referred to as the interface device.

[0870] Note that only one message to the Smart Card can be outstanding; the response or time out from the previous message must be received before another message can be sent to the Smart Card.

[0871] Initialization

[0872] At power-up there is required initialization by the application software. The application software will have to perform two operations to initialize the interface. First initialization step performed by the user is to load the address of smcSmartCardIsr into the IRQ vector table. The second initialization step is then to invoke the function smcIntrfcInit with the required parameters to initialize the internal firmware variables.

[0873] The Smart Card interface will initialize on a system reset.

[0874] Module Description

[0875] The ISO-7816-3 specification defines the interaction between the card and the interface device as conducted through the following consecutive operations:

[0876] Connection and activation of the contacts by the interface device

[0877] Reset of the card

[0878] Answer to Reset by the card

[0879] Subsequent information exchange between the card and the interface device

[0880] Deactivation of the contacts by the interface card

[0881] Connection and Activation of the Contacts by the interface

[0882] The interface device controls the powering of the card. The following conditions are required as part of the powering sequence to the card. RST (Reset) is in state L (SCCSR bit 11 to Inactive(0)) VCCEN (SCCSR bit 12 to Enable(1)) VPP is raised to idle state (0 to SCCSR bit VPPE)

[0883] Reset Of The Card

[0884] The reset command is the signal to the card that provides a known starting state. The information exchange between the card and the interface device cannot begin until the Reset signal has been asserted to the card and the interface has received an answer to the reset sequence from the card. The interface is responsible for initiating the reset command and any following message transactions with the card.

[0885] To initiate the Reset sequence to the card set bit 2 active (URST=1) in the SCICR register. The Smart card will then respond to the reset signal on the I/O line within 40,000 clock cycles. Once the card responds to the reset signal then CCP hardware will itself reset the URST line. The interrupt handler for the interface will use a time out to determine when the answer to reset (ATR) sequence has finished. The interrupt handler for the interface will then issue an interrupt with a ATR received complete status to the application software. This interrupt completes the ATR sequence.

[0886] If the card does not respond to the reset command within the time period specified in the ISO-7816-3 specification the UART hardware will generate an interrupt (ARST) to the firmware. The interface interrupt handler will, upon receiving a no answer to reset interrupt, generate a ATR error status interrupt to the application software. This interrupt indicates that the ATR sequence failed.

[0887] Also note that before the Reset sequence command can be issued, bit 3 must have been set active (VCCEN=1) in the SCICR register.

[0888] Subsequent Information Exchange Between the Card and the Interface Device

[0889] Information transfer is always initiated by the interface device, never by the Smart Card. The interface will send a command header to the card. The card will acknowledge the receipt of the header using procedure bytes, which will be then followed by a data transfer that can be either from or to the card.

[0890] The interface to card transaction

[0891] Command header is transmitted to the card

[0892] Card responds with a procedure byte (ACK) that indicates single data or block transfer of data bytes and what the VPP state should be.

[0893] Depending on the direction of the command the card or interface will transfer the data or data bytes.

[0894] After the transfer of data bytes the card will transfer the SW1 byte (9xH or 6XH) and then SW2 byte which indicates the end of this transaction between the interface device and the card.

[0895] A flow control mechanism at the hardware layer controls when a character can be transmitted on the link. Either the card or the interface can hold transmission by exercising the flow control mechanism. On the interface side there is not firmware access to the flow control. When the receive FIFO in the UART is full the UART hardware will exercise the flow control to prevent further characters from being transmitted from the card.

[0896] A time out mechanism called Work Wait time is used only to measure the maximum time difference between the start bits of two consecutive characters transmitted on the link (Received and Transmitted). This timing mechanism is programmable through a register in the firmware with a value passed from the application software. When the Work Wait time expires the UART will issue an interrupt which the firmware will then generate an interrupt to the application software.

[0897] Command Header

[0898] A header is composed of five bytes and is always sent by the interface device. The header bytes are CLA, INS, P1, P2, P3:

[0899] CLA is the instruction class

[0900] INS is the instruction code in the instruction class

[0901] P1, P2 are a reference that completes the instruction code

[0902] P3 is the number of data bytes that will be transferred either to or from the Smart Card. The direction is determined by the instruction. A direction indicator will be passed as a parameter from the API telling the communication routine what the direction will be.

[0903] Procedure Byte

[0904] Following the transmission of the command header the interface will wait for the response from the card. The response has the form of a procedure byte (can be considered an ACK byte) followed by one or more data bytes. There are three possibilities for the procedure byte, ACK, NULL, SW1.

[0905] The ACK byte's seven most significant bits will be either equal or complimentary to the INS byte. This byte will be used to control data transfer and VPP state.

[0906] The NULL=60, is used to reset work wait time. If a command is sent to the card and the processing time required is longer than the work wait time the NULL byte would cause a reset of the work wait time which would then allow further card processing time. Additionally any character received will reset the work wait time, the NULL byte just allows a way to reset the work wait time without requiring the transfer of data.

[0907] The SW1 byte followed by the SW2 byte indicates the end of the command process. SW1 has two possible base values 9X or 6X (60 H is a NULL character). If the SW1 byte is received anywhere in the stream of characters from the card that is an indication that the transaction between the card and the interface device is about to be complete. This is regardless of what the expected byte count that was passed in the command header. Once the SW2 character is transmitted and the guard time for the SW2 has expired then the interface to card transaction is complete.

[0908] The following are the possibilities for the values of the ACK byte which will control the transfer of data and control the state of VPP. The ACK byte is divided into two sections, the seven most significant bits are used to control data transfer (bits 1-7) and the least most significant bit (bit 0) is used to control the state of the VPP. An exclusive OR operation is performed between the procedure ACK byte and the command INS byte from the command header to obtain the transfer state and VPP state.

[0909] Possible Data Transfer States and VPP States

[0910] Exclusive OR operation yields a ‘00’ then all the remaining data bytes are transferred subsequently. The VPP state is maintained at or set to zero (idle).

[0911] Exclusive OR operation yields a ‘01’ then all the remaining data bytes are transferred subsequently. The VPP state is maintained at or set to one (active).

[0912] Exclusive OR operation yields a ‘FF’ then only the next data byte if one remains is transferred. The VPP state is maintained at or set to zero (idle).

[0913] Exclusive OR operation yields a ‘FE’ then only the next data byte if one remains is transferred. The VPP state is maintained at or set to one (active).

[0914] Deactivation of the Contacts

[0915] The Deactivation of the contacts occurs after the information session has terminated. The steps required are:

[0916] Set RST inactive.

[0917] Set the Clock line to L, (This is not under software control)

[0918] Set VPP inactive

[0919] Set I/O line to L, (This is not under software control)

[0920] Set VCC inactive

[0921] Status Information Exchange from the Interface Device to the User

[0922] The user will be notified through an IRQ and a status word when the following Smart Card events occur:

[0923] Smart Card Detect (Insertion/Removal)

[0924] VCC detect loss

[0925] Transaction complete

[0926] Work Wait Time out

[0927] NAK error

[0928] Parity error

[0929] No answer to reset

[0930] Once one of the Smart Card conditions listed above becomes active the RTSL interrupt service routine will use the IRQ number that the user designated with the smcIntrfcInit function to notify the user that a Smart Card event has occurred. Before the IRQ is generated the ISR will set a bit in the mailbox status word as to the cause of the Smart Card IRQ. The mailbox status word is allocated and supplied by the user through the smcIntrfcInit function. It is the responsibility of the user to clear the bits in the mailbox status word after each event occurs. In Table 35 are the bit values that will be passed back in the Smart Card status mailbox status word.

[0931] Smart Card Interface

[0932] The following routines specify the interface to the Smart Card.

[0933] smcIntrfcInit( )

[0934] Returns

[0935] The return from this call does not indicate a successful operation but rather if the operation was allowed and if the passed parameters were correct. The completion of this operation will be indicated to the application software through an interrupt. This call returns 0 on successful execution. Otherwise it returns non zero error code.

[0936] ERR_RESETSC2 Smart card reset failure due to Null pointer for return data.

[0937] ERR_COMMSC2 One or more of the passed parameters is out of range or a NULL pointer.

[0938] ERR_INITSCI SCI initialization failure due to that the UART could not apply VCC to the Smart Card.

[0939] Description

[0940] Called by user at power up to initialize internal interface parameters. Initialize pointers to the register locations, initialize the global data area and initialize the UART so that the work wait time and transmitter holding register empty interrupts are masked. The IRQ number passed is chosen by the user and the unsigned integer for the mailbox status word is allocated by the user. It is important to note that the Smart Card interrupt service routine is not loaded into the IRQ vector table, it is up to the user to load the vector to the Smart Card ISR separately.

[0941] Function Overview

[0942] Initialize the following pointers to point to the hardware interface registers of the Smart Card UART. These are global parameters: scdata_reg=SCURB, sccc_reg=SCCCR, scs_reg=SCSR, scic_reg=SCICR, scbdr_reg=SCBRD, scvccdt_reg=VDTIM scwwtim_reg=WWTIM.

[0943] Initialize the return status parameters irq_num and *status into the global data structure. Initialize in the global data structure the internal state machine of the Smart Card interface to UNDEF_ST (undefined state).

[0944] Clear the SCIC register to initialize the UART for configuration.

[0945] Set the mask bits for the work wait time and transmitter empty interrupts and set the FREE bit in the SCIC register to enable transmission on the UART.

[0946] smcInitSmartCardUart( )

[0947] Syntax

[0948] unsigned char smcInitSmartCardUart( )

[0949] Returns

[0950] This call returns 0 on successful execution. Otherwise it returns non zero error code.

[0951] Error Code

[0952] ERR_INITSCI SCI initialization failure due to most probable cause of the Smart Card is not detected

[0953] Description

[0954] This routine would be called to set the UART with default parameters prior to issuing a reset command. The VCCEN enable routine is called to enable the power to the Smart Card.

[0955] The Work Waiting time it is important to recognize the units that the value that is passed in from the application software and the correlation to the unit that the hardware timer is using. For example the application software will pass in a value of seconds. The UART hardware is counting cycles which is 1/ETU, cycles per ETU times 16. The clock speed of the UART is running at a rate of sixteen times the clock to the card. The work wait time default is set so that when a Reset command is issued the time out will occur in 1.2 seconds. This number is derived from 373/4.6 MHz *124=10 mS*120=1.2 S. All time passed from the user will be in 10 mS units.

[0956] Function Overview

[0957] Write to SCICR (Bits 0-1): 1=4.6 MHz Clock Frequency

[0958] Write to SCICR (Bit 7): VCCEN set active through call to smcSmartCardVccen

[0959] Write to BDR (Bits 0-15): 24 Initial baud rate divisor number

[0960] Write to SCCCR (Bits 4-7): 3 Number of NAK retries allowed per character

[0961] Write to SCCCR (Bits 0-3): 3 Number of Parity error retries allowed per character

[0962] Write to SCCCR (Bits 8-15):0 Additional Guardtime ETU's

[0963] Set state Smart UART state machine to Pre Reset State (PR_RST_ST)

[0964] smcResetSmartCard( )

[0965] Syntax

[0966] unsigned char smcResetSmartCard( )

[0967] Returns

[0968] The return from this call does not indicate a successful operation but rather if the operation was allowed and if the passed parameters were correct. The completion of this operation will be indicated to the application software through an interrupt. This call returns 0 on successful execution. Otherwise it returns non zero error code.

[0969] Error Code

[0970] ERR_RESETSC Smart Card reset failure

[0971] Description

[0972] This routine resets the Smart Card and retrieves the Answer-to-Reset (ATR) string (usually 11-Bytes). The completion of the ATR will result in an interrupt. smcResetSmartCard will enable the reset line to the Smart Card through the SCCR register. Using the addresses from the global data structure that was set up using smcIntrfcInit the interrupt handler will place the received characters into the buffer specified and increment the size of the returned string. The end of the Reset transaction will be when the Work Wait Timer expires 1.2 seconds after the last character has been received from the Smart Card. After the Work Wait Timer expires the user will be notified through the IRQ that the user designated for the Smart Card Interface in the smcInitIntrfc function.

[0973] The reset command cannot be issued without having VCCEN active to the Smart Card. Before any call to the reset routine the card must have been inserted and successfully powered up. Once the ICOM (Initialization complete) interrupt has been received the initialization of the UART is complete and the smcResetSmartCard function can be called. The ICOM interrupt will have assured. that there is an active VCC to the card and also assured that there is a card installed.

[0974] The work wait time error interrupt is unmasked since there will now be characters being exchanged between the interface and the Smart Card.

[0975] Function Overview

[0976] Verify passed parameters (No Null pointers) and pass them in global data structure to interrupt handler routine

[0977] Test to see if the interface can issue a Reset. Current state must be Pre Reset State

[0978] Enable Work Wait time error detection

[0979] Write to SCICR (bit 2=1): Enables the reset line to the Smart Card, command bit will be reset by the hardware after either a response to the reset or a timeout of the reset command. The answer to reset string will be handled in the interrupt handler.

[0980] Initialize size of return string to zero

[0981] See Also

[0982] Interrupt Handler

[0983] smcSetSmartCardUart

[0984] Syntax

[0985] unsigned char smcSetSmartCardUart(

[0986] unsigned char clock,

[0987] unsigned char baud,

[0988] unsigned char xmit_retry,

[0989] unsigned char rcv_retry,

[0990] unsigned long work_wait,

[0991] unsigned char guard_time)

[0992] where:

[0993] Returns

[0994] This call returns 0 on successful execution. Otherwise it returns non zero error code.

[0995] Error Code

[0996] ERR_SETSCI SCI UART configuration failure

[0997] Description

[0998] This routine would be called to set the UART with parameters received from an answer to reset sequence. This routine can be called prior to reset if the default parameters are known. The following parameters are set in this routine:

[0999] The parameters baud rate, wwtime and clock are closely related. Each of the parameters may have different limits depending of what the values of the other two parameters. Please consult table for the relationship.

[1000] Also note that VCC should be enabled before setting the UART, but is not checked in this routine. Note the passed parameters are verified for range accuracy. wwtime is checked in the routine smcCalWrkWt( ), if the time is greater than 1.2 seconds the routine will return a 0 and this routine will return an error condition because of it. This routine will also return an error if the clock selection is not 5,10,20.

[1001] The clock rate can be changed after reset as specified by the CAM in the ATR. The interface is responsible for maintaining phase lock during clock rate change. The clock must never be stopped and restarted when this routine is called.

[1002] Function Overview

[1003] Write to SCICR (Bits 0-1): 1=4.6 MHz, 2=9.2 MHz, 3=18.4 MHz Clock Frequency

[1004] Write to BRD (Bits 0-15): Baud rate divisor number

[1005] Write to WWTIM (Bits 0-16): Work Wait Time

[1006] Write to SCCCR (Bits 4-7): 3 Number of NAK retries allowed per character

[1007] Write to SCCCR (Bits 0-3): 3 Number of Parity error retries allowed per character

[1008] Write to SCCCR (Bits 8-15): 0 Additional Guardtime ETU's

[1009] smcSmartCardCommunication

[1010] Syntax

[1011] unsigned char smcSmartCardCommunication(unsigned char dir, unsigned char sizeout)

[1012] where:

[1013] Returns

[1014] The return from this call does not indicate a successful operation but rather if the operation was allowed and if the passed parameters were correct. The completion of this operation will be indicated to the application software through an interrupt. This call returns 0 on successful execution. Otherwise it returns non zero error code.

[1015] Error Code

[1016] ERR_COMMSC1 The UART state machine is not in the correct state to start a transaction.

[1017] ERR COMMSC2 Problem of data direction is from CAM and size of expected data is zero.

[1018] ERR_COMMSC3 Passed value for Work Wait time is too large for current baud rate to handle.

[1019] Description

[1020] This routine is called to invoke the communication sequence necessary to send a command to the Smart card (CAM) interface, in accordance with the ISO 7813-3 standard. Some commands transfer data to the CAM while others retrieve data from the CAM.

[1021] This function will send the first byte of the command header to the Smart Card and rely completely on the RTSL Smart Card interrupt handler to complete the transaction. The error codes that are returned by this function deal strictly with requirements needed to start a transaction and do not cover possible errors that may occur during the transaction.

[1022] The pointers passed to this routine (scout, scin, sizein) must not be NULL pointers. If any of the pointers are NULL then the function will return an error and the transaction will not have been started. It is assumed that the pointers that are passed by the user point to memory locations that are sufficient in size to complete the transaction.

[1023] Prior to calling this function the user must have called and completed successfully the smcSmartCardReset function. This routine is usually very time critical. The successful completion of the CAM communication will result in an interrupt to the user.

[1024] The RTSL interrupt handler for the Smart Card transactions will follow the I/O sequence in the following steps:

[1025] Send a 5-Byte header to the CAM.

[1026] Read a one-Byte CAM response (ACK byte). Do not store in the input buffer.

[1027] Send data to the CAM, or read data from the CAM, depending on the dir indicator.

[1028] Read the 2-Byte response, and store it in the input buffer.

[1029] Protection Level

[1030] This routine needs to run with protection OFF

[1031] Function Overview

[1032] Check Smart Uart state machine to verify that the interface is ready for a message transaction. Current state must be Post Reset state (PST_RST_ST)

[1033] Verify passed parameters (No Null pointers) and pass them in global data structure to interrupt handler routine

[1034] Advance Smart Uart state machine to message transaction state

[1035] Initialize the global data area with passed parameters to be used by interrupt handler

[1036] Initiate the transaction by sending first byte of command header, (Interrupt handler will handle the rest of the transaction)

[1037] Enable Work Wait time error detection

[1038] Return to caller

[1039] See Also

[1040] Interrupt Handler

[1041] smcSmartCardStatus( )

[1042] Syntax

[1043] unsigned char smcSmardCardStatus( )

[1044] Returns

[1045] This call returns 1 on successful execution. Otherwise it returns zero error code.

[1046] Description

[1047] This routine returns the In/Out status of the Smart Card.

[1048] Function Overview

[1049] Read SCSR bit SCSTAT(9) if equal to one then Card is detected.

[1050] Return a 1 if Card is detected and 0 if not.

[1051] smcSmartCardIsr( )

[1052] Syntax

[1053] void interrupt smcSmartCardIsr(void)

[1054] Returns

[1055] Nothing( )

[1056] Description

[1057] This routine is an interrupt service routine. The SCS register is read to determine which interrupts occurred. The interrupts for the Smart UART are not mutually exclusive so several interrupts could be present at one time. On each activation of the ISR the SCS register must be completely scanned. The functions that the ISR will invoke are stored in an array of void function pointers called smcisr_functions[]. This array has an element for each bit in the SCS register. Bits that are not used in the SCS register will have the corresponding elements in the array initialized to a NULL pointer. SCS register bits will have their corresponding array elements initialized with pointers to the individual functions that will process those causes of interrupts.

[1058] This is the interrupt service routine that will handle the interrupt from the Smart UART. There are eight (10) possible causes for an interrupt to be generated by the Smart Card UART. These interrupts are also listed in increasing priority.

[1059] RCWE: Receive Character Waiting Error (FIFO full no further characters will be received)

[1060] PE: Parity Error

[1061] NAK: NAK error

[1062] ARST: Answer to Reset never occurred

[1063] VCCDE: VCC Detect Event

[1064] SMDE: Smart Card Detect Event

[1065] ICOM: Initialization complete

[1066] WWTE: Work Wait time out error

[1067] DR: Data Ready

[1068] THRE: Transmitter Holding Register Empty

[1069] Function Overview

[1070] Shift the value in the SCS register from right to left shifting out the four most significant bits, these are receive FIFO count bits. Keep track of the number of shifts that have been performed.

[1071] Examine most significant bit to see if it is set. Invoke an ISR if the bit is set using the number of shifts performed to index the array of ISR pointers. If array has a NULL pointer for the indexed element do not process.

[1072] Examine to shifted value of the SCS register if any other bits are set. If no further bits are set then the function can be exited else go on step 4. This is done for performance purposes, there is no need to do any further processing if there are not any other interrupt conditions set.

[1073] Shift from right to left 1 bit and perform step 2 until 16 shifts have been performed.

[1074] General Purpose UARTs

[1075] The circuit 200 hardware includes three UARTs. One is dedicated to the ‘SmartCard®” interface. The other two UARTs are general purpose; their support software will be discussed in this section.

[1076] Initialization

[1077] At power-up there is required initialization by the application software. The application software will have to invoke the function uartIntrfcInit with the required parameters to initialize the firmware.

[1078] Module Description

[1079] All UART control and status registers are memory mapped and are fully accessible by the API. The support software for all UARTs will execute in the application software domain, using IRQ interrupts.

[1080] The UART is a simple two wire, buffered UART with optional software flow control (XON/XOFF). The functionality consists of transmit and receive of single characters. Features of the UART drivers include:

[1081] Programmable Baud rate

[1082] Programmable number of start/stop bits (1 or 2)

[1083] Programmable number of data bits (7 or 8)

[1084] The UART registers are located in the Communication Processor address space.

[1085] Assumptions

[1086] Full duplex interface

[1087] No Echo of received characters

[1088] ASCII characters only

[1089] Interface will initialize on system reset

[1090] Character-based driver

[1091] The RTSL driver supplied will allow the user to support (XON/XOFF) flow control. There is not a receiver that is able to unconditionally accept a sender's data A flow control protocol allows the receiver to control the rate or amount of data from the sender during the course of a transaction.

[1092] Operation

[1093] After initialization the user will call the uartSetUart function to define parameters such as baud rate, data size and parity enable. The UART driver is single event driven which means that the user will get an IRQ after each character is sent or received. Other single events such as character errors and breaks will also generate IRQs to the user. The development of the UART driver is at the discretion of the application developer.

[1094] Inter-Integrated Circuit (I²C) Bus Driver

[1095] The circuit 200 will support the I²C protocol. To interface the application program to the hardware, a driver known as the I²C Driver will handle several API functions that enable the application to send, receive and configure some parameters of the I²C bus.

[1096] Module Description

[1097] As defined, the device that is currently transmitting is known as the transmitter and the device that is currently receiving is known as the receiver. Each device is recognized by a unique address and can operate as either a transmitter or receiver. A device can also be recognized and known as a master or slave. The master is the device that initiates the data transfer. The slave is the device that is addressed by the master. The circuit 200 is assumed to be programmed as the master on a single master bus.

[1098] Multi-Master

[1099] Although recognized as a multi-master protocol, this implementation will not support an arbitrated multi-master bus. The circuit 200 may be programmed either as a master or slave, but will only support one master on the bus.

[1100] Bit Rate

[1101] The Low Speed Mode, the 100 kbit/s, is the only mode supported. Fast Speed Mode of 400 kbit/s is not supported as a master. This does not prohibit operation because the Low-Speed Mode is a subset of the Fast-Speed Mode.

[1102] Addressing

[1103] Only seven bit addressing is supported. Extended 10-bit addressing is not supported as a master. Programming of slave addresses in software using the protocol is also not supported. All addresses are generated internally as part of the device.

[1104] Start Condition

[1105] A start condition must come before any command. A start can be identified by a high to low transition on the data line while the clock is in a high state.

[1106] Stop Condition

[1107] A stop condition will terminate any communication between the slave and master device. A stop can be identified by a low to high transition on the data line while the clock is in a high state.

[1108] Acknowledge

[1109] All data transfers use the acknowledge for each byte transferred. The transmitter releases the SDA line high during the acknowledge clock pulse. The receiver pulls the SDA line low during the acknowledge clock pulse. Any non acknowledge will cause the master to abort the transfer. An exception to this may be made during the last byte of the byte of a data transfer when the master is the receiver. On the last byte transferred, the Master will NAK the byte to single that byte as the last.

[1110] Byte Format

[1111] Each byte is eight bits long. The number of bytes transmitted is limited only in the buffer length used to hold the data. Each byte is followed by an acknowledge bit. Data is transmitted with the most significant bit (MSB) first.

[1112] General Call

[1113] The general call is used to address all devices on the bus at the same time. If a device does not need any data provided by a general call, it may ignore this address by not issuing an acknowledge. If a device does need the data from a general call, it will acknowledge the address and act as a slave receiver. Each byte after the address will be acknowledged by every device capable of using the data.

[1114] The second byte defines one of two potential protocols to follow. If the LSB of the byte is ‘0’ with a value of 0×06, the device will reset and take on the programmable part of their address. If the LSB of the byte is ‘0’ with a value of 0×04, the device will not reset, but will take on the programmable part of their address. All other codes will be ignored.

[1115] If the second byte LSBit is a ‘1’, this is generated from a hardware device general call. Since as a hardware master this device does not know what other devices are on the bus, this call enables it to announce its address in the upper seven bits of the second byte.

[1116] Timing

[1117] The receiver can place the transmitter into a hold state by forcing the clock line low. This places the transmitter into a wait state that enables the receiver to perform other tasks until ready to receive. The receiver releases the clock line which enables the transmitter to continue the data transfer.

[1118] I²C Interface

[1119] Table 37 lists the I2C APIs. These routines are described in more detail in the following section.

[1120] I2cINit( )

[1121] Syntax

[1122] ferror=i2cInit (I2CPBLOCK *pblock);

[1123] where:

[1124] <Address> contains the 7 bit address in bits 7:1. This address is used to represent the I2C device address.

[1125] <Mode> is set to 0 to program the interface as a slave device. A value of 1 in bit 0 indicates the device should respond as a master.

[1126] <*Status> is a pointer that provides a status register at irq time. The irq is used to indicate a previously issued command has completed. It is also used to indicate progressive information about the current driver state or need for information. The register is set by the driver and cleared by the application reading it. It is the responsibility of the application to copy/clear the register during the irq processing to prevent conflict.

[1127] <Irq> is the numeric FW irq to be used as the signal for command completion or event notification. This value should be programmed from 0-x1F.

[1128] <byteTimer> is used by the hardware to provide a byte to byte timer. Any incomplete byte transactions can be aborted using this timer. The timer is in resolutions of 25 usec and is 23 bits wide. A value of zero will turn the timer off. Beware that turning this timer off can cause the hardware to stall if another device fails. The only recovery from this stall is a hardware reset.

[1129] Returns

[1130] ferror NOERROR

[1131] Description

[1132] i2cInit is used to setup the run-time parameters needed for I2C operation. This function must be called before any other I2C functions are executed.

[1133] I2cStatus( )

[1134] Syntax

[1135] ferror=i2cStatus(I2CSTATUS *pblock);

[1136] where:

[1137] Returns

[1138] ferror NOERROR

[1139] Description

[1140] This function will return the current status of the I2C Registers as well as the IRQ status register at the end of the command when signaled by the irq. The organization and content of the status is TBD.

[1141] I2cIOSequence( )

[1142] Syntax

[1143] ferror=i2cIOSequence (uchar I2CAddress,

[1144] uchar *data,

[1145] uint dataLength,

[1146] uint retryCount);

[1147] where:

[1148] I2Caddress=The device address defined in the upper seven bits (bit 1-7). The LSB (bit 0) defines the function as a read or write. 0=write and 1=read.

[1149] *data=Indicates the location to place the incoming data from the read device in <I2Cadress>

[1150] dataLength=The number of bytes expected to receive and store at <*data>

[1151] retrycount=Value used to indicate how many attempts at retransmission is taken before an error is indicated. A value of 0 indicates no retries

[1152] Returns

[1153] ferror NOERROR

[1154] Description

[1155] i2cIOSequenceWithAddress( ) writes to or reads from the I2C device specified in <I2CAddress>. After the <I2CAddress> is sent, the Master will then either send the data referenced by <*data> or receive data for the length of <dataLength> and place the bytes at <*data>. After the transaction is complete, the function will signal the application via the status word <I2CStatus> and <I2CIrq> set during <i2cInit( )>.

[1156] During the transaction. An internal byte attempt timer will manage the byte to byte timing. This parameter <byteTimer> is defined in the <i2cInit( )> function. Any failure to fully receive a valid framed byte will result in this timer expiring and a retry attempted if programmed.

[1157] The caller will define the number of attempts to retry using <retrycount> if the byteTimer expires, an acknowledge fault or framing error will occur.

[1158] I2cIOSequenceWithAddress( )

[1159] Syntax

[1160] ferror=i2cIOSequenceWithAddress(uchar I2CAddress,

[1161] uint address,

[1162] uint addressLength,

[1163] uchar *data,

[1164] uint dataLength);

[1165] where:

[1166] I2Caddress=The device address defined in the upper seven bits (bit 1-7). The LSB (bit 0) defines the function as a read or write. 0=write and 1=read.

[1167] Address=A random access address defined in the device targeted by <I2CAddress>. The format of the address is device dependent. The address will be transmitted MSB first. The address should be left justified in the word <address>. 1^staddress byte in bits 31-24, 2^ndin bits 23-16, 3^rdin bits 15-8, 4^thin bits 7-0.

[1168] addressLength=The length of the address as defined in <address>. This length is measured in 8 bit bytes.

[1169] *data=Indicates the location to place the incoming data from the read device in <I2Cadress>

[1170] dataLength=The number of bytes expected to receive and store at <*data>

[1171] Returns

[1172] ferror NOERROR

[1173] Description

[1174] i2cIOSequenceWithAddress( ) writes to or reads from the I2C device specified in <I2CAddress>. The device is assumed to have read/write and random capability by using <address> as an internal pointer to the data desired. After the I2CAddress and Address is sent, the Master will then either send the data referenced by <*data> or receive data for the length of <dataLength> and place the bytes at <*data>. After the transaction is complete, the function will signal the application via the status word <I2CStatus> and <I2CIrq> set during <i2cInit( )>.

[1175] During the transaction. An internal byte attempt timer will manage the byte to byte timing. This parameter <byteTimer> is defined in the <i2cInit( )> function. Any failure to fully receive a valid framed byte will result in this timer expiring and notification via irq of a failed transaction.

[1176] This function does not attempt any error recovery via retransmission. An error will be indicated in the <I2CStatus>.

[1177] I2cReceive( )

[1178] Syntax

[1179] ferror=i2cReceive(I2CREAD *pblock);

[1180] where:

[1181] *pblock=A pointer that contains the location to write the status words structure.

[1182] Returns

[1183] ferror NOERROR

[1184] Description

[1185] This function will receive a message and place the data at <*data> until <size> or normal completion of the receive data. If <size+1> is reached abnormally, the read is terminated. The driver will then go into hunt mode again, looking for a new start after notifying the application of the error via status.

[1186] MPEG Video Decoder

[1187] Initialization

[1188] The MPEG video decoder requires the following initialization:

[1189] Load the MPEG video decoder microcode into DRAM

[1190] Load the code loader and init. microcode to IMEM set the cpu_cntl register

[1191] Write the “play” command to the command FIFO

[1192] The above will start the MPEG video decoder.

[1193] Module Description

[1194] The run time support for the MPEG video decoder consists of a routine to allow the API to send commands to the video decoder. This routine is vidSendCommand( ). In addition, an initialization routine is needed to setup the MPEG video decoder at bootup time. The bootup sequence for the decoder will leave it in free running “PLAY” mode.

[1195] The Video firmware interfaces with the MPEG video decoder via the command FIFO located in the MPEG video decoder hardware. The command set that needs to be supported by the firmware consists of:

[1196] PLAY

[1197] FREEZE

[1198] STOP

[1199] SCAN

[1200] NEW_CHANNEL

[1201] RESET

[1202] In addition the firmware is responsible for writing the SCR to the MPEG video decoder. The SCR packet handling is described in the TPP section of this software design specification. The SCR is sent to the MPEG video decoder every time that the SCR packet is detected in the DSS stream. The packet SCID for the SCR is determined by the application software at system startup time. The SCR that is sent to the MPEG video decoder is the SCR from the packet, not the system SCR.

[1203] The MPEG video decoder registers are memory mapped. The command FIFO is located in SDRAM. The location of the FIFO is dynamically established during the startup of the MPEG video decoder micro code. The initialization program of the ARM incorporates the checking of a status bit in the MPEG decoder to verify that micro code is running in IDLE state. Once the micro code is running, the location of the FIFO command buffer structure can be read from a dedicated SDRAM address.

[1204] Video Decoder Interface

[1205] The following routines specify the interface to the video decoder.

[1206] vidInit( )

[1207] Syntax

[1208] void vidInit;

[1209] Returns

[1210] The function does not return an error code.

[1211] Description

[1212] Example

[1213] Protection Level

[1214] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1215] vidCommand( )

[1216] Syntax

[1217] void vidCommand(long command);

[1218] where:

[1219] command:

[1220] PLAY

[1221] FREEZE

[1222] STOP

[1223] SCAN

[1224] NEW_CHANNEL

[1225] RESET

[1226] Returns

[1227] There is no error checking in the routine for valid input data range. Validation of the calling parameter is the responsibility of the caller. The function does not return an error code.

[1228] Description

[1229] This function allows the application software to send a command to the MPEG video decoder. The following commands are supported:

[1230] Example

[1231] Note

[1232] This function is NOT re-entrant.

[1233] Protection Level

[1234] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1235] MPEG Audio Decoder

[1236] Initialization

[1237] The MPEG audio decoder initialization writes the default values of Table 38 to the audio control register.

[1238] Module Description

[1239] The runtime support of the MPEG audio decoder consists of:

[1240] PCM changes, API selects from following

[1241] 16 bit, no over sampling

[1242] 16 bit, 256×over sampling

[1243] 18 bit, no over sampling

[1244] 18 bit, 384×over sampling

[1245] Dual channel mode Output mode select

[1246] Ch0=left, Ch1=right

[1247] Ch0=left and right

[1248] Ch1=left and right

[1249] Mute/unmute

[1250] Reset audio mode

[1251] Audio Decoder Interface

[1252] The following routines specify the interface to the audio decoder.

[1253] audinit ( )

[1254] Syntax

[1255] void audIni ( );

[1256] Returns

[1257] The function does not return an error code.

[1258] Description

[1259] The routine initializes the audio decoder to initial state. The initial state is:

[1260] Audio decoder in RESET state and MUTE (No decoding, no output)

[1261] Channel output setup as CHANOLLR (Channel 0 left, Channel 1 right)

[1262] PCM setup as PCM16₁₃0 (16 bit output no oversampling)

[1263] Example

[1264] Protection Level

[1265] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1266] See Also

[1267] audCommand( )

[1268] audCommand( )

[1269] Syntax

[1270] void audCommand(long command);

[1271] where:

[1272] command: Maximum one element from each group below OR'd together

[1273] Group1: CHAN0L1R or CHAN0LR or CHAN1LR

[1274] Group 2: PCM16_0 or PCM16_256 or PCM18_0 or PCM18_256

[1275] Group 3: MUTE or UNMUTE

[1276] Group 4: RESET

[1277] Returns

[1278] There is no error checking in the routine for valid input data range. Validation of the calling parameter is the responsibility of the caller. The function does not return an error code.

[1279] Description

[1280] The function examines the command parameter and takes action upon each of the commands that are OR'd together. It will only test for one element from each of the groups (1, 2, 3 and 4) below. If more than one element from a group is specified, the outcome of the call is undetermined.

[1281] Subsequent calls will only change those values that are different from the previous call. See examples below.

[1282] Example

[1283] Note: When the RESET command is issued, all other commands in that call will be ignored, the values remain those set in previous calls.

[1284] Protection Level

[1285] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1286] NTSC/PAL Encoder

[1287] Initialization

[1288] The initialization of the Video Encoder is limited to setup of the VIDEO_MODE0, VIDEO_MODE1 and HSYNC_OFFSET registers according to Table 39.

[1289] Module Description

[1290] The NTSC/PAL encoder will be directly accessible from the ARM.

[1291] Close caption data consists of 2 characters per frame, encoded in line 21 (odd field). The generation of the CC data is automatically done by the NTSC/PAL encoder; it uses the data in the caption data registers. The data is written to these registers by the OSD.

[1292] The MacroVision copy protection will be supported. The activation/de-activation will take place via an ARM RTSL routine. It will be callable from the API.

[1293] NTSC/PAL Encoder Interface

[1294] The following routines specify the interface to the NTSC/PAL encoder.

[1295] encInit( )

[1296] Syntax

[1297] void encInit(uchar mode, enc_s *parms);

[1298] where:

[1299] The video_mode0_register and video_model_register have to be setup to reflect the appropriate bit pattern for the respective registers.

[1300] Hsync_offset contains one of 3 values according to the following table:

[1301] The video mode 0 and 1 bits need to be setup to reflect the appropriate function according to the specification.

[1302] Note: If the parms parameter upon call is NULL, the software will setup the encoder for the default parameters as defined in the specification.

[1303] Returns

[1304] There is no error checking in the routine for valid input data range. Validation of the calling parameter is the responsibility of the caller. The function does not return an error code.

[1305] Description

[1306] encInit( ) allows the caller to initialize the NTSC/PAL encoder for the appropriate mode.

[1307] Example

[1308] Protection Level

[1309] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1310] encCommand( )

[1311] Syntax

[1312] void encCommand(uchar mode, long command);

[1313] where:

[1314] Returns

[1315] There is no error checking in the routine for valid input data range. Validation of the calling parameter is the responsibility of the caller. The function does not return an error code.

[1316] Description

[1317] encCommand allows the caller to change the current setup of the NTSC/PAL encoder with the appropriate parameters.

[1318] The ‘command’ parameters can contain any or all of the parameters OR'd together into the appropriate parameter. As it is shown, every bit contains either an ENABLE or a DISABLE type command and they are mutually exclusive. The runtime support software will evaluate each ‘command’ parameter according to the table below.

[1319] The commands are defined in the encoder.h file as follows:

[1320] Note that the commands are listed in pairs of ‘ENABLE’ or ‘DISABLE’ type of function. If an ENABLE and DISABLE type function are both OR'd together in the same call, the DISABLE type function prevails.

[1321] For color bar generation, the following are defined in encoder. h:

[1322] Example

[1323] NOTE: Only those commands that are specified in the ‘command’ parameter will be changed. All other command parameters remain as they were previously. If mutually exclusive parameters are specified, the DISABLE type overrides the ENABLE type.

[1324] Protection Level

[1325] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1326] encGetStatus( );

[1327] Syntax

[1328] char encGetStatus( );

[1329] Returns

[1330] The function returns the status byte from the encoder, with bit description as follows:

[1331] All other bits are 0.

[1332] Description

[1333] The function can be used to obtain the current status of the video encoder. It returns the snapshot at the time the status register was read.

[1334] Protection Level

[1335] This routine needs to run with protection ON, as it accesses the on-chip protected resources.

[1336] On Screen Display (OSD) and Graphics Acceleration

[1337] The OSD and Graphics acceleration modules provide the API-to-firmware interface for all on-screen display and graphics drawing functions. There are two major sections, OSD, and graphics acceleration. Each section consists of an overview of the API capabilities and constraints, followed by the API description.

[1338] The following section details the data structures that are visible to the application developer and common to both the on screen display hardware and the graphics acceleration hardware.

[1339] System Data Structures

[1340] disptype: disptype enumerates all of the possible hardware display types, including half resolution displays.

[1341] Note: the order of the list is important: place at top of the list the display types that require a palette, with BITMAP8HR last. That allows a fast check on the attributes of the displayed windows. The code works correctly with any list order.

[1342] osdpaltype: OSDPaltype enumerates all possible palette types that are available.

[1343] It corresponds to the number of entries/colors in the palette table. If the value is zero, no palette structure is needed: for example this is the case of the video windows.

[1344] osdblendtype: OSDBlendType enumerates all possible blending types that are available.

[1345] memtype: memtype is used to describe the different memory types that the bitblt module may transfer data to and from. The bitblt module needs to know what kind of memory it is accessing because each memory type requires different hardware signaling.

[1346] typedef enum {SDRAM, EBIF} memtype;

[1347] Buffer: Buffer defines a basic structure that defines a continuous region of memory. The storage is cwBuffersize words long, at the address pBuffer.

[1348] Hpalette: HPALETTE defines the handler of a palette that has been created by using the related API routine. Actually, its value is equal to the address of the buffer where the palette is stored.

[1349] typedef word HPALETTE; /* Palette Handler */

[1350] Hdisplay: HDISPLAY defines the handler of a hardware display that has been created by using the related API routine. Actually, its value is equal to the address of the buffer where the display structure is stored.

[1351] typedef word HDISPLAY; /* Palette Handler */

[1352] Error Conditions

[1353] #define E_NONE 0

[1354] No error.

[1355] #define E_ERROR 0xFF

[1356] General purpose error: some kind of error occurred.

[1357] #define E_HDM_ADJUSTED_VIDEO_DIM 0x80

[1358] The display coordinates were changed by the routine.

[1359] #define E_HDM_MAX_PHYSICAL_EXCEEDED 0x81

[1360] The application tried to create more than eight physical displays. A virtual display is created instead of a physical one.

[1361] #define E_MEMORY_TYPE_INCORRECT 0x82

[1362] The application tried to create a physical display with the display buffer stored in the external memory.

[1363] A virtual display is created instead of a physical one.

[1364] #define E_HDM_DISPLAY_BUSY 0x83

[1365] The application tried to create a physical display with the same ID of another active display. A virtual display is created instead of a physical one.

[1366] #define E_HDM_VIDEO_DISPLAY_EXCEEDED 0x84

[1367] The application tried to create more than one video display (either decimated or full screen). A virtual display is created instead of a physical one.

[1368] General Module Description

[1369] The On Screen Display (OSD) hardware is capable of concurrently managing up to eight different types of displays or virtual windows concurrently on a NTSC or PAL type monitor.

[1370] Error! Reference source not found. shows three different types of displays: a 4:4:4 Graphic image, a 4 bit bitmap, and an MPEG video. We use the term display instead of window because each display may be of a different type, such as:

[1371] Graphic or “TrueColor”—1 or more may be shown

[1372] Bitmap—1 or more may be shown

[1373] MPEG Video—up to 1 may be shown

[1374] The firmware maintains attributes for each display, such as size, position, palette if necessary, and display type.

[1375] TrueColor displays use Luminance(Y), Red Chrominance (Cr), and Blue Chrominance (Cb) color components to store an image. The CbYCr image is stored in either 4:4:4 or 4:2:2 format. 4:4:4 is a 24 bit format, where each color component is 8 bits, resulting in 24 bits per pixel. 4:2:2 halves the chrominance information, resulting in an average pixel depth of 16 bits.

[1376] Bitmaps are 1,2,4, or 8 bits pixel. Each pixel is an index into the 24 bit hardware color lookup table. The palette attribute contains an offset into the hardware palette. This offset is used to calculate the actual color index into the table. Using the color index, the 24 bit CbYCr value can be determined.

[1377] The MPEG video window is capable of displaying a full size NTSC or PAL video, or a decimated version of the MPEG video. Only one video display may be used at any time.

[1378] Up to eight overlapping displays can be shown concurrently on the screen. If a hardware cursor is required, then one hardware window must be used for that purpose, leaving seven application programmable hardware displays.

[1379] The on screen display firmware is responsible for managing the following hardware resources:

[1380] Color Lookup Table (CLUT) or Palette

[1381] Eight Hardware Windows

[1382] Hardware Cursor

[1383] The OSD maintains a 256 entry color lookup table. Each entry in the table contains a 24 bit CbYCr color value. The lookup table is used by bitmap displays to generate CbYCr 24 bit color values from the 1,2,4, or 8 bit color indices.

[1384] Any number of user palettes may be defined on the hardware palette. The palettes may use mutually exclusive regions of the palette memory, or color palettes may overlap others. Error! Reference source not found. shows two examples of how the CLUT may be organized. Example (a) shows four non-overlapping palettes. example (b) shows 4 palettes, each one larger bit palette overlapping the smaller. An application may use a combination of overlapping and non-overlapping palettes if desired.

[1385] Once a palette is defined, it may be attached to a bitmap display. The bitmap display will then use that particular palette to define its new color-set. It is the responsibility of the application to make sure the entries in the color palette are correct. Application firmware will not check for color consistency across hardware displays.

[1386] The application software is required to perform the necessary housekeeping and memory management on the CLUT, including:

[1387] Tracking where in the CLUT all of the palettes are

[1388] Palette memory fragmentation (see cltFreePalette( ) below)

[1389] Palette Color management, i.e. making sure color are consistent with application requirements.

[1390] During repeated cltNewPalette( ) and cltDeletePalette( ) function calls, the 256 palette memory may become fragmented. For example, Error! Reference source not found. shows how fragmentation of the memory palette could prevent optimum use. At first, 6 different palettes were active in the palette. Then, three of the 2 bit palettes were freed, leaving small gaps in between the larger palettes. Item 4 in the figure shows how the palette was allocated after the palette memory was packed. Again, it is the responsibility of the application to determine how to manage this issue.

[1391] The hardware window management API is responsible for managing the OSD hardware that controls the display windows. The OSD allows up to 8 different displays to be viewed at any given time. The following display types are allowed:

[1392] Bitmap 1 bit/pixel

[1393] Bitmap 2 bits/pixel

[1394] Bitmap 4 bits/pixel

[1395] Bitmap 8 bits/pixel

[1396] CbYCr 4:4:4 24 bits/pixel

[1397] CbYCr 4:2:2 16 bits/pixel (avg.)

[1398] MPEG video (full size or decimated)

[1399] In addition, a half-resolution mode for Bitmap and CbYCr 4:4:4 displays is allowed. This features essentially allows a horizontally-decimated-by-two image to be stored in memory. The decimated image is rendered full size by the hardware, which replicates every pixel horizontally on the output. Only decimated half, quarter or eighth resolution MPEG video displays are maintained by the OSD firmware.

[1400] A hardware display may be created anywhere in application memory, such as SDRAM or memory on the external extension bus. However, due to internal bandwidth requirements of the circuit 200, only displays created in SDRAM may be rendered by the OSD hardware. A hardware display on the extension bus must always have a Z plane priority less than 8, which will ensure that the screen is invisible (because the top 8 displays are managed by the OSD hardware). This is not true for displays created in SDRAM, which do not have a priority.

[1401] An application may create as many displays as needed within available hardware resources. This feature allows the application to create more displays in SDRAM than the OSD hardware can display. For example, if an application creates 10 different displays, only 8 of them will be viewable.

[1402] The OSD determines which display is viewable through 2 attributes: its id and a show/hide bit. If the display id is between 0-7, then it corresponds to one of the 8 Z-plane levels managed by the OSD. The top level display is id 0, the bottom is id 7. Id or level 0 may be used by the hardware cursor if needed, but otherwise may be used as the highest priority hardware display. Only one hardware display is allowed per Z-Plane. This is because the OSD allows the user to overlap hardware windows. Windows with a lower Z-plane will overlap windows with a higher Z-plane. See Error! Reference source not found. for an illustration. The API allows an application to set what level a display should be. If a display is set to a plane between 0 and 7, an application can control whether it is viewable or not by calling a function that will set the visibility of the window.

[1403] Note that a portion of a display of any type, except for the decimated MPEG windows, can lie outside the visible part of the screen: the part of the display that is out of the screen is automatically cropped. There are only two limitations: the upper-left corner of a window must lie inside the video screen and the display size cannot be greater than the screen dimension.

[1404] If a display is not between 0-7, then is should be marked VIRTUAL (see irqInit( )for details). Virtual displays work just like normal displays, except that they cannot be viewed.

[1405] User application code is responsible for managing the OSD window memory. The user provides starting addresses for each hardware window it creates. The application software will provide as much memory management support software as needed. For example, if memory fragmentation occurs, it will be up to the application software to pack the display memory (see Error! Reference source not found. for a related problem).

[1406] Bitmap, graphic 4:4:4 or 4:2:2 displays may be blended with an MPEG video display when they overlap the video display or with the background color when they don't overlap an MPEG window. If window blending is enabled, the amount of blending is determined by a blend factor. Table 42 indicates the supported blending levels.

[1407] Also color blending on the pixel level is supported: this feature is available for the bitmap displays only. If the color blending is enabled, the amount of blending of each pixel is determined by the LSB of the chrominance components of the pixel itself: in other words, the blend factor of a pixel corresponds to the LSB of the Cb and Cr values that are stored in the CLUT entry corresponding to that pixel. As shown in Table 42, the window blending supports 16 different levels, whereas the color blending can support either 4 or 16 levels, according to the selected blending mode. Actually, only four levels of blending are displayed exactly for each pixel: these four main level are those corresponding to the ratios 25%, 50%, 75% and 100% of OSD window contribution. The other levels are achieved by mixing the four main blending levels in every 2×2 pixel square area of the display. The resulting effect should approximate the real 16 level blending. Error! Reference source not found. shows an example of the blending technique.

[1408] The hardware also supports a transparency mode with bitmap, graphic 4:4:4 or 4:2:2 displays. If transparency is enabled, then any pixel on the graphic or bitmap display that's value is 0, will allow video to be displayed. Essentially, 0 valued pixels are considered the transparent color, i.e. the MPEG video underneath or the background color will show through the bitmap.

[1409] Table 43 shows the connection between transparency and blending on the same window.

[1410] OSD Internal Data Structures

[1411] Type Definitions

[1412] OSDParams: defines the parameters stored in the OSD SRAM used by the OSD hardware display module. Actually, this is an exact copy of window attribute area inside the OSD SRAM.

[1413] OSDDisplayCoord: Defines the upper left and bottom right coordinates of a hardware display. The units of the coordinates are in pixels. The coordinates must be even valued. Only the coordinates of the upper-left corner of the display must correspond to a point inside the video screen. Also, the horizontal size and vertical size of a display cannot be greater than the corresponding dimension of the screen (720×480).

[1414] OSDDisplay: Defines all the parameters required to maintain a Hardware Display.

[1415] OSDPalette: Defines the required attributes for a palette.

[1416] This data structure is filled in before being passed to the cltNewPalette( ) function.

[1417] where:

[1418] Note: One color is stored in a 32 bit memory cell: the leading 8 MSB are undefined and the following three bytes contains the color definition, according to the CCIR-601/ CCIR-656 specifications.

[1419] Color Lookup Table Management API

[1420] All Color Lookup Table Management API (Table 45) functions are prefixed by the clt mnemonic. Error! Reference source not found. briefly describes what functions are provided by the circuit 200 firmware for palette management. In general, the firmware will provide the capability to create new palettes, assign palettes to bitmap displays, and change individual colors within a specified palette.

[1421] In this section all the API routines are defined.

[1422] cltQueryPaletteStorage: it returns the number of words that the application must allocate before creating a new color palette structure.

[1423] Syntax:

[1424] word cltQueryPaletteStorage (OSDPaltype paltype);

[1425] cltNewPalette: this function creates a new palette structure. The palette is stored in the memory buffer that has been previously created by the application. The parameters that identifies the palette are the number of colors and, eventually, the index into the CLUT where the palette begins.

[1426] Syntax:

[1427] HPALETTE cltNewPalette (OSDPaltype paltype, uchar clutoffset, Buffer *pbuf);

[1428] cltFreePalette: it deletes a color palette structure.

[1429] Syntax:

[1430] FERROR cltFreePalette (HPALETTE hpalette);

[1431] cltSetDisplayPalette: it associates a color palette to a window. This window could be either an active display or a virtual display.

[1432] Syntax:

[1433] FERROR cltSetDisplayPalette (HDISPLAY hDisplay, HPALETTE hpalette);

[1434] cltGetDisplayPalette: this functions returns the handler of the color palette that is attached to a window.

[1435] Syntax:

[1436] HPALETTE cltGetDisplayPalette (HDISPLAY hDisplay);

[1437] cltSetPaletteColors: it copies an array of colors in the CLUT. The number of colors to be copied and the CLUT offset where the colors have to be copied are defined by the palette structure.

[1438] Syntax:

[1439] FERROR cltSetPaletteColors (HPALETTE hpalette, word *pcolors);

[1440] cltGetPaletteColors: this function reads the colors stored in the CLUT. The number of colors to be read and the CLUT offset where the colors have to be read are defined by the palette structure

[1441] Syntax:

[1442] FERROR cltGetPaletteColors (HPALETTE hpalette, word *pcolors);

[1443] cltSetoneColor: it writes one color in the CLUT. The address id defined by the CLUT offset of the color palette and by the color index inside the palette.

[1444] Syntax:

[1445] FERROR cltSetOneColor (HPALETTE hpalette, word color, uchar index);

[1446] cltSetOneColor: it reads one color in the CLUT. The address id defined by the CLUT offset of the color palette and by the color index inside the palette.

[1447] Syntax:

[1448] FERROR cltGetOneColor (HPALETTE hpalette, word *color, uchar index);

[1449] cltGetPaletteType: this function returns the type (number of colors) of a color palette. If the return value is zero, the palette structure is incorrect.

[1450] Syntax:

[1451] OSDPaltype cltGetPaletteType (HPALETTE hpalette);

[1452] cltPalTypeRequire: this function returns the palette type required by a window display. If the display does not require a palette structure (for example, it is a video display or a YCrCb display), the return value is zero.

[1453] Syntax:

[1454] OSDPaltype cltPalTypeRequire (HDISPLAY hdisplay);

[1455] Following is a brief description of some of the color lookup table API commands.

[1456] cltQueryPaletteStorage( )

[1457] Syntax

[1458] word cwPalBuffer=cltQueryPaletteStorage(OSDPaltype paltype);

[1459] where:

[1460] paltype The type of palette to query for, as defined by one of the entries in OSDPaltype.

[1461] Returns

[1462] cwPalBuffer, Number of words application should malloc( ) for use in allocating internal storage for palette as required by palette defined by pal.

[1463] Description

[1464] cltQueryPaletteStorage( ) is used to determine how many words of memory are required by cltNewPalette( ).

[1465] Algorithm

[1466] Actually, the return value is constant, since the memory storage area does not depend on the number of colors.

[1467] Example

[1468] HPALETTE hpalette;

[1469] word cwpalMemSize;

[1470] /* Allocate Memory Required by firmware to maintain palette information */

[1471] cwpalMemSize=cltQueryPaletteStorage(Pal2Bit);

[1472] See Also

[1473] cltNewPalette( )

[1474] cltDeletePalette( )

[1475] cltNewPalette( )

[1476] Syntax

[1477] HPALETTE hPalette=cltNewPalette(OSDpaltype paltype, uchar clutoffset, Buffer *pbuf);

[1478] where:

[1479] Returns

[1480] hpalette, A handle value returned by cltNewPalette( ) that identifies the firmware hardware palette with application software.

[1481] If hPalette==NULL, then an error occurred. Possible error conditions are:

[1482] 1. invalid palette type.

[1483] 2. invalid offset.

[1484] Description

[1485] cltNewPalette( ) creates a palette of type paltype.

[1486] Example

[1487] HPALETTE hpalette;

[1488] word *palmem;

[1489] Buffer buffer;

[1490] /* Allocate memory for palette */

[1491] buffer.cwBufferSize=cltQueryPaletteStorage(Pal2Bit);

[1492] buffer.pbuffer=(word *) malloc (buffer.cwBufferSize * sizeof(word) );

[1493] /* Create Palette */

[1494] hPalette=cltNewPalette(Pal2Bit, 8, &buffer);

[1495] See Also

[1496] cltQueryPaletteStorage( )

[1497] cltFreePalette( )

[1498] Syntax

[1499] FERROR fError=cltFreePalette(HPALETTE hpalette, Buffer *pbuf);

[1500] where:

[1501] hPalette A handle identifying a palette created by cltNewPalette( ).

[1502] pbuf The internal buffer storage structure that was created by cltNewPalette

[1503] Description

[1504] This function frees up the memory associated with the creation of hpalette. The application software is responsible for cleaning up the memory stored in pbuf.

[1505] It will return 0, if no errors occurred, and a non-zero value if an error occurred.

[1506] The application software is required to ensure that no hardware windows are using the palette before it is freed. This routine will not change any values in the CLUT table.

[1507] Example

[1508] Buffer buffer;

[1509] /* The deletion of a palette must be the same as the creation- a two part process. */

[1510] cltFreePalette(hPalette, &buffer);

[1511] free(buffer.pBuffer);

[1512] See Also

[1513] cltNewPalette( )

[1514] cltSetDisplayPalette( )

[1515] Syntax

[1516] FERROR fError=cltSetDisplayPalette(HDISPLAY hDisplay, HPALETTE hPalette);

[1517] where:

[1518] hDisplay: handle to a display

[1519] hpalette: handle to palette being used for hardware display indicated by hDisplay

[1520] Returns

[1521] fError=0, No Errors

[1522] Possible error conditions are:

[1523] 1. the palette does not correspond to the display type.

[1524] Description

[1525] This function will attach a palette indicated by hPalette to a hardware display indicated by hDisplay. If the display is not a bitmap display, the function will have no effect. A non-zero value will be returned if an error occurs.

[1526] In order to reduce visible artifacts that may be caused by changing the OSD palette, the change should only take place when the display is inactive, or during the vertical blanking interval.

[1527] See Also

[1528] cltGetDisplayPalette( )

[1529] cltGetDisplayPalette( )

[1530] Syntax

[1531] HPALETTE hPalette=cltGetDisplayPalette(HDISPLAY *phDisplay);

[1532] where:

[1533] phDisplay Pointer to a Display Handle.

[1534] Returns

[1535] hPalette, the palette associated with phDiplay.

[1536] Description

[1537] cltGetDisplayPalette( ) returns a handle to the palette attached to the hardware display indicated by phDisplay.

[1538] See Also

[1539] cltSetdisplayPalette( )

[1540] cltSetPaletteColors( )

[1541] Syntax

[1542] FERROR fError=cltSetPaletteColors(HPALETTE hpalette, word *pcolors);

[1543] where

[1544] hPalette Handle to a palette

[1545] pcolors An array of color values;

[1546] Returns

[1547] ferror=0, No Errors

[1548] Possible error conditions are:

[1549] 1. invalid palette parameters

[1550] Description

[1551] Sets the palette indicated by hPalette with the colors in pcolors. These colors will overwrite any other colors that were stored in the OSD for this palette.

[1552] The actual writing of the color data to the OSD palette memory should be restricted to the vertical blanking interval to reduce visual artifacts.

[1553] Example

[1554] HPALETTE hPalette;

[1555] OSDPaltype paltype;

[1556] word pcolorset[4]={YELLOW, BLACK, WHITE, BLUE}; hPalette=cltGetPalette(&hDisplay);

[1557] /* Paltype will tell us how many entries are in this palette, so we know how many colors to set. */

[1558] paltype=cltGetPaletteType(&hPalette);

[1559] if (paltype==Pal2Bit) { /* paltype is valid, i.e. this is a 2 bit CLUT, which requires four colors */ cltSetPaletteColors(hPalette, pcolorset);

[1560] }

[1561] See Also

[1562] cltGetPalette( )

[1563] cltGetPaletteType( )

[1564] cltSetOneColor( )

[1565] Syntax

[1566] FERROR fError=cltSetOneColor(HPALETTE hpalette, word color, uchar index);

[1567] where

[1568] hPalette Handle to a palette

[1569] colors The color value;

[1570] index The offset of the color inside the palette.

[1571] Returns

[1572] fError=0, No Errors

[1573] Possible error conditions are:

[1574] 1. invalid palette parameters

[1575] 2. invalid index

[1576] Description

[1577] Sets one entry in palette indicated by hpalette. This color will overwrite the color that was stored in the CLUT.

[1578] The actual writing of the color data to the OSD palette memory should be restricted to the vertical blanking interval to reduce visual artifacts.

[1579] Example

[1580] HPALETTE hpalette;

[1581] OSDPaltype paltype;

[1582] word color=YELLOW;

[1583] unsigned char index=2;

[1584] hPalette=cltGetPalette(&hDisplay);

[1585] /* Paltype will tell us how many entries are in this palette, so we now how many colors to set.

[1586] paltype=cltGetPaletteType(&hPalette);

[1587] if (paltype==Pal2Bit) { /* paltype is valid, i.e. this is a 2 bit CLUT, which requires four colors */

[1588] cltSetOneColor(hPalette, color, index); /* set the

[1589] third palette entry */

[1590] }

[1591] cltGetPaletteColors( )

[1592] Syntax

[1593] FERROR fError=cltGetPaletteColors(HPALETTE hpalette, word *pcolors);

[1594] where

[1595] Returns

[1596] fError=0, No Error

[1597] Possible error conditions are:

[1598] 1. invalid palette parameters

[1599] Description

[1600] cltGetPaletteColors( ) will copy all of the colors for the palette indicated by hPalette into the array indicated by pcolors. Note that pcolors is not a pointer to the internal colors array, so changing the values in pcolors once cltGetPaleteColors( ) has completed will not change the palette colors.

[1601] Example

[1602] word pcolors[4];

[1603] HPALETTE *hPalette;

[1604] OSDPaltype paltype;

[1605] hPalette=cltGetPalette(hDisplay);

[1606] paltype=cltGetPalettetype(hPalette);

[1607] if (if paltype==Pal2Bit) {cltGetPaletteColors(hPalette, pcolors);

[1608] }

[1609] See Also

[1610] cltSetPaletteColors( )

[1611] cltGetOneColor( )

[1612] Syntax

[1613] FERROR fError=cltGetOneColor(HPALETTE hPalette, word *pcolor, uchar index);

[1614] where

[1615] Returns

[1616] fError=0, No Error

[1617] Possible error conditions are:

[1618] 1. invalid palette parameters

[1619] 2. invalid index

[1620] Description

[1621] cltGetPaletteColors( ) will copy the color for the palette indicated by hPalette into the variable pointed by pcolor.

[1622] Example

[1623] word *pcolor;

[1624] HPALETTE *hPalette;

[1625] OSDPaltype paltype;

[1626] uchar index=3;

[1627] hPalette=cltGetPalette(hDisplay);

[1628] paltype=cltGetPalettetype(hPalette);

[1629] if (if paltype==Pal2Bit) {cltGetPaletteColors(hPalette, pcolor,index);

[1630] }

[1631] cltGetPaletteType( )

[1632] Syntax

[1633] OSDPaltype paltype=cltGetPaletteType(HPALETTE hPalette);

[1634] where

[1635] hPalette Handle to a palette

[1636] Returns

[1637] paltype: A palette type as defined by OSDPaltype.

[1638] Description

[1639] cltGetPaletteType( ) returns the type of palette indicated by hPalette.

[1640] Hardware Display Management Software Architecture

[1641] The hardware display management (hdm) is responsible for controlling the OSD windowing hardware of the circuit 200. This document uses the term hardware display instead of hardware window to describe one of the eight OSD hardware controlled windows. This is because from a software perspective, one can have many “windows” in a hardware display.

[1642] The hdm is responsible for maintaining all hardware displays. There are three main types of displays: bitmap, graphic, and video. They are outlined in Table 46.

[1643] Each Display has an associated list of attributes that describe its characteristics. Table 47 defines the attributes for each of the three display types.

[1644] id: The id attribute has three different meanings:

[1645] If the display is viewable, then the id corresponds to a value 0≦id<8. In this case it indicates the Z-plane level of the display.

[1646] If the display is a virtual display. then the id≧8.

[1647] If the display is a full screen MPEG display, then id value is not significant.

[1648] Note that a viewable decimated MPEG video display would have a value corresponding to its Z-plane.

[1649] Coordinates: The top left (x0,y0) and bottom corner (x1,y1) coordinates of the display. Due to hardware limitations there are a few constraints on where a display may be positioned. For all displays:

[1650] x0 must be an even pixel

[1651] x1 must be an odd pixel

[1652] x0<720

[1653] y0<480

[1654] x1−x0<720

[1655] y1−y0<480

[1656] If the display is a decimated video display, then also:

[1657] y0 must start on an even pixel

[1658] y1 will always be odd (because decimated display heights are always even).

[1659] fVisibility: Defines whether or not the display is viewable or not.

[1660] fTransparency: Indicates whether or not transparency is enabled for that display. The fTransparency attributes works for all bitmap and graphic displays.

[1661] fBlend: Indicates whether or not window blending is enabled for that display. The fBlend attribute works for all bitmap and graphic displays. It contains the two bits that identify the blending mode.

[1662] If blending and transparency are enabled, then when that display overlays a video image, 0 valued pixels will be transparent, and all other pixels will be blended with the video.

[1663] BlendFactor: Determines how much to blend the graphic or bitmap display with the video display (window blending). See Table 48.

[1664] ChannelControl: Every hardware display except for VIDEO displays have a ChannelControl attribute. This attribute defines which output ports the OSD information will be displayed. Table 49 defines the valid values for this attribute.

[1665] ColorBlend: Indicates whether or not color blending is enable for that display. The ColorBlend attribute works for all bitmap displays.

[1666] If blending and transparency are enabled, then when that play overlays a video image, 0 valued pixels will parent, and all other pixels will be blended g to the LSBs of Cb and Cr.

[1667] Palette: The palette attribute is used by bitmap displays to define a set of 24-bit CbYCr color values for a set if bitmap index values.

[1668] OSD Memory Interface

[1669] Hardware Display Management API

[1670] All hardware window management API functions are prefixed with hdm. Table 54 describes the functionality of the API. In general, the API allows an application to create hardware windows, move them around on the screen a set their Z plane order.

[1671] The application software is required to manage the memory where the hardware displays are stored. Note that only displays that are in SDRAM may be actually rendered to the display.

[1672] Following are further explanations of some of the function above.

[1673] hdmGetVideoCoords( )

[1674] Syntax

[1675] STATUS status=hdmGetVideoCoords(disptype dtype, word pixX, word pixY,OSDCoords *pcoords)

[1676] where

[1677] Returns

[1678] status The error condition. Possible return value are

[1679] E_NONE: no error

[1680] E_ERROR: invalid display type

[1681] E_HDM_ADJUSTED_VIDEO_DIM: the coordinates of the upper left corner have been changed by the routine.

[1682] Description

[1683] hdmGetVideoCoords( ) determines what the upper left and bottom right x,y coordinate pairs are based upon the video display type, and the upper left corner x,y input parameters. If the dtype is VIDEOHSIZE, then the coordinates for a half resolution video display will be returned. If the dtype is VIDEOQSIZE, then the coordinates for a quarter resolution video display will be returned.

[1684] The value of pixX and pixY must be even. If disptype is VIDEO, pixX and pixY must be zero.

[1685] If the value of pixX1 or the value or pixY1 are greater than the screen size, the window is not cropped: in this case the return values of the coordinates are, respectively, the maximum X size or Y size of the screen: the coordinates of the upper-left corner are adjusted in order to verify the display width and height.

[1686] See Also

[1687] hdmNewDisplay( )

[1688] hdmQueryIntAPIStorageReq( )

[1689] Syntax

[1690] word cwDispBuffer=hdmQueryIntAPIStorageReq(disptype dtype);

[1691] where

[1692] dtype The type of hardware display window as defined by disptype

[1693] Returns

[1694] cwDispBuffer Number of words required for allocating internal memory for the hardware display indicated by dtype.

[1695] Description

[1696] hdmQueryIntAPIStorageReq( ) returns back the number of words (32 bit) that are required for internal data structure storage to maintain a display context.

[1697] Example

[1698] disptype dtype;

[1699] cwDisplayMemory=hdmQueryIntAPIStorageReq(YCRCB444);

[1700] See Also

[1701] hdmNewDisplay( )

[1702] hdmQueryDisplayBufferSize( )

[1703] Syntax

[1704] word cwDisplay=hdmQueryDisplayBufferSize(OSDcoords coords, disptype dtype);

[1705] where

[1706] coords The coordinates of the hardware display.

[1707] dtype The type of display, as defined by the disptype type.

[1708] Returns

[1709] cwdispay: Number of words required to allocate for the hardware display dtype.

[1710] If an error occurs, cwdisplay returns 0.

[1711] Description

[1712] hdmQueryDisplayBufferSize( ) returns the number of words (32 bit) required to allocate a frame buffer for the hardware display indicated by dtype.

[1713] See Also

[1714] hdmNewDisplay( )

[1715] hdmNewDisplay( )

[1716] Syntax

[1717] STATUS status=hdmNewDisplay(Buffer *pbufData, memtype mem, Buffer *pbufDisp,

[1718] DISPTYPE dtype, OSDCoords *plocation, word id, HDISPLAY *hDisplay);

[1719] where

[1720] Returns

[1721] status The error condition. Possible return value are E_NONE: no error.

[1722] E_HDM_MAX_PHYSICAL_EXCEEDED: the application tried to create more than eight physical displays. A virtual display is created instead of a physical one.

[1723] E_MEMORY_TYPE_INCORRECT: the application tried to create a physical display with the display buffer stored in the external memory. A virtual display is created instead of a physical one.

[1724] E_HDM₁₃DISPLAY_BUSY: the application tried to create a physical display with the same ID of another active display. A virtual display is created instead of a physical one.

[1725] E_HDM_VIDEO_DISPLAY_EXCEEDED: the application tried to create more than one video display (either decimated or full screen). A virtual display is created instead of a physical one.

[1726] Description

[1727] This function creates a new display of type dtype. For details on how to create different displays, see the examples below.

[1728] Note: No check is executed on the display coordinates: invalid parameters can cause strange artifacts on the screen.

[1729] If disptype is VIDEO, the display ID and the coordinates are ignored.

[1730] If disptype is CURSOR, the display ID is ignored: its value is automatically set to 0.

[1731] The display is created with the following default parameters:

[1732] In order to reduce visible artifacts that may be caused by changing the OSD memory, this function should only take place during the vertical blanking interval.

[1733] Creating a YCRCB444 Display

[1734] HDISPLAY hDisplay

[1735] OSDcoords coords;

[1736] Buffer bufdisp, bufapi;

[1737] STATUS status

[1738] /* Define the Size and location of the window by specifying the upper left and bottom right coordinates. */

[1739] coords.pixX0=50; /* Must be an even pixel */

[1740] coords.pixY0=100;

[1741] coords.pixX1=251; /* must be an odd pixel */

[1742] coords.pixY1=201;

[1743] /* Determine Size of Buffer and allocate memory for it. The malloc( ) routine would probably be replaced with some kind of dependent routine that would allocate memory in SDRAM or EBIF DRAM depending upon where the user wanted the frame buffer

[1744] */ bufdisp.cwBuffer=hdmQueryDisplayBufferSize(coords, YCRCB444);

[1745] bufdisp.pBuffer=(word *) malloc(bufdisp.cwBuffer * sizeof(word));

[1746] /* Allocate internal memory needed for handling this hardware display */

[1747] bufapi.cwBuffer=hdmQueryIntAPIStorageReq(YCRCB444);

[1748] bufapi.pBuffer=(word *) malloc (bufapi.cwBuffer * sizeof(word));

[1749] status=hdmNewDisplay(&bufapi, SDRAM, &bufdisp, YCRCB444, coords, 1, &hDisplay);

[1750] Creating an MPEG Video Display

[1751] This next example shows how an MPEG video window is created using this API call.

[1752] HDISPLAY hDisplay;

[1753] OSDcoords coords;

[1754] Buffer bufapi;

[1755] /* get coordinates for half size MPEG video display * ?

[1756] coords=hdmGetVideoCoords(VIDEOHSIZE, 10,10);

[1757] /* find out how much memory is required for internal storage */

[1758] bufapi.cwBuffer=hdmQueryIntAPIStorageReq(VIDEOHSIZE);

[1759] /* allocate internal API memory */

[1760] bufapi.pBuffer=(word *) malloc (cwAPIMemory * sizeof(word));

[1761] /* Allocate Display */

[1762] status=hdmNewDisplay(&bufapi, SDRAM, NULL, VIDEOHSIZE, coords, 3, &hDisplay);

[1763] hdmDeleteDisplay( )

[1764] Syntax

[1765] FERROR fError=hdmDeleteDisplay(HDISPLAY hDisplay, Buffer *pbufdisp, Buffer *pbufapi);

[1766] where

[1767] Returns

[1768] fError=0, No Errors

[1769] Possible error conditions are:

[1770] 1. invalid display handler

[1771] Description

[1772] hdmDeleteDisplay( ) deletes the display indicated by hDisplay and returns the pointers to the memory that was originally created by the user application and passed to the firmware by the hdmNewDisplay( ) API call.

[1773] In order to reduce visible artifacts that may be caused by changing the OSD memory, this function should only take place during the vertical blanking interval.

[1774] Example

[1775] Buffer *pbufapi, *pbufdisp;

[1776] hdmDeleteDisplay(hDisplay, pbufapi, pbufdisp);

[1777] /* Now, use whatever memory management routines supplied by OS to delete

[1778] * the memory.

[1779] */

[1780] free(pbufapi.pBuffer);

[1781] free(pbufidsp.pBuffer);

[1782] See Also

[1783] hdmNewDisplay( )

[1784] hdmSetVisibility( )

[1785] Syntax

[1786] FERROR fError=hdmSetVisibility(HDISPLAY hDisplay, on_off switch);

[1787] where

[1788] Returns

[1789] fError=0, No Errors

[1790] Possible error conditions are:

[1791] invalid display handler

[1792] the display type is VIDEO

[1793] the display is virtual

[1794] Description

[1795] hdmSetVisibility( ) controls the visibility of the hardware display indicated by hDisplay.

[1796] Example

[1797] /* Enable */

[1798] hdmSetVisibility(hDisplay, ON);

[1799] /* Disable */

[1800] hdmSetVisibility(hDisplay, OFF);

[1801] See Also

[1802] hdmGetVisibility( )

[1803] hdmGetVisibility( )

[1804] Syntax

[1805] on_off switch=hdmGetVisibility(HDISPLAY hDisplay);

[1806] Returns

[1807] fStatus contains the visibility status of the display.

[1808] Possible error conditions are:

[1809] invalid display handler

[1810] the display type is VIDEO

[1811] the display is virtual

[1812] Description

[1813] hdmGetVisibility( ) returns the current visibility status of the display indicated by hDisplay. This function is only meaningful for the top eight hardware displays, as all other displays are VIRTUAL, and cannot be visible.

[1814] See Also hdmSetVisibility( )

[1815] hdmSetCoords ( )

[1816] Syntax

[1817] FERROR fError=hdmSetCoords(HDISPLAY hDisplay, OSDcoords coord);

[1818] where

[1819] Returns

[1820] fError=0, No Errors

[1821] Possible error conditions are:

[1822] 1. invalid display handler

[1823] Description

[1824] hdmSetCoords ( ) changes the coordinates of the hardware display window. This function may be used to move a window around the screen, or to shrink or grow it. If the display type is VIDEO, the coordinates are ignored.

[1825] In order to reduce visible artifacts that may be caused by changing the OSD memory, this function should only take place during the vertical blanking interval.

[1826] See Also

[1827] hdmGetCoords

[1828] hdmGetCoords( )

[1829] Syntax

[1830] OSDcoords coord=hdmGetCoords(HDISPLAY hDisplay);

[1831] where

[1832] hDisplay Handle to a hardware display

[1833] Returns

[1834] coord the coordinates to the hardware display indicated by hDisplay

[1835] Description

[1836] Returns the coordinate pair for the hardware display indicated by hDisplay.

[1837] See Also

[1838] hdmSetCoords( )

[1839] hdmSetBlendEnable( )

[1840] Syntax

[1841] FERROR fError=hdmSetBlendEnable(HDISPLAY hDisplay, OSDBlendType blendmode);

[1842] where

[1843] Returns

[1844] fError=0, No Errors

[1845] Possible error conditions are:

[1846] 1. invalid display handler

[1847] Description

[1848] Set a specific window blending mode for the display indicated by hDisplay. Window blending only works when a graphic 4:4:4, 4:2:2 or bitmap display is selected. Color blending only works for bitmap displays.

[1849] See Also

[1850] hdmGetBlendEnable( )

[1851] hdmGetBlendEnable( )

[1852] Syntax

[1853] OSDBlendType blendmode=hdmGetBlendEnable(HDISPLAY hDisplay);

[1854] where

[1855] hDisplay Handle to a hardware display

[1856] Returns

[1857] blendmode, the current blending mode for hDisplay.

[1858] Description

[1859] hdmGetBlendEnable( ) returns the current window blending mode for the display indicated by hDisplay. Valid modes are indicated by the type OSDBlendType.

[1860] See Also

[1861] hdmSetBlendEnable( )

[1862] hdmSetBlendFactor( )

[1863] Syntax

[1864] FERROR fError=hdmSetBlendFactor(HDISPLAY hDisplay, word factor);

[1865] where

[1866] hDisplay Handle to a hardware display

[1867] factor blending factor for display.

[1868] Returns

[1869] fError 0, No Errors

[1870] Possible error conditions are:

[1871] 1. invalid display handler

[1872] Description

[1873] hdmSetBlendFactor( ) sets the blending factor for the display indicated by hDisplay. Valid blending factors are listed in Table 42.

[1874] See Also

[1875] hdmSetBlendFactor( )

[1876] hdmGetBlendFactor( )

[1877] Syntax

[1878] word factor=hdmGetBlendFactor(HDISPLAY hDisplay)

[1879] where

[1880] hDisplay Handle to a hardware display

[1881] Returns

[1882] factor blending factor for display.

[1883] Description

[1884] hdmGetBlendFactor( ) returns the current blending factor for the display indicated by hDisplay. Valid blending factors are listed in Table 42: Blending Levels.

[1885] See Also

[1886] hdmSetBlendFactor( )

[1887] hdmSetTransparencyEnable( )

[1888] Syntax

[1889] FERROR fError=hdmSetTransparencyEnable(HDISPLAY hDisplay, on_off flag);

[1890] where

[1891] Returns

[1892] fError=0, No Errors

[1893] Possible error conditions are:

[1894] invalid display handler

[1895] Description

[1896] hdmSetTransparencyEnable( ) sets the transparency mode of the display indicated by hdisplay to either ON or OFF. Transparency mode only works when a bitmap or graphic window is on top of an MPEG video window. It will not work between graphic or bitmap windows. The transparency color for a window is 0. This allows bitmaps or graphic displays with 0 in their image to allow the MPEG video image to show through at those pixel locations.

[1897] See Also

[1898] hdmGetTransparencyEnable( )

[1899] hdmGetTransparencyEnable( )

[1900] Syntax

[1901] on_off switch =hdmGetTransparencyEnable(HDISPLAY hDisplay);

[1902] where

[1903] hDisplay Handle to a hardware display

[1904] Returns

[1905] switch, the current transparency enable for hdisplay, either ON or OFF.

[1906] Description

[1907] hdmGetTransparencyEnable( ) returns the current status of transparency mode for the hardware display indicated by hDisplay in switch, either ON or OFF.

[1908] See Also

[1909] hdmSetTransparencyEnable( )

[1910] hdmSetChannelControl( )

[1911] Syntax

[1912] FERROR fError=hdmSetChannelControl(HDISPLAY hDisplay, word wcontrol);

[1913] where

[1914] hDisplay Handle to a hardware display

[1915] wcontrol control word for the hardware display

[1916] Returns

[1917] fError=0, No Errors

[1918] Possible error conditions are:

[1919] invalid display handler

[1920] Description

[1921] hdmSetchannelControl( ) sets the current out of the hardware display indicated by hDisplay to the output ports defined in Error! Reference source not found.

[1922] See Also

[1923] hdmGetChannelControl( )

[1924] hdmGetChannelControl( )

[1925] Syntax

[1926] word wControl=hdmGetChannelControl(HDISPLAY hDisplay);

[1927] where

[1928] hDisplay Handle to a hardware display

[1929] Returns

[1930] wcontrol, the output channel control word for the display hDisplay.

[1931] Description

[1932] hdmGetChannelControl( ) returns the current output channel control word as defined in Error! Reference source not found.

[1933] See Also

[1934] hdmSetChannelControl( )

[1935] hdmSetZOrder( )

[1936] Syntax

[1937] FERROR fError=hdmSetZOrder(HDISPLAY hDisplay, uchar wNewOrder);

[1938] where

[1939] Returns

[1940] fError=0, No Errors

[1941] Possible error conditions are:

[1942] invalid display handler

[1943] the display type is VIDEO or CURSOR

[1944] the display is virtual.

[1945] Description

[1946] hdmSetZOrder( ) changes the Z order of the hardware display indicated by hDisplay to the new level in wNewOrder. If the new z-plane level is lower than the current one, then the displays at the new level are increased to fill the vacant slot left by the current level. For example, if the current display is at level 5 and it want to be changed to level 2, then displays 2-4 drop down by one. See Error! Reference source not found. for how this works. The function returns an error when the display is not a physical display or its type is either VIDEO or CURSOR.

[1947] If the new z-plan level is higher than the current one, then the displays at the new level are decreased to fill the vacant slow left by the current level. See Error! Reference source not found. for how this works. hdmSetZorder( ) only works on real OSD hardware windows, not virtual ones.

[1948] In order to reduce visible artifacts that may be caused by changing the OSD memory, this function should only take place during the vertical blanking interval or when the moved displays are not visible.

[1949] See Also

[1950] hdmGetZOrder( )

[1951] hdmGetZOrder( )

[1952] Syntax

[1953] uchar wOrder=hdmGetZOrder(HDISPLAY hDisplay);

[1954] where

[1955] hDisplay Handle to a hardware display

[1956] Returns

[1957] wOrder, the current Z-plane order of the hardware display, or the virtual display id., if it is a virtual display.

[1958] Description

[1959] hdmGetZOrder( ) returns the Z-plane order of the hardware display indicated by hDisplay, or the id. of the display, if it is virtual.

[1960] See Also

[1961] hdmSetZOrder( )

[1962] hdmInit( )

[1963] Syntax

[1964] FERROR fError=hdmInit(void)

[1965] Returns

[1966] fError=0, No Errors

[1967] Description

[1968] hdminit( ) initializes the on screen display hardware. It must be called before any hdm commands are called.

[1969] hdmSetBackGroundColor( )

[1970] Syntax

[1971] FERROR fError=hdmSetBackGroundColor(word bgcolor);

[1972] where

[1973] bgcolor background color for the display.

[1974] Returns

[1975] fError=0, No errors

[1976] Description

[1977] hdmSetBackGroundColor( ) sets the background color for the NTSC/PAL display.

[1978] See Also

[1979] hdmGetBackGroundColor( )

[1980] hdmGetBackGroundColor( )

[1981] Syntax

[1982] word bgcolor=hdmGetBackGroundColor(void)

[1983] Returns

[1984] bgcolor background color

[1985] Description

[1986] hdmGetBackGroundColor( ) returns the current background color of the NTSC/PAL screen.

[1987] See Also

[1988] hdmSetBackGroundColor( )

[1989] hdmVerifyCoords( )

[1990] Syntax

[1991] STATUS status=hdmVerifyCoords(OSDCoords *pcoords, disptype dtype);

[1992] where

[1993] dtype The display type.

[1994] pcoords The coordinate data structure that defines the upper left and bottom right corners of the video display.

[1995] Returns

[1996] status The error condition. Possible return value are

[1997] E_NONE: no error

[1998] E_HDM_ADJUSTED_VIDEO_DIM: the coordinates have been changed by the routine.

[1999] Description

[2000] This function verifies that the coordinates in the pcoords structure is valid for the display type indicated by dtype. This routine will also adjust the coordinates to meet hardware requirements.

[2001] Rules:

[2002] pixX0 must always be an even pixel

[2003] pixX1 must always be an odd pixel

[2004] If dtype is VIDEOHSIZE, VIDEOQSIZE, or VIDEOESIZE, the following further conditions apply:

[2005] pixY0 must be an even pixel

[2006] pixY1 must be odd

[2007] pixX1<screen Xsize

[2008] pixY1<screen Ysize

[2009] pixX1−pixX0 must be equal to the correct display X size (359 half size, 179 quarter size, 79 eighth size)

[2010] pixY1−pixY0 must be equal to the correct display Y size (239 half size, 119 quarter size, 59 eighth size)

[2011] See Also

[2012] hdmGetVideoCoords( )

[2013] hdmSwapDisplay( )

[2014] Syntax

[2015] FERROR fError=hdmSwapDisplay(HDISPLAY hDisplayl, HDISPLAY hDisplay2);

[2016] where

[2017] Returns

[2018] fError=0, No Errors

[2019] Possible error conditions are:

[2020] invalid display handler

[2021] one of the display type is VIDEO or CURSOR

[2022] Description

[2023] hdmSwapDisplay( ) swaps the Z order of two displays. The function returns an error when the display type is either VIDEO or CURSOR. Unlike hdmSetZorder( ), the current routine works also on virtual windows: it is possible to exchange a virtual display with a physical display.

[2024] See Also

[2025] hdmSetZOrder( )

[2026] Hardware Cursor Management API

[2027] The circuit 200 hardware cursor is really just a hardware display at the highest Z plane level. Because it is an extension of the OSD window management hardware, it must be rectangular in shape. Its size and color are configurable.

[2028] Table 55 describes the current API for handling the hardware cursor. Except for the two functions described below, the cursor is managed by using the same routines of the other display types: it is created by the function hdmNewDisplay( ), it is deleted by the function hdmDeleteDisplay( ) and the position can be changed by using hdmSetCoords( ). Also the visibility of the cursor display is set by the function hdmSetVisibility( ).

[2029] curSetColor( )

[2030] Syntax

[2031] FERROR ferror=curSetColor(HDISPLAY hDisplay, word color);

[2032] where

[2033] hDisplay Handle to a hardware display

[2034] color the cursor color

[2035] Returns

[2036] fError=0, No Errors

[2037] Possible error conditions are:

[2038] the display type is not CURSOR

[2039] Description

[2040] curSetColor( ) sets the color of the cursor display.

[2041] See Also

[2042] hdmSetBackGroundColor( )

[2043] curSetBlinkRate( )

[2044] Syntax

[2045] FERROR ferror=curSetBlinkRate(HDISPLAY hDisplay, word level);

[2046] where

[2047] hDisplay Handle to a hardware display

[2048] level The cursor blink rate

[2049] Returns

[2050] fError=0, No Errors

[2051] Possible error conditions are:

[2052] the display type is not CURSOR

[2053] Description

[2054] curSetBlinkRate( ) sets the blink rate of the cursor display. Valid blink rate values are in the range between 0 and 15. They are outlined in Table 56.

[2055] curGetColor( )

[2056] Syntax

[2057] word color=curGetColor(HDISPLAY hDisplay);

[2058] where

[2059] hDisplay Handle to a hardware display

[2060] Returns

[2061] color the cursor color

[2062] Description

[2063] curGetColor( ) gets the color of the cursor display.

[2064] See Also

[2065] hdmGetBackGroundColor( )

[2066] curGetBlinkRate( )

[2067] Syntax

[2068] word level=curGetBlinkRate(HDISPLAY hDisplay);

[2069] where

[2070] hDisplay Handle to a hardware display

[2071] Returns

[2072] level The cursor blink rate

[2073] Description

[2074] curGetBlinkRate( ) gets the blink rate of the cursor display.

[2075] See Also

[2076] curSetBlinkRate( )

[2077] Graphics Acceleration

[2078] The graphics acceleration module provides the API interface with the firmware for high speed data transfer and translation. The translation feature allows the application software to generate a graphics screen in a bit-map mode and have the on-chip hardware translate the bit-map to graphics true-color data on the fly.

[2079] Detailed module description

[2080] The circuit 200 is capable of accelerating certain types of graphics functions, including:

[2081] reading and writing pixel data

[2082] rectangular block transfers

[2083] horizontal line drawing

[2084] vertical line drawing

[2085] All of the graphics acceleration functions are based upon the circuit 200 blitter module. The blitter module is responsible for moving two dimensional display memory from a source location to a destination location.

[2086] There are three major graphics formats: bitmap, 4:4:4 YCrCB, and 4:2:2 CbYCr. A bitmap display is sequence of 1,2,4, or 8 bits per pixel that represent an index value into a 24-bit palette. The OSD hardware will convert bitmap displays to 24 CbYCr when the graphic window is displayed. The last two formats are different types of “true color” or graphic formats. They specify the color component ratio of the format. In 4:4:4 mode, there is an equal number of bits used for Luminance, Chrominance Red, and Chrominance Blue. In 4:2:2 mode, there is only half of both Cr and Cb as related to Y.

[2087] Graphics data is stored in a linear packed format. Table 57 shows how 4:4:4 graphics data is stored. Each color component requires 8 bits, thus 4:4:4 mode is 24 bits/pixel. Note that pixels are not word aligned, and may span word boundaries.

[2088] Table 57 shows the 4:2:2 packed format. In this format, the chrominance information has been decimated by a factor of two over the luminance information. As the table shows, chrominance information is only supplied every other pixel.

[2089] The circuit 200 employs a simple coordinate system. The origin of each hardware display window is at the top left corner of the window. The origin starts at x=0, y=0, up to the size of the window. Error! Reference source not found. illustrates this system.

[2090] The blitter API is responsible for fill rectangular regions with a single color and copying rectangular regions of memory from one memory location to another. Table 59 shows the valid memory regions that the bitBLT hardware supports. SDRAM→SDRAM transfers will be used for moving block of memory around between hardware windows or within a hardware window. EBIF→SDRAM transfers may be used for moving graphics stored in external DRAM, such as fonts, to onscreen display memory. EBIF→EBIF transfers allow a software developer to move graphics data stored in memory on the EBIF. As Table 59 shows, all user DRAM accessible memory regions are a valid source or destination for a bitBLT transfer.

[2091] Table 60 shows the valid bitBLT transfers across different display types. The most common types of displays have the most interactivity, i.e. Bitmap and 4:4:4. The 4:2:2 mode is more difficult to work with graphically because full color information is only present in half of the pixels stored in memory (refer to Table 58 Graphic 4:2:2 Format), so 4:2:2 images may only be hardware accelerated to displays that are also 4:2:2.

[2092] Table 61 shows whether relication or decimation occurs during a bitBLT transfer to or from a half resolution display. As defined for this table, replication means that that each pixel in the source display is replicated twice on the destination display on the horizontal axis. Decimation means that only every other pixel in the source display is copied to the destination display.

[2093] In addition to decimation/replication due to transferring bitmaps to and from half resolution displays, bitBLT transfers from bitmaps of different pixel depths may occur. In this case, the following rules apply:

[2094] Bitmap x bit/pixel→bitmap y bit/pixel, where x>y. The MSBs of x is truncated to equal y.

[2095] Bitmap x bit/pixel→bitmap y bit/pixel, where x<y. x is padded on MSB with 0's, until x=y.

[2096] Graphics Data Structures

[2097] The following data structures may be used in the blitter API.

[2098] functype: functype describes all the hardware accelerated functions the bitblt module may perform. The bitblt hardware requires the firmware to tell it what function to perform when setting up its command registers.

[2099] rw_dir: rw_dir specifies the read/write direction that the bitblt module will use to perform block copy operations. In any transfer the software is responsible for determining the appropriate direction.

[2100] typedef enum {

[2101] TBLR=0, /* Top-->Bottom, Left-->Right */

[2102] TBRL=1, /* Top-->Bottom, Right-->Left */

[2103] BTLR=2}/* Bottom-->Top, Left-->Right */

[2104] rw_dir; /* Read/Write Direction */

[2105] The rw_dir variable is required for the bitBLT functions that copy a block of information. Error! Reference source not found. shows all of the possible directions the firmware must consider to determine the assigned of rw_dir.

[2106] The algorithm in Error! Reference source not found. describes the a method to use in determining how to set rw_dir. The worst case requires four conditionals.

[2107] bltblock: This data structure defines a rectangular block.

[2108] Blitter API

[2109] Table 62 presents a summary of the blitter API. Following the table is a description of each function.

[2110] bltInit( )

[2111] Syntax

[2112] FERROR fError=bltInit(void);

[2113] Returns

[2114] fError=0, No errors

[2115] Description

[2116] bltInit( ) initializes the bitBLT hardware and initializes the internal data structures required for the bitBLT API.

[2117] Hardware Requirements

[2118] The bltInit( ) function will initialize the hardware state machine.

[2119] bltSetPixel( )

[2120] Syntax

[2121] FERROR fError=bltSetPixel( HDISPLAY display, UINT pixX, UINT pixY, UINT wcolor);

[2122] where

[2123] display: display handle returned from osdCreateDisplay( )

[2124] pixX: X coordinate on current display in pixels

[2125] pixY: Y coordinate on current display in pixels

[2126] wColor: bitmap color value for bitmap displays, or a 24 bit CbYCr color value for graphic displays. For a 4:2:2 display the color value should be CbYCrY. The color information should be stored in the lower 24 (32 if 4:2:2) bits of the 32 bit value.

[2127] Returns:

[2128] fError=E_NONE, No errors

[2129] E_ERROR—Not defined.

[2130] Description

[2131] bltSetPixel( ) will set the color of a pixel on any hardware display. If the display is bitmap, wColor should be the appropriate bitmap value. If the display is a graphic display, then wColor is a 24 (32 if 4:2:2)bit CbYCr value.

[2132] Special Considerations

[2133] In Graphics 4:2:2 mode, the firmware will have to set two pixels at a time. This is because the chrominance information is spread across two pixels in this mode. For example, if the user wants to change pixel P0 in Table 58, then the software will have to read a 32 bit value from address 0XFE0000, to obtain all of the color information for P0, It would then modify the Cb,Cr, and Y information based upon wcolor and write back the 32 bit value, which would have an effect on P1, the adjacent pixel. In 4:2:2 mode, the hardware writes two pixels at a time.

[2134] If the disptype is one of the half resolutions displays, then pixX must be an even number. Software will provide the hardware with the proper half resolution base address, even though pixX and pixY will be the actual coordinates as if the display were not half resolution.

[2135] See Also

[2136] bltGetPixel( )

[2137] bltGetPixel( )

[2138] Syntax

[2139] FERROR fError=bltGetPixel(HDISPLAY display, UINT pixX, UINT pixY, UINT *pwColor);

[2140] where

[2141] display: display handle returned from osdCreateDisplay( )

[2142] pixX: X coordinate on current display in pixels

[2143] pixY: Y coordinate on current display in pixels

[2144] wColor: bitmap color value for bitmap displays, or a 24 bit CbYCr color value for graphic displays. For a 4:2:2 display the color value should be CbYCrY. The color information should be stored in the lower 24 (32 if 4:2:2) bits of the 32 bit value.

[2145] Returns

[2146] fError=E_NONE, No errors

[2147] E_ERROR Not defined.

[2148] Description

[2149] bltGetPixel( ) will get the color of a pixel on any hardware display. If the display is bitmap, value of *pwColor should be the appropriate bitmap value. If the display is a graphic display, then *pwColor is a 24 bit CbYCr value.

[2150] Hardware Requirements

[2151] Software will provide the following parameters to the bitBLT hardware:

[2152] Function type, as defined in functype

[2153] Display Type, as defined in disptype

[2154] Color Value=/* Get color value from wColor input parameter */

[2155] Base Address of Pixel, and bit offset

[2156] Memory Type=/* Get Memory type from hDisplay Context */

[2157] Special Considerations

[2158] In Graphics 4:2:2 mode, the firmware will have to set get pixels at a time, however it will construct a 24 bit CbYCr value from the 32 bit value. This is because the chrominance information is spread across two pixels in this mode. For example, if the user wants to get pixel P0 in Table 58, then the software will have to read a 32 bit value from address 0XFE0000, to obtain all of the color information for P0, It would then modify the Cb,Cr, and Y information based upon pwColor, which would have an effect on P1, the adjacent pixel.

[2159] If the disptype is one of the half resolutions displays, then pixX must be an even number. Software will provide the hardware with the proper half resolution base address, even though pixX and pixY will be the actual coordinates as if the display were not half resolution.

[2160] See Also

[2161] bltSetPixel( )

[2162] bltDrawHLine( )

[2163] Syntax

[2164] FERROR fError=bltDrawHLine(HDISPLAY display, UINT pixX,UINT pixY, UINT cpixLength, UINT wColor)

[2165] where

[2166] display: display handle returned from osdCreateDisplay( )

[2167] pixX: X coordinate on current display in pixels

[2168] pixY: Y coordinate on current display in pixels

[2169] cpixLength: Length of line in pixels

[2170] wColor: bitmap color value for bitmap displays, or a 24 bit CbYCr color value for graphic displays. For a 4:2:2 display the color value should be CbYCrY. The color information should be stored in the lower 24 (32 if 4:2:2) bits of the 32 bit value.

[2171] Returns

[2172] fError=E_NONE, No errors

[2173] E_ERROR Not defined

[2174] Description

[2175] bltDrawHLine( ) will draw a one pixel wide horizontal line of length cpixLength starting at the coordinates specified by (pixX,pixY). The color of the line is specified by wColor.

[2176] Special Considerations

[2177] In Graphics 4:2:2 mode, the firmware will provide the base address of even pixels only the hardware. The hardware will draw the line two pixels at a time because two pixels occupy 32 bits in 4:2:2 mode. In addition the length of the line must also be even.

[2178] If the disptype is one of the half resolution displays, then cpixX must be an even number. In addition, the firmware will compute the real base address, taking into account the ½ resolution pixel decimation along the horizontal axis. For example,

[2179] DrawHLine(10,20,36,BLUE); means to draw a blue horizontal line at location 10,20 on the full resolution display that is 36 pixels long.

[2180] If any of the command would result in writes outside of the display, the X width is adjusted to stop at the display edge.

[2181] See Also

[2182] bltDrawVLine( )

[2183] bltDrawVLine( )

[2184] Syntax

[2185] FERROR fError=bltDrawVLine(HDISPLAY display, UINT cpixX,UINT cpixY, UINT cpixLength, UINT wColor)

[2186] where

[2187] display: display handle returned from osdCreateDisplay( )

[2188] cpixX: Number of pixels in the X direction

[2189] cpixY: Number of pixels in the Y direction

[2190] cpixLength: Length of line in pixels

[2191] wColor: bitmap color value for bitmap displays, or a 24 bit CbYCr color value for graphic displays.

[2192] For a 4:2:2 display the color value should be CbYCrY. The color information should be stored in the lower 24 (32 if 4:2:2) bits of the 32 bit value.

[2193] Returns

[2194] fError=E_NONE, No errors

[2195] E_ERROR Not defined.

[2196] Description

[2197] bltDrawVLine( ) will draw a one pixel wide vertical line of length cpixLengh starting at the coordinates specified by (cpixX,cpixY). The color of the line is specified by wColor.

[2198] Special Considerations

[2199] In Graphics 4:2:2 mode, the firmware will provide the base address of even pixels only the hardware. The hardware will draw the line two pixels at a time because two pixels occupy 32 bits in 4:2:2 mode. There is no restriction on the length of a vertical line.

[2200] If the disptype is one of the half resolution displays, then cpixX must be an even number. In addition, the firmware will compute the real base address, taking into account the ½ resolution pixel decimation along the horizontal axis. For example,

[2201] DrawVLine(10,20,36,BLUE); means to draw a blue horizontal line at location 10,20 on the full resolution display that is 36 pixels long. The user does not have to worry about the actual size of the display.

[2202] If any of the command would result in writes outside of the display, the Y length is adjusted to stop at the display edge.

[2203] See Also

[2204] bltDrawHLine( )

[2205] bltDrawBlock( )

[2206] Syntax

[2207] ERROR fError=bltDrawBlock(HDISPLAY display, Bltblock *pblock)

[2208] where:

[2209] display: display handle returned from osdCreateDisplay( )

[2210] pblock: pointer to a Bltblock data structure that defines a rectangular block.

[2211] Returns

[2212] fError=E_NONE, No errors

[2213] E_ERROR Not defined.

[2214] Description

[2215] bltDrawBlock( ) will draw a rectangular block on the current display set by bltSetCurrentDisplay( ). The values in pblock define the parameters of the rectangular block to be filled. The wColor value should be set appropriately to the display. If the display in bitmap, then wColor should be a bitmap color value, otherwise it should be a 24 bit CbYCr value. For a 4:2:2 display the color value should be CbYCrY. The color information should be stored in the lower 24 (32 if 4:2:2) bits of the 32 bit value.

[2216] Special Considerations

[2217] In Graphics 4:2:2 mode, the firmware will provide the base address of even pixels to the hardware. The hardware will draw the line two pixels at a time because two pixels occupy 32 bits in 4:2:2 mode. In addition the length of the box must also be even.

[2218] If the disptype is one of the half resolution displays, then piX must be an even number. In addition, the firmware will compute the real base address, taking into account the ½ resolution pixel decimation along the horizontal axis.

[2219] If any of the command would result in writes outside of the display, the X width and Y length are adjusted to stop at the display edge.

[2220] bltCopyBlock( )

[2221] Syntax

[2222] Returns

[2223] fError=E_NONE, No errors

[2224] E_ERROR Not defined.

[2225] Description

[2226] bltCopyBlock will copy a rectangular region of memory, described by block, and copy it from one memory location to another. The block is located in the display indicated by hdispsource, and is to be copied into the display indicated by hdispDest, at the coordinates (pixXd, pixYD).

[2227] Transparency only works under the source and destination displays described in Table 63. The transparency color is defined as the first entry in the palette for the source display. If the fTransparency flag is set, and the source and destination displays are valid for transparency, then all palette color values of 0, are not copied to the destination display. Note that the color value referred to is the actual palette index, not the 24 bit YCRCB value that the palette color index references. This allows a palette to define any color to the be transparent color, as long as it stored at location 0 in the palette.

[2228] Special Considerations

[2229] The circuit 200 hardware will allow block copied from any user memory location to any other user memory location. The memory block may be in either SDRAM or EBIF DRAM. See Table 59: Valid Source/Destination bitBLT Memory Regions, for valid source and destinations.

[2230] The circuit 200 has many different types of hardware displays. Table 60: Valid bitBLT Transfers Across Hardware Displays, shows which block copies are valid.

[2231] For half resolution mode refer to Table 61: Half Resolution Decimate/Replicate, which indicates which shows how pixel expansion and reduction occurs through replication and decimation.

[2232] If any of the command would result in writes outside of the destination display, the X width and Y length are adjusted to stop at the display edge.

[2233] This function considers overlapping blocks when the source and destination displays are the same. The direction of the copy is adjusted to account for this.