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.

CCS/TMS320C6678: System Analyzer: Events missing for some cores

Part Number: TMS320C6678
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi,

I'm trying to use System Analyzer / UIA in JTAG Stop Mode with a C6678 device. As soon as I start using more than 5 cores, no application log events (Main Logger) for one of the cores are completely missing in the Live Session window or other System Analyzer views.

The following Execution Graph illustrates missing benchmark events for core 5:

But with the RTOS Object Viewer I can see that events are present in the log buffer of core 5:

I verfied this problem with CCS v6.2 and v7 using TI RTOS C6000 2.0.1.23. With CCS v5 and UIA 1.3.1.8 all events are shown correctly for all cores.

This is the UIA related stuff in the .cfg file of my project:

    Main.common$.diags_INFO = Diags.RUNTIME_ON;
    var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup');
    LoggingSetup.benchmarkLogging = true;
    LoggingSetup.loadTaskLogging = true;
    LoggingSetup.sysbiosLoggerSize = 32768;
    LoggingSetup.mainLoggerSize = 8192;
    LoggingSetup.memorySectionName = "MSMCSRAM";
    LoggingSetup.numCores = 8;                          // Required when using shared memory for log buffers
    LoggingSetup.multicoreEventCorrelation = true;
    LoggingSetup.loggerType = LoggingSetup.LoggerType_STOPMODE;
    Idle.addFunc('&LogSyncIdle');                    // This idle function writes a UIA Sync Point every second for Multicore Correlation

Thanks,
Ralf

  • Hi Ralf,

    Is Core 5 the only one that is using MSMCSRAM for the Log memory section?  When I use that memory section, for some reason there is no data showing up in RTOS Analyzer.  I do see the data in ROV, however.  I'm trying this with CCS 6.2.

    Thans,

    Janet

  • Hi Janet,

    all cores are using the same program binary.

    The problem seems to be related to using shared memory for the log buffers. If I change the configuration to use the L2SRAM section or a private mapped DDR3 section, it seems to work properly:

    LoggingSetup.memorySectionName = "L2SRAM";
    LoggingSetup.numCores = 1;

    Thanks,
    Ralf

  • Hi Ralf,
    Good to know that it works with the Log buffers in L2SRAM and DDR3. I'll look into this some more to see why it does not work with MSMCSRAM.
    Best regards,
    Janet