Re: [Bluetooth mesh]CONFIG_BT_PERIPHERAL, what does it mean?

Johan Hedberg

Hi Kai,

On Thu, Mar 22, 2018, Kai Ren wrote:
I’m try to run ./sample/Bluetooth/mesh/ on micro:bit, I found that
current source code for micro:bit just support PB-ADV, don’t support
PB-GATT. So, I want to add PB-GATT on it, but I found that it’s really
hard to pass the build process because it runs out of RAM if I
modified prj_bbc_microbit.conf.
Meanwhile, I also found that there is a configuration flag,
CONFIG_BT_PERIPHERAL, it consumes about 2KB RAM when I enable it, so
I’m just curious that what function does this flag provide? And is it
necessary for PB-GATT on micro:bit? Thanks!
There's actually a samples/bluetooth/mesh/microbit_gatt.conf
configuration that's intended to be used for a GATT-based build of the
mesh sample. That said, I just tried it and it actually overflows the
RAM by 300 bytes. That's much less than 2k however, and hopefully easily
to fix. Looking into it now. It might e.g. be possible that the
CONFIG_BT_L2CAP_TX_BUF_COUNT=5 variable can be lowered since there was
recently an extra segmentation buffer introduced for outgoing ACL

Note: you can select microbit_gatt.conf e.g. by passing the following
to cmake: -DCONF_FILE=microbit_gatt.conf


Join to automatically receive all group messages.