MCSA UIA on C6670 no usable logs

Ian Cole (old profile)

Other Parts Discussed in Thread: SYSBIOS

Hi. I have added the smallest change to the cfg that should enable SA:

var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup');
LoggingSetup.loadLoggerSize = 1024;
LoggingSetup.mainLoggerSize = 32768;
LoggingSetup.sysbiosLoggerSize = 32768;

(sizes are defaults - probably don't need lines 2,3,4)

Although the target is multicore. Let's get analysis working for a single core first.

I'm able to start/configure SA. When I suspend execution - I get some Logs.

But - the vast majority are EventClass Unknown and all analysis shows blank charts or graphs.

What should I do to get meaningful data from SA?

.cfg 0385.bios.cfg

log snip

over 13 years ago

0 Ian Cole (old profile) over 13 years ago

Intellectual 260 points

Not sure .png worked. lets try .jpg

0 Ian Cole (old profile) over 13 years ago

Intellectual 260 points

Tools:

CCS Version: 5.1.0.201205041800
Build id: N201205041800

0 ToddMullanix over 13 years ago in reply to Ian Cole (old profile)

TI__Guru* 96960 points

Hi Ian,

Which analysis graphs and views are you trying to look at?

Todd

0 Ian Cole (old profile) over 13 years ago in reply to ToddMullanix

Intellectual 260 points

Hi Todd.

To start with - CPU Load and Task Load would be good. Clearly there is UIA traffic when execution is suspended. But the events that drive task/cpu load have not been captured.

Just to add a little info:

I ran the stairstep example (using our platform definition) on our target with success. So target hardware and emulator / gel file are proven.

Our application has it's own background task. (Along with 30 or so other tasks)

Ian

0 ToddMullanix over 13 years ago in reply to Ian Cole (old profile)

TI__Guru* 96960 points

Hi Ian,

Can you sort the "Live Session Log" by the Logger and see if you have any Load events? For example:

You probably need to increase the size of the Load Logger since you have so many Tasks. For example

LoggingSetup.loadLoggerSize = 4096;

Each Load record is ~48 bytes, so 30 Tasks will generate ~1500bytes every 500ms. Also note with StopMode, old records are overwritten. So you need to make the logger size big enough to get enough meaningful data.

Todd

0 Ian Cole (old profile) over 13 years ago in reply to ToddMullanix

Intellectual 260 points

Hi Todd,

I've found the 'main' problem. Our background task does not yield. So the kernel idle task does not get scheduled. If I add Load_update() call (to the background busy loop) I get task/CPU load information.

Which leads me to my next issue.

All our tasks are started thru a common entry function 'taskEntrypoint' so that we can perform housekeeping before and after task execution. Unfortunately - the TSK_Attrs.name (which we setup to unique task names) is not used for labeling the tasks. All our tasks are called taskEntrypoint after the common function used as the launch point.

Is there a config parameter that will force use of TSK_Attrs.name ?

Thanks.

0 ToddMullanix over 13 years ago in reply to Ian Cole (old profile)

TI__Guru* 96960 points

Hi Ian,

Glad you figured out the problem. Regarding the Task name... can you post a new question? This allows us to manage the posts better and will probably get your question answered faster.

Thanks,
Todd

Processors

Processors forum

MCSA UIA on C6670 no usable logs