Can not run nomally when setting CONFIG_BT_BONDABLE

[Llama12580]

I am running demo nrf/samples/matter/lock.

I tried to use CHIP_NUS so I set CONFIG_CHIP_NUS=y, it worked well.

After that, I wanted to make it bondable so I set CONFIG_BT_BONDABLE=y,  but it could not work and got this booting error.

I didn't modify any other code except these two config CONFIG_CHIP_NUS=y, CONFIG_BT_BONDABLE=y.

So what should I do to make it bondable?

[Hung Bui]

Hi Barry,

If you don't define CONFIG_BT_BONDABLE=y what's the issue do you have ? As far as I know bonding is supported by default. 
If you want the characteristic to require encryption (bonding) you can edit the permission in \zephyr\include\zephyr\bluetooth\services\nus\inst.h to change the 

BT_GATT_PERM_WRITE to BT_GATT_PERM_WRITE_ENCRYPT  for example. 

As far as I can see in the bt_nus_service.cpp , settings is used, so I assume bonding is supported. 

[Llama12580]

I did change BT_GATT_PERM_WRITE to BT_GATT_PERM_WRITE_ENCRYPT, but I still could not bond to my 54L15 board.(BTW, 'MTS' is a BLE Service I customed myself.)

And I checked the ".config" file, I found CONFIG_BT_BONDABLE not set.

Besides, I also tried matter_lock demo and enabled CONFIG_CHIP_NUS, actually it could not bond either even if  I changed BT_GATT_PERM_WRITE to BT_GATT_PERM_WRITE_ENCRYPT. Every time I reconnect to the matter_lock using nRF Connect APP, I have to retype passcode.