Texas Instruments SPRAA56 appendix References, Capture and Display Task Benchmarking

Page 26

SPRAA56

The value of N, which is used by modes 2 and 3, is 30 frames by default. As a result, RTA data is logged every 1 second in NTSC applications. This value can be changed using the GELrtaWindow slider. This slider asks for a value between 1 and 10 seconds, and multiplies the value by 30 before updating the control variable in the application. For PAL applications, change the multiplier value in the GEL file to 25.

5.4.2 Capture and Display Task Benchmarking

In addition to the RTA modes, you can enable or disable instrumentation in the capture and display tasks using the USER0 and USER1 bits in the RTA Control Panel. They are turned on by default. In order to view the latency from the input to output task, it is necessary to turn these bits on. After a typical latency measurement is recorded, the amount of data the capture and display tasks deliver to the Message Log may be more than is useful.

6References

H.263 Loopback on the DM642 EVM (SPRA933)

The TMS320DM642 Video Port Mini-Driver (SPRA918)

Reference Frameworks for eXpressDSP Software: RF5, An Extensive, High-Density System (SPRA795)

Reference Frameworks for eXpressDSP Software: API Reference (SPRA147)

TMS320 DSP/BIOS User's Guide (SPRU423)

TMS320C6000 DSP/BIOS API Reference Guide (SPRU403)

DSP/BIOS TextConf User's Guide (SPRU007)

DSP/BIOS Driver Developer's Guide (SPRU616)

26DSP/BIOS Real-Time Analysis (RTA) and Debugging Applied to a Video Application

Image 26
Contents Viewing Benchmarks in the Instrumented Application Modifications to the Base ExampleRTA Techniques for Performance Measurement References Appendix A. Performance ImpactImportant Benchmarks for Video Applications FiguresBase Application Overview SPRAA56TskInput DSP/BIOS and RF5 Components Used 1 LOG4 UTL 2 STS3 TRC Modifications to the Base Example Requirements for Viewing RTA BenchmarksSplitting the Encode and Decode CELLs Adding the Control TSK and MBX CommunicationTskO utput Querying the H.263 Encoder for StatusTskInput Controlling the Frame Rate RTA Techniques for Performance Measurement Measuring Function Execution Time with the UTL ModuleMeasuring Task Scheduling Latencies Measuring End-to-End LatenciesMeasuring the Frame Rate Programmatic Measurement of Total CPU Load Memory Bus Utilization 14,400 B 720*480 = 345,600 B86,400 B External memoryBitrate and Frame Type Methods for Transmitting Measured Performance Data Requirements Viewing Benchmarks in the Instrumented ApplicationApplication-Specific Control via GEL Scripts in CCStudio Running the Application Load the h263loopbackrta.out programSPRAA56 Interpreting the Benchmarks Expected Values for the STS Objects Expected and Measured STS Benchmarks Controlling the Run-Time Parameters Dynamically Debug ModeExpected Values Delivered to the Message Log Expected and Measured Logged BenchmarksReferences Capture and Display Task BenchmarkingRTA Effects on CPU Load Appendix A. Performance ImpactOverhead of Performance Measurement Techniques Measured Performance of Benchmarking TechniquesMemory Footprint Memory Footprint DetailsImportant Notice