You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2021/10/17 10:57:37 UTC

[GitHub] [mynewt-nimble] andrzej-kaczmarek commented on pull request #1056: nimble/phy/nrf: Fix checking for resolved addr

andrzej-kaczmarek commented on pull request #1056:
URL: https://github.com/apache/mynewt-nimble/pull/1056#issuecomment-945091864


   I am not really sure why current code actually works, but noticed this on qualification test cases after some changes in initiator code as it started hitting this assert: https://github.com/apache/mynewt-nimble/blob/master/nimble/controller/src/ble_ll_scan.c#L1836 (in this particular case static random address was somehow "resolved").
   
   This was likely triggered by the fact that address resolution was disabled, but the previous iteration enabled encryption and this apparently messed up NRF_AAR registers, I think because it shares AES block with NRF_CCM.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org