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.

Clarification on use of System Analyzer (UIA Target)

Other Parts Discussed in Thread: SYSBIOS

Customer is using the following software combination, which appears to be a supported combination based on the release notes of SYSBIOS v6.35.03.47.

CCS v5.40
ControlSuite v3.21
Compiler version TI 6.1.3
SYSBIOS v6.35.3.47
XDCTools v3.25.2.70

Device : TMS320F28069

Under project properties > CCS General > RTSC, we see the System Analyzer (UIA Target) item.  We’ve attempted to add this to our project, but have been unable to get it to function properly.  Is this even something we should be using?

  • Brandon,

    Yes. UIA has a28FP libs. There is no ti.uia.runtime.ServiceMgr (and related modules) for C28. All the loggers and events should work fine.

    What is not working?

    Todd

  • Not sure exactly as this issue was relayed to me.  You have the example project from an offline email.

    Is there an example of using the UIA with C2000 that could be used as a reference to understand what features are available?  Perhaps a wiki article on the topic?

  • Brandon,

    Is this issue still pending?

  • Sort of, in the sense that it is still unclear if UIA is applicable for C2000 and how to enable it and actually see it work.  I have yet to accomplish this.

  • Hello Brandon,

    What version of UIA are you using?  When you say "not working", do you mean that you do not see any data showing up in System Analyzer?  There is a bug in UIA 1.03.00.02, which was causing System Analyzer to not display any events on some targets:

    SDOCM00101390 No events displayed in System Analyzer when using JTAG transport on C6457 / TCI6484

    It has been fixed in the latest UIA release (1.03.01.08).  Could you update to this version if not already using it, and please let us know if the problem goes away?

    Best regards,

        Janet

  • janet said:

    What version of UIA are you using?

    UIA v1.03.00.02

    janet said:

    When you say "not working", do you mean that you do not see any data showing up in System Analyzer?  There is a bug in UIA 1.03.00.02, which was causing System Analyzer to not display any events on some targets:

    SDOCM00101390 No events displayed in System Analyzer when using JTAG transport on C6457 / TCI6484

    Would this bug also apply to JTAG transport to C2000?

    janet said:

    It has been fixed in the latest UIA release (1.03.01.08).  Could you update to this version if not already using it, and please let us know if the problem goes away?

    Preparing to download now... please stand by.

  • I was able to reproduce this problem on the F28069 control stick using UIA 1.03.00.02, and it went away when I switched to UIA 1.03.01.08.

        Janet

  • Awesome.

    Would you send me the link to the UIA download?  I just kicked off a CCS update and it didn't catch the UIA upgrade.  I probably don't have the correct repository specified to see it.

  • Janet,

    When you were able to add UIA into the project and get the UIA System Analyzer to operate, updating the information in the CCS Debug perspective System Analyzer view?

    Right now, when I include UIA LoggingSetup only, the execution of the program when I "run to main" goes into the abort().

  • I have made some progress when including just the UIA LoggingSetup.  The Event Upload Mode is set to JTAG Stop Mode.  Again, I'm running on C2000.  I have only included SYSBIOS Logging for Tasks (Enable Task logging & runtime control) as well as Application logging.

    I am able to launch the Live Session for UIA System Analyzer and see data populated when I halt the processor.

    However, if I let the processor run the application for a few seconds, it will eventually stop on its own.  Not a halt by the emulator, but the application will be found in the abort() routine after I halt the processor.  I get an indication of this visually, because I have a task that is blinking an LED based on a clock object.

    Since I have relatively limited RAM resources of the device, I have only 1024 set for the Buffer size.

    Is this expected, or have I misconfigured something?

  • Hi Brandon,

    Does the call stack in CCS give any indication as to what call is causing the abort to happen?  It could be caused by a stack overflow.  Can you use ROV to see if this is the case?  If you select "Task" in ROV, look at the "Detailed" tab, you will see the stack peaks.

    Another cause for aborting would be due to a memory allocation failure, but that is probably not likely in your case, since you are able to run for a few seconds.

    Thanks,

        Janet