This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R-Q1: cc2642 pairing state complete update ID address

Part Number: CC2642R-Q1

Tool/software:

 Hi engineers,

My customer reported a question:

after gapbond_pairing_stet_complete, there's a condition before peer address updating. [!Util_isBufSet]. under the red circle below.

my question is why do we need to make sure the addrPriv is not all-zero. if we delete that condition, what could be the risk

  • Hello Simon, 

    Hope you are doing well! 

    The condition is checking if the peer private address has been populated (addrPriv). If the addrPriv was not populated, the pairing will fail, if peer device is using a private address. 

    The purpose of this condition is to have an additional check on the private address. Checking the addrType for ADDRTYPE_PUBLIC_ID and ADDRTYPE_RANDOM_ID will limit the peer address to RPA but verifying that the RPA was populated is essential for verifying pairing success. 

    In summary, this condition verifies the RPA was populated, if the RPA is not populated, the pair should fail. Removing the condition can lead to errors down the road with pairing, as the addrtype will show RPA, but the populated addrPriv may show zeros still. 

    Let me know if you have any questions. 

    Thanks, 

    Isaac