S130 potential unstability case

RE: S130 potential unstability case

Gaucho — Fri, 19 Aug 2016 14:23:52 GMT

@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

RE: S130 potential unstability case

Fabien Comte — Wed, 02 Sep 2015 10:10:58 GMT

Hello,

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

RE: S130 potential unstability case

Hung Bui — Mon, 31 Aug 2015 12:51:53 GMT

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.

RE: S130 potential unstability case

Fabien Comte — Mon, 31 Aug 2015 07:53:21 GMT

a board can notify to central until this board become central too (at the same time as its device role), then the error appears.

RE: S130 potential unstability case

Fabien Comte — Mon, 31 Aug 2015 07:47:30 GMT

13313 is for ERROR_BLEGATTS_SYS_ATTR_MISSING

this is the code in mbed that call function

error_t error = (error_t) sd_ble_gatts_hvx(gapConnectionHandle, &hvx_params); if (error != ERROR_NONE) { switch (error) { case ERROR_BLE_NO_TX_BUFFERS: /* Notifications consume application buffers. The return value can be used for resending notifications. */ case ERROR_BUSY: returnValue = BLE_STACK_BUSY; break;

            case ERROR_INVALID_STATE:
                returnValue = BLE_ERROR_INVALID_STATE;
                break;
                
            case ERROR_BLEGATTS_SYS_ATTR_MISSING:
                printf("%d\r\n", error);
                returnValue = BLE_ERROR_INVALID_STATE;
                break;

            default :
                ASSERT_INT( ERROR_NONE,
                            sd_ble_gatts_value_set(connectionHandle, attributeHandle, &value),
                            BLE_ERROR_PARAM_OUT_OF_RANGE );
                break;
        }
    }

does anyone have an idea how to fix error ?

RE: S130 potential unstability case

Fabien Comte — Mon, 31 Aug 2015 07:26:25 GMT

inside write function of nrf5xgattserver.cpp, call of sd_ble_gatts_hvx returns 13313 (decimal)

RE: S130 potential unstability case

Fabien Comte — Mon, 31 Aug 2015 07:23:50 GMT

It's tiny ble boards (www.seeedstudio.com/.../Tiny_BLE) connected and powered by usb on a hub. I never lost serial connection to pc, the broken connection is radio test between boards.

RE: S130 potential unstability case

Pål Håland — Mon, 31 Aug 2015 06:06:27 GMT

Hi Fabien, have you stacked all of the boards on top of each other? If so you need to disconnect the serial pins from the stack. ( So that they are not connected between the boards)