• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 671 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.

Fail "Trace System Control" for DM368

Yulin
Expert 1625 points

Other Parts Discussed in Thread: CCSTUDIO

Hi there,

CCS: v5.1.0.09000
Emulator: TI XDS560 POD
Target: DM368-based PCBA with 14pin JTAG connector.

The ARM9 can be connected and debugged.
However, when I press the "Apply" button in the "Trace System Control", the following message shows:

Debug configuration is attached.8204.davinci.xds560.zip

Please help to enable the ETB trace in DM368.

Thanks & regards,
Yulin.

 

  • 0
    TI__Guru**** 163035 points

    Yulin,

    Prior to CCSv5.2.0 I have had very little luck in getting ETB going.  With 5.2.0 and later it has worked well for me.  I don't have a DM368 (will try to track one down) but I would suggest updating to 5.2.0 or 5.2.1.  There is also a newer "TI emulation" package on the update manager that includes a number of trace fixes.

    We have created a page here that has instructions on how to get trace on a number of devices:

    http://processors.wiki.ti.com/index.php/CCS_Trace_Support

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1625 points

    John,

    Trace on DM365 with a "XDS510" still fails.

    Trace on DM365 with a XDS560 suceeds with the following steps:
    1. Update all emulation-related packages in CCS 5.1
    2. Add a subpath with port number 0x11 and add a CPU "ETB11" in this subpath
    3. Follow http://processors.wiki.ti.com/index.php/OMAPL138_Trace#ETB.

    Regards,
    Yulin.

  • 0 in reply to Yulin
    TI__Guru**** 163035 points

    Yulin,

    Good to know.  I am supposed to get DM368 and DM365 boards on Friday.  If they arrive in time I will see if I can tweak the device xml files so that you won't have to manually add the subpath and ETB11.  If that works I will get the updated files checked in for the next CCS release.  I will also try out xds510.  Should work on any xds, if not I will follow up with the vendor.  Which xds510 were you using?

    Regards,

    John

     

  • 0 in reply to JohnS
    TI__Guru**** 163035 points

    Yulin,

    My boards showed up today so I was able to try this out.  Just adding the subpath and ETB was not enough for me as it still failed to recognize the device ID.  I additionally had to go into the trace database xml and add info for DM365 and DM368.

    In the attached zip file the DM365.xml and DM368.xml need to go into /ccsv5/ccs_base/common/targetdb/devices

    Those files add the subpath and ETB to the device xmls used for creating target configuration files (ccxmls).  Note that you will have to recreate your ccxml.  Just open your ccxml, delete the device you added, then on the basic tab select the appropriate dm36x device or board.  It will then setup the subpath and ETB.

    The device_dm36x.xml file goes into /ccsv5/ccs_base/emulation/analysis/xmldb/trace_config/devices

    When you start CCS after dropping in these files it is best to run ccstudio.exe with the -clean parameter to make sure it updates its cache of the xml files.

    5432.DM36x_ETB.zip

    I was able to use ETB on both DM365 and DM368 using a Blackhawk XDS560v2 and a Spectrum Digital XDS510 USB Plus.  Should work with any emulator even an XDS100v2.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1625 points

    John,

    Your files work the DM365 ETB using my XDS510 USB.

    Thanks & regards,

    Yulin.