FreeRTOS compilation failure

[sushmasan]

Hello Team,

I am trying to build FreeRTOS module using MCUXpresso IDE, but the build is failing.

All the respective header files exist in the stack. The header file path is set in the includes.

"portmacrocommon.h" is already present in this path "freertos\freertos-kernel\portable\GCC\ARM_CM33_NTZ\non_secure"

Please find the snapshots below for your reference.

Can someone please let us know, what is still missing?

[sushmasan]

Finally, I was able to compile the FreeRTOS component.

[Harry_Zhang]

Hi @sushmasan 

Sometimes, using relative paths can cause issues. As a test, try adding the absolute path to the non_secure folder containing portmacrocommon.h directly in your project settings to rule out any issues with relative paths.

If your problem has not been resolved, can you share your project？

BR

Hang

[sushmasan]

Hi @Harry_Zhang ,

I set the complete the filesystem path, but still I am getting the same error.

Please find the attached my project.

Regards,

San

[Harry_Zhang]

Hi @sushmasan 

I import your project into my MCUXpresso IDE, and i haven't made any changes,

I compiled without any errors.

So I suggest you delete this workspace and create a new one.

BR

Hang

[sushmasan]

Hi @Harry_Zhang ,

I am seeing few changes in your code, but you mentioned my workspace was directly imported and built without any issues.

Can you please share the workspace you created just to make sure?

One more thing, while creating the workspace for FreeRTOS, what are all the components you picked from SDK, in order to build it without errors?

Regards,
San

[Harry_Zhang]

Hi @sushmasan 

I mean that change the MCUxpresso workspace, not the workspace for FreeRTOS.

When you open the MCUXpresso, It will prompt you to choose a workspace.

You can create a new workspace.

BR

Hang

[andrewsglenn]

What happens if you set the path in the Includes tab of "Properties->C/C++ General->Paths and Symbols" ?

[sushmasan]

Even after setting the path in this location, still there is no change in the behavior, I am getting the same error.

[sushmasan]

Hello Team,

Can someone please check this error?

Regards,

San