Re: [DISCUSSION] Moving NimBLE to separate project

[will sanfilippo]

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 either way but since they are going to diverge eventually.

Will
> On Feb 22, 2018, at 1:01 AM, Andrzej Kaczmarek 
>  wrote:
> 
> Hi all,
> 
> As some of you may already noticed, there is apache/mynewt-nimble
> repository created where NimBLE code was pushed along with some extra
> changes, most notably initial attempt to create port of NimBLE for
> FreeRTOS, but other platforms will be supported as well (native Linux port
> is also prepared).
> 
> The problem is that this repo is now not synced with apache/mynewt-core and
> having two repositories with the same code is troublesome so we'd like to
> end development of NimBLE code in core repository and move it entirely to
> nimble repository. There are three open points on how this should be done:
> 1. When to do this switch? Before 1.4 release or after it?
> 2. How to deal with NimBLE in core repository?
> 3. How to manage NimBLE releases?
> 
> My proposals are as follows:
> 
> 2a. Remove NimBLE code from mynewt-core repository leaving only packages
> with dependencies to mynewt-nimble repository. The process of upgrading to
> new version should be as easy as doing 'newt upgrade' to fetch newt
> repository, assuming there are no local changes to NimBLE code. This is
> preferred option.
> 2b. Leave NimBLE code at its current state in mynewt-core and use it by
> default for next release, with option to use mynewt-nimble instead. This is
> safe option and can be also applied before 1.4 release.
> 
> 3. NimBLE has its own releases, depending on needs, and Mynewt will use
> latest stable release of NimBLE at all time. First release of NimBLE will
> be synced with Mynewt release, I guess we can call it the same as Mynewt
> release and then start independent releases with 2.0. For those who would
> like to use latest NimBLE, of course it would be just a matter of switching
> repository version manually.
> 
> Any thoughts on this?
> 
> Best regards,
> Andrzej

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Sterling Hughes]

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 integration with
github issues and PRs is very good and there's a lot of people 
already

using it on other projects.
Thanks,

Miguel

On Thu, Feb 8, 2018 at 5:34 AM, Fabio Utzig  wrote:

+1

I prefer as much information in a single place as possible, and GH 
as been adding more and more "project management" features making it 
better suited as a Jira alternative (and btw, we already made this 
move with MCUBoot!).


Cheers,
Fabio Utzig

On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:

On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:

Hi,

Multiple people have suggested that issues be tracked on Github 
close
to the code. The benefit is that contributors don’t have to 
switch

between two systems to raise and clear issues.  Please let your
thoughts known either way.


I agree with switching to github issues.

Jira seems more powerful and I do like it, but I find the extra
flexibility is outweighed by the difficulty of using two different
systems (github for PRs, Jira for issues).

Chris




--
--
Miguel Azevedo

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Fabio Utzig]

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
> 
> On Thu, Feb 8, 2018 at 5:34 AM, Fabio Utzig  wrote:
> > +1
> >
> > I prefer as much information in a single place as possible, and GH as been 
> > adding more and more "project management" features making it better suited 
> > as a Jira alternative (and btw, we already made this move with MCUBoot!).
> >
> > Cheers,
> > Fabio Utzig
> >
> > On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:
> >> On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:
> >> > Hi,
> >> >
> >> > Multiple people have suggested that issues be tracked on Github close
> >> > to the code. The benefit is that contributors don’t have to switch
> >> > between two systems to raise and clear issues.  Please let your
> >> > thoughts known either way.
> >>
> >> I agree with switching to github issues.
> >>
> >> Jira seems more powerful and I do like it, but I find the extra
> >> flexibility is outweighed by the difficulty of using two different
> >> systems (github for PRs, Jira for issues).
> >>
> >> Chris
> 
> 
> 
> -- 
> --
> Miguel Azevedo

Re: BLEMESH PB GATT

[Michał Narajowski]

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 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 = _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.
>
> 00 Unhandled interrupt (2), exception sp 0x20001280
> 00  r0:0x  r1:0x  r2:0x8000  r3:0xe000ed00
> 00  r4:0x00019a3f  r5:0x  r6:0x  r7:0x
> 00  r8:0x  r9:0x r10:0x r11:0x
> 00 r12:0x  lr:0x8add  pc:0x8aec psr:0x6100
> 00 ICSR:0x00421802 HFSR:0x CFSR:0x
> 00 BFAR:0xe000ed38 MMFAR:0xe000ed34
> 00 Assert @ 0x19a3f
>
>
>
>> On 23-Feb-2018, at 5:26 PM, Andrzej Kaczmarek 
>>  wrote:
>>
>> 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 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
>

Re: BLEMESH PB GATT

[Aditya Xavier]

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 = _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.

00 Unhandled interrupt (2), exception sp 0x20001280
00  r0:0x  r1:0x  r2:0x8000  r3:0xe000ed00
00  r4:0x00019a3f  r5:0x  r6:0x  r7:0x
00  r8:0x  r9:0x r10:0x r11:0x
00 r12:0x  lr:0x8add  pc:0x8aec psr:0x6100
00 ICSR:0x00421802 HFSR:0x CFSR:0x
00 BFAR:0xe000ed38 MMFAR:0xe000ed34
00 Assert @ 0x19a3f



> On 23-Feb-2018, at 5:26 PM, Andrzej Kaczmarek  
> wrote:
> 
> 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 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

BLEMESH PB GATT

[Aditya Xavier]

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.

Thanks and Regards,
Aditya Xavier