Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GATT Service #189

Open
FisherKei opened this issue Jun 22, 2017 · 19 comments
Open

GATT Service #189

FisherKei opened this issue Jun 22, 2017 · 19 comments

Comments

@FisherKei
Copy link

I have a problem understanding GATT Service in the How it works doc. As described in the Air interface packets, the packets are broadcasted as regular BLE Nonconnectable Advertisements, so I wonder how external devices as phones can connect to GATT Service when a device is in Nonconnectable Advertisements state?
I'm not really with Nordic BLE SDK so it would be nice if you can explain the process above in detail since I'm working to porting OpenMesh to TI CC26xx devices.
Thank you in advance and this project is great!

@trond-snekvik
Copy link
Contributor

Hi,

The GATT connection is initiated through different advertisements from the ones the mesh runs in.

For the connection, the mesh uses the SoftDevice, which has to run its own connectable advertisements, to be picked up. You can see this being done in the BLE_Gateway example nrf_adv_conn.c module.

As explained in the "how it works" document, the mesh operates directly on the radio through the SoftDevice timeslot API.

I'm working to porting OpenMesh to TI CC26xx devices.

This sounds like a cool project :) do you plan on publishing your port?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@trond-snekvik @FisherKei and others