Hi Mynewt Team,
I have been going through and testing the BLEMESH sample app.
Turning on only one device, which does not have BLE_MESH_GATT_PROXY &
BLE_MESH_PB_GATT flag, still allows the Silicon Labs application to scan and
connect to it.
Correct me if am wron
Hi Aditya,
On Fri, Feb 23, 2018 at 12:50 PM, Aditya Xavier wrote:
> Hi Mynewt Team,
>
>
> I have been going through and testing the BLEMESH sample app.
>
> Turning on only one device, which does not have BLE_MESH_GATT_PROXY &
> BLE_MESH_PB_GATT flag, still allows the Silicon Labs
Thanks for quick reply !
With BLE_MESH_PB_GATT: FALSE and BLE_MESH_GATT_PROXY: FALSE, build fails for
the app.
Error: repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c: In function
'proxy_send':
repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c:852:21: error: unused
variable 'o
Hi Aditya,
Please use BLE_MESH_PB_GATT: 0 and BLE_MESH_GATT_PROXY: 0. But "0"
should work too. What other settings do you have? You can use "newt
target show " to show target settings.
Best regards,
Michał Narajowski
2018-02-23 13:17 GMT+01:00 Aditya Xavier :
> Thanks for quick reply !
>
> With
Hi Aditya,
Seems like you're using Mynewt 1.3.0 release and probably see issue
fixed by following commit on master branch:
https://github.com/apache/mynewt-core/commit/0fd8239b7f914ddae77ac396bfce288fd6bc5b5f
Please apply this change to your tree and check if this solves your problem.
Best regar
So, when is a decision going to be made?
On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote:
> +1
>
> I strongly agree to track issues on github, the integration with
> github issues and PRs is very good and there's a lot of people already
> using it on other projects.
> Thanks,
>
> Miguel
>
Perfect got it to run..
> On 23-Feb-2018, at 6:13 PM, Andrzej Kaczmarek
> wrote:
>
> Hi Aditya,
>
> Seems like you're using Mynewt 1.3.0 release and probably see issue
> fixed by following commit on master branch:
> https://github.com/apache/mynewt-core/commit/0fd8239b7f914ddae77ac396bfce288f
I think we’ve left enough time, and everybody has agreed. Let’s get
on GitHub issues ASAP!
On 23 Feb 2018, at 5:31, Fabio Utzig wrote:
So, when is a decision going to be made?
On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote:
+1
I strongly agree to track issues on github, the integ
My thoughts:
1. Since the 1.4 release is coming up very quickly I would do this for 1.5
(personally).
2. I would choose 2a.
3. Seems a bit confusing to me to label nimBLE releases with same number as
Mynewt releases. Why not just make the first stable release of nimBLE 1.0? Not
a big deal eithe
