RE: Quesitons to softdevice and app version

Bjoern Gutgesell — Thu, 09 Jan 2020 16:03:37 GMT

hi Einar,

thanks for reply, this solves my questions.

best regards

Bjoern

RE: Quesitons to softdevice and app version

Einar Thorsrud — Thu, 09 Jan 2020 15:20:20 GMT

Hi,

1. There are API differences between major versions of SoftDevices, so typically they cannot be changed without some effort. Generally, I recomend you stick with the SoftDevice that was shipped with the SDK. You can refer to the compatibility matrix for SDKs and SoftDevices to see more details. In practice, if you migrate your application to a new SDK, you will probably also migrate to a new SoftDevice, and that does usually not provide any issues. You also mention PCB design in this question, and that is not relevant in this context. The reference design is the same regardless of which SoftDevice or SDK you use.

2. Segger Embedded Studio projects can be configured to upload additional .hex files, and that is how the example SDK projects are configured. Looking at <SDK 16>\examples\ble_peripheral\ble_app_hrs\pca10056\s140\ses\ble_app_hrs_pca10056_s140.emProject as an example, you can see that the SoftDevice .hex file is listed as an Additional Load File in the Debug settings:

This file is always loaded together with the application .hex file.