BareMetal or FreeRTOS: conflicting definitions?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

BareMetal or FreeRTOS: conflicting definitions?

Jump to solution
1,985 Views
davenadler
Senior Contributor I

MCUXpresso 11.1 on Windows 10, Kinetis K64F, using CMSIS DSP.
With MCUXpresso, I created a new FreeRTOS project.

The generated .cproject contains the following definitions:

FSL_RTOS_BM
FSL_RTOS_FREE_RTOS
SDK_OS_BAREMETAL
SDK_OS_FREE_RTOS

Why are FSL/SDK definitions set to indicate both bare metal and FreeRTOS?

Thanks!
Best Regards, Dave

Tags (1)
0 Kudos
Reply
1 Solution
1,880 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi Dave:

Some components like USB, LwIP, AWS, littlevgl,  they are designed to work both in RTOS mode and Bare metal mode.  That is why we need to keep these macros.

I would  recommend you keep FSL_RTOS_BM and SDK_OS_BAREMETAL or

FSL_RTOS_FREE_RTOS/SDK_OS_FREE_RTOS according to your project.  Remove the wrong macros

Regards

Daniel

View solution in original post

3 Replies
1,880 Views
davenadler
Senior Contributor I

@Daniel Chen - Can you tell me:

  1. What is the purpose of these defines?
  2. They do not seem to be referenced in my project - should I remove them?

Thanks,
Best Regards, Dave

0 Kudos
Reply
1,881 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi Dave:

Some components like USB, LwIP, AWS, littlevgl,  they are designed to work both in RTOS mode and Bare metal mode.  That is why we need to keep these macros.

I would  recommend you keep FSL_RTOS_BM and SDK_OS_BAREMETAL or

FSL_RTOS_FREE_RTOS/SDK_OS_FREE_RTOS according to your project.  Remove the wrong macros

Regards

Daniel

1,880 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi Dave:

Thank you very much for your feedback, this is an issue. I have created a ticket for this.

Regards

Daniel