• State Not Answered
  • Replies 1 reply
  • Subscribers 67 subscribers
  • Views 36 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 336773
Options

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?

Parents
  • 0

    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. 

Reply
  • 0

    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. 

Children
No Data
Related