• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 54 subscribers
  • Views 1859 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.

Using DSS to load and run a .out file.

Jason Corrigan
Prodigy 50 points
Other Parts Discussed in Thread: OMAP-L138

I am trying to use DSS to load and run on an OMAP-L138 experimenter board. I am able to connect to the target and debug through CCS v4 but when I use loadti or any of the other example scripts for DSS it just hangs there until I kill the process.  I added some print statements to the scripts and found that it is hanging on the code:
debugSession = debugServer.openSession(".*").  When I run go.bat from the \DebugServerExamples\ I get the printout about openSession:

openSession: ENTRY sPattern: .*
start: ENTRY
start: Firing: onServerStarting()
start: Connecting to XPCOM DebugServer

 

I am running on Windows XP Pro SP3.  CCS v4.2.0.10017

  • 0
    TI__Guru**** 473961 points

    Are you trying to use loadti or the examples on the OMAP L138? If so, that will not work unless you modify the scripts. (By default,) loadti does not support multi-core targets like L138 and the examples are hard coded to work with specific targets.

    ki

     

  • 0 in reply to Ki
    Prodigy 50 points

    I have tried loadti and have also tried the DSS example found in the .\DebugServerExamples directory.  I did modify Memory.js to use the .ccxml file that is used when I connect to the L138 through CCS.

     

    Thanks

    -Jason

  • 0 in reply to Jason Corrigan
    TI__Guru**** 473961 points

    You should also have to change this call:

    debugSession = debugServer.openSession(".*").

    This is basically saying to open a debug session for the first core on the JTAG scan chain. That's fine for single core devices since the first core is the only core. But on multi-core devices like L138, which has an ARM and DSP, you should be more explicit.

    http://processors.wiki.ti.com/index.php/Debug_Server_Scripting#Multiple_Debug_Sessions_for_Multi-core_Debug

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    I am having trouble finding the exact board name and cpu name(s) in the .ccxml file.  I attached the .ccxml file I am using.

    Fullscreen 8345.config.txt Download 
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Emulator_0" href="connections\TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Emulator_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
            <instance XML_version="1.2" href="drivers\tixds100icepick_c.xml" id="drivers" xml="tixds100icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers\tixds100c674x.xml" id="drivers" xml="tixds100c674x.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320C6748_0" href="Devices\c6748.xml" id="TMS320C6748_0" xml="c6748.xml" xmlpath="Devices"/>
            <device HW_revision="1" XML_version="1.2" description="C674x Floating point DSP" id="TMS320C6748_0" partnum="TMS320C6748">
                    <router HW_revision="" XML_version="1.2" description="" id="device_0" isa="ICEPICK_C">
                        <subpath id="device_1">
                            <cpu HW_revision="" XML_version="1.2" description="" id="device_2" isa="TMS320C674X">
                                <property Type="filepathfield" Value="..\gel\OMAPL138_ARM.gel" id="GEL File"/>
                            </cpu>
                        </subpath>
                    </router>
                </device>
            </platform>
        </connection>
    </configuration>
</configurations>

    Thanks,

    -Jason

  • 0 in reply to Jason Corrigan
    TI__Guru**** 473961 points

    Your ccxml file looks odd. You are configured for a C6748, not an L138. An L138 has an ARM and a DSP while the C6748 only has the DSP. Which device are you actually using?

    Also your ccxml file for the C6748 has the DSP configured to use the gel file for the ARM.

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    I am using a development board from logic, zoom OMAP-L138 Experimenter kit.  It came with some example programs that I am able to build and debug through CCS v4.  I found the .ccxml file these example programs were using and attempted to use DSS because our goal is to continuos automated integration unit testing with DSS.

    Thanks,

    -Jason

  • 0 in reply to Jason Corrigan
    TI__Guru**** 473961 points

    I think I understand what is going on now. XDS100v1 does not support ARM so when using that emulator (the on-board emulation on the board), only the DSP shows up. But i don't know why the DSP is using the ARM gel file.

    So both loadti and the examples should work. Sorry for the diversion.

    Could you generate a verbose DSS log and attach that here?

    http://processors.wiki.ti.com/index.php/Debug_Server_Scripting#Logging

    traceSetFileLevel(TraceLevel.ALL);

    Thanks

    ki

     

  • 0 in reply to Ki
    Prodigy 50 points

    What emulator is needed to support ARM?  I believe we have some XDS510 USB emulators.

    Fullscreen 6724.MemoryTestLog.xml Download 
    <?xml version="1.0" encoding="windows-1252" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="DefaultStylesheet.xsl"?>
