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.

CODECOMPOSER: Problem with command line build

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO

I am trying to build my CCS project via command line and i am facing following issue.
When i try to import the existing project into a new workspace i get the following error:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Importing project from '<path\to\existing\project>'...
Exception in thread "Loading device information" java.lang.NullPointerException
at com.ti.ccstudio.system.setup.SystemSetupReader.<init>(SystemSetupReader.java:2416)
at com.ti.ccstudio.system.setup.SystemSetupWriter.<init>(SystemSetupWriter.java:463)
at com.ti.ccstudio.system.setup.SystemSetupWriter.getInstance(SystemSetupWriter.java:61)
at com.ti.ccstudio.devicemodel.DeviceModelLoader$SetupModelCache.load(DeviceModelLoader.java:328)
at com.ti.ccstudio.devicemodel.DeviceModelLoader.loadRealDevices(DeviceModelLoader.java:1168)
at com.ti.ccstudio.devicemodel.DeviceModelLoader.access$1(DeviceModelLoader.java:1160)
at com.ti.ccstudio.devicemodel.DeviceModelLoader$InitializationJob.run(DeviceModelLoader.java:907)
at com.ti.ccstudio.devicemodel.DeviceModelLoader$InitializationJob$2.run(DeviceModelLoader.java:825)
!ERROR: null
Done!
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I am using the following command:

Fullscreen
1
"C:\ti\ccsv8\eclipse\eclipsec.exe" -noSplash -data <path\to\workspace> -application com.ti.ccstudio.apps.projectImport -ccs.location <path\to\existing\project>
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I am working with CCS 8.3.1 on windows and the project itself is working just fine, i can import it manually inside CCS -> no problem.
It also works when running the command prompt as an administrator, but i need it to work without administrator privileges!

Any ideas why the project import does need admin privileges and/or how to solve it?

EDIT: What i forgot to mention: When starting the CCS GUI, i also the the error message <Exception in thread "Loading Device Information" java.lang.NullPointerException>, but i can just click "OK" and continue with importing the project.

  • Hello Stefan,

    Which processor are you building a project for?

    Regards,

    Nick

  • C6701, and we are using the CGT C6000 Version 5.1.0

  • Ok, to confirm: this is an issue with importing a project, NOT with building the project. You are able to get the import to work properly with the GUI interface in CCS. But you are having trouble importing through the command line?

    I am going to send this over to the CCS team to see if they have any input.

    Regards,

    Nick

  • Yes. Building works just fine both ways (command line and GUI) as long as the project import succeded.
    GUI project import works fine even without admin privileges.
    Command line project import only works WITH admin privileges and i dont get why. What is different between GUI and command line project import?

  • Hello Stefan,

    A few questions:

    What version of Windows are you running? 

    Under what permissions was CCS installed under (admin or user?)?

    Thanks

    ki

  • Hello Ki,

    version is Windows 10 and CCS was installed under my user (with admin privileges).

  • CCS was installed under my user (with admin privileges).

    For the workspace that is being specified, is this a new (clean) workspace or an existing one? If it is an existing one and created via CCS, was CCS running as admin or user at the time?

  • the workspace is a new (clean) one.

  • I found the problem.

    Inside the .metadata folder there is a log file which contained a detailed error

    Fullscreen
    1
    !MESSAGE CommonCorePlugin - failed attempt to get p2 context: Profile not locked due to exception: C:\ti\ccsv8\eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.cpp.profile\.lock (Access is denied)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Allowing the user to modify this .lock file made it work.

    Thanks for your help anyways.

    Cheers

    Stefan

  • Glad to hear you resolved the problem and thank you for sharing your solution!