The DSP’sEDMA is used to transfer data between memory and the TMS320DM642Video Port.
Tomaximize code reuse and streamline the integration process, bothdrivers are designed of two distinctive parts: the genericpart and the board specific part. The external devicecontrol interface (EDC) is defined to bind these two parts togetherin a plug-and-play manner.
The generic part of the drivers uses EDMAs totransfer data to and from the video ports.; The board-specific partmainly consists of code that in the case of the capture driver,initializes and configures the SAA7115 video decoder, and in thecase of the display driver, initializes and configures the SAA7105video encoder.These
EDC-compliant modules set up the video codecs towork together with the video ports to capture or display thedesired video data in a specific format. For example, the SAA7105can be configured to output video data in composite NTSC format orcomponent High-Definition 1080i format or a wide range of othervideo formats, depending on application requirements. In the meantime, the associated video port must also be configuredaccordingly.
The board-specific part also requires the EVM andthe DM642 DSP to be initialized by calling the EVM642_init()function from the DM642 EVM Board Support Library (BSL), whichcomes with the EVM. This will set up the EMIF, pin-muxconfigurations and the I2C controller. An application must link allthree libraries necessary in order to function correctly: one fromthe board-specific part, such as the SAA7115 or the SAA7105, onefrom the generic VPORTCAP or VPORTDIS part, and one from the BSL.These three libraries are called evm642_saa7115.l64, evm642_vportcap.l64, andevmdm642.l64, respectively for capture, and are calledevm642_saa7105.l64, evm642_vportdis.l64, and evmdm642.l64, respectively fordisplay.
2 Usage
2.1 Configuration
To use the capture or display device driver, adevice entry must be added and configured in the DSP/BIOSconfiguration tool.
The following are the device configurationsettings required to use the capture driver:
_ Init function: N/A, not used by this driver
_ Function table ptr: _VPORTCAP_Fxns
_ Function table type: IOM_Fxns
_ Device id: 0 or 1 for DM642 EVM:, specify which video port touse
_ Device params ptr: An optional pointer to an object of typeVPORT_PortParams as defined in the header file vport.h. Thispointer will point to a device parameter structure. Setting thispointer to NULL requires that an additional FVID_control call madefrom the application to initialize the video port. The parameterstructure is described below. An example of this structure is the
_