Segger Embedded Studio Project for nRF51 development

Motivation

According to the Bluetooth Sig official web page (Source: Bluetooth SIG Email)

The Bluetooth Special Interest Group (SIG) recently announced their decision to deprecate and withdraw older versions of Bluetooth Core specifications from v2.0 to v4.1. Firstly, there is no need to panic. Secondly, here is what you need to know.

Customers who have already certified/listed their product with the Bluetooth SIG are not affected – once certified, always certified. – Additionally, none of this has any impact on Laird’s ability to produce and supply any of our Bluetooth modules.
Bluetooth v2.0 has been deprecated for some time now and is finally coming to an end. Products using a Bluetooth v2.0 radio (e.g. Laird’s TRBLU23-00200 or BT730) must be Bluetooth SIG listed before January 28, 2019. However, it is important to note that as the standard is already deprecated, it will mean a $25,000 listing fee as opposed to the usual $4,000/$8,000.
The biggest area for review is the mass deprecation of Bluetooth v2.1 – v4.1 on January 28, 2019 and complete withdrawal by July 1, 2020. Again, any certification/listing at these specification levels must be completed before the start of 2019 to keep costs at the usual $4,000/$8,000 listing fees.

Thus, if you need to use the nRF51 for the new bluetooth qualification, you SHOULD use the Softdevice S130v2.0.1 for the qualification approval.

Example

There are multiple example projects.

ble_app_uart_bas_schedule : BLE application with UART, Battery Service with App Scheduler (Baseline)
ble_app_uart_bas_ecdh_aes128 : BLE application with ECDH + AES128 for data protection

Enhance BLE modules

S130v2.0.1 doesn't support the LONG MTU and Data Length Extension. I implemented a new API for sending data longer than MTU=23 (20 bytes payload).

//uint32_t ble_nus_send_file(ble_nus_t * p_nus, uint8_t * p_data, uint32_t data_length, uint32_t max_packet_length)
      
// Send 256 bytes with MTU = 23 (each packet payload is 20 bytes).
err_code = ble_nus_send_file(&m_nus, dataBuffer, 256, 20);

Nordic SDK version working with Bluetooth 4.2 (Softdevice S130 v2.0.1).

You can use either SDK 12.3.0 (the last SDK working with NRF51) with S130 v2.0.1. Here is the demo example SES project on SDK 12.3.0 for nRF51 series.

Requirements

nRF5 SDK version 12.3.0
nRF51 PCA10028 DK Board
Segger Embedded Studio 4.12