• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 726 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[CCS v5 + UIA] => Execution Graph not working

Ram R
Intellectual 420 points

Hello CCS experts,

Here is my setup:

  • Version: 5.1.0.09000
  • uia_1_00_03_25
  • bios_6_33_00_19
  • ipc_1_23_05_40
  • C6000 Code Generation Tools 7.3.2
  • COFF ABI
  • Device: C6424

Firstly, I get the following warnings:

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

warning: xdc.runtime.Log: "C:/ti/xdctools_3_23_00_32/packages/xdc/runtime/Log.xs", line 168: xdc.runtime.Log idToInfo: Two events with the same id: ti.uia.event
s.UIABenchmark.start and xdc.runtime.Log.L_start share the msg: 'Start: %$S'.  You must reconfigure the message of one of these events to ensure its id will be
unique.
warning: xdc.runtime.Log: "C:/ti/xdctools_3_23_00_32/packages/xdc/runtime/Log.xs", line 168: xdc.runtime.Log idToInfo: Two events with the same id: ti.uia.event
s.UIABenchmark.stop and xdc.runtime.Log.L_stop share the msg: 'Stop: %$S'.  You must reconfigure the message of one of these events to ensure its id will be uni
que.
warning: xdc.runtime.Log: "C:/ti/xdctools_3_23_00_32/packages/xdc/runtime/Log.xs", line 168: xdc.runtime.Log idToInfo: Two events with the same id: ti.uia.event
s.UIABenchmark.startInstance and xdc.runtime.Log.L_startInstance share the msg: 'StartInstance: %$S'.  You must reconfigure the message of one of these events t
o ensure its id will be unique.
warning: xdc.runtime.Log: "C:/ti/xdctools_3_23_00_32/packages/xdc/runtime/Log.xs", line 168: xdc.runtime.Log idToInfo: Two events with the same id: ti.uia.event
s.UIABenchmark.stopInstance and xdc.runtime.Log.L_stopInstance share the msg: 'StopInstance: %$S'.  You must reconfigure the message of one of these events to e
nsure its id will be unique.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

If I user versions of SYS/BIOS and XDC that is part of the CCSv5 install (I forget the exact versions...) the warnings go away.

BUT

In either case, the Execution Graph seems flat and bunched up...See attached picture.

I read through the UIA manuals and tried various Diags switches to no effect.

The problem can be reproduced by building the stairstep example for

  • ti.platforms.evm6424 and
  • LoggingSetup.eventUploadMode = LoggingSetup.UploadMode_SIMULATOR.

A quick turnaround is is greatly appreciated!

Thanks!

  • 0
    TI__Expert 5670 points

    Ram,

    The dotted line indicates data loss. This is most likely because the log buffers on the target are not large enough for the amount of data you're logging. You can use Diag masks to filter some logs (sounds like you tried this already) or you can increase the buffer size. See this thread for discussion on this: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/182938/665772.aspx#665772.

    Note that you can click on the name/label of the channel on the y-axis to get a discrete graph. You can also zoom into the graph with the buttons on the view toolbar or by using mouse selection just below the x-axis.

    I will have someone else comment on the warnings you're receiving.

    Regards,

    Imtaz.

  • 0 in reply to Imtaz Ali
    TI__Expert 3745 points

    Hi Ram,

       Please ignore the warnings generated by Log.xs, line 168 - you do not have to make any changes to your code or use an older version of XDC. 

    The warnings are being caused by some new events that were introduced recently in the xdc.runtime.Log module for use in the OSAL product.   The message strings for the events will be modified in a future release of xdc which will prevent the warnings from being issued.   

    Regards,

      Brian