[
https://issues.apache.org/jira/browse/MYNEWT-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Ratner updated MYNEWT-642:
--------------------------------
Description:
The format of the eddystone beacon, as generated by
`ble_eddystone_set_adv_data_uid`, is incorrect.
According to https://github.com/google/eddystone/tree/master/eddystone-uid, the
UID frame starts with 0x00, followed by calibrated rssi at 0m, followed by the
16 byte uid, and finally 2 zero bytes to pad to the full 31 bytes.
By comparison, `ble_eddystone_set_adv_data_url` seems to be doing the right
thing.
was:
The format of the eddystone beacon, as generated by
`ble_eddystone_set_adv_data_uid`, is incorrect.
According to https://github.com/google/eddystone/tree/master/eddystone-uid, the
UID frame starts with 0x00, followed by calibrated rssi at 0m, followed by the
uid, and finally followed by 2 zero bytes to make up the full 31 bytes.
By comparison, `ble_eddystone_set_adv_data_url` seems to be doing the right
thing.
> Eddystone UID format is incorrect
> ---------------------------------
>
> Key: MYNEWT-642
> URL: https://issues.apache.org/jira/browse/MYNEWT-642
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v1_0_0_rel
> Reporter: Simon Ratner
>
> The format of the eddystone beacon, as generated by
> `ble_eddystone_set_adv_data_uid`, is incorrect.
> According to https://github.com/google/eddystone/tree/master/eddystone-uid,
> the UID frame starts with 0x00, followed by calibrated rssi at 0m, followed
> by the 16 byte uid, and finally 2 zero bytes to pad to the full 31 bytes.
> By comparison, `ble_eddystone_set_adv_data_url` seems to be doing the right
> thing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
