S130 potential unstability case

[Fabien Comte]

This code do a test triangle with 3 boards on mbed (using BLE API). I have digged in BLE_API and it looks like if instability was in S130. Have you this kind of test in internal ?

I want to help, do you have a code like that on pure SDK style that i could test ?

link 1: board A is central, board B is device link 2: board B is central, board C is device link 3: board C is central, board A is device

every time a char is received on serial port of a board, it's reported to the serial ports of the 2 other boards connected.

It works not so bad but depending on connections order, some half links are not working.

For the boards that did first connection as central and second as device, both TX are working. For the boards that did first connection as device and second as central, half TX are working.

Characteristics discovery sometimes fails.

code.txt

[Hung Bui]

Hi Fabien,

mbed is ideal for simple application and quick prototyping. I would suggest you to continue your development with our SDK.

For you application, I think you can start first with the ble_app_uart example we provided in the SDK. The counterpart for central can be found here. The central part was made for S120 but you shouldn't have a big problem porting it to S130.

What the example does is to forward what received on serial port to BLE via a notification.

You need to add the part that the central device when receiving the notification beside forwarding it to UART, will again update its own TX characteristics and notify the new value to its central (if it's a new packet). So that all 3 devices will be updated with the new value.

[Fabien Comte]

Hello,

I rewritted my test "SDK style" and it works. But it's slow...

[Gaucho]

@Fabien Comte I have the same error ERROR_BLEGATTS_SYS_ATTR_MISSING. Can you please help me to understand more? read here: github.com/.../2446 or also here: github.com/.../74