Device not responding to LL_FEATURE_REQ

[HSAADI]

Hi,

My custom device with custom firmware don't respond to LL_FEATURE_REQ so the device disconnect.

The connectivity part of my project is very similar to the example BLE_p2p_server, the device start advertising and when I connect to it with the mobile app ST BLE TOOLBOX the connection fail, in wireshark I see the master device is sending LL_FEATURE_REQ but the device doesn't respond.

Can you please help me as I'm stuck for a week now?

I share with you the wireshark logs (remove the .csv extension)

MCU : STM32WB55

Stack: stm32wb5x_BLE_Stack_full_fw.bin v 1.13.1

Thanks by advance for the help.

[Remy ISSALYS]

Hello,

If you try to use BLE_p2pServer example, did you have the same behavior ? If not, maybe you have a mistake in your application concerning the feature supported. If you have the same behavior with BLE_p2pServer example, you can try to update your stack with the BLE Full Stack v1.14.0 available in the STM32CubeWB package.

Best Regards

[HSAADI]

Hello Remy,

The example BLE_p2pServer work well on the nucleo WB55 board, the issue is in my project (on my custom board) but I can't find where, my project is not based on the p2pServer example but the configuration parameters for the connectivity is the same.

In my project scanning beacons and beaconing works well, and I can advertise for connectivity, just the pairing procedure fail, and I'm not able to find the issue! maybe a config that I missed, that's why I need help as I can't found in the documentation what I need.

Thanks

[Remy ISSALYS]

Hello,

Can you give more information about your setup and what you want to do ? Maybe you have debug trace. With your custom, are you able to establish a BLE connection or it never worked ?

Best Regards

[HSAADI]

The Board is a custom board based on MCU STM32WB55, the firmware was generated by Cube and modified to match our consumption criteria, and to run our feature, we want to do either beaconing or beacon scan or connectivity, the two first was done but the connectivity not yet.

the BLE connection never worked because its a new feature under development.

What I need to do is to establish a connection and discover our custom services to be able to change parameters in the board, for now I didn't added the custom services, I just added the DIS service.

I share with you the main BLE APP code and the app_conf.h

[HSAADI]

app_conf.h

[HSAADI]

when I try to establish a connection, the phone send LL_FEATURE_REQ but the device don't respond, I'm trying to figure why, did the device received the REQ or no! if it does received it why it doesn't respond!

Best Regard

[HSAADI]

Hello,

Can we set a teams call so we can explore the problem better?

and can you please send the link for the BLE stack v1.14.0?

Thanks

[Remy ISSALYS]

Hello,

You can recover the reason of the disconnection in HCI_DISCONNECTION_COMPLETE_EVT_CODE maybe it can help to find the root cause of the disconnection. You can find the BLE Stack v1.14.0 in STM32CubeWB package.

Best Regards

[HSAADI]

Hello,

The result is ** DISCONNECTION EVENT WITH CLIENT status 0 - Reason 8

I just found that :

 ret = aci_gatt_update_char_value(gap_service_handle,

                         gap_appearance_char_handle,

                         0,

                         2,

                         (uint8_t *)&appearance);

return error int 96

Do you have any idea of the reason that the appearance is not set?

thanks.

[Remy ISSALYS]

Hello,

For the disconnection, the value 8 means Connection timeout and for return error of aci_gatt_update_char_value, the value 96 means Invalid handle. Maybe, you have a wrong configuration for the role, so the aci_gap_init isn't executed, check your configuration in ble_conf.h file.

Best Regards