This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE backward compatibility

Hello!

I have questions.

I develop a central and peripheral devices at nrf52832.

I use SDK 15.3.0, s132 v6.1.1.

1.If I program Nordic's BLE peripheral sample into a device as is, can the device be said to be Bluetooth 4.2 compliant? One of the features of bluetooth 4.2 is mitm. Even if miti is not enabled, is the device compliant with Bluetooth 4.2?

I want to know the conditions under which a Bluetooth version can be declared.

2.When should a Bluetooth device decide which Bluetooth version to communicate with?

3.bluetooth le has backward compatibility, but is it necessary to branch the settings in the application layer for each version? For example, when developing a device that can use the function of bluetooth5.0, do I need to perform branching judgment processing in the application layer for Bluetooth4.0, 4.1, 4.2?

Or do SDKs and soft devices automatically negotiate in lower layers? Does the designer have to worry about backward compatibility?

Thank you in advance.

Parents
  • Hello,

    Or do SDKs and soft devices automatically negotiate in lower layers? Does the designer have to worry about backward compatibility?

    Backward compatibility should generally not be a problem. The BT stacks do what's called a "feature exchange" at the beginning of connections to determine what features they can use. This is without any involvement from the app. 

    1. MITM protection is available in all versions, but there are different ways to achieve it. The most common way is with the use of a 6 digit passkey that the user must submit to allow the pairing or bonding to complete. The requirement for this is that at least one of the devices to have a keyboard input capability so the user can provide the passkey. 

    2. This is taken care of by the feature exchange mentioned above. 

Reply
  • Hello,

    Or do SDKs and soft devices automatically negotiate in lower layers? Does the designer have to worry about backward compatibility?

    Backward compatibility should generally not be a problem. The BT stacks do what's called a "feature exchange" at the beginning of connections to determine what features they can use. This is without any involvement from the app. 

    1. MITM protection is available in all versions, but there are different ways to achieve it. The most common way is with the use of a 6 digit passkey that the user must submit to allow the pairing or bonding to complete. The requirement for this is that at least one of the devices to have a keyboard input capability so the user can provide the passkey. 

    2. This is taken care of by the feature exchange mentioned above. 

Children
Related