Use open source for embedded software test

I wrote the article and everything in there should work.  What specifically is not working for you?

Darian

Hi, Darian,

       Glad to know the author is here.

       I am trying to debug a target via junit test in CCSv4. But whenever I am debug a junit test, it prompts, "An internal error occurred during: "Model Proxy installed notification job."  (see the attachmed figure.)

What is the problem?

AppleCat

First, what version of CCS are you using?  Is this beta 5 update 1?  Did you download any any updates after adding Java support?  I've tried this again on beta5 update 1, without any other eclipse updates, and it's still working in this version.

Second, can you open the error log (Window->Show View->Other and browse for "Error Log"), clear it, and try to debug the junit test again?  A new entry should be added.  If you double click that, an exception stack trace should be visible.  Could you copy that and add it here?

Thanks,
Darian

Hi, Darian,

Darian Sale said:

First, what version of CCS are you using?  Is this beta 5 update 1?  Did you download any any updates after adding Java support?  I've tried this again on beta5 update 1, without any other eclipse updates, and it's still working in this version.

            Is this beta 5 update 1? :        Yes, after the night of installing CCSv4_4.0.0.14000_package.exe, I also update it according to the following Figure -1.

           Did you download any any updates after adding Java support?   Yes, beside the above update, I remember that I also have another installing of a Java(Eclispe?) update.

           To avoid the posted problem, I had tried to uninstall the CCSv4 (but I had not  deleted all the files under folder \Texas Instruments\!!!) and re-run CCSv4_4.0.0.14000_package.exe, re-extract JDT to \Texas Instruments\ccsv4, the problem still existed !!!

           However, when in this morning I uninstalled the CCSv4, and deleted all the files under the folder \Texas Instruments\, re-run CCSv4_4.0.0.14000_package.exe, then re-extract JDT to \Texas Instruments\ccsv4, the prompt disapppear!!!

Darian Sale said:

Second, can you open the error log (Window->Show View->Other and browse for "Error Log"), clear it, and try to debug the junit test again?  A new entry should be added.  If you double click that, an exception stack trace should be visible.  Could you copy that and add it here?

         I am sorry to say that I did not keep the Error Log, but if next time I come across the same prompt, I will copy the exception stack trace.

        Really thanks for your advice.

Br,

AppleCat

Thanks,
Darian

Figure-1

<quote>You were correct to uninstall, delete any of the files in there, and then re-install and re-patch.  I'm not sure what you meant by the prompt disappearing though - could you elaborate on that?

</quote>

"prompt disappearing" means the problem is resolved.

Sorry for my mis-description.

I totall agree with you. I think this post could be closed.

Hi,

       http://www.embeddeddesignindia.co.in/STATIC/PDF/200904/EDIOL_2009APR16_ETEST_TOOL_TA_01.pdf?SOURCES=DOWNLOAD

        From the above link, it seems that a junit test could be debugged in a Eclise-based CCS envrionment, and the junit test case could lauch another debug session to debug a program in a targer during the running time. Am I understand correctly? But unforturnately, I failed.

        In the above link, it says,

    I am quite confused: where to run the DSS command, ScriptingEvironment.instance().getServer("CCSServer.1").openSession(".*")? is it in the Scripting console? or shall I add the following code to the java test case?

ScriptingEnvironment env = ScriptingEnvironment.instance(); 

Br,

AppleCat

Hi, Darian, 

             It seems that the link, http://community.itg.ti.com/digital/forums/t/900.aspx, does not work, doesn't it?

Br,

AppleCat

Hi, Ki,

        The url in your reply is about using RHINO_DEBUGGER (NOT CCSv4 with jdt installed) to debug the javascript. However, I want to know whether I could run junit test running in the ccsv4, so that the junit test could lauch another ccs debug session to debug a target.

Br,

AppleCat

Hi, Darian,

              Yes,  when I am using the following code, and I set a breakpoint after openning another CCSSession, another CCS4 will start , and then I choose another workspace. However, when I continue to run the java code, the newly-lauched CCV4 shows nothing at all !!! Am I missing some necessary configurations?

Best regards,

AppleCat

     ScriptingEnvironment env = ScriptingEnvironment.instance();
     
      DebugServer debugServer = null;
      DebugSession debugSession = null;
     
      env.getServer("CCSServer.1").openSession("C64xp Megamodule Cycle Accurate Simulator, Little Endian/TMS320C64+");

      // Create a log file in the current directory to log script execution
      env.traceBegin("BreakpointsTestLog.xml", "DefaultStylesheet.xsl");

//       Set our TimeOut
      env.setScriptTimeout(15000);

//       Log everything
      env.traceSetConsoleLevel(TraceLevel.ALL);
      env.traceSetFileLevel(TraceLevel.ALL);
     
        debugServer = (DebugServer ) env.getServer("DebugServer.1");

        debugServer.setConfig("tisim_c64xple.ccxml"); // You always need to specify a target configuration with DSS

        debugSession = debugServer.openSession("C64xp Megamodule Cycle Accurate Simulator, Little Endian/TMS320C64+");

Hi, Ki,

            Yes, I am using Eclise as my debugger of the junit, but I still could not repeat in Eclise what the rhino debugger could do. I am confused by the difference between CCSServer/CCSSesion and DebugServer/DebugSession.

Best regards,

AppleCat

Hi, Darian,

        Great thanks to you.  It works the same as what  you mention in your paper.

        Thank both Darian and Ki. After fixing this problem, I can set out my program unit test now.

Br,

Apple

Hi, Darian,

         Thanks a lot.  Unfortunately, according to the post, I have to manually launch the debugssion in the new launched CCSServer.

         I am wondering, whether there is a method  to automate the lauch of a specific debug session whenever the new CCSv4 server is launched.

         Glad to hear your advice.

Br,

AppleCat

You can create a script call autoLaunch.js and place it in <install dir>\CCS4.0.0.16000\ccsv4\common\IDE\scriptingConsole\scripts, if these folders doesn't exist, than create them.

Enter this line into your script, "launchTIDebugger();". Open the scripting console, shutdown the IDE without closing the scripting console. Than the next time you startup the IDE, launch TI debugger will be call automatic for you.

Hope this help.

Regards,
Patrick

Hi, Patrick, sincere thanks for this trick.  It works and helps, except that

Initializing ................................................................................................................................................................................................................................................

TIMEOUT: failed to initialize scripts, try to increase timeout value by setting the environment variable SCRIPTING_CONSOLE_INIT_TIMEOUT to a larger value, in millisecond, and restart.

ReferenceError: "loadJSFile_InternalCmd" is not defined

Although the above TIMEOUT ERROR occurs, a debug session is also lauched after as the start-up is completed.

I think, the "loading device information..." consumes a lot of time.

You are correct, loading the device info blocks the script to launch the debug session.

You can set the system enviornment variable to a larger number to prevent the time out to occur.

No, disabling the list of plugin in your screenshot won't help the load time of the device info. It is parsing a bunch of target database xml files.

Hi, Patrick,

        Any advice to reduce the "loading-device information" time? Should I uninstall the following "rectangled" configurations

?

Hi, Patrick,

  I found a way to reduce the device information loading time,

Browser to %install_dir%ccsv4\common\targetdb\

remove all the unnecessary target files (ie. .xml)  from the following folders,

boarddat

boards

configurations

cpus

Devices