BLE Mesh SDK along with peripheral mode.

RE: BLE Mesh SDK along with peripheral mode.

Hung Bui — Tue, 31 Oct 2017 08:22:10 GMT

It should be possible. The only issue is that SDK v14.1 uses S140 v5.0.0 when the Mesh SDK uses S140 v5.0.0-3 alpha. There are some differences in the header files. But it shouldn't be too hard to merge.

RE: BLE Mesh SDK along with peripheral mode.

Butu — Mon, 30 Oct 2017 22:36:12 GMT

Thank you very much! The example works very well. I want to combine ble_app_uart with light_control_client, additionaly I want to do for nRF 52840. I will use instruction from yours new post. Is it possible to do ? Or will it be easier for nRF 52832?

RE: BLE Mesh SDK along with peripheral mode.

Hung Bui — Mon, 30 Oct 2017 16:46:28 GMT

@Butu: an example for SDK v14.1 was posted here.

RE: BLE Mesh SDK along with peripheral mode.

Hung Bui — Mon, 30 Oct 2017 13:29:28 GMT

I assume you use the example created by Rick? The example was made for Keil. You would need to port it to SES. The error you got most likely from the missing header file.

Have you tested with the normal SDK example (in MESH SDK) ?

RE: BLE Mesh SDK along with peripheral mode.

Butu — Mon, 30 Oct 2017 12:17:24 GMT

Thank you for suggestion. I got 56 errors...Do you know what I do wrong? Below I paste link to picture with errors. link errors.jpg

RE: BLE Mesh SDK along with peripheral mode.

Hung Bui — Mon, 30 Oct 2017 10:26:01 GMT

I assume you are using KEIL IDE ? You need to get a license to compile a project which is more than 32kB in size.

I would suggest to use Segger Embedded Studio, as you can use it for free if you use Nordic chip.

RE: BLE Mesh SDK along with peripheral mode.

Butu — Sat, 28 Oct 2017 23:56:59 GMT

Hi All,

I did according to the instruction, but I have 1 error. I do not know how can I do it. My error: ._build\nrf52832_xxaa.axf: error: L6050U: The code size of this image (97840 bytes) exceeds the maximum allowed for this version of the linker.

Someone knows how to fix it?

RE: BLE Mesh SDK along with peripheral mode.

sara — Tue, 17 Oct 2017 07:30:37 GMT

Hello ms3412amo, Thanks for your response, but my project still has some problems. I'll open a new question about it, thanks again.

RE: BLE Mesh SDK along with peripheral mode.

ms3412amo — Fri, 13 Oct 2017 03:46:43 GMT

Yes, there is a diffrence in sdk 0.9.1 and 0.9.2, this Keil project was with 0.9.1 and the Mesh_serial files are not the same. If you use 0.9.2 remove all Mesh_serial file and replace with those of 0.9.2, this is not just serial_handler.c replaced by serial_handler_app.c, replace all Mesh_serial files, or try with server node from 0.9.1, as this Keil client project is with 0.9.1.

RE: BLE Mesh SDK along with peripheral mode.

sara — Fri, 13 Oct 2017 01:12:59 GMT

Hello ms3412amo, have you solved the problem? I also have the same question that using the example ant it runs well but no LED ON/ OFF.

RE: BLE Mesh SDK along with peripheral mode.

ms3412amo — Sat, 23 Sep 2017 21:36:25 GMT

Hi, I'm trying your solution, but it is not working fine. I erase/flash 3 server with the exemple from Segger, than I erase/flash client with your Keil project including Nordic UART service. Provisioning happens, I got configuration of device 0,1,2 from client's RTT output. I see Nordic UART in nRF_Connect, I try sending '0'. In client's RTT I see "access.c, 393, TX: [aop: 0x00C1]" 8 times and nothing else happens, no LED On and no "RX: [...]" from the server as with both client and server from SES exemple. It's the same behavior sending 0 from RTT, I also see the TX log 8 times. I try changing the downward arrows in nRF_Connect, but same behavior. Does anyone have a idea what I should check or try to make this working. I'm pretty sure it is not a big issue. Thank you.

RE: BLE Mesh SDK along with peripheral mode.

Sourabh Barve — Mon, 21 Aug 2017 08:48:34 GMT

Hi Rick. I disabled the setting (the one with 3 downward facing arrows) in front of TX characteristic in the Nordic UART Service, which changed the "Value" (in "Descriptors") from 0x0000 to 0x0100. This solved the error 8 that I was receiving.

RE: BLE Mesh SDK along with peripheral mode.

Jui-Chou (Rick) Chung — Mon, 21 Aug 2017 07:22:57 GMT

Hello Sourabh Barve, would you please tell me what cause the notification failed in nRFconnect ? :)

RE: BLE Mesh SDK along with peripheral mode.

Sourabh Barve — Mon, 21 Aug 2017 04:27:49 GMT

Thanks Rick. Your solution worked. The error 8 (NRF_ERROR_INVALID_STATE) from the ble_nus_string_send function was because of a setting in the nRFConnect app.

RE: BLE Mesh SDK along with peripheral mode.

Sourabh Barve — Thu, 17 Aug 2017 11:16:44 GMT

Hi Rick, thanks. The problem solved partially. Now the mesh part works after client connects with phone. I can send commands to the server through client (through mesh). But there is one problem. I'm still getting the error 8 (NRF_ERROR_INVALID_STATE) from the ble_nus_string_send function. Also when I disconnect the client from the phone, the client advertises weirdly (The name is changed to "N/A" (the MAC address is same), it advertises after long intervals (almost 10seconds)) and I cannot connect to it.

RE: BLE Mesh SDK along with peripheral mode.

Sourabh Barve — Thu, 17 Aug 2017 05:24:24 GMT

Hi Rick, thank you for the reply. But the solution you provided didn't worked. I have made one more observation: When I power only client and connect it with mobile, it connects successfully. But when I power the server, even the provisioning doesn't happen.

RE: BLE Mesh SDK along with peripheral mode.

Jui-Chou (Rick) Chung — Wed, 16 Aug 2017 12:12:05 GMT

Hello, Have you ever check if softdevice_handler can dispatch the mesh event? For me, I add the following line in intern_softdevice_events_execute(), which under softdevice_handler.c

while (sd_evt_get(&evt_id) == NRF_SUCCESS)
{
    nrf_mesh_on_sd_evt(evt_id);
}

I also update my main.c in the attachment. And in my experience, if you moving all the mesh resource to nRF5x SDK workspace. Please do not use the uECC resource inside the SDK12.1. Instead, please add the uECC.c and include eECC.h from mesh SDK.

The Keil project (which is very rough) is also attached in the enclosure.

To using nRFconnect the mesh light control client, please:

Unzip the mesh.7z, and place it under SDK12.1\components\
Unzip the mesh_example.7z and place it under SDK12.1\examples\
Open the Keil project in SDK12.1\examples\mesh_example\light_control\client\arm5_no_packs
Compile and program it to nRF52-DK
After provisioning with three light control server, please open nRFconnect or nRFTool box with UART control on mobile device

Write ‘0’ -> control LED1 on the light control server 0
Write ‘1’ -> control LED1 on the light control server 1
Write ‘2’ -> control LED1 on the light control server 2
Write ‘3’ -> control LED1 on all the light control server

Hope this can help you.

softdevice_handler.c main.c mesh.7z mesh_example.7z