ble communication in a separate C file

RE: ble communication in a separate C file

Jørgen Holmefjord — Wed, 23 May 2018 08:59:09 GMT

I would recommend that you post your issue in a new thread where you describe the problem in detail, and also include your code. SDK 15 is quite different from any SDK that support nRF51 series (12.3.0 is the latest with nRF51 support). This will make it easier for other users to find the correct information for their versions if they face similar issues at a later point.

RE: ble communication in a separate C file

Kristian Hansen — Fri, 18 May 2018 12:35:04 GMT

I have this problem too (with S140, SDK15.0) Did you find out what the problem was?

RE: ble communication in a separate C file

jj — Thu, 28 Sep 2017 01:44:12 GMT

Thanks for the reply. I just uploaded the ble and main files here, please have a look. Thank you!

RE: ble communication in a separate C file

Jørgen Holmefjord — Wed, 27 Sep 2017 10:47:56 GMT

Could you upload the ble and main files, showing exactly how you separated the BLE part in a separate file?

RE: ble communication in a separate C file

jj — Tue, 26 Sep 2017 01:15:53 GMT

Hi, I did tried placing the loop in both the main and separate c file but both are not working. And yes, I did debugging using J-link. When the for loop is placed in main.c, I am able to initialise everything and return back to main but when I connect, it does not go into the on_ble_evt function case of BLE_GAP_EVT_CONNECTED to print a statement. Writing to it is not possible. When the for loop is placed in the separate BLE communication file, the same thing happens as above, except that it is not return back to main this time. No error codes were returned anywhere.

RE: ble communication in a separate C file

Jørgen Holmefjord — Mon, 25 Sep 2017 14:05:39 GMT

I would suggest you put the loop in main() function. It should not matter on the functionality, in what file the code is placed. Have you tried debugging your application, to see if any error codes are returned anywhere?