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.

Information on usage of running .out file on CCS from DSS

Other Parts Discussed in Thread: CCSTUDIO

Actually, I have 1 makefile and I generated .out file for that. Now I want to use this .out file and run my project in CCS. So my friend suggested me to use DSS and invoke CCS from command line prompt. But it is opening the Eclipse window and it is similar to CCS where I can create , build and run my project. Will you please tell me how can I run CCS from command line without any GUI. I didn't see any difference between the normal CCS and invoking CCS from DSS. If I am wrong, you please provide the correct information on the use case of DSS.

Thanks,

Mounika.

  • Hello Mounika,
    How are you invoking DSS and can you attach your script?

    Note that if you just want to simply run your *.out file from the command-line, maybe you can just use loadti:
    processors.wiki.ti.com/.../Loadti

    Thanks
    ki
  • Hi Ki-Soo Lee, thanks for your reply. I attached my code snippet below and using this I am invoking DSS in command line using the command " dss.bat -dss.debug myScript.js ". So with this can I invoke CCS automatically and see the output on the console?

    importPackage(Packages.com.ti.debug.engine.scripting)
    importPackage(Packages.com.ti.ccstudio.scripting.environment)
    importPackage(Packages.java.lang)

    // Create our scripting environment object - which is the main entry point into any script and
    // the factory for creating other Scriptable ervers and Sessions
    var script = ScriptingEnvironment.instance()

    script.traceBegin("CCSSession.xml", "DefaultStylesheet.xsl")

    // Log everything
    script.traceSetConsoleLevel(TraceLevel.ALL)
    script.traceSetFileLevel(TraceLevel.ALL)

    // Start up CCS
    ccsServer = script.getServer("CCSServer.1")
    ccsSession = ccsServer.openSession("C64x+ Megamodule Cycle Accurate Simulator, Little Endian")

    // Start up the debugger with the C64 simulator; it will start up the session in CCS
    debugServer = script.getServer("DebugServer.1")
    debugServer.setConfig("C:/ti/ccsv6/ccs_base/scripting/examples/C64/tisim_c64xple.ccxml")
    debugSession = debugServer.openSession("C64x+ Megamodule Cycle Accurate Simulator, Little Endian")

    // Load a program
    var isaName = "../C64"
    script.setScriptTimeout(15000);
    debugSession.memory.loadProgram(isaName + "/modem/Debug/modem.out")

    // terminate the debugger
    debugSession.terminate()
    debugServer.stop()

    // stop the Logging
    script.traceSetConsoleLevel(TraceLevel.INFO)
    script.traceWrite("TEST SUCCEEDED!")
    script.traceEnd()

    // Terminate CCS
    ccsSession.terminate()
    ccsServer.stop()

    Thanks,
    Mounika
  • Sridevi chinny said:
    using this I am invoking DSS in command line using the command " dss.bat -dss.debug myScript.js "

    Note that -dss.debug will run your script in the rhino debugger. You can remove this if you want to run everything from the shell

    Sridevi chinny said:
    // Start up CCS
    ccsServer = script.getServer("CCSServer.1")
    ccsSession = ccsServer.openSession("C64x+ Megamodule Cycle Accurate Simulator, Little Endian")

    These calls are for launching the CCS GUI. If you don't want the CCS GUI visible, remove these lines from your code. And remove the below lines too.

    Sridevi chinny said:
    // Terminate CCS
    ccsSession.terminate()
    ccsServer.stop()

    Sridevi chinny said:
    // Start up the debugger with the C64 simulator; it will start up the session in CCS
    debugServer = script.getServer("DebugServer.1")
    debugServer.setConfig("C:/ti/ccsv6/ccs_base/scripting/examples/C64/tisim_c64xple.ccxml")
    debugSession = debugServer.openSession("C64x+ Megamodule Cycle Accurate Simulator, Little Endian")

    Note that you are trying to use a simulator. Simulators are no longer available with CCSv6. You must use CCSv5.5 (or earlier) if you wish to use simulators).


    Did you explore using loadti?


    Thanks

    ki

  • Hi Ki-Soo Lee, I tried with your suggestions by commenting the CCSServer and commenting the debugserver. But it is not able to identify the simulator. I am using CCSV6 with simulator brought up from CCSV5.

    I tried with loadti. I set the path and I tried to run the below code ,

    C:\ti\ccsv6\ccs_base\scripting\examples\loadti\loadti -c "D:\mounika\TI_Intrinsi
    cs\diff_inp\NewTargetConfiguration.ccxml" -x "D:\mounika\TI_Intrinsics\diff_inp\
    diff_inp.xml" "D:\mounika\TI_Intrinsics\diff_inp\Debug\diff_inp.out"

    I got the below error as,
    'CMD' is not recognized as an internal or external command,
    operable program or batch file.

    Is there any other process that how can I run CCS from shell without using GUI? If so, please provide the information.
  • Sridevi chinny said:
    But it is not able to identify the simulator

    There is no simulator support in CCSv6.

    Sridevi chinny said:
    I am using CCSV6 with simulator brought up from CCSV5.

    I'm not sure what you are trying to do here. If you are trying to use the simulator in CCSv5 with CCSv6, that will not work.

    If you want to use simulators, you MUST use CCSv5.

    Sridevi chinny said:
    I got the below error as,
    'CMD' is not recognized as an internal or external command,
    operable program or batch file.

    Are you calling this from a DOS command window?

    Thanks

    ki

  • I'm having this error, can any one tell me what am I doing wrong?

  • Same problem than Leonardo, can you help me?
  • Leonardo Rodriguez48 said:

    I'm having this error, can any one tell me what am I doing wrong?

    The most common reason for that particular error is that the debugger failed to file the specified file in the specified location. Check to see if the file name and path is valid. The debugger is expecting a *.out file to load (in most cases). The error message shows what looks like a path to the project folder but not the *.out file. Check you script and make sure the file name is specified also.

    Thanks

    ki

  • I solve the error, I just changed the folder where *.out file was located (changed to desktop), and runs well.