Re: [Bluetooth mesh]unprovisioned device (micro:bit) can't be discovered
Hi Johan,toggle quoted messageShow quoted text
Thanks for the prompt reply.
I think you're expert of Zephyr Bluetooth, I have two questions before getting into the detail for optimization:
1. compiling same sample code, like sample/bluetooth/mesh/, compared with v1.12.0, do you think v1.14.0 is hungry or efficient for RAM consumption?
2. as your estimation, how many bytes will be consumed if add persistent storage?
From: Hedberg, Johan <firstname.lastname@example.org>
Sent: Friday, March 15, 2019 6:23 PM
To: Kai Ren <email@example.com>
Subject: Re: [Zephyr-devel] [Bluetooth mesh]unprovisioned device (micro:bit) can't be discovered
On 15 Mar 2019, at 12.12, Kai Ren <firstname.lastname@example.org> wrote:
I had done it, the micro:bit can be:I wouldn’t say it’s impossible. I bet there’s still place for memory optimisation, e.g. thread stacks that can be shrunk, buffer sizes & counts that can be lowered, and possibly unneeded features that can be disabled. Someone would just need to find the time to look into this :)