Closed AGlass0fMilk closed 4 years ago
Still doesn't work -- my phone continuously attempts to connect and it goes into an infinite disconnection loop. This is seen with both the lightblue app and the nRFConnect app.
Internal Jira reference: https://jira.arm.com/browse/IOTPAN-504
Any update on this?
Nearing 3 weeks...
@pan @donatieng
@bentcooke - any advice here?
Just tried this with the nRF52840_DK from a fresh clone. Attempted to connect with my iPhone SE using the LightBlue scanner app. Still does not seem to be working properly. I get a connection/disconnection loop until the phone terminates the connection attempts with the following console output:
PERIPHERAL
f9:91:38:7f:c9:c8
Please connect to device
Connected to peer: 47:6e:c3:44:a1:3f
Error during SM::setLinkSecurity 4
Advertising timed out - aborting
CENTRAL
Diconnected
PERIPHERAL
f9:91:38:7f:c9:c8
Please connect to device
Connected to peer: 47:6e:c3:44:a1:3f
Error during SM::setLinkSecurity 4
Advertising timed out - aborting
CENTRAL
Diconnected
PERIPHERAL
f9:91:38:7f:c9:c8
Please connect to device
Connected to peer: 47:6e:c3:44:a1:3f
Error during SM::setLinkSecurity 4
Advertising timed out - aborting
CENTRAL
Diconnected
PERIPHERAL
f9:91:38:7f:c9:c8
Please connect to device
@0xc0170 @adbridge @donatieng @pan- @desmond-blue @paul-szczepanek-arm
This has a customer behind it. Further, there is potential for it and other products from this customer to connect to Pelion, via gateway or other.
I'll talk to the team to check this issue.
@ranshe
Any updates on this?
I've the same problem. any updates on this?
Thank you for raising this issue. Please note we have updated our policies and now only defects should be raised directly in GitHub. Going forward questions and enhancements will be considered in our forums, https://forums.mbed.com/ . If this issue is still relevant please re-raise it there. This GitHub issue will now be closed.
@0xc0170 This falls under the category of defect I believe
@AGlass0fMilk Is it still an issue ? I can't reproduce it.
This issue is now outdated and probably resolved thanks to updates to the BLE stack. If I encounter this again I will open a new issue.
Hi,
While attempting to build and test the
BLE_SM
example on thenRF52840_DK
target, my phone is able to connect but the Mbed-OS device encounters an error when attempting to upgrade the link's security. The following debug output is shown:The
SM:setLinkSecurity
call is returningBLE_ERROR_INVALID_PARAM
at this line:https://github.com/ARMmbed/mbed-os/blob/033fffea8406fc32b4a19d92d76912c86b010f86/features/FEATURE_BLE/source/generic/GenericSecurityManager.tpp#L367-L370
get_control_blocks
loops through a number of connection control blocks trying to find the one given by the caller. None of the control blocks are in theconnected
state yet -- so the call fails to find the control block and thus the security manager returnsInvalid Parameter
.My theory is that the internal state hasn't been updated before the stack's
onConnectionComplete
handler is called.I'm going to try and delay the link security upgrade by deferring to the example's event queue for a few milliseconds. I'll post back with my findings...