RTOS: SYSBIOS 6.35.04 / How to see RTOS Analyzer views in my development environment

Hello Todd.

I tried to get the 4.2 views, but the link that you had informed me was not found.
Here, I listed what I did as follows
1. I used System Analyzer (UIA Target) 1.3.1.08 (installed in CCS V5.5).
2. I added LoggingSetup module to the application by default settings.
3. I built the project without any error and ran a debug session.
3.1. But, a message appeared in Console view as follows
3.1.1. "out of memory : heap=0x0, size-14"
3.1.2 . "xdc.runtime.Error.raise : terminating execution"
3.2. I terminated the debug session and I modified the "heap size" in the menu below
3.2.1. Available Products -> BIOS -> Runtime -> Runtime Momeory Options -> Heap size = 512
3.3. I re-built the project without any error and ran a debug session again.
4. The message disappeared and I could resume the second debug session.
4.1. The souce code seemed to work properly,but any RTOS Analyzer menu even the previously available
menus didn't work.
4.1.1 A breakpoint stopped exactly at the line 82 : Semaphore_pend(mySem, BIOS_WAIT_FOREVER);
4.1.2 Any RTOS Analyzer memu didn't work
4.1.2.1. Even the previously available menus(Raw Logs, Printf Logs) didn't work.
4.1.2.2. The other menus still didn't work.

These are problems after your comments.
Thanks in advance.
Sincerely yours.
Sinho kim

Hi Todd

While I was waiting for your answer, I also skimmed through the article that you had previously informed me(System Analyzer, spruh43f). Unfortunately, the context of the article didn't match my development environment such as the target platform(C6000 in the article, but F28335 in my development environment) and the version of CCS (unknown in the article as I know, but v5.5 in my development environment).

Thus, I folllowed the instructions in the article as possible as I could.
1. I went to <5.1 Quickly Enabling UIA Instrumentation> on the page 88.
1.1. Next, I looked over the instructions <Configuring Steps to Perform on All Targets> as follows
1.1.1. Remove Legacy Modules. Remove any statements in your application’s configuration file (*.cfg)
that include and configure the following modules:
— ti.sysbios.rta.Agent(I could not find it)
— ti.rtdx.RtdxModule(I could not find it)
— ti.rtdx.driver.RtdxDvr(I could not find it)
If you have logger instances for the xdc.runtime.LoggerBuf, delete those instances.
1.1.1.1. I tried to delete those instaces as follows :
1.1.1.1.1. Outline window->LoggerBuf->logger 0 -> Delete logger0
1.1.1.1.2. An error message appeared.
Unable to delete logger0
Reason :
logger0 is stll being used, on line 84
1.1.1.1.3. I made line 84 a commnent by adding "//" at the first of the line.
//Defaults.common$.logger = logger0;
1.1.1.1.4. Next, I deleted "logger0" successfully.
1.1.1.2. I also deleted LoggerBuf in the Outline window.
1.1.1.2.1. Outline window->LoggerBuf->Stop Using LoggerBuf
1.1.2. Remove xdc.runtime.LoggerBuf from your application's configuration file. Events logged with
LoggerBuf cannot be viewed in RTOS Analyzer(Already removed at the above step).
1.1.3. Use the LoggingSetup Module. Add the following statement to include UIA’s LoggingSetup module
in your application’s configuration. For example:
var LoggingSetup =
xdc.useModule('ti.uia.sysbios.LoggingSetup');
Including the LoggingSetup module creates logger instances needed by UIA and assigns those
loggers to the modules that need them in order to provide UIA data.
1.1.3.1. I confirmed that this code existed in the "task.cfg" file.
1.1.4. If you intend to use a UIA logger other than LoggerStopMode, set the LoggingSetup.loggerType
parameter as described in “Configuring the UIA Logger” on page 94. This example uses the
LoggerMin minimal footprint logger:
LoggingSetup.loggerType = LoggingSetup.LoggerType_MIN;
1.1.4.1. I decided to use the default setting(LoggerStopMode).
1.1.4.2. I didn't do anything here.
2. And, I also see over <5.1.1 Using XGCong to Enable UIA Instrumentation> on the page 89
2.1. However, the version of CCS in the article didn't match that of CCS in my development environment.
(Unkown in the article as I know, but v5.5 in my development environment)
2.2. I couldn't successfully follow the instructions on this section.
2.1. "ti.sysbios.rta.Agent" was not found in the Ouline window.
2.2. "xdc.runtime.LoggerBuf->logger0" and "xdc.runtime.LoggerBuf" had been already eliminated from
the Ouline window.
3. I successfully built the project without any error and ran a debug session again.
3.1. There was no change from my first reply.
3.2. Any RTOS Analyzer menu still didn't work.

Additionally, there was something wrong that I had to inform you.
I found that the sub-menus of RTOS Analzyer disappeared after the list 4 in the my first reply.

I have done up to here.
How do I solve these problems?
Help me, please.

Thanks in advance.
Sinho KIm