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.

command line scripting DebugServer

xp sp3, c6748, ccs5.2.0.00069

I am trying to run a program through the command scripting engine.  It used to run in ccs5.0.x.xxxxx.  But now it hangs up. I have attached the partial log file from the .metadata folder.  The last entry says, "Connecting to XPCOM DebugServer". Then nothing. Apparently it is not statring and I cannot find out why.

  • Hi Kurt,

    do you have a v5 license?  If so what type?  If this is not a scripting error, then it is potentially a license issue.  5.0.x works with a v4 license, v5 does not.

    Please keep us informed.

    Best Regards,

    Lisa

  • Yes I have a v5 license. As I said, "It used to run in ccs5.0.x.xxxxx"  It does not run now after I updated to 5.2. I don't kno9w when it stopped running as I have not tried it for a couple months.  Now I need to get it working.

    A clue?  In the eclipse log I found a couple of error entries with a time stamp matching the lockup - note the last two entries with a time stamp of 07:25:07 - 7:25 is the time stamp of the last timestampe of any file updated in my workspace. The .ccsproject files really do exist but are read-only as these are extracted from version control at run time from. I do not understadn why the DebugServer cares about Nanoscan2 and Unity as the project I am running is UnitTests.

    Another clue? The DebugServer locks up when running under the TFS Build system which is running under the SYSTEM account. This should actually give it more privileges. Maybe there is some connection to the user name in the licensing?

  • Changed my procedure to make the previously offending .ccproject files writable. It appears to go farther in some ways but we are still stuck waiting for DebugServer to startup.

    Attached is a much lengthier .log file that describes some kind of eclipse thread that is stalled and timing out.  Could this be the problem?

     

  • Kurt,

    1. are you able to start a debug session for that ccxml file from within the GUI? I would guess yes but I just want to confirm

    2. how are you calling your DSS script? Are you using the dss.bat file provided by the CCS install or are you doing something on your own (perhaps a modified dss.bat from your old CCS install)

    Thanks

    ki

  • 1) Yes, the program runs fine in CCSv5 with the same ccxml. It was running at one point under CCSv5.1.1.00031 but would not stop when running fom the command line - http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/180427.aspx - I had to work on other projects but am now supposed to get all this working.

    2) I am invoking my DSS script using dss.bat

    cmd /c "%CCS5_INSTALL_ROOT%\ccs_base\scripting\bin\dss.bat" RunUnitTests.js

    I have attached a copy of the js file

  • Just wondering if anyone is looking at this problem

  • Hi Kurt,

    we are at a loss for ideas at the moment.

    The only thing is to go back to my original point ... are you sure you are properly licensed?

    5.0.x works on a different license basis than 5.1 and 5.2 in that 5.0.x accepts a v4 license and the released versions will not.   If you launch CCS do you see that you are licensed?  Were you using a trial license when you changed versions?

    Please confirm your license.  One thing we can then do is potentially generate another trial license for you as necessary to verify this.

    Best Regards,

    Lisa

  • Hi Lisa,

    Sory, I mispoke in one of my posts.  If you read the link I posted you will see that I was using CCSv5.1.1.00031 when I could not get SYS/BIOS to stop running.  Now I think I know how to do that but first I need the DebugServer to start.

    The build occurs under the SYSTEM account.  Is the license somehow tied to the user account?

    Is there any kind of logging I can turn on to find out why DebugServer will not start?

    Kurt

  • Hi Kurt,

    so the problem is only in one account?  Am I understanding correctly, can you confirm?  This may not be a license issue, but possibly windows permission issue. 

    You can find the information on the error logs and enabling them here:

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

    Best Regards,
    Lisa

  • I don't know about the one account. It was running as is in April using 5.1.  Then I put it aside when I couldn't get help.  Since April the only change that I am aware of is CCS changning from 5.1 to 5.2. I do not see any security or application events in the Windows Event Viewer.

    I have attached the Debug Server log.

  • Hi Kurt,

    just to update you we are going to run this by some colleagues and give you any feedback as soon as we have some  A potential next step here is a webex.

    Best Regards,

    Lisa

  • Kurt,

    The log file you attached looks like you went into Help->CCS Support to enable it, then ran the script from the command line.  The Help->CCS Support method only enables logging for the current CCS process, so the log doesn't contain anything from running the script.

    To capture it in the script, start a command prompt and set the following two environment variables:

    set TI_DS_ENABLE_LOGGING=1

    set TI_DS_LOGGING_OUTPUT=c:/temp/or/some/other/valid/path/logfile.log

    then run the script from that open command window and attach the log that it generates.

    Darian

  • Yes, sorry I did not know there was a difference.

    I added your SET statements to DSS.bat as I invoke it using a CMD statement.  Attached is the new DebugServer.log

  • Kurt,

    Can you please modify dss.bat jump over the commands in the "LAUNCH_IDE_SCRIPT" section.  For instance, by adding a "goto LAUNCH_DSS_SCRIPT" on line 19, just before the label.  I'd like to see if that fixes the issue.

    If it doesn't, could you download and run Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645).  Filter out everything but processes named java.exe and eclipsec.exe, then run the script and attach the logged results from processor monitor to this thread.

    Darian

  • Yes, that seems to have fixed it.  Thank you very much!  It has taken many months to get this command line build to run to completion.

    Is this something specific to my setup or is this an error fixed in a future upgrade?

  • Kurt,

    It's something specific to your setup, but I don't know what.  I suggested it only because it was a 5.2 change with how scripting starts, and I had no other ideas on what could have changed.

    If you have some time, I'd appreciate if you could revert the change and run process monitor once.  I'd still like to know why it's not working so that we can ensure it's fixed in future versions.

    Darian

  • OK.  I ran with ProcessMonitor watching until it hung up.  The PML file is 210Mb. Do you have some place where I can deposit this PML file?

  • Kurt, if you send me an email to the address in my profile, I'll send some instructions on where to place this file.

  • > if you send me an email to the address in my profile

    cannot see how to do that