www.pudn.com > JPEGMotion.rar > appResources.c
/* * Copyright 2002 by Texas Instruments Incorporated. * All rights reserved. Property of Texas Instruments Incorporated. * Restricted rights to use, duplicate or disclose this code are * granted through contract. * */ /* "@(#) RF5_IEK 2.00.01 11-26-02 (swat-c18)" */ /* * ======== appResources.c ======== * * Definition of appllication-wide global variables. */ #include#include #include "appResources.h" /* * Definition of STS-based objects for use with UTL_sts*() functions. * * UTL_Sts objects are an extension of standard STS objects, so that * UTL_stsStart/UTL_stsStop, UTL_stsPeriod and UTL_stsPhase functions are * supported. They measure execution time, period between periodic executions * of a point in code, and phase between two periodic points, by placing * the appropriate result to the specified STS object. * * Assuming the BIOS database (CDB) has some STS objects defined (and the * default configuration for RF5 defines stsTime0, stsTime1, ..., stsTime9 * STS objects for convenience), the only requirement to use a UTL_sts*() * function in a module is to include ; the argument(s) to UTL_sts*() * functions are names of STS objects from CDB (for instance, * UTL_stsPeriod( stsTime4 ); or UTL_stsStart( mySts ); * * However, it is necessary to define the extended STS objects, i.e. * UTL_Sts objects, somewhere in the application. It is most convenient * to define all such STS objects in one file such as this one. * We use UTL_stsDefine() macro for every STS object * in the CDB that we intend to use with UTL_sts*() functions: * UTL_stsDefine( stsTime4 ); * UTL_stsDefine( mySts ); etc. * * UTL_stsDefine() is a macro, which expands to nothing if UTL_sts* * functionality is disabled. Otherwise, the macro defines a variable * and provides initial values for its fields. */ UTL_stsDefine( stsCycleTime ); UTL_stsDefine( stsCapTime ); UTL_stsDefine( stsExeTimeChJpegEnc ); UTL_stsDefine( stsExeTimeChJpegDec ); UTL_stsDefine( stsDispTime );