Quesitons to softdevice and app version

[Bjoern Gutgesell]

hello again,

i spent the last three days on the theme dfu, bl, app, sd. Now there are some questions I can't answer me with reading.

Question 1) Does a new app works (envired with sdk16) on an old sd with sdk15? Or: If we change the release of sdk (same from 15.2 to 15.3, from 15.3 to 16 and so on) is it necessary to change the softdevice on the dk's or custom designs/pcb too? Change only sd, if we use new features? Or every time change sd, because of new entrypoints of functions?

We work with segger embedded studio and programm our dk's/pcb with jlink and. Erase the target with [Target][connect jlink], then [Target][Erase All]. The first time wie program the target [F5], the softdevice is programed automtically.

Question 2) Where are the dependencies between Segger-Embedded-Studio, properties and the real "s140_nrf52_7.0.1_softdevice.hex" (start at 0x00000, end at 0x26590) on the filesystem. In the project-properties-Preprocessor-Definitions there is only a refer to S140 but not to a file (hex-file). In my project output-Hex file is only the app (start at 0x27000, end at 0x2db30 , no sd. How does Segger-Linker and Jlnk now what file or where the file of the sd is? Hardlinked?

Best regards

Bjoern

[Einar Thorsrud]

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.

[Bjoern Gutgesell]

hi Einar,

thanks for reply, this solves my questions.

best regards

Bjoern