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.

MCSDK System Analyzer example

Other Parts Discussed in Thread: SYSBIOS

Hi,

I am trying to run the MCSA-related MessageQ and Stairstep examples on the C6670 simulator (CCS 5.0.3.00025 + MCSDK Beta-2), which are located in:

ccsv5\uia_1_00_01_09_eng\packages\ti\uia\examples\simtci6616

 

I get the following output for both examples:

 

[TMS320C66x_0] **************************************************

[TMS320C66x_0] ******* Ethernet Single Core Example Start *******

[TMS320C66x_0] **************************************************

[TMS320C66x_0] Error: Inserting memory region 0, Error code : -131

[TMS320C66x_0] QMSS init failed 

Why does this happen?
thanks
Ran

  • Hi Ran,

    We decided to remove the explicit support for the simtci6616. Trying to support the funky WinPCap connection for the Ethernet was deemed lower priority once we had support for stopmode and simulator (and runmode for C64P and C66 devices). Also, the NDK is now supported on the real 6616 hardware. These changes will be reflected in the next release of the MCSDK.

    So what should you do now? I'd recommend moving to stopmode or probepoint/simulator mode for UIA. These are supported in the version you have. With stopmode, the records are read from the simulator (or real hardware) when you halt the target. With probepoint/simulator mode, the target is halted brief during the Log call and MCSA reads the record and continues the target.

    Try the following. Create one of the SYS/BIOS example (e.g. Task Mutex Example). Also add System Analyzer (UIA) into your "Products and Repositories" for your project. Build it and run it to make sure it works as expected. (note: simulators are slow sometimes, so it might take 20-30 seconds for the example to run).

    Now remove all the LoggerBuf lines from the .cfg. For example.

    var LoggerBuf = xdc.useModule('xdc.runtime.LoggerBuf');
    var loggerBufParams = new LoggerBuf.Params();
    loggerBufParams.numEntries = 32;
    var logger0 = LoggerBuf.create(loggerBufParams);
    Defaults.common$.logger = logger0;
    Main.common$.diags_INFO = Diags.ALWAYS_ON;

     Add the following lines into the .cfg

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

    Rebuild the app and run it to main(). Open MCSA->Live. Select collect "until stop is requested" and hit "OK". Now continue the target. When you halt the target (or the example completes), so should see data in the SA Live Session. You can add some Log_printf calls into the example and they should show up in the SA Live Session also. Note: the Task Mutex example might not generate any Load events since it could terminate before 500ms (period for generating Load events).

    Todd