ADSP-BF707
Production
This device is a member of the ADSP-BF70x Blackfin Digital Signal Processor (DSP) product family. The new Blackfin+ processor core combines dual-MAC 16...
Datasheet
ADSP-BF707 on Analog.com
Hi all,
we've been using CrossCore Embedded Studio (CCES) in headless mode by calling ccesc.exe under Windows for quite a while.
For some days we see our builds failing and seeing strange error messages in the build log. Here are three excerpts from real build logs:
---- snip ---- INFO: [buildHeadless.bat] "C:\Analog Devices\CrossCore Embedded Studio 2.10.0\Eclipse\ccesc.exe" -nosplash -application com.analog.crosscore.headlesstools -data <CCES_Workspace> -project <CCES_PROJECT> -cleanBuild "Debug" -regensrc 21:20:15 **** Build of configuration Debug for project <CCES_PROJECT> **** make -j16 all (...) (some ccblkfn compiler call) ccblkfn -c -file-attr ProjectName="<CCES_PROJECT>" -proc ADSP-BF707 (... more flags and switches ...) cc3154: fatal error: Unknown target architecture `ADSP-BF707' [Error ea1184] "command-line":1 The assembler was unable to locate the following .xml file: 'C:\Analog Devices\CrossCore Embedded Studio 2.10.0\System\ArchDef\ADSP-BF707-compiler.xml'. Or the file might be corrupted. Check the -proc option on the command-line and the contents of the .xml file. [Warning ea1142] Unrecognized silicon revision 1.1 specified, supported revisions are: . Reverting to . [Error ea1156] A valid license is required but could not be found. A licensing error has occurred. Error Code: -5.357 Feature: ASSEMBLER- Description: No such feature exists. (-5,357) Context: Unknown make: *** [somefile.doj] Error 1 make: *** Waiting for unfinished jobs.... [Errcc3089: fatal error: Assembler failed (code:1) or ea1184] "command-line":1 The assembler was unable to locate the following .xml file: 'C:\Analog Devices\CrossCore Embedded Studio 2.10.0\System\ArchDef\ADSP-BF707-compiler.xml'. Or the file might be corrupted. Check the -proc option on the command-line and the contents of the .xml file. [Warning ea1142] Unrecognized silicon revision 1.1 specified, supported revisions are: . Reverting to . [Error ea1156] A valid license is required but could not be found. A licensing error has occurred. Error Code: -5.357 Feature: ASSEMBLER- Description: No such feature exists. (-5,357) Context: Unknown make: *** [....doj] Error 1 cc3089: fatal error: Assembler failed (code:1) make: *** [system/drivers/sport/adi_sport.doj] Error 1 ' ' 'Finished building: ../system/adi_initialize.c' ---- snip ----
---- snip ---- cc3154: fatal error: Unknown target architecture `ADSP-BF707' (some ccblkfn compiler call) [Error ea1184] "command-line":1 The assembler was unable to locate the following .xml file: 'C:\Analog Devices\CrossCore Embedded Studio 2.10.0\System\ArchDef\ADSP-BF707-compiler.xml'. Or the file might be corrupted. Check the -proc option on the command-line and the contents of the .xml file. [Warning ea1142] Unrecognized silicon revision 1.1 specified, supported revisions are: . Reverting to . [Error ea1156] A valid license is required but could not be found. A licensing error has occurred. Error Code: -5.357 Feature: ASSEMBLER- Description: No such feature exists. (-5,357) Context: Unknown cc3154: fatal error: Unknown target architecture `ADSP-BF707' (some ccblkfn compiler call) cc3154: fatal error: Unknown target architecture `ADSP-BF707' A valid license is required but could not be found. A licensing error has occurred. Error Code: -5.357 Feature: COMPILER- Description: No such feature exists. (-5,357) Context: Unknown cc1458: Catastrophic error: could not obtain license 1 catastrophic error detected in the compilation of "..\system\startup_ldf\app_cplbtab.c". Compilation terminated. cc3089: fatal error: Compilation failed (code:4) (some ccblkfn compiler call) A valid license is required but could not be found. A licensing error has occurred. (some ccblkfn compiler call) Error Code: -5.357 Feature: COMPILER- Description: No such feature exists. (-5,357) Context: Unknown cc1458: Catastrophic error: could not obtain license 1 catastrophic error detected in the compilation of "..\system\startup_ldf\app_handler_table.c". Compilation terminated. cc3154: fatal error: Unknown target architecture `ADSP-BF707' cc3089: fatal error: Compilation failed (code:4) ---- snip ----
---- snip ---- INFO: [buildHeadless.bat] "C:\Analog Devices\CrossCore Embedded Studio 2.10.0\Eclipse\ccesc.exe" -nosplash -application com.analog.crosscore.headlesstools -data <CCES_Workspace> -project <CCES_PROJECT> -cleanBuild "Debug" -regensrc 06 Okt 12:34:54, 001 [Thread: Worker-4: Checking Add-in status of project <CCES_PROJECT>] ERROR com.analog.crosscore.system.components (Component.java:304) - Invalid Add-in version: 06 Okt 12:34:54, 223 [Thread: Worker-0: Checking Add-in link paths/build variables and upgrading Add-ins in project: <CCES_PROJECT>] ERROR com.analog.crosscore.system.components (Component.java:304) - Invalid Add-in version: 06 Okt 12:34:54, 227 [Thread: Worker-0: Checking Add-in link paths/build variables and upgrading Add-ins in project: <CCES_PROJECT>] ERROR com.analog.crosscore.system.components (Component.java:304) - Invalid Add-in version: 06 Okt 12:34:54, 229 [Thread: Worker-0: Checking Add-in link paths/build variables and upgrading Add-ins in project: <CCES_PROJECT>] WARN com.analog.crosscore.system.components.ui (ComponentHealthMonitor.java:372) - Add-in "SPI Driver Base for Blackfin (-1.-1.-1.-1)" installed in project "<CCES_PROJECT>" is NOT found. ---- snip ----
I think the first two snippets are related. We see a variety of errors:
I do not see why silicon revision or target architecture should be unknown or the XML file is not detected. The XML file seems to be fine and the DSP/architecture related values have been known during previous (and more recent) build runs.
I am not sure if this is caused by a license error (appearing in the middle of the build logs). But I've double checked the license.dat file on the machine and it is also perfectly fine to me and matches my local one.
Do you have an idea what could trigger this chain of errors?
For the third snippert: I do not understand why the add-in is unable to read the proper version number and outputs "(-1.-1.-1.-1)" instead. The system.svc file mentions versions "1.0.0" for all SSLDD add-ins, the .cproject file contains several tags *-service-version with a value of "1.0".
I am happy for any feedback & ideas.
Best regards,
Matthias
Hello Mattias,
We’re trying to reproduce the problem that you’ve encountered. But we are unable to simulate and can't find exact scenario or causes. If you could provide more information regarding this issues that you’re experiencing, it would be helpful for us to proceed further.
From your code snippet, we could see that you are trying to use scripting to compile the project using CCES Headless tool.
1. Could you please send an example command line used in CCES headless tool and scripting file, so that we can verify the options you are using to build the project.
2. When you are building from a command line, what terminal are you using? Is this through Command Prompt, a Cygwin Bash shell or other? And is the shell being run as Administrator or a normal user.
3. Please confirm whether you are facing problem when using only with parallel build "make -j16 all", could you please try to run the script without using this "make -j16 all" option and please confirm whether you are facing the same issue.
4. Please try to use only "make -j4" and "make -j16", please confirm whether you are facing same issue.
5. Please confirm whether you are facing same licensing, assembler issue with CCES IDE using parallel build option "make -j16 all"
6. Please share us the exact steps you have followed with the screenshot to replicates this issue in our end.
Regarding for the third snippet>>
We have already locked this issue in our database which will be fixed in future release of CCES.
Additionally, could you please provide the below details to assist you further on licensing issue.
1.License.dat file from C:\ProgramData\Analog Devices\CrossCore Embedded Studio
2.Screenshot of the manage license page(CCES help -> Manage License).
3.Copy the license report in a notepad (CCES Help -> Manage Licenses -> Report) and send it to us.
4.Screenshot of the command prompt window after running the ipconfig/all command
5. Operating system you are using.
For licensing queries, support we can offer may be limited here - Please contact private support through the link below:
https://www.analog.com/support
Or you can email to Processor Tools Support through: processor.tools.support@analog.com
Please make sure to add the link of this EZone thread while contacting private support.
Regards,
Santhakumari.K
Hi Santhakumari,
thank you for your answer and sorry for the delayed response.
1. The core of our headless build is the following call:
"%CCES_HOME%\Eclipse\ccesc.exe" -nosplash -application com.analog.crosscore.headlesstools -data %CCES_WORKSPACE% -project "%PROJECT_DIR%" -cleanBuild "Debug" -regensrc
2. We are using Windows default command prompt. The shell is being run as a Jenkins service user on our Windows server.
I haven't had the time to play around with the "-j" parameter for parallel builds so far.
If this issue is related to running out of licenses - is there a way to see what machine and what user the set of licenses are being used by?
Best regards
Matthias
Hi Matthias,
We understand that you have already contacted our private support. To avoid duplication of efforts, please continue the discussion there.
Best Regards,
Santhakumari.K