Full error report:
<info> app: Connected
<error> peer_manager_sm: Could not perform security procedure. smd_params_reply() or smd_link_secure() returned NRF_ERROR_INVALID_ADDR. conn_handle: 0
<error> peer_manager_handler: Unexpected fatal error occurred: error: NRF_ERROR_INVALID_ADDR
<error> peer_manager_handler: Asserting.
<error> app: ERROR 16 [NRF_ERROR_INVALID_ADDR] at :0
PC at: 0x00000000
<error> app: End of error report
(Windows10, Segger 4.52c, SDK 15.2.0, nRF52832 dev board)
I'm starting with ble_uart example and I'm using it to drive three PWM lines to an RGB LED. When I use nRFConnect, it works perfectly. I send a command and value, the light changes.
Next is a custom Android app. However when I attempt to pair with my Android S10, I get the above error (This is outside of the custom app, just connecting in settings on the phone)
Since I started with the uart example, I added the peer manager myself from another example.
nRFConnect connects regardless if peer manager code is added or not.
Why does nRFConnect work but normal pairing from a phone does not?