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/TMS320F28379D: RTOS Analyzer does not show any information

Part Number: TMS320F28379D

Tool/software: TI-RTOS

Hi,

I'm working through the TI-RTOS workshop and I have just made it to lab 4 where I'm supposed to configure the AIU to be used in the project and check some of the execution information.

I believe I have followed all the necessary steps in the lab manual to configure the operation, but I don't get any information out of RTOS Analyzer's System Load.

I'm attaching my app.cfg for you to view.

For now, all I have are two idle tasks: taskFxn1 and 2, and the outline of both functions is more or less the same (different GPIO and variables. I use Log_info1() for both functions):

Void taskFxn1(UArg a0, UArg a1)
{
  System_printf("enter taskFxn1()\n");

  GpioDataRegs.GPBTOGGLE.bit.GPIO34 = 1;
  taskFxn1Counter += 1;

  Task_sleep(1000);

  if (taskFxn1Counter >= 10000)
    {
      System_printf("taskFxn1Counter reached 10 000!\n");
      taskFxn1Counter = 0;
    }
  else
    {
      System_printf("taskFxn1Counter value: %i\n", taskFxn1Counter);
    }

  Log_info1("Toggled LED [%u] times", taskFxn1Counter);

  System_printf("exit taskFxn1()\n");
  System_flush(); /* force SysMin output to console */
}

The LEDs blink and I get the System_printf() output to the console, but when I try to use the RTOS Analyzer, I get nothing. To halt the controller, I use Scripts->Full Halt. I have also used Susped, but that doesn't do the trick either.

Is there something I'm missing?

Best regards,

Tero

2437.app.cfg

  • Hi Tero,

    We've found an issue with CCS 8.3. It does not parse the log records properly and therefore displays nothing. Are you using 8.3? I'd recommend moving back to CCS 8.2 if this is needed.

    If you are not using CCS 8.3, can you use CCS->Tools->RTOS Object View (or some versions call it ROV Classic) to look at the LoggerStopMode module to see if any records are present.

    Todd

  • Oops!!! I updated the above post to say "It does NOT parse"....
  • Hi Todd,

    That might explain it then, I just updated to CCS8.3. I'm only using the RTOS Analyzer for the workshop at the moment to get to know the tools and platform.

    I will try to downgrade CCS back to 8.2.

    Thank you.

    -Tero

  • This is really too bad. I had the same experience on 8.3 which we recently upgraded to. Everything was working fine on a previous version of CCS. I just upgraded to 8.3 because the ROV (Classic) was not working on 8.2 - apparently because of a known bug. So it looks like it will be necessary to go back to 8.1 if one wants both a functioning ROV and RTOS Analyzer.

    Todd: Would you be able to give us an idea of when the next version of CCS will be made available that addresses both of these issues?

    Thank you.
    Paul
  • Hi Paul,

    CCS is basically on a quarter release cadence now. We've figure out the issue, but we missed the freeze date for the Q1 release. So it will be in the following release.

    Todd
  • Thank you Todd.

     I have rolled back to CCS 8.1 and am still not able to get the log entries to show up.  I have checked and rechecked all of the settings/code, and everything seems to be in order as far as I can tell.  This feature used to work reliably.

    I am using the LoggerRunMode ETHERNET upload.  The NDK is setup and provides an ip address that I can ping.  I do not see anything being blocked by our firewall.  I am out of ideas about what to check.

    Currently I am using CCS 8.1, along with the latest 2.40.0.11 SDK, and XDCTools 3.50.8.24.  I have tried an earlier SDK to no avail as well as an earlier version of the XDC Tools.

    Do I need to go back to an even earlier version of CCS?  Is it just CCS that is involved in the failure to display the log messages, or are there issues with other components involved?

    Will much appreciate your help.

    Paul

  • Hi Paul,

    Can you start a new thread? This looks like a different issue.

    Todd