Perfect got it to run..

> On 23-Feb-2018, at 6:13 PM, Andrzej Kaczmarek <andrzej.kaczma...@codecoup.pl> 
> 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/0fd8239b7f914ddae77ac396bfce288fd6bc5b5f
> 
> Please apply this change to your tree and check if this solves your problem.
> 
> Best regards,
> Andrzej
> 
> 
>> On Fri, Feb 23, 2018 at 1:17 PM, Aditya Xavier <adityaxav...@me.com> wrote:
>> 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 'om' [-Werror=unused-variable]
>>     struct os_mbuf *om;
>>                     ^~
>> At top level:
>> repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c:126:3: error: 
>> 'gatt_svc' defined but not used [-Werror=unused-variable]
>> } gatt_svc = MESH_GATT_NONE;
>>   ^~~~~~~~
>> repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c:95:41: error: 
>> 'proxy_adv_param' defined but not used [-Werror=unused-variable]
>> static const struct ble_gap_adv_params *proxy_adv_param = &fast_adv_param;
>>                                         ^~~~~~~~~~~~~~~
>> repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c:83:40: error: 
>> 'slow_adv_param' defined but not used [-Werror=unused-const-variable=]
>> static const struct ble_gap_adv_params slow_adv_param = {
>>                                        ^~~~~~~~~~~~~~
>> cc1: all warnings being treated as errors
>> 
>> With BLE_MESH_PB_GATT: “0” and BLE_MESH_GATT_PROXY: “0”, build is 
>> successful. However, device restarts.
>> 
>> 000000 Unhandled interrupt (2), exception sp 0x20001280
>> 000000  r0:0x00000000  r1:0x00000000  r2:0x80000000  r3:0xe000ed00
>> 000000  r4:0x00019a3f  r5:0x00000000  r6:0x00000000  r7:0x00000000
>> 000000  r8:0x00000000  r9:0x00000000 r10:0x00000000 r11:0x00000000
>> 000000 r12:0x00000000  lr:0x00008add  pc:0x00008aec psr:0x61000000
>> 000000 ICSR:0x00421802 HFSR:0x00000000 CFSR:0x00000000
>> 000000 BFAR:0xe000ed38 MMFAR:0xe000ed34
>> 000000 Assert @ 0x19a3f
>> 
>> 
>> 
>>> On 23-Feb-2018, at 5:26 PM, Andrzej Kaczmarek 
>>> <andrzej.kaczma...@codecoup.pl> wrote:
>>> 
>>> Hi Aditya,
>>> 
>>>> On Fri, Feb 23, 2018 at 12:50 PM, Aditya Xavier <adityaxav...@me.com> 
>>>> 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 application to scan 
>>>> and connect to it.
>>>> 
>>>>       Correct me if am wrong, but I thought only those devices with 
>>>> BLE_MESH_PB_GATT should be scannable / connectable by the Silicon Labs app.
>>>> 
>>>>       Am I missing something ?
>>>> 
>>>>       For reference am using the master branch.
>>> 
>>> Did you disable GATT PB and proxy flags in your target settings? If
>>> not then these are enabled by default in Mesh package so blemesh will
>>> work with app from Silicon Labs.
>>> 
>>>> Thanks and Regards,
>>>> Aditya Xavier
>>> 
>>> Best regards,
>>> Andrzej
>> 

Reply via email to