About central pair issues

RE: About central pair issues

Amanda Hsieh — Mon, 22 Mar 2021 14:11:32 GMT

Hi,

Sorry, it's my loss. Also, need to set the optimization level to 0. Please follow this guide.

After that you can add a breakpoint in app_error_handler() (or where app_error_fault_handler is called), and you can find information about

error_info_t error_info =
{
    .line_num    = line_num,
    .p_file_name = p_file_name,
    .err_code    = error_code,
};

-Amanda H.

RE: About central pair issues

daoms — Sat, 20 Mar 2021 07:05:11 GMT

The fact is when DEBUG enabled ,app_error_save_and_stop gives out nothing.

RE: About central pair issues

Amanda Hsieh — Fri, 19 Mar 2021 08:19:30 GMT

Hi,

What did you modify the ble_app_hrs_c?

Do you test with ble_app_hrs on the peripheral device?

Do you have the same issue on SDK17?

I recommend to define DEBUG in the project as this thread suggested.

-Amanda H

RE: About central pair issues

daoms — Fri, 19 Mar 2021 03:32:15 GMT

And actually, the peer device support LESC feature.

But when CENTRAL enables LESC, app reboots or fatal error.

RE: About central pair issues

daoms — Fri, 19 Mar 2021 02:45:38 GMT

It's weird, LESC will cause system reboot or ERR:Fatal.

RE: About central pair issues

daoms — Thu, 18 Mar 2021 14:40:58 GMT

Thanks for your kind suggestion.

I use KEIL, you mean provide the NRF_LOG_DEBUG info output from RTT log Viewer?

RE: About central pair issues

Amanda Hsieh — Thu, 18 Mar 2021 14:11:35 GMT

Hi,

If it is possible, I would suggest you use the latest version of SDK. Now it is 17.0.2 which fixes bugs and includes new features.

It's hard to say anything without the debug log from the device. Are you able to provide it? If you are playing an example, you should be able to build with the Debug.

-Amanda H.

RE: About central pair issues

daoms — Thu, 18 Mar 2021 13:52:33 GMT

1.I'm playing SDK13.1.0 S132_4.0.2. ble_app_hrs_c.

I detected this AUTH_NOT_SUPP error by adding a log as below.

And if it is the version, what is the right way to play Nordic SKD? Always use the latest version, or just keep on a stable version?

RE: About central pair issues

Amanda Hsieh — Thu, 18 Mar 2021 12:32:13 GMT

Hi,

[quote user=""]1.When I enable LESC, the pair fails with the AUTH_NOT_SUPP error. Why ?[/quote]

Which SDK version are you using?

Are you able to provide the complete log? You could build with debug or add DEBUG into Processor Definitions.

Which function returns AUTH_NOT_SUPP error?

[quote user=""]2.When CENTRAL disconnects from a bounded connection and erased the bond info(earphone still keep the bond info), it cannot make the connection again. There will be error=0x3e immediately happens on every connect attempt.[/quote]

Please beware that repairing is not secure. If repairing is allowed anyone can just pretend it has the same MAC address and read all the data by bonding again.

It's recommended to instead remove the pairing info on both sides. This can also be done "remotely", like with a "restore factory defaults" setting in your device, or with a button. For the SDK examples, you can delete all bonds by pressing board button 2 while resetting the device. If you choose to allow repairing anyways, the user data should at least be removed so no one can get access to them.

The peer manager which handles pairing requests will for security reasons* reject new pairing requests from an already bonded peer device. You may add the following event handling to the PM callback if you want to allow repairing:

       case PM_EVT_CONN_SEC_CONFIG_REQ: 
       {
            pm_conn_sec_config_t config = {.allow_repairing = true};
            pm_conn_sec_config_reply(p_evt->conn_handle, &config);
       }

-Amanda H.