CC2642R: new GAPBOND_ALLOW_DEBUG_KEYS in simplelink SDK v5.10

Ming Sun

Part Number: CC2642R

Hi,

There is a new parameter GAPBOND_ALLOW_DEBUG_KEYS in the latest SDK v5.10, and I want to verify this configuration.

I download the simple_peripheral demo from SDK v5.10, and make sure the GAPBOND_ALLOW_DEBUG_KEYS is true (default value is true), to a TI LaunchPad(A).

and I download the simple_central demo from SDK v4.40 and set the GAPBOND_SC_HOST_DEBUG true (default value is false), to another TI LaunchPad (B).

Then I can connect A and B, read RSSI value and run GATT write.

That's correct. But after I set the GAPBOND_ALLOW_DEBUG_KEYS value to false in Pad A, B can connect and communicate with A as well. Nothing difference after I change the value of GAPBOND_ALLOW_DEBUG_KEYS.

I am not sure whether this parameter (GAPBOND_ALLOW_DEBUG_KEYS ) will be checked during the connection establishment or pairing/bonding time. How Can I verify the change of this parameter?

Cheers,

Ming Sun

over 4 years ago

0 Ming Sun over 4 years ago

Prodigy 30 points

After further testing, it was found that this configuration is checked after the pairing started. The status for the failure was 10, I'm not sure where this value is defined.

0 Ming Sun over 4 years ago in reply to Ming Sun

Prodigy 30 points

The failure status value (10) may be SMP_PAIRING_FAILED_INVALID_PARAMETERS, is it correct? It is the error code for DEBUG KEYS parameter?

0 desouza over 4 years ago in reply to Ming Sun

TI__Guru**** 171104 points

Hi,

Thanks for your inquiry. I notified a colleague and he will reply as soon as possible.

Regards,

Rafael

+1 Ammar N over 4 years ago in reply to desouza

TI__Mastermind 25810 points

Hey Ming,

Great questions.

Ming Sun said:
After further testing, it was found that this configuration is checked after the pairing started. The status for the failure was 10, I'm not sure where this value is defined.

This is the correct observation. The devices should still connect to each other, but will fail to pair and form a secure connection.

Ming Sun said:
The failure status value (10) may be SMP_PAIRING_FAILED_INVALID_PARAMETERS, is it correct? It is the error code for DEBUG KEYS parameter?

This is correct, it is defined in the spec (v5.2, Vol 3, Part H ~Pg 1647).

Please let me know if you have any further questions!

0 Ming Sun over 4 years ago in reply to Ammar N

Prodigy 30 points

Thanks Ammar.

Bluetooth®︎

Bluetooth forum

CC2642R: new GAPBOND_ALLOW_DEBUG_KEYS in simplelink SDK v5.10