|
|||||||||||
Technical Support Support Resources
Product Information |
LICENSE: Q9932E MISSING DEVICE (R003) or (R20D) ErrorsInformation in this knowledgebase article applies to:
SYMPTOMThe following post built command fails with this error: After Build - User command #1: C:\Keil_v5\ARM\BIN40\fromelf.exe --bin -o file.bin file.axf ARM FromELF, 4.1 [Build 894] Fatal error: Q9932E: MISSING DEVICE (R003: SECURITY KEY NOT FOUND) Finished: 1 information, 0 warning, 0 error and 1 fatal error messages. "image.axf" - 0 Errors, 0 Warning(s). Or this error: ARM FromELF, 4.1 [Build 894] Fatal error: Q9932E: LICENSE ERROR (R20D: CONTENT ERROR IN FLF FILE) Finished: 1 information, 0 warning, 0 error and 1 fatal error messages. "image.axf" - 0 Errors, 0 Warning(s). CAUSEThis issue occurs after upgrading to a newer version of MDK. A project might run a post build command that points to an old location of a particular tool, for example, the fromelf utility in older versions of MDK (and other ARM compilation tools) were located in the following directory: C:\Keil_v5\ARM\BIN40 In newer versions of MDK the directory layout has changed and tools like fromelf now live in the following directory: C:\Keil_v5\ARM\ARMCC\bin However, one of the main causes of this issue is that some licenses, for example, Cortex-M only licenses, are only recognized in MDK-ARM version 4.60 and later. RESOLUTIONUpdating post build commands to point to the latest version of a particular tool such as fromelf can help to resolve such an issue. It is also recommended to use the latest compilation tools such as the fromelf utility, if possible. MORE INFORMATION
SEE ALSO
Last Reviewed: Thursday, April 12, 2018 | ||||||||||
|
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.