You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "William San Filippo (JIRA)" <ji...@apache.org> on 2016/03/29 23:33:25 UTC

[jira] [Created] (MYNEWT-271) Nimble stack was not interpreting the set advertising data command properly.

William San Filippo created MYNEWT-271:
------------------------------------------

             Summary: Nimble stack was not interpreting the set advertising data command properly.
                 Key: MYNEWT-271
                 URL: https://issues.apache.org/jira/browse/MYNEWT-271
             Project: Mynewt
          Issue Type: Bug
          Components: Nimble
    Affects Versions: v0_8_0_beta2
            Reporter: William San Filippo
            Assignee: William San Filippo
             Fix For: v0_8_0_rel


The set advertising data command always requires 31 bytes of advertising data to be sent via the HCI interface. The actual valid advertising data length is also passed in the HCI. Our host was only sending the actual advertising data length via the HCI interface and the controller checks to make sure the total length of the advertising PDU matches what is expected.

Fix was simple: always send 31 bytes of advertising data even if < 31 are actually used. Do not check the adv data length in the PDU against the PDU length.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)