ARM: MDK-Spansion License Not Working with FMx Devices

Information in this knowledgebase article applies to:

• Keil::FM0plus_DFP 1.2.0 and newer
• Keil::FM3Basic_DFP 1.1.0 and newer
• Keil::FM3HighPerformance_DFP 1.2.0 and newer
• Keil::FM3LowPower_DFP 1.1.0 and newer
• Keil::FM3UltraLowLeak_DFP 1.1.0 and newer
• Keil::FM4_DFP 1.6.0 and newer
• Keil MDK 5 all versions

SYMPTOM

I have activated my MDK installation with an MDK-Spansion (former MDK-Fujitsu) license, which covers the FM0 to FM4 devices. But, when trying to create a new project, I am not able to select any of these devices. Why does the license not work as it should?

CAUSE

Unfortunately, the changes in the pack versions:

• Keil::FM0plus_DFP 1.2.0
• Keil::FM3Basic_DFP 1.1.0
• Keil::FM3HighPerformance_DFP 1.2.0
• Keil::FM3LowPower_DFP 1.1.0
• Keil::FM3UltraLowLeak_DFP 1.1.0
• Keil::FM4_DFP 1.6.0

cause the licensing system in Keil MDK to fail to identify the FMx devices correctly and so they appear as if the license would not support them. As a result, the devices can't be selected. Or, if you have an existing project and updated the DFP recently, the compilation will fail with a message, that the device is not supported by this license.

RESOLUTION

As a workaround, install the respectively previous DFP version, which has not yet been changed in this regard. So with this, the license mechanism correctly identifies the FMx devices as supported and they can be used as expected.

STATUS

The MDK-Spansion edition is as of July 2019 also discontinued and the issue with MDK described here will also not get fixed any more. So, if the most recent DFP version is required, another license type is required to use the FMx devices. In this case, please contact sales or your local distributor for details to find a usable solution.

MORE INFORMATION

• Refer to Packs Dialog in the µVision User's Guide.
• Refer to Setup the Project in the µVision User's Guide.

Last Reviewed: Friday, November 13, 2020