Using the S130 alpha SD

RE: Using the S130 alpha SD

Ole Bauck — Wed, 09 Dec 2015 10:26:17 GMT

Ok, I misunderstood your first question and thought you were going from alpha release to v1.0.0. I realize now that you are going from the v1.0.0 release to v2.0.0 alpha. I have made a quick walkthrough for the s132 v2.0.0 alphas here (it will be updated with a more in depth document). The procedure is the same for s130 v2.0.0 alphas, only the ROM and RAM size is different.

RE: Using the S130 alpha SD

Bret Foreman — Tue, 08 Dec 2015 16:38:40 GMT

I'm using the s130 alpha which came with a new set of include files. Are those files backward compatible to s130 v1.0.0?

As you say, the SDK 10 s130 examples work with s130 v1.0.0 out of the box, but they don't work with S130alpha and the S130alpha release notes don't give a clue about how to make them work.

RE: Using the S130 alpha SD

Ole Bauck — Tue, 08 Dec 2015 10:01:39 GMT

SDK 10 s130 examples should work with SoftDevice s130 v1.0.0 out of the box. sd_ble_enable(...) in s130 v1.0.0 takes one argument, and in s130 v2.0.0-4.alpha or v2.0.0-7.alpha it takes two arguments. If you are using v1.0.0, I suggest that you download SDK again, it seems that you have changed the ble header files.

RE: Using the S130 alpha SD

Bret Foreman — Mon, 07 Dec 2015 21:22:05 GMT

I got everything to build. It took a while because many header and c files were moved from SDK 9 to SDK 10. I also added a second NULL argument to sd_ble_enable and that fixed the build issue.

Now I'm having trouble with notify_enable. Here's the code, which is the same in SDK 9 and SDK 10:

static void notify_enable(void)
{
    ble_gattc_write_params_t write_params;
    uint8_t                  buf[BLE_CCCD_VALUE_LEN];
	
    buf[0] = BLE_GATT_HVX_NOTIFICATION;
    buf[1] = 0;

    write_params.write_op = BLE_GATT_OP_WRITE_REQ;
    write_params.handle   = RX_cccd_handle;
    write_params.offset   = 0;
    write_params.len      = sizeof(buf);
    write_params.p_value  = buf;
 write_params.flags    = BLE_GATT_EXEC_WRITE_FLAG_PREPARED_WRITE;

    APP_ERROR_CHECK( sd_ble_gattc_write(conn_handle, &write_params) );
}

On SDK 9, this code works fine. With SDK 10, sd_ble_gattc_write() returns code 8, illegal state. Has there been a change in how this function is used?

RE: Using the S130 alpha SD

Bret Foreman — Fri, 04 Dec 2015 23:48:43 GMT

A little more research leads me to believe that the __CC_ARM macro identifies the ARM compiler. How do I turn that on in Keil?

RE: Using the S130 alpha SD

Bret Foreman — Fri, 04 Dec 2015 23:16:18 GMT

I'm now working with SDK 10 and the compiler is still complaining about sd_ble_enable. A look at ble.h reveals that the one-argument version of the function requires the macro __CC_ARM to be defined. A little more looking around shows that this macro is used all over the place so I'm reluctant to add it to the project for fear of other side effects. What is it? And if I do add it, should it be local to this file or global to the project? Or is this macro defined somewhere in a header file I need to include?

RE: Using the S130 alpha SD

Bret Foreman — Fri, 04 Dec 2015 22:41:50 GMT

I installed SDK version 10 and tested the build of some sample projects. I see that IS_SRVC_CHANGED_CHARACT_PRESENT is simply defined to be 0 at the top of the main in the version 10 examples.

RE: Using the S130 alpha SD

Bret Foreman — Fri, 04 Dec 2015 16:50:48 GMT

I'm following the release notes that came with the alpha release. They mention that sd_ble_enable has changed, but not in enough detail to understand how to use it.

I did a complete search of my 9.0.0 dev environment and I don't have a header file that defines IS_SRVC_CHANGED_CHARACT_PRESENT. And it's not in any of the new header files that came with the alpha release. I'm guessing that I'm missing a file. Can you tell me where to find the header for this macro?

And my compiler complains that sd_ble_enable takes two arguments, not one. It looks like it takes some kind of memory base. In fact, I can't find the header where the prototype for this function is defined.

RE: Using the S130 alpha SD

Ole Bauck — Fri, 04 Dec 2015 10:05:40 GMT

For an example of how to call sd_ble_enable, take a look at ble_stack_init() in the SDK examples. For your convenience, here it is:

#if defined(S110) || defined(S130) || defined(S132)
    // Enable BLE stack.
    ble_enable_params_t ble_enable_params;
    memset(&ble_enable_params, 0, sizeof(ble_enable_params));
#if (defined(S130) || defined(S132))
    ble_enable_params.gatts_enable_params.attr_tab_size   = BLE_GATTS_ATTR_TAB_SIZE_DEFAULT;
#endif
    ble_enable_params.gatts_enable_params.service_changed = IS_SRVC_CHANGED_CHARACT_PRESENT;
    err_code = sd_ble_enable(&ble_enable_params);
    APP_ERROR_CHECK(err_code);
#endif

The macro S130 is defined in the preprocessor symbols, so you can add your old code inside an #ifdef S130_ALPHA and change the macro to S130_ALPHA to use old code.

I don't have a complete overview of the changes, but they should be in the release notes located in the SoftDevice folder (zip file downloaded).

As far as I know, you don't need to tell the SoftDevice to accept 3 packets per connection interval, this is automatic.