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.

Getting started with System Analyser

Other Parts Discussed in Thread: SYSBIOS

Hi

I am running CCS 5.1 and developing for a C6618 target (using TMDXEVM6618LXE board).  I want to use System Analyser with my project, but cannot get it to work yet.

This is what I have done:

1) Added to my .cfg file:

var LoggingSetup                =   xdc.useModule('ti.uia.sysbios.LoggingSetup');

LoggingSetup.eventUploadMode = LoggingSetup.UploadMode_JTAGRUNMODE;

2) In Project properties, enabled 'System Analyser (UIA Target) 1.0.3.25

 

Here is the output of running vers on my project .out file:

C:\>vers PingTest.out
PingTest.out:
        __ASM__ = C:/SVNProj/Orione/trunk/Source/PingTest/Debug/configPkg/package/cfg/RlcDrv_pe66e
        __ISA__ = 66
        __PLAT__ = evm6670_TML
        __TARG__ = ti.targets.elf.C66_big_endian
        __TRDR__ = ti.targets.omf.elf.Elf32

I am running:

CCS 5.1.0.09

UIA 1.0.3.25

XDS 3.22.1.21

on Windows 7.

 

When I run my project, in debug build, I get error:

Debugger based auto-detection

Cannot detect a valid UIA session. Problems:
Endpoints[O][1].uiaFile: Cannot find the UIA metadata file. Check existence of (.uia.xml)

 

Can you help please?

 

David

  • I have fixed this problem by creating a UIA Config File.

    Next problem is that one of my cores is marked as not instrumented. What would cause this please?

  • Ok, I added an endpoint for core 1 to my UIA config file and now both core 0 and core 1 are shown as instrumented.  However, with core 0 and core 1 both running, results are only shown for core 0 - never for core 1.

    Any thoughts on this please?

     

    David

  • I have found the cause of my problem.  Core 1 (which did not show in System Analyser) runs an application task that never yields.  I added a Task_sleep(1) to its while
    loop.  Core 1 then appeared in System Analyser.  Obviously, System Analyser needs the Idle task, or some other low priority task to run.  I don’t know how I could have detected this
    problem from the System Analyser windows.

     

  • David,

    I am just now seeing this posting ... Great job resolving/working around these issues!

    If the only logging you have turned on are the BIOS logs then logs will only be generated when:

    • a task/hwi/swi switch occured
    • a semaphore event occured
    • the idle task runs to log load events

    If none of those are occuring (and your running task don't have any user instrumentation) then there will be no data in System Analyzer. You point about not detecting this from System Analyzer view is well taken ... we'll look at providing some feedback if data is not receive for certain period.

    For configuration, System Analyzer will look in the default location <project>/Debug/configPkg/package/cfg/ and in the folder containing the .out file. Is your uia.xml file located in either of these places or is it being moved it to a different location?

    Thanks,

    Imtaz.

  • Hello David,

    I am trying to build a .ccxml file for TMDXEVM6618 board CCS Version: 5.1.1.00031, but I am unable to find a board or device name for that in the General setup. Which device or the board name you are using to work with this board?

    For the time being, I am using TMS320C6616 device in generating .ccxml file, but CCS crashes a lot with this selection, though I am able to work with the board with this setting.

    Regards,

    Pankaj