Keil Logo

DS-MDK: Configuring ARM Compiler Version


Information in this knowledgebase article applies to:

  • DS-MDK 5.24

SYMPTOM

In an imported project, an instance of DS-MDK cannot find compiler version from MDK-Pro. A build returns the following error:

**** Build of configuration Debug for project <<project_name>> ****

Toolchain required to build project is not registered: ARM Compiler X.XX

CAUSE

Imported project was created with a particular toolchain. The toolchain has not been added yet to DS-MDK environment.

RESOLUTION

Add a toolchain to DS-MDK. Go to Windows => Preferences => DS-MDK => Toolchains => Add. Specify the installation of MDK to /ARM/ARMCC or /ARM/ARMCLANG. You can review release notes for specific versions to find the corresponding compiler version. If the compiler has a special name, the next screen will allow it to be entered. Otherwise, a standard name is automatically generated. Click "Finish", then "Apply". Click "Restart Eclipse".

WARNING: The next step, changing or resetting the compiler version, loses the configuration options for the build tools. Backup the project if you are editing a custom project. Imported projects can be recopied from the CMSIS Pack Manager; this will recover configuration options.

In Project Explorer, select the project or a source file in the project, then go to Project => Properties => C/C++ Build => Tool Chain Editor. If enabled, disable "Display compatible toolchains only". Now, select (or re-select) the newly-added compiler version.

Load the backup project or recopy project from CMSIS Pack Manager to regain build tool configurations. Then build. If using a Flex license, and build is unsuccessful, it may contain the following error:

XX:XX:XX **** Incremental Build of configuration Debug for project <<project_name>> ****
make all
'Building file: ...
'Invoking: ARM ...'
...
Error: X9555E: Failed to check out a license.Cannot find license file.
 The license files (or license server system network addresses) attempted are
listed below.  Use LM_LICENSE_FILE to use a different license file,
 or contact your software provider for a license file.
Feature:       mdk_pro_compiler5
Filename:      c:\program files\arm\licenses\license.dat
License path:  C:\Users\XXXXXXXXX\AppData\Roaming\ARM\DS-5\licenses\*.lic;
               c:\program files\arm\licenses\license.dat;
FlexNet Licensing error:-1,359.  System Error: 2 "No such file or directory"
...
 - LM_LICENSE_FILE: unset
 - ARM_TOOL_VARIANT: 'mdk_pro_flex'
 - ARM_PRODUCT_PATH: 'C:\Keil_v5\ARM\sw\mappings'

Notice that license path does not contain "port@server" string, and LM_LICENSE_FILE is unset.

If using an MDK-Professional, Flex license, go to Project => Properties => C/C++ Build => Environment. Add variable LM_LICENSE_FILE and set its value to equal "port@server" string from MDK's License Management dialog. Enable "Add to all configurations", click "OK". Click "Apply" and "OK". The project should now be able to find the license and use the build tools.

If using a 7-day trial of MDK-Professional, check the file, TOOLS.INI. From the MDK installation, the file should contain lines that match the description at the bottom of knowledgebase article: ARMCC: 7 day MDK Professional Evaluation generates error C9593E.

MORE INFORMATION

Last Reviewed: Wednesday, August 3, 2016


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.