This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

UIA LoggingSetup doesn't support LoggerSM as a loggerType

Hello everyone,

(target C6678, CCSv6, UIA 2.00.2.39)

The UIA LoggingSetup module has several configuration settings

One of them is:

LoggingSetup.loggerType

which offers the choice

LoggerType_MIN ; STOPMODE (value by default) ; JTAGRUNMODE ; RUNMODE ; IDLE ; STREAMER2

LoggerSM is NOT in this list and should be.
LoggerSM is meant to be used along LoggingSetup

As a result a STOPMODE logger instance is present in the final application (along with the LoggerSM instance)

Will this be fixed ?

Regards,
Clement

  •  Hi Clement,

    LoggingSetup was intended to be a module that made setting up logging easier for non-advanced use cases. We wanted to make it easy for 95% of the applications. If we tried to cover 100% of the use cases, LoggingSetup would have become overly complicated. Unfortunately, we felt that LoggerSM falls into that 5%. For example, LoggerSM has a single buffer for each core. So how are the different sizes specified in LoggingSetup interpeted? Do we sum them, do we ignore them, etc.

    For this reason, we do not plan on adding LoggerSM into LoggingSetup.

    Please note that LoggingSetup is not required to be present for LoggerSM. The examples have both LoggerSM and LoggingSetup, but it not required. You can create a LoggerSM instance and plug it into the different modules as needed.

    myLoggerSM_instance = LoggerSM.create(...);

    Task.common$.diags_USER1 = Diags.ALWAYS_ON;
    Task.common$.diags_USER2 = Diags.ALWAYS_ON;
    Task.common$.logger = myLoggerSM_instance;

    Todd

  • Hi Todd,

    The relationship between LoggerSM and LoggingSetup wasn't clear at all from the documentation.

    If I create an instance of LoggerSM and plug it to Default.common$.logger it would be enough for all modules to use it ?

    I agree that a lot of settings of LoggingSetup doesn't make sense for LoggerSM (which was very confusing on what to set)

    I understand the design choice for LoggingSetup. Just please write in the documentation of LoggingSetup that it's not meant to be used with LoggerSM.

    Clement
  • I'll update your enhancement request (allow LoggerSM to use the Timestamp provider instead of hard-coding TSCL/H) to include better documentation in regards to LoggerSM and LoggingSetup.