Processor SDK RTOS TF
|RTOS Software Developer Guide||→||TF|
In a multicore environment there would be data generated by a producer in one core and would need to be consumed by multiple consumers in other cores/same core. For example, a target log information to be consumed by ARM and CCS System Analyzer.
The trace framework (TF) provides a mechanism to send the information to multiple consumers for a given producer. In trace framework, Producer populates the associated Ring buffer. Consumers consume the ring buffer and send the data to external actual consumers (like System Analyzer in CCS). The hand shake between producers and consumers happen using shared memory area known as contract memory between producers and consumers.
It is upto the consumer application to either send the data to final consumers (using ethernet for System Analyzer) or local consuption for any OAM (Operations and maintenance) features on ARM.
Traceframework requires Producer, Consumer and Contract shared memory to be configured using tf_contractInit(), tf_contractCreate(), tf_prodCreate() and tf_consCreate() functions. For details about individual fields of this structure, see the Doxygen help by opening PDK_INSTALL_DIR\Traceframeworkckages\ti\drv\Traceframework\docs\doxygen\html\index.html.
API reference for application:
|| Expected Results|
Unit Test application to test all APIs
User observes the output printed over the CCS console
Application Integration Details
Sys BIOS DSP (C66) Use case
Reference library path to be included in application build environment:
SysBIOS based application
Any RTSC application that needs to use trace framework library, should have a RTSC configuration file. Please refer to <ti/instrumentation/traceframework/test/TFUnitTest/<soc>/c66/bios/tfw_Uia_utest.cfg> sample RTSC cfg file for reference.
|Traceframework Library Summary|
|Project Type||Eclipse RTSC|
|Linker Sections||.vecs , .switch, .args, .cio|