• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 56 subscribers
  • Views 1211 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.

Starting CCSv5 from JAVA failing

Peter Robertson
Expert 2770 points
Other Parts Discussed in Thread: CCSTUDIO

I have a Java application that starts CCS via DSS.

          m_dssScriptEnv.getServer("CCSServer.1").openSession(".*");

This works perfectly under CCSv4 and brings up the CCS user interface without problems.

When I change the path used to locate the various components from CCSv4 to CCSv5, no CCS user interface appears.

The two paths are:

E:\Texas Instruments\ccsv4\DebugServer  -- this works

C:\ti\ccsv5\ccs_base\DebugServer  -- this fails

Is there any documentation that describes the changes from CCSv4 to CCSv5 in this area?

There does not seem to be an equivalent for CCSv5 of "http://processors.wiki.ti.com/index.php/Java_Scripting_with_DSS"

  • 0
    TI__Guru**** 463481 points

    Hi Peter,

    startup.jar has been replaced in v5 and I'm trying to find out which v5 jar files you'll need to get this going with DSS in v5....

    ki

  • 0 in reply to Ki
    TI__Prodigy 680 points

    Eclipse no longer has startup.jar as it did in eclipse 3.2 or older version. Since ccs5.2 is using eclipse 3.7, the corrsesponding file that acts like startup.jar is really something like org.eclipse.equinox.launcher_1.2.0.v20110502.jar. The exact file name (that embeds its version inside the filename) can be found in eclipse.ini or ccstudio.ini

     

  • 0 in reply to W Lai
    TI__Guru**** 463481 points

    Winnie Lai said:
    Since ccs5.2 is using eclipse 3.7, the corrsesponding file that acts like startup.jar is really something like org.eclipse.equinox.launcher_1.2.0.v20110502.jar.

    Right, I tried that but seems like it needs more than just 'org.eclipse.equinox.launcher_1.2.0.v20110502.jar'.

  • 0 in reply to Ki
    Expert 2770 points

    Adding org.eclipse.equinox.launcher_1.2.0.v20110502.jar (along with startup.jar for backwards compatibility) allows my code to start the CCS5 UI.

    Thanks for your efforts and practical help, although it would have been better had such fundamental changes been properly documented.

  • 0 in reply to Peter Robertson
    Expert 2770 points

    I spoke too soon!

    Unfortunately I still had CCSv4 on my path, so I was getting that started. Even with the new jar file, CCSv5 does not start.

    What else needs to be done?

  • 0 in reply to Peter Robertson
    TI__Guru**** 463481 points

    Peter - just curious, what is your use case for launching CCS? Are you looking to debug your Java application by seeing GUI in action as the application runs?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2770 points

    We produce a multiprocessor development software suite, Diamond, that handles many of the difficulties in using multiple
    processors/cores. (see www.3L.com).

    Normally, the multiprocessor hardware is accessed using manufacturer-specific fast links. In the general case, for example
    on the EVM boards, our host server program has an option to use JTAG to talk to the hardware, and this works by firing up
    CCS to manage the JTAG link.  In parallel with this, we need the option to make CCS visible for debugging. This all worked
    well until CCSv5 came along...

  • 0 in reply to Peter Robertson
    TI__Guru**** 463481 points

    Hi Peter,

    We have been looking into this issue and here is an update (both bad news):

    1. CCSv5 supports a different implementation for having DSS associated with a running CCS. Unfortunately this is currently broken and it is under investigation. We hope to resolve this soon.

    2. This new implementation will only supports JavaScript. To have access to this functionality, you would need to move from a Java application to JavaScript.

    Sorry,

    ki

  • 0 in reply to Ki
    Expert 2770 points

    As you say, CCSv5 has been bad news from the start - this is just the final straw.

    It seems that backwards compatibility isn't a major concern for TI.

    Thanks for your efforts.

  • 0 in reply to Peter Robertson
    TI__Guru**** 463481 points

    Sorry for the pain. JavaScript is the default and officially supported language for DSS (though you would think Java would be too since DSS is basically a set of Java APIs). Other alternatives (Java, Perl, Jython, etc) can be made to work but is not officially supported.

  • 0 in reply to Ki
    Expert 2770 points

    It's not your fault :-)

    The problem is that for the immediate future (with the current CCS) I have no way to load a multicore program into the C6678.

    Having customers waiting doesn't make life easier.

    (Before you suggest obvious to you, note that the application I need to load is not in any format you know about).

  • 0 in reply to Peter Robertson
    Expert 2770 points

    Do you have any pointers to documents that describe what should be available and what is currently broken about it?

  • 0 in reply to Ki
    Prodigy 30 points

    Hi Ki,

    Thank you for the information. It has been a year after your reply, is there any update on it? Also, is there anyway I can call JavaScript from Matlab to start CCS 5.4? 

    Thanks,

    Da