<log>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367917</millis>
  <sequence>3</sequence>
  <logger>com.ti</logger>
  <level>FINER</level>
  <class>com.ti.ccstudio.scripting.environment.ScriptingEnvironment</class>
  <method>traceSetFileLevel</method>
  <thread>10</thread>
  <message>RETURN</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367948</millis>
  <sequence>4</sequence>
  <logger>com.ti</logger>
  <level>FINER</level>
  <class>com.ti.ccstudio.scripting.environment.ScriptingEnvironment</class>
  <method>getServer</method>
  <thread>10</thread>
  <message>ENTRY sServerName: DebugServer.1</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367948</millis>
  <sequence>5</sequence>
  <logger>com.ti</logger>
  <level>FINER</level>
  <class>com.ti.ccstudio.scripting.environment.ScriptingEnvironment</class>
  <method>getServer</method>
  <thread>10</thread>
  <message>Getting definition for: DebugServer.1</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367948</millis>
  <sequence>6</sequence>
  <logger>com.ti</logger>
  <level>FINER</level>
  <class>com.ti.ccstudio.scripting.environment.ScriptingEnvironment</class>
  <method>getServer</method>
  <thread>10</thread>
  <message>Constructing server</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367948</millis>
  <sequence>7</sequence>
  <logger>com.ti</logger>
  <level>FINER</level>
  <class>com.ti.ccstudio.scripting.environment.ScriptingEnvironment</class>
  <method>getServer</method>
  <thread>10</thread>
  <message>RETURN com.ti.debug.engine.scripting.DebugServer@77158a</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>8</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>setConfig</method>
  <thread>10</thread>
  <message>ENTRY sConfigurationFile: R:/V22/OMAP-L138_GEL_BSL_Files_v2.3/bslevmomapl138.ccxml</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>9</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>setConfig</method>
  <thread>10</thread>
  <message>RETURN</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>10</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>openSession</method>
  <thread>10</thread>
  <message>ENTRY sPattern: .*</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>11</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>start</method>
  <thread>10</thread>
  <message>ENTRY</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>12</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>start</method>
  <thread>10</thread>
  <message>Firing: onServerStarting()</message>
</record>
<record>
  <date>2011-04-29T14:39:27</date>
  <millis>1304102367964</millis>
  <sequence>13</sequence>
  <logger>com.ti.debug.engine.scripting.DebugServer</logger>
  <level>FINER</level>
  <class>com.ti.debug.engine.scripting.DebugServer</class>
  <method>start</method>
  <thread>10</thread>
  <message>Connecting to XPCOM DebugServer</message>
</record>
</log>

    Thanks,

    -Jason

  • 0 in reply to Jason Corrigan
    TI__Guru**** 473961 points

    Thanks. I'll analyze the log

    Jason Corrigan said:
    What emulator is needed to support ARM?  I believe we have some XDS510 USB emulators.

    XDS510 USB will support the ARM. So will XDS100v2 (v1 doesn't).

    ki

  • 0 in reply to Ki
    Prodigy 145 points

    Ki,

    did you ever get a chance to look at that log?  I'm picking up where Jason left off.

    I've found that I can run loadti just fine on a desktop computer targeting both the simulator and hardware via emulator. 

    The problem is that it hangs when I run using a laptop logged in with my user account.  If I login as administrator it also works like a champ.

    So, I am assuming that there is some permission issue that I don't understand.  Is there a piece of this tool-chain that requires me to login as administrator?

    Many thanks for your help,

    Bryan

  • 0 in reply to Bryan Ash
    Prodigy 145 points

    I've done some more experiments and it turns out that I can successfully run loadti on my laptop if I am logged in as a local user instead of a domain user.

    Any thoughts?