[
https://issues.apache.org/jira/browse/MYNEWT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095343#comment-16095343
]
ASF subversion and git services commented on MYNEWT-285:
--------------------------------------------------------
Commit d04fc83c1011a457c1a6398c70180e3b862dcfb8 in mynewt-core's branch
refs/heads/master from [~andk]
[ https://gitbox.apache.org/repos/asf?p=mynewt-core.git;h=d04fc83 ]
Merge pull request #449 from andrzej-kaczmarek/nimble-crc-check
[MYNEWT-285] nimble/phy: Fix CRC checking
> NRF52 decryption failures (intermittent)
> ----------------------------------------
>
> Key: MYNEWT-285
> URL: https://issues.apache.org/jira/browse/MYNEWT-285
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Nimble
> Affects Versions: v1_0_0_beta2
> Reporter: William San Filippo
> Assignee: Andrzej Kaczmarek
> Fix For: v1_1_0_rel
>
>
> The current ble phy driver for the nrf52 counts occasional errors when
> decrypting received frames. What we see is that the CCM peripheral does not
> set the ENDCRYPT event, indicating that decryption never finished (or even
> started although we do see the ENDKSGEN event which signifies we generated
> the key stream). When this occurs there is no other indication; the CRC check
> passes and it passes the MIC. Note that we only see this occurring for LL
> empty PDU's. These packets have zero length and are supposed to pass through
> the CCM engine as empty pdu's are not encrypted.
> A note on this bug: this only occurs when the device is the slave, not the
> master.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
