CCES Launch issue

Hi,

Thank you for your inquiry.

Could you please provide the below details to assist you further on this issue.

1. Are you using the CCES Console program (ccesc.exe) or the CCES Runner (CCES_runner.exe)?

2.Is this the first time you are facing this issue, or have you encountered it before?

3.If possible, please share us the example project and python scripts along with the steps to reproduce the issue here. This would be helpful for us to assist you further.

Awaiting for your reply.

Regards,
Santhakumari.V

Thank you for the previous reply. Answers to your questions are as below.

The project is based on ADSP SC 589 wherein each core is built separately. So in generating the exe file as we need all three core dxes, during automation cces will be launched, project is built and cces is closed in the automation process. This happens three times as we three cores for generating one exe file. This process repeats for generating the multiple exe files with minor tweaks in code. So in this process randomly we are getting the exit code.

1. Are you using the CCES Console program (ccesc.exe) or the CCES Runner (CCES_runner.exe)?

Ans : I am using ccces.exe to run the command, I am trying to run eclipse-based commands through python

2.Is this the first time you are facing this issue, or have you encountered it before?

Ans: I have faced the error before when I am running multiple times

3.If possible, please share us the example project and python scripts along with the steps to reproduce the issue here. This would be helpful for us to assist you further\

Ans: The code cannot be shared but the python command that I am using to build the project is as follows

start "" "C:\Analog Devices\CrossCore Embedded Studio 2.12.1\Eclipse\cces.exe" -data "C:\Users" -application org.eclipse.cdt.managedbuilder.core.headlessbuild -import "C:\project" -cleanBuild "project"

Regards

BVS

Hi,

For CCES automation we usually recommend headless builder(ccesc.exe) for building and CCES Runner (CCES_runner.exe) for running the program.

Please refer the below FAQ to Build and Run using the Command line for Automation:

FAQ: Using Blackfin and SHARC from the command line in CrossCore Embedded Studio

https://ez.analog.com/dsp/software-and-development-tools/cces/w/documents/5248/using-blackfin-and-sharc-from-the-command-line-in-crosscore-embedded-studio?queryID=c6e1fc9ef804ccae47dc4729b2fb0eb6&objectId=244359ce-9f37-4972-8117-017a140e2b52&eztype=Docs%20%26%20FAQs

FAQ: Using CrossCore Embedded Studio's CCES Runner Utility
https://ez.analog.com/dsp/software-and-development-tools/cces/w/documents/5263/using-crosscore-embedded-studio-s-cces-runner-utility-audit

Hope this helps.

Regards,
Santhakumari.V

Hi,

For CCES automation we usually recommend headless builder(ccesc.exe) for building and CCES Runner (CCES_runner.exe) for running the program.

Please refer the below FAQ to Build and Run using the Command line for Automation:

FAQ: Using Blackfin and SHARC from the command line in CrossCore Embedded Studio

https://ez.analog.com/dsp/software-and-development-tools/cces/w/documents/5248/using-blackfin-and-sharc-from-the-command-line-in-crosscore-embedded-studio?queryID=c6e1fc9ef804ccae47dc4729b2fb0eb6&objectId=244359ce-9f37-4972-8117-017a140e2b52&eztype=Docs%20%26%20FAQs

FAQ: Using CrossCore Embedded Studio's CCES Runner Utility
https://ez.analog.com/dsp/software-and-development-tools/cces/w/documents/5263/using-crosscore-embedded-studio-s-cces-runner-utility-audit

Hope this helps.

Regards,
Santhakumari.V