This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCU-PLUS-SDK-AM263X: FreeRtos - error on enabling MPU wrapper in freeRtos

Part Number: MCU-PLUS-SDK-AM263X

Hi Team,

We are facing some compilation error while enabling portUSING_MPU_WRAPPERS in mpu_wrappers.h file. Some structure types are not defined any where and some function prototypes are also miss matched.

  • Hi Karthikeyan,

    In MCU+ SDK the MPU settings are defined agnostic to the kernel outside of the FreeRTOS port. That's why you can't find them in the portmacro.h header file in our port layer. May I know the reason why you want to use the MPU wrappers from inside FreeRTOS?

    Regards,
    Anand Mahadevan SS

  • Hi mahadevan,

    We are planning to protect the whole kernel code and we are planning to use trusted task feature and protected system call(supervisory system call) these features will be enabled only MPU wrappers.

    And safety feature are mandatory for our project and this was throwing compilation error while compiling.

    kindly Can you verify from your side, it was present the Ti official SDK release.

  • In MCU+ SDK the MPU settings are defined agnostic to the kernel outside of the FreeRTOS port.

    It's not clear (to me) why this is a reason for the missing definition. Surely for a specific port nothing should be agnostic and everything should be defined for the target.

    I downloaded FreeRTOS. There are definitions for xMPU_SETTINGS in many of the ports including GCC:

    \FreeRTOS-Kernel\portable\GCC\ARM_CM4_MPU\portmacro.h

    But it is not in this file or any other CCS file:

    \FreeRTOS-Kernel\portable\CCS\ARM_CM4F\portmacro.h

    It indicates that perhaps MPU is yet to be developed for CCS/TI processors.

  • yes, true, we can find definition for CM4, but we were not able to find the definition R5F core.

  • Karthikeyan,

    Let me check with the team internally to understand the history why this was not done. Upon discussion if there are no problems with enabling, we will file an internal issue and close it for the next major release of the SDK depending on the effort involved. Give me a couple of days to get back with the details and timeline for the fix if applicable.

    Regards,
    Anand M

  • Karthikeyan, Kier,

    We can probably take this as a requirement for the next major release of the MCU+ SDK (9.1). Keeping the MPU settings outside was an initial design decision because of the limited MPU entries, from what I can understand. 

    Regards,
    Anand Mahadevan SS