• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 586 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.

Where to find STM_Utility scripts for CCSv5 and OMAP4

Bruce Samhaber
Prodigy 120 points

Hi,

The following TI wiki page

http://processors.wiki.ti.com/index.php/Using_System_Trace_%28STM%29

has the following description for connecting to the ETB.

How to collect STM information in the ETB

**** Start : Device Specific ****

  • For OMAP4 connect to the "CSETB" node from the debug view
  • For C66x based devices connect to the TETB_STM node.
  • For OMAP4 devices, enable STM data sending to ETB via Scripts->STM_Utility->EnabeTraceFunnelforETB

However, the installation of CCSv5 does not have  " STM_Utility " in the scripts menu. Where do we find that?

Thank you,

Bruce.

  • 0
    TI__Guru**** 163055 points

    Bruce,

    I searched through the GEL scripts in CCS and I see a Trace_OMAP4430.gel file that seems to have the necessary function.  The file is located in ccsv5/ccs_base/emulation/gel

    It looks like it will add a Config STM -> EnableTraceFunnelforETB() menu item.

    You would need to load the GEL file to get access to the function.  When in a debug session go to the Tools menu.  Select GEL Files.  Right click in the view that opens and select Load GEL.  After you do that the menu item should appear.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 120 points

    Hi,

    This helped. We now have the EnableTraceFunnelforETB() function.

    But What I actually wanted was.

    How to collect STM information by XDS560v2 System Trace Emulator receiver

    **** Start : Device Specific ****

    • For OMAP4 enable trace data export to EMU pin 0-N via Scripts->STM_Utility->Configure_EMU0_N_For_STM. Current supported value of N is either 1, 2, or 4. The recommended pin value is 4 as higher pin value provides higher bandwidth.

    **** End: Device Specific ****

    • Open Trace Control from CCS menu and focus current tab to the 'STM" tab.
    • Click on "Receiver" button; select "560 V2 Trace" from the popup menu and click on "OK".

    **** Start : Device Specific ****

    Now change the configuration parameters as appropriate in the Trace Control. For OMAP4 users the Trace Bits setting should be N Bit. N is the number used in step 2. For all other devices select 4 bits. The default parameters for all other options are optimal for most users.

    **** End: Device Specific ****

    Press "OK" now and this will setup the trace receiver channel for STM collection. On success, you are ready to collect STM data with the XDS560v2 System Trace Emulator.

    But now that I know where to load gel files I loaded the      omap4430_stm.gel     from a download from another posting; I have loaded the gel file and seem to have trace config tool now.

    However, if I only connnect to the CSSTM_0 module then I get the error message

    failed to calibrate channel: unable to detect sampling position

    There will be no data in the Trace Data Viewer..

    Or if I connect to all the devices and click on OK, I get the following:

    OR if I just click on Data Viewer instead I get :    "Trace is disabled"

    How does one enable the Trace?

    Overall what I am trying to do is view the L3  connection IDs out to the STM trace buffers on the Emulator. It appears that I need to configure the L3 to send the appropriate data to the STM through the OCP-WP , probably using L3_INSTR registers. This all appears to be accessible from the Debug port.

    Are there configuration scripts avaiable to setup this up or are the registers accesses simple?

    Thank you,

    Bruce.

  • 0 in reply to Bruce Samhaber
    TI__Guru**** 163055 points

    Bruce,

    I haven't used STM myself.  I am going to pass this over to another of our team members who may be able to help more.

    Regards,

    John