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.

System Analyzer Live - EventTransportUndefined

Other Parts Discussed in Thread: SYSBIOS

c6748, ccsv5.2.1.00018, sys/bios 6.33.4.39

I am trying to use the System Analyzer.  I have added and configured LoggingSetup for JTAGSTOPMODE. But when I bring up Tools | System Analyzer | Live in the debugger the "auto detected" Transport says None. Tried to "Create UIA Config File" but the only choiuce seems to be JTAGRUNMODE.

How do I get System analyzer to correctly auto detect the mode set in my LoggingSetup?

  • went ahead and created a UIA config file based on the instructions from the tutorials. clicked Run, clicked Run(do I have to click Run in the Live Session window?  this is not mentioned in the tutorial...) paused my program, click Stop on the Live Session window and...nothing. no events were captured.  the log appears to be empty. apparently I missed some step.

    been working on this all day with no results.  any ideas?

  • Kurt,

    I think “None” is what will be shown when you’ve configured one of the JTAG modes.  I don’t have a setup to easily verify this at the moment though.

    Can you please post the generated UIA config file (with the .usmxml extension)?

    Thanks,
    Scott

  • The the user's guide says it should auto detect when I set Event Upload Module to UploadMode_JTAGSTOPMODE. Tutorial 1 shows"Stop-Mode JTAG".  But, Tutorial 1 is about logging not execution profiling.  I was looking for Tutorial 3 so that I could compare with my project.

    Maybe I could get it to work by starting over but this is a fully developed project which would difficult and complicated to reconstruct.

  • Hi Kurt,

         As you mentioned, you should see "Stop-Mode JTAG" in the transport field, not NONE.  It looks like your project is not configured properly.  Could you post your .cfg file and the *.uia.xml and *.rta.xml files that are located in Debug\configPkg\package\cfg ? 

    Regards,

      Brian

  • Can only upload one file per reply.

    *.rta.xml and *.uia.xml to follow...

  • Hi Kurt,

       Your .cfg script should use LoggerStopMode (for stop-mode event capture) instead of LoggerCircBuf (which is used for JTAG Run Mode capture).  If you replace lines 9-20 of your .cfg file with the following, System Analyzer should properly detect the transport type:

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

    Program.sectMap[".cinit"] = "DDR";
    Program.sectMap[".myLoggerSection"] = "DDR";

    var LoggerStopMode = xdc.useModule('ti.uia.runtime.LoggerStopMode');
    var loggerStopModeParams = new LoggerStopMode.Params();
    loggerStopModeParams.transferBufSize = 4194304;
    loggerStopModeParams.bufSection = ".myLoggerSection";
    var logger = LoggerStopMode.create(loggerStopModeParams);
    logger.instance.name = "My Main Logger";
    LoggingSetup.mainLogger = logger;

    Regards,

      Brian

  • Yes, that did it.  Thank you.

    Guess I did not read something close enough.  Where would this solution be discussed?

  • Hi Kurt,

        It should be discussed in the System Analyzer User's guide.   Unfortunately, the User's Guide text doesn't cover this properly, and only mentions using LoggerCircBuf for doing custom configurations.  I'll file a problem report against the User's Guide to add text to clarify this. 

    Thank you for identifying this problem!

    Regards,

      Brian

  • Yo migh also look into what hapend to tutorials 3 & 4.

    Thanks again.

  • Hi Kurt,

      Please see my post to http://e2e.ti.com/support/embedded/bios/f/355/p/247533/867004.aspx#867004 for clarifications to tutorial 3.   I think Tutorial 4B should be clear enough as is.  Tutorial 4C does not cover the C6748 - please let me know if you need to use Ethernet as a transport on your platform and have problems getting this to run .

    Regards,

      Brian

  • Thought I'd throw in my 2 cents for how to do this on CCSv6, it took awhile since the UIA 2.0 is very different.

    My configuration:

    CCSv6, C6472, XDC 3.30.1.25_core, IPC 3.20.0.06, NDK 2.23.2.03, SYSBIOS 6.40.1.15, UIA 2.0.0.28 and XDAIS 7.10.0.06, CGT 7.4.8. (you will need the cmd file for_ipc.cmd that Janet supplied in the link ) http://e2e.ti.com/support/embedded/tirtos/f/355/p/347073/1215308.aspx#1215308

    I have the following logger configuration in multicore example code (its a modified NDK-less version the CCS message queue example).

    Log = xdc.useModule('xdc.runtime.Log');
    var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup');
    LoggingSetup.loggerType = LoggingSetup.LoggerType_MIN;
    LoggingSetup.loadLoggerSize = 512;
    LoggingSetup.mainLoggerSize = 512;
    LoggingSetup.sysbiosLoggerSize = 128;
    LoggingSetup.sysbiosTaskLogging = false;
    LoggingSetup.loadLogging = false;
    LoggingSetup.mainLoggingRuntimeControl = false;
    LoggingSetup.memorySectionName = "DDR2";

    // Only use this if the buffer is in shared memory. We hope to do this
    // when its in DDR.
    LoggingSetup.numCores = 6; // tells logger that cores share a memory location.

  • I've also found that CCSv6.0.0.00190 doesn't always upload the printf logs and does not update the Tools->ROV->Records when you switch cores.