[
https://issues.apache.org/jira/browse/MYNEWT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095342#comment-16095342
]
ASF subversion and git services commented on MYNEWT-285:
--------------------------------------------------------
Commit 97353f844c48de443ca546e1b3fdfce039bfadd3 in mynewt-core's branch
refs/heads/master from [~andk]
[ https://gitbox.apache.org/repos/asf?p=mynewt-core.git;h=97353f8 ]
[MYNEWT-285] nimble/phy: Fix CRC checking
The CRCSTATUS register is not cleared automatically by hardware so it
may not reflect current state of CRC check in some cases. The better way
to check CRC is to clear EVENT_CRCOK when starting to receive a packet
and then check its state when done.
> 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)
