This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Import FreeRTOS to project BLE mesh have library duplicate name problem

Hello everyone

Now i am trying to import Freertos to my project BLE mesh in SEGGER studio. However, it had library name duplicate and i dont know how to solve that problem.

I used BLE mesh SDK:  nrf5_SDK_for_Mesh_v2.1.1.

            and nrf5_SDK:   nRF5_SDK_15.0.0.

In the BLE mesh SDK already had header file:  nrf5_SDK_for_Mesh_v2.1.1_src\mesh\core\include\queue.h 

                                                                           nrf5_SDK_for_Mesh_v2.1.1_src\mesh\core\include\list.h 

and nrf5_SDK freertos also have same that file name and just only differ content inside:  nRF5_SDK_15.0.0_a53641a\external\freertos\source\include\queue.h

                                                                                                                                             nRF5_SDK_15.0.0_a53641a\external\freertos\source\include\list.h

When I add path to user include directories, the compiler always get the wrong header file to another source in dependencies folder.

So pls tell me if you have any ideas. Thank you so much.

Parents
  • That is what I meant. How it will effect the Mesh stack I don't know. I don't know if anyone has tested mesh (our SDK) with FreeRTOS before. You will probably notice that you will have to include some other files as well when the project properly includes the FreeRTOS queue.h and list.h. 

     

    It is not only those two .h files that makes up FreeRTOS. Have you implemented some source code in main that uses the FreeRTOS features? I would suggest that you look at one of the FreeRTOS examples in the regular SDK, and use some parts from there to make Mesh run in a thread, simultaneous to doing some other simple task in another thread.

     

    Best regards,

    Edvin

Reply
  • That is what I meant. How it will effect the Mesh stack I don't know. I don't know if anyone has tested mesh (our SDK) with FreeRTOS before. You will probably notice that you will have to include some other files as well when the project properly includes the FreeRTOS queue.h and list.h. 

     

    It is not only those two .h files that makes up FreeRTOS. Have you implemented some source code in main that uses the FreeRTOS features? I would suggest that you look at one of the FreeRTOS examples in the regular SDK, and use some parts from there to make Mesh run in a thread, simultaneous to doing some other simple task in another thread.

     

    Best regards,

    Edvin

Children
No Data
Related