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

Problems with BLE address handling #135

Open
andresag01 opened this issue Dec 4, 2015 · 1 comment
Open

Problems with BLE address handling #135

andresag01 opened this issue Dec 4, 2015 · 1 comment

Comments

@andresag01
Copy link

In BLE there are 4 types of addresses:

  • Public MAC address:
  • Random static
  • Random unresolvable
  • Random resolvable

According to the BLE spec v4.2 in Vol 6, Part B Section 1.3:

If a device is using Resolvable Private Addresses, it shall also have an Identity Address that is either a Public Device Address or Random Static Device Address type.

Currently, the available APIs to handle addresses are getAddress() and setAddress() in Gap.h. But it is not clear from the documentation how can a user make sure that a call to setAddress() with ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE will not clear the previous Public or Random static address.

This feature is important for bonding because without the Public or Random static address in the BLE server the client has no way of identifying the bonded peripheral.

@ciarmcom
Copy link
Member

ciarmcom commented Dec 4, 2015

ARM Internal Ref: IOTSFW-1374

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

No branches or pull requests

3 participants