Can you elaborate on connup_callback and conndown_callback?
Talking about callbacks in Android or on the BLE device?
connup_callback means : registered by " bleprofile_regAppEvtHandler(BLECM_APP_EVT_LINK_UP
conndown_callback means : registered by " bleprofile_regAppEvtHandler(BLECM_APP_EVT_LINK_DOWN
using android phone, i connected to BCM92073X app (modified hello_client).
From my experience, when you pair with the ble device, conndown_callback does not get called.
When you pair, connup_callback gets called. Then when the pairing is done, smp_bond_result callback gets called.
After the pairing, the ble device will stay connected.
If you are seeing conndown_callback when you are trying to pair, it's probably because Android device is not pairing with the ble device properly.
How are you connecting to hello_client?
Using an Andoid app? or just by pairing in the Bluetooth Setting in Android?
in the Bluetooth Setting in Android
when i select hello_client(modified), paring is success. (is involved paired devices in android)
and then, Through "auto(wait some seconds)" or "manually select hello_client in paired devices", connection is successed.
at this flow,
which is right?
1) connup -> smp_bond_result -> connup
2) connup -> smp_bond_result -> conndown -> connup
3 ) connup -> smp_bond_result
4) others... ??
To be more specific it should be:
4) connup -> encryption_changed (also callback) -> smp_bond_result
So when you hello_client in Bluetooth Setting in Android to pair, it should automatically connect to the ble device.
thanks a lot, James