BLE NUS receive callback pass the incoming to non-static object.

RE: BLE NUS receive callback pass the incoming to non-static object.

HorstvanGrass — Tue, 18 Jul 2023 14:38:24 GMT

However when I remove the static definition I get compile error:

error: cannot convert 'bt::bt_receive_cb' from type 'void (bt::)(bt_conn*, const uint8_t*, uint16_t)' {aka 'void (bt::)(bt_conn*, const unsigned char*, short unsigned int)'} to type 'void (*)(bt_conn*, const uint8_t*, uint16_t)' {aka 'void (*)(bt_conn*, const unsigned char*, short unsigned int)'}
23 | };

Second option would be my last resort, but I thought there is a more elegant already coded solution...

RE: BLE NUS receive callback pass the incoming to non-static object.

Ali Aljaani — Tue, 18 Jul 2023 13:52:23 GMT

Hi HorstvanGrass,

bt_receive_cb does not have to be static. It was made static to limit the function scope to the file where it is defined. The prototype for it is void (*received)(struct bt_conn *conn, const uint8_t *const data, uint16_t len); as defined in <nRF Connect SDK Installation Path>\nrf\include\bluetooth\services\nus.h .

You also have the option to move the NUS service to your application if you require further adjustment to the code organization. Similar to how it was done in Lesson4- Exercise 2 for the LBS service.