[
https://issues.apache.org/jira/browse/MYNEWT-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665424#comment-15665424
]
ASF subversion and git services commented on MYNEWT-486:
--------------------------------------------------------
Commit 0874dceae14dbc8301bed36a104f7c3f249dba49 in incubator-mynewt-core's
branch refs/heads/1_0_0_b1_dev from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=0874dce
]
MYNEWT-486: Further fixes for ACL data buffer size/count.
While not exactly related to the ACL data buffer size, when
testing the controller-only blehci code we noticed that the number
of ACL buffers being reported by the controller and what was sent
to the host in the read buffer size command were not the same.
These changes address that issue.
> ACL data packet sizes of 256 or greater will not work.
> ------------------------------------------------------
>
> Key: MYNEWT-486
> URL: https://issues.apache.org/jira/browse/MYNEWT-486
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v1_0_0_beta1
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_0_0_beta1
>
>
> It appears that there is a bug in the controller. If the ACL data packet
> length is set to greater than 255, the controller will probably fail to send
> the packet. The issue is that the controller uses a uint8_t internally at
> some point and is truncating the packet length.
> There is a work-around for now: setting the BLE_LL_ACL_PKT_SIZE syscfg value
> to 255 or less. This can be done in a target or APP if desired. We will do
> some more testing on this to verify that this is an issue and that the
> work-around is functional. The code will also be fixed in the beta 1 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
