Port nrf52840 based application into SES or Keil build environment for maintainability, debugging and better user experience reasons.

Hello,

My current project is using an BLE application with:

  • nRF52840 which seems to be an evolution of the relay example.
  • based on nrf5 SDK 16.0.0
  • built under Maxim Integrated environment which is not maintainable anymore (still uses make files though).
  • and without any debugging facility! 

Before I proceed with adding new features, I would like to port the entire solution to:

  1. SES or KEIL
  2. Using latest nrf5 SDK (but not essential)
  3. And support debugging using one of the IDE's mentioned above.

Do you have any guideline which might help me?

Regards

George

  • Hi George,

    The preferred SDK for the recent releases of the nRF5 SDK is Segger Embedded Studio (SES), which is also free to use with Nordic Devices. You can obtain your free license here. So I would recommend that you port your application to SES.

    There is no good automatic or straight-forward way to take a project form a different toolchain or IDE and port it to a Segger Embedded Studio project for the nRF5 SDK, so what I would do is to find a nRF5 SDK example project that is somewhat similar to your project (particularily, if you use a SoftDevice, pick an example project that also use a SoftDevice). Then port things gradually, adding configurations, files and include paths as you see from your existing project.

    Migrating from SDK 16 to 17.1.0 could also be doen in the same way. You may want to do this in one go, or if you first migrate to a SES project in SDK 16 I would suggest looking at the same example project in SDK 16 and 17.1.0 to see the differences, and adjust your SDK 16 project file for what is needed for SDK 17. The simplest here is often to work with the SES project files in a text editor, as it is XML that it is OK to work with, and finding things there is often faster/simpler than in the GUI if you are not familiar with it.

    Debugging works out of the box with both SES and Keil. But it make sense to make a special debug build without optimizations, and perhaps with some additional defines set that has meaning in the SDK (like DEBUG). You will see that most SES projects in the SDK has two build configurations, release and debug. The difference there is the optimization and some defines for the debug variant.

    Einar

  • Hi Einar,

    Many thanks for coming back to me. I will follow your advice.

    Regards

    George

Related