Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Why is CY_CPU_CORTEX_M0P not defined while editing firmware or code in PSoC Creator™ 4.2 for PSoC® 6 as shown in Figure 1?
Figure 1. Undefined CY_CPU_CORTEX_M0P
When Arm® GCC is used as compiler toolchain, CY_CPU_CORTEX_M4 is defined while CY_CPU_CORTEX_M0P is not defined as shown in Figure 1.
If you use Arm MDK as compiler toolchain, then e. CY_CPU_CORTEX_M0Pwill be defined and CY_CPU_CORTEX_M4 will not be defined.
This is a limitation when files are edited in PSoC Creator. The Inline Code diagnostics feature is unable to associate the code with its corresponding core. By default, either Cortex®-M0+ or Cortex-M4 is active based on the selected compiler toolchain.