- This topic has 0 replies, 1 voice, and was last updated 1 month, 2 weeks ago by
Logan Moon.
-
AuthorPosts
-
February 6, 2025 at 10:29 pm #16831
(This message was transferred over from our old forum)
Posted August 19, 2015
By Todd DeBoer
[hr]
On 10/5/11 jwhatle asked, “Error[Pe147]: declaration is incompatible with “__interwork __softfp unsigned long __STREXB(unsigned char, unsigned char *)” (declared at line 181 of “C:\\Program Files\\IAR Systems\\ C:\\Users\\jwhatle\\Desktop\\NXP_erWin\\uEZ_v1.11_sourceold\\uEZ_SRC v1.11\\Source\\Processor\\NXP\\LPC1788\\IAR\\include\\CMSIS\\core_cm3.h 1187Happens for a bunch of functions. Unmodified source/project information.”
[hr]
(Follow up post)Answered:
I found the solution, this way pls: https://supp.iar.com/FilesPublic/UPDINFO … m.ENU.html
Or in the text:
A special note on CMSIS integration:
If your application source code include CMSIS header files explicitly, then you should not check the Use CMSIS check-box Project>Options…>General Options>Library Configuration>Use CMSIS. Some of the Cortex-M application examples includes CMSIS source files explicitly, do not check the said check-box in these projects.
However, due to the evolution of the IAR C/C++ Compiler for ARM, older versions of CMSIS are incompatible with the current version of the compiler. One simple example of how to solve this issue is:
a) Press F4 to bring up the erroneous source (header) file in the editor – in most cases named core_cm3.h.
b) Right-click on the window tab of that editor window, choose File Properties….
c) Add (or remove) any character to the file name – so the compiler won’t find it any more.
d) Modify project options: Check Project>Options…>General Options>Library Configuration>Use CMSIS.
Steps a) to c) might need to be done for more than one file. Normally, the names of these files are core_cm0.h, core_cm3.h, core_cm4.h, core_cmFunc.h and core_cmInstr.h.For more information about CMSIS integration in the IAR Embedded Workbench for ARM, see the Development guide
-
AuthorPosts
- You must be logged in to reply to this topic.