Hi Aditya,
On Sat, Apr 07, 2018 at 07:59:44AM +0530, Aditya Xavier wrote:
> Hi Christopher,
>
> That is the expected behaviour, however if you try running the sample app I
> gave you would notice the following
> After step 11, I.e initialise the os_mbuf by doing a os_mbuf_get from a
>
Hi Christopher,
That is the expected behaviour, however if you try running the sample app I
gave you would notice the following
After step 11, I.e initialise the os_mbuf by doing a os_mbuf_get from a
mempool, the new value is overwritten on the previous value.
I.e
1. Accessing the mbuf after
Hi Aditya,
On Fri, Apr 06, 2018 at 07:36:41PM +0530, Aditya Xavier wrote:
> Hi Mynewt Team,
>
> Please help me understand the behavior of MBUF.
>
> PFB the steps I did :-
>
> 1.os_mempool_init
> 2.os_mbuf_pool_init
> 3.Initialized a os_mbuf by os_mbuf_get
> 4.Triggered Console
Hi Aditya,
Mesh is using Adv extensions under the hood if you have Łukasz's patch
and enable BLE_EXT_ADV and set BLE_MULTI_ADV_INSTANCES to at least 1.
Blemesh_shell has a command "init" which initializes mesh stack and
starts advertising Unprovisioned Mesh Beacon.
I tested this now and I
Hi Michał / Łukasz,
I have been trying to understand the blemesh_shell, and I fail to understand
how / where it is using the Advertisement extensions.
Basically, could you point me towards the difference if I need to implement, in
order to use blemesh instead.
From what I gathered /
