Difference between the various projects within an example in the nRF51 SDKs

[brianreinhold]

There are the following projects under the Health Thermometer example for Keil

What is the difference between them when trying to install on the nRF51 DK? I could not find any documentation or read me describing what these are for.

Which should I use when I desperately want to get something to work on the DK? So far I have had no luck with the s110 project. Should I be using the UART?

s110
ser_s110_hci
ser_s110_spi
ser_s110_uart

[Vidar Berg]

Hi,

You should use  "s110" configuration. The other ones pre-fixed with "ser_" are configured for serialization (i.e. 2 chip solution - one host processor + one connectivity process. See Running a serialized application).

Which SDK/Softdevice combination are you testing with (comp. matrix SDKs and SoftDevices )?

[brianreinhold]

Okay, that was my guess. So I am choosing the correct one. One day I might get rid of that damn Cortex-M0 error on flashing. 

[Vidar Berg]

This error usually means that the app is overlapping with the Softdevice in flash. I guess you may have tried it already, but I suggest you first try to erase the flash, then program the Softdevice flash target followed by the app from Keil as explained in the SDK getting started guide here: Running examples that use a SoftDevice

[brianreinhold]

You are right, I have tried that many times, just now in SDK version 12.3.0 with the only soft device it supports. Same result. And the documentation you point to was where I started a few days ago.

There MUST be some important critical piece of information missing somewhere that every version I have tried fails the same way; 8.1.0, 10.0.0, and now 12.3.0. The last using s130 as that is the only SoftDevice provided.

Is this just impossible using Keil version 5?

Or are all the SDK projects simply configured wrong memory layout wise?

I know of only two places to change them; in the flash download config and the Target.

[Vidar Berg]

brianreinhold said:

Or are all the SDK projects simply configured wrong memory layout wise?

No, the default layout is correct. But note that Keil resets to the default layout if you change device variant (i.e. default layout for the device variant), could that be the reason?

Default layout for ble_app_hrs_s130 in SDK 12.3.0

[brianreinhold]

Well that would be a critical piece of information. I did switch to nrf51822 as that is the chip I have to work with. But resetting the values to the ones you provided did not solve the issue. Do I also need to do something in the flash config (the programming and algorithm starts)? Or are the values different for the nRF51822?

Since I am using the hts (thermometer) would that be different?

[Vidar Berg]

No, it should have worked, we use the same flash algorithm for all 51 variants.

Is this the board you're using: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF51-DK ?

[brianreinhold]

Yes it is. I bought it a few months ago. I have been using it as a debugger for an nrf51822 chip in a production device (pin 20) but that is not connected now. I had to cut SB9 (advice from you guys) but have jumpered the current measurement pins to give power back to the main chip.

SoftDevice loads, the HTS hex does not.

[Vidar Berg]

brianreinhold said:

Yes it is. I bought it a few months ago. I have been using it as a debugger for an nrf51822 chip in a production device (pin 20) but that is not connected now. I had to cut SB9 (advice from you guys) but have jumpered the current measurement pins to give power back to the main chip.

 That's ok as long as you remember to short the connection with a jumper when you want to program the nRF51 chip on the DK.

I tried to program the hts example as well and took some screenshots if you want to compare settings: