Re: [Bluetooth mesh]unprovisioned device (micro:bit) can't be discovered
I’d be curious to hear if you can still fit a Mesh + PB-GATT build onto the micro:bit, since I suspect Zephyr’s RAM footprint may have gone up slightly during the past year.I had done it, the micro:bit can be:
1. provisioned by nRF Mesh and meshctl through PB-GATT
2. don't support provisioningdata persistent storage;
3. model configuration, just two models here: Configuration Server and Generic OnOff Server. Micro:bit can be configured through PB-GATT.
4. don't support Proxy.
5. basing on Zephyr v1.12 release.
I tried to put it basing on v1.14-rc1, but I think it's impossible.
From: Hedberg, Johan <firstname.lastname@example.org>
Sent: Tuesday, March 12, 2019 10:54 PM
To: Kai Ren <email@example.com>
Subject: Re: [Zephyr-devel] [Bluetooth mesh]unprovisioned device (micro:bit) can't be discovered
On 12 Mar 2019, at 16.29, Kai Ren <firstname.lastname@example.org> wrote:
This is the commit I used: 3aa8443ab41202f978258810961dbc5a74ad2727It doesn’t. It seems like a possible oversight with this configuration file. There’s a second one for this sample app called microbit_gatt.conf which does have PB_GATT=y. Note that the micro:bit with its 16k of RAM was always quite tricky when it came to fitting both the mesh and the provisioning protocols on it. That’s why we’ve done self-provisioning e.g. with samples/bluetooth/mesh_demo since it doesn’t require any provisioning bearer to be compiled in. I’d be curious to hear if you can still fit a Mesh + PB-GATT build onto the micro:bit, since I suspect Zephyr’s RAM footprint may have gone up slightly during the past year.