[
https://issues.apache.org/jira/browse/MYNEWT-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261221#comment-15261221
]
ASF subversion and git services commented on MYNEWT-85:
-------------------------------------------------------
Commit 8ddc20eed045e5d9d0abe6b0bd5d6af83f872dcf in incubator-mynewt-core's
branch refs/heads/develop from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=8ddc20e
]
MYNEWT-85: Fix BLE timing for start of connection events.
MYNEWT-283: Slave anchor point now set correctly on CRC error.
Please read the respective tickets for a discussion of
the changes.
> Transmit timing for certain BLE transmissions may not meet the specification.
> -----------------------------------------------------------------------------
>
> Key: MYNEWT-85
> URL: https://issues.apache.org/jira/browse/MYNEWT-85
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Affects Versions: v0_8_0_beta1
> Reporter: William San Filippo
> Assignee: William San Filippo
> Priority: Critical
> Fix For: v0_9_0_rel
>
>
> Although the unplugfest went well in this regard, it could have been because
> we "exaggerated" the amount of clock drift. The current BLE controller code
> does not use an output compare to transmit a BLE frame at a specific time.
> This could cause the transmission to occur outside the BLE specification. The
> code should be modified to use the BLE transceiver HW to enforce more exact
> transmission timing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
