• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1574 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Headless build is failing

David Aldrich92784
Genius 3720 points
Other Parts Discussed in Thread: TCI6638K2K

Hi

I am running CCS 5.4.  I want to do a headless build so I run the following command:

C:\ti\ccsv5\eclipse>eclipsec -noSplash -data "c:\users\daldrich\workspace_Osiris_trunk" -application com.ti.ccstudio.apps.projectBuild -ccs.projects Osiris2_K2KCoreA -ccs.configuration Debug


Eclipsec shows an error message box telling me to look at .metadata\.log, which contains:

!SESSION 2014-02-05 15:28:11.945 -----------------------------------------------
eclipse.buildId=M20120914-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Framework arguments:  –noSplash -application com.ti.ccstudio.apps.projectBuild -ccs.projects Osiris2_K2KCoreA -ccs.configuration Debug
Command-line arguments:  -os win32 -ws win32 -arch x86 –noSplash -data c:\users\daldrich\workspace_Osiris_trunk -application com.ti.ccstudio.apps.projectBuild -ccs.projects Osiris2_K2KCoreA -ccs.configuration Debug

!ENTRY org.eclipse.osgi 4 0 2014-02-05 15:28:15.482
!MESSAGE Application error
!STACK 1
java.lang.ExceptionInInitializerError
	at org.eclipse.rtsc.xdctools.ui.utils.XDCUtils.getRtscPackageRepositories(Unknown Source)
	at org.eclipse.rtsc.xdctools.ui.RTSCUtilsServer2.getRTSCPackageRepositories(Unknown Source)
	at org.eclipse.rtsc.xdctools.managedbuild.core.RTSCServer.getPackageRepositories(RTSCServer.java:181)


Please can you explain how to fix this problem?

Best regards

David

  • 0
    TI__Guru**** 451311 points

    Hi David,

    Can you provide more details about your project? Does it use SYS/BIOS?

    Also, there were a few bug fixes made to command-line builds in CCSv5.5 if you are willing to update your CCS version. It may address your particular issue (don't know for sure). Unfortunately I think incremental updates are disabled for CCSv5.5 so you may have to do a whole new install which I know is a pain. One thing I can say is that CCSv5.5 is pretty much the last of the CCS updates for v5 so once you get to CCSv5.5, there will not be any more patches for it (there will be no v5.6)

    ki

  • 0 in reply to Ki
    Genius 3720 points

    Hi Ki

    Thanks for your reply.  Yes, my project does use Sys/Bios 6.

    As you suggested, I am now trying CCS 5.5 instead of 5.4, but am now facing a problem of building the project with the GUI.

    My target is a Keystone2 device: TCI6638K2K

    When I installed CCS 5.5 I selected 'C6000 Multicore DSPs'.  I have also installed:

     - MCSDK 3.0.3.15

     - Keystone2 emupack 1.0.0.4

    When I build (using the GUI) I see error:

    This project was created for a device that is not currently recognized: TMS320C66XX.TCI6638. Please install the device descriptor, or migrate the project to the closest match from the supported devices by adjusting project properties.

    Also, I noticed that, in Project Properties, all the paths specified for --xdcpath have disappeared.

    Do I need to rebuild my custome platform and re-enter the path to the platform?

    Do you have any suggestions please?

    BR

    David

  • 0 in reply to David Aldrich92784
    TI__Guru**** 451311 points

    David Aldrich92784 said:
    This project was created for a device that is not currently recognized: TMS320C66XX.TCI6638. Please install the device descriptor, or migrate the project to the closest match from the supported devices by adjusting project properties.

    Can you attach the .ccsproject file in your project folder?

  • 0 in reply to Ki
    Genius 3720 points

    Hi Ki

    I changed the device type from TCI6638 to TCI6638K2K using CCS5.4.  The projects then imported correctly into CCS5.5.

    The command line build is now working correctly for me under CCS5.5.  So that is all good news.

    My final problem is to run the command line builds as a Jenkins job ( you may know that Jenkins is a continuous integeration tool ).  Another E2E thread discusses this:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/207668.aspx

    It seems that that approach can fail because the Jenkins user is unable to create a display as it does not have its own open X session.

    That thread doesn't give a clear solution.  Do you have any knowledge of how to fix this problem please?

    Best regards

    David

  • 0 in reply to David Aldrich92784
    TI__Guru**** 451311 points

    David Aldrich92784 said:
    The command line build is now working correctly for me under CCS5.5.  So that is all good news.

    That is good

    David Aldrich92784 said:

    It seems that that approach can fail because the Jenkins user is unable to create a display as it does not have its own open X session.

    That thread doesn't give a clear solution.  Do you have any knowledge of how to fix this problem please?

    I don't have much knowledge of this. I'll see if I can find someone who is experienced with jenkins.

    Thanks

    ki

  • 0 in reply to Ki
    Genius 3720 points

    Hi Ki

    Actually, the CCS headless build is running fine under Jenkins.  From other threads it seems that the issues were resolved in CCS 5.3 and I am running 5.5. 

    So let's close this thread. I'll open another if I find other issues with this topic. Thanks for your help.

    David

  • 0 in reply to David Aldrich92784
    TI__Guru**** 451311 points

    Good to hear. Thanks for the update.

    ki