RTOS/TM4C129ENCPDT: LoggerIdle - LibType_Instrumented

Roy Cooley

Part Number: TM4C129ENCPDT

Tool/software: TI-RTOS

Basically I followed the example LoggerIdle setup example available here:

processors.wiki.ti.com/.../LoggerIdle_Uart

This presented a couple of problems. It appears that when this example was written there was an ability to use the .cfg to selectively disable Instrumentation. From the LoggerIdle_Uart example's .cfg:

UART.libType = UART.LibType_NonInstrumented;

This option appears to be no longer be supported. Futuremore I only want to turn off Instrumentation for the log data I am sending out a UART in the Idle task. To make this work right now I have to turn off all Instrumentation with:

driversConfig.libType = driversConfig.LibType_NonInstrumented

If I don't do this the log data I write out the UART triggers additional logging.

I really want to use your Instrumentation to analyse interactions with several other serial devices I have interfaced to the processor. Is there a good way to use the Idle task logging out a diagnostic UART port and leave the rest of the Instrumentation in place?

Best regards,

Roy Cooley

with InstrucmentIs there a way to turn

project's don in a ing there was a options Hi

over 5 years ago

0 ToddMullanix over 5 years ago

TI__Guru* 96960 points

Hi Roy,

We removed the driver specific settings in the .cfg file in newer releases. In newer versions, you say whether you want the instrumented driver library or non-instrumented one (not individual ones).

To summarize your issue/question: how do you have instrumented TI driver libraries and use the UART to send out log data (and not have the act of sending out the UART cause more log data).

Two options
1. You can add the UART driver files directly into your project and disable the logging. (add defines for xdc_runtime_Log_DISABLE_ALL at the very top of the UART files).
2. Do #1 in the UART files in the product and rebuild the driver libraries.

What are you looking for in the log data? You can always have the kernel and application log data even if the TI drivers library is not instrumented. This avoids the cyclical issue of UART causing more log data as it sends out log data.

Todd