KV30F64 wrong MCUXpresso symbols

[steverhodes]

I'm using "MCUXpresso IDE v10.1.0 [Build 589] [2017-11-14] " with a MKV30F64xxx10 selected as the MCU. The C/C++ General>Paths and Symbols>Symbols tab shows __ARM_ARCH = 4 and __ARM_ARCH_4T__ = 1. Cortex-M4 core is ARMv7E-M, and the lack of symbol __ARM_ARCH_7EM__ is keeping me from accessing the BASEPRI register using CMSIS functions. I've added __ARM_ARCH_7EM__ and removed __ARM_ARCH_4T__ to solve the immediate problem, but what else should be changed?

[steverhodes]

The attached project has MKV30F64xxx10 selected as the MCU, but C/C++ General>Paths and Symbols>Symbols tab shows __ARM_ARCH = 4 and __ARM_ARCH_4T__ = 1. Cortex-M4 core is ARMv7E-M, so the symbols don't match the processor core. This prevents access to some M4 features via the SDK, and might have other optimization side effects, I guess.

[steverhodes]

Just a fresh, new MKV30F64xxx10 C-project created in MCUXpresso has the wrong symbols. I'm nervous to change the symbols because I don't know the side effects, but I'd like the right ones so I get the full value of the Cortex-M4 core. I'd send the zipped project if I knew how to attach one, or if the reply to Jennie's email didn't bounce.

Thanks for your help,

Steve.

[ZhangJennie]

Hi Steve,

Please enable "Use advanced editor" after clicking on Reply button.

Then you will see Attach button at the bottom left of the text field.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[ivekengineer]

I also want to access some of the intrinsic functions of the CM7 core (KV5 device) - especially the multiply/accumulate instructions.  In the "cmsis_gcc.h" file it looks like the __ARM_FEATURE_DSP needs to be defined to 1 as well (line 1539).  Based on the comment to the right of that line, it looks like it will change in a future version to pre-process this section of code based on architecture instead.  I really don't want to modify these things manually, however, since they are controlled by NXP (and CMSIS), and I may not fully understand the implications of changing these.  It would be great if NXP could comment on whether adding these symbols to the list mentioned above is sufficient to access these CMSIS intrinsics.

[ZhangJennie]

Hi Steve.

Basically I understand your questions.

Could you please send me a demo project regarding "lack of symbol __ARM_ARCH_7EM__ is keeping me from accessing the BASEPRI register using CMSIS functions."

I will check it from my side.
Thanks.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------