DevHeads IoT Integration ServerDIIS
DevHeads IoT Integration Server•2y ago
Sterling

Is it correct that most BLE communication uses GATT server/client relationships or BLE mesh networks

I am developing a Zephyr OS runtime system to use BLE for communication between two nrf52840dk boards. I want a generic API for facilitating this BLE communication, which would look like this:

/* Send a message to conn */
void send(struct bt_conn *conn, void* data, u16_t len);

/* Callback when a message is received from conn */
void recv(struct bt_conn *conn, void* data, u16_t len);


Currently, I have a GATT server and client setup where the server notifies the client of attribute changes to send messages and the client also writes to the server's attribute to send messages.

In other words, I have two questions to ask:
  1. Is it correct that most BLE communication uses GATT server/client relationships or BLE mesh networks?
  2. Where can I find more information on creating a generic API like the one above, or does such an API already exist? @Middleware & OS
Solution
You can check out this GitHub link

https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/bluetooth/mesh_provisioner/README.rst
GitHub
zephyr/samples/bluetooth/mesh_provisioner/README.rst at main · zeph...
Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures. - zephyrproject-rtos/zephyr
Jump to solution
Was this page helpful?