• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 901 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/SW-EK-TM4C123GXL: RTOS Analyzer Does Not Display Data

scott
Expert 1190 points
Part Number: SW-EK-TM4C123GXL
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hi, I'm running the ROV Runtime Object Viewer using CCSv7 on the TivaC TM4C Launchpad. Everything seems to be a green light, but I cannot see any information displayed in the "Load Graph" for example. 

I'm starting with The "minimal" RTOS version of a blinking LED, then running the RTOS analyzer:

Project -> New -> RTOS -> Minimal

Tools -> Runtime Object Viewer

Tools -> RTOS Analyzer

Tools -> RTOS Analyzer -> Load Analysis.

The log/console shows:

CORTEX_M4_0: GEL Output:
Memory Map Initialization Complete

  • 0
    TI__Guru* 96960 points
    Hi Scott,

    The minimal empty does not have debug features enabled. Can you try the uartecho example instead? It has all debug features turned on.

    If you still do not see log records in Load Analysis, can you confirm records are being logged on the target. Look at ROV->LoggerStopMode->Records to see if there are any there.

    The key configuration to get logging turned on is the following in the .cfg
    1. Enabled the kernel to log records: BIOS.logsEnabled = true;
    2. Set up loggers. The easiest (and is enough for 90% of the customers) is to configure LoggingSetup. For example
    var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup');
    LoggingSetup.loadLogging = true;
    LoggingSetup.loadTaskLogging = true;
    LoggingSetup.loadSwiLogging = true;
    LoggingSetup.loadHwiLogging = true;
    LoggingSetup.loadLoggerSize = 256;
    LoggingSetup.mainLoggerSize = 512;
    LoggingSetup.sysbiosLoggerSize = 2048;

    By default LoggingSetup configures 3 StopMode loggers with the above sizes. The log records are maintained in these buffers for CCS to read out when the target is halted.

    Todd
  • 0 in reply to ToddMullanix
    Expert 1190 points

    Hi Todd,

    Thank you for the quick reply. I tried the uartecho example and it seems to be working better ( I didn't see all the LoggingSetup config settings you listed, so I added them). I'm able to see some activity now, although it seems to be dropping out sometimes. Probably I just have to experiment with it a little. more

    thank you.