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.

does a custom bleUserConfig.h also need to go into stack?

I have created a custom bleUserConfig.h to setup my BLE front end configuration according to our board layout (single ended, internal bias, etc). I have added the location of this custom header to the include path in CCS and the app seems to build fine with it. 

My question is if this header also need to be used by the stack or does the stack not need to know about this?

Thanks.

  • Hello,

    Based on section 5.7 of the software developer's guide, I believe that it only needs to be included in the application, and then is passed down to the BLE protocol stack at initialization.
  • Thank you. Reading this section indeed does clarify that.

    What confused me was that the stack project includes bleUserConfig.c. which includes bleUserConfig.h, so i was just wondering which one it should include. Looks like it's ok to include the default one, as any customizations are going to overwrite it at runtime.

    Strangely, i set the stack's include path to pick up my custom .h first, but does doesn't seem to do so.