Re: [ANNOUNCE] NimBLE code moved to separate repository

[Simon Ratner]

Heads up - make sure you clean your targets after upgrading.

For some reason the newt tool is unable to detect that the files have
changed, perhaps because they are at a new path; had fun debugging
exceptions in the data segment because of mismatched compilation units 

Cheers,
simon

On Mar 16, 2018 02:09, "Andrzej Kaczmarek" 
wrote:

> Hi all,
>
> A few minutes ago I merged
> https://github.com/apache/mynewt-core/pull/907 which removed NimBLE
> code from mynewt-core repository. NimBLE code can be now found in
> mynewt-nimble  repository https://github.com/apache/mynewt-nimble
> which has complete history of NimBLE files imported with extra
> information about original commit id.
>
> Mynewt-core repository is configured with dependency to new
> mynewt-nimble repository - this requires new "newt" version which will
> be part of 1.4 release or if you work with master, please build "newt"
> from current master and then upgrade project with "newt upgrade".
>
> To make migration seamless, all @apache-mynewt-core/net/nimble/*
> packages have dependency created to corresponding packages in
> @apache-mynewt-nimble. This is a temporary solution and we'll probably
> remove this in one of future releases (for sure not in 1.4).
>
> Soon we will also close all pending PRs which touch NimBLE code (there
> are only few of them) asking authors to port them to new repository.
>
> Best regards,
> Andrzej
>

Re: Convenience header: mynewt.h

[Vipul Rahane]

Sounds good.

+1 

- Vipul

> On Mar 21, 2018, at 3:45 PM, Wayne Keenan  wrote:
> 
> +1
> 
> Sent from my iPhone
> 
>> On 21 Mar 2018, at 20:15, aditi hilbert  wrote:
>> 
>> +1
>> 
>> aditi
>> 
>>> On Mar 21, 2018, at 10:47 AM, Christopher Collins  wrote:
>>> 
>>> Hello all,
>>> 
>>> I was thinking about adding a new header to the core repo that just
>>> includes the (more or less) mandatory headers:
>>> 
>>>  * syscfg/syscfg.h
>>>  * sysinit/sysinit.h
>>>  * os/os.h
>>>  * defs/error.h
>>> 
>>> The rule of thumb would be: just include "mynewt.h" in every file.  I
>>> think this would make an application developer's job easier, and
>>> simplify the introduction to Mynewt.
>>> 
>>> Thoughts?
>>> 
>>> Thanks,
>>> Chris
>> 

Re: Convenience header: mynewt.h

[Wayne Keenan]

+1

Sent from my iPhone

> On 21 Mar 2018, at 20:15, aditi hilbert  wrote:
> 
> +1
> 
> aditi
> 
>> On Mar 21, 2018, at 10:47 AM, Christopher Collins  wrote:
>> 
>> Hello all,
>> 
>> I was thinking about adding a new header to the core repo that just
>> includes the (more or less) mandatory headers:
>> 
>>   * syscfg/syscfg.h
>>   * sysinit/sysinit.h
>>   * os/os.h
>>   * defs/error.h
>> 
>> The rule of thumb would be: just include "mynewt.h" in every file.  I
>> think this would make an application developer's job easier, and
>> simplify the introduction to Mynewt.
>> 
>> Thoughts?
>> 
>> Thanks,
>> Chris
> 

Re: Convenience header: mynewt.h

[aditi hilbert]

+1

aditi

> On Mar 21, 2018, at 10:47 AM, Christopher Collins  wrote:
> 
> Hello all,
> 
> I was thinking about adding a new header to the core repo that just
> includes the (more or less) mandatory headers:
> 
>* syscfg/syscfg.h
>* sysinit/sysinit.h
>* os/os.h
>* defs/error.h
> 
> The rule of thumb would be: just include "mynewt.h" in every file.  I
> think this would make an application developer's job easier, and
> simplify the introduction to Mynewt.
> 
> Thoughts?
> 
> Thanks,
> Chris

Re: Convenience header: mynewt.h

[Fabien Lepoutre]

+1

On Wed, Mar 21, 2018 at 12:12 PM, Miguel Azevedo 
wrote:

> +1
>
> On Wed, Mar 21, 2018 at 4:47 PM, Fabio Utzig  wrote:
> > +1
> >
> > On Wed, Mar 21, 2018, at 2:47 PM, Christopher Collins wrote:
> >> Hello all,
> >>
> >> I was thinking about adding a new header to the core repo that just
> >> includes the (more or less) mandatory headers:
> >>
> >> * syscfg/syscfg.h
> >> * sysinit/sysinit.h
> >> * os/os.h
> >> * defs/error.h
> >>
> >> The rule of thumb would be: just include "mynewt.h" in every file.  I
> >> think this would make an application developer's job easier, and
> >> simplify the introduction to Mynewt.
> >>
> >> Thoughts?
> >>
> >> Thanks,
> >> Chris
>
>
>
> --
> --
> Miguel Azevedo
>

Re: Convenience header: mynewt.h

[Miguel Azevedo]

+1

On Wed, Mar 21, 2018 at 4:47 PM, Fabio Utzig  wrote:
> +1
>
> On Wed, Mar 21, 2018, at 2:47 PM, Christopher Collins wrote:
>> Hello all,
>>
>> I was thinking about adding a new header to the core repo that just
>> includes the (more or less) mandatory headers:
>>
>> * syscfg/syscfg.h
>> * sysinit/sysinit.h
>> * os/os.h
>> * defs/error.h
>>
>> The rule of thumb would be: just include "mynewt.h" in every file.  I
>> think this would make an application developer's job easier, and
>> simplify the introduction to Mynewt.
>>
>> Thoughts?
>>
>> Thanks,
>> Chris



-- 
--
Miguel Azevedo

Convenience header: mynewt.h

[Christopher Collins]

Hello all,

I was thinking about adding a new header to the core repo that just
includes the (more or less) mandatory headers:

* syscfg/syscfg.h
* sysinit/sysinit.h
* os/os.h
* defs/error.h

The rule of thumb would be: just include "mynewt.h" in every file.  I
think this would make an application developer's job easier, and
simplify the introduction to Mynewt.

Thoughts?

Thanks,
Chris

[GitHub] sdalu opened a new pull request #12: ble service: Device Information Service

[GitBox]

sdalu opened a new pull request #12: ble service: Device Information Service
URL: https://github.com/apache/mynewt-nimble/pull/12
 
 
   See: https://github.com/apache/mynewt-core/pull/901


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] rymanluk commented on a change in pull request #11: mesh: Add example implementation of generic onoff and level models

[GitBox]

rymanluk commented on a change in pull request #11: mesh: Add example 
implementation of generic onoff and level models
URL: https://github.com/apache/mynewt-nimble/pull/11#discussion_r176059882
 
 

 ##
 File path: nimble/host/mesh/src/light_model.h
 ##
 @@ -0,0 +1,25 @@
+/*
+ * Copyright (c) 2017 Intel Corporation
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ */
+#ifndef __BT_MESH_LIGHT_MODEL_H
+#define __BT_MESH_LIGHT_MODEL_H
+
+#include "mesh/mesh.h"
 
 Review comment:
   don't we need #include "syscfg/syscfg.h" ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Sample apps in mynewt-core

[Lukasz Wolnik]

Hi Łukasz,

Thanks for the tip! I'll try it out.

Kind regards,
Łukasz

On Wed, Mar 21, 2018 at 9:09 AM, Łukasz Rymanowski <
lukasz.rymanow...@codecoup.pl> wrote:

> Hi Łukasz,
>
> If your application supports pairing (like btshell for example), you
> will get Secure Connections  by setting MYNEWT_VAL BLE_SM_SC to 1.
> It is stack who handles it for you then.
>
> Hope that helps.
>
> Best regards
> Łukasz
>
> On 20 March 2018 at 19:11, aditi hilbert  wrote:
> > Lukasz,
> >
> > Yes - great addition!
> >
> > thanks,
> > aditi
> >
> >> On Mar 20, 2018, at 8:16 AM, Lukasz Wolnik 
> wrote:
> >>
> >> Hi Aditi,
> >>
> >> Could we also add a sample app that uses NimBLE's Secure Connections
> please?
> >>
> >> Kind regards,
> >> Lukasz
> >>
> >> On Tue, Mar 20, 2018 at 1:11 AM, aditi hilbert 
> wrote:
> >>
> >>> Hi all,
> >>>
> >>> We have been adding a lot of features and functionality in Apache
> Mynewt
> >>> recently. Sample apps make it easy to see how to use them; so adding
> some
> >>> sample apps would be much appreciated. Here's an initial list of sample
> >>> apps that we could add. Please respond if you wish to contribute one
> or add
> >>> to the list. And I think we should add a README.md for every app in the
> >>> repo.
> >>>
> >>> * PWM - control LED brightness
> >>> * ADC, UART - read voltage on ADC, print value to UART
> >>> * ADC, I2C - read out an ADC over I2C
> >>> * Expose a resource by enabling a CoAP server
> >>> * CoAP, LoRa - enable CoAP client on one LoRa node, CoAP server on
> >>> another, retrieve a resource value
> >>> * Cycle through available power states (deep sleep, low power etc.)
> >>> * Sensor - change sampling rate
> >>> * Sensor - read multiple I2C sensors simultaneously
> >>> * Sensor - trigger a notification when a threshold is crossed
> >>> * Logging, Sensor - enable FCB to log timestamped sensor data
> >>> * MMC, SPI, stats - write system stats to the card, read back
> >>> * testutil - adding a test for a package in sim using the testutil
> >>> framework
> >>> * sensor, testutil - how to add a test for a sensor HW using the
> testutil
> >>> framework
> >>>
> >>> thanks,
> >>> Aditi
> >
>

Re: Sample apps in mynewt-core

[Łukasz Rymanowski]

Hi Łukasz,

If your application supports pairing (like btshell for example), you
will get Secure Connections  by setting MYNEWT_VAL BLE_SM_SC to 1.
It is stack who handles it for you then.

Hope that helps.

Best regards
Łukasz

On 20 March 2018 at 19:11, aditi hilbert  wrote:
> Lukasz,
>
> Yes - great addition!
>
> thanks,
> aditi
>
>> On Mar 20, 2018, at 8:16 AM, Lukasz Wolnik  wrote:
>>
>> Hi Aditi,
>>
>> Could we also add a sample app that uses NimBLE's Secure Connections please?
>>
>> Kind regards,
>> Lukasz
>>
>> On Tue, Mar 20, 2018 at 1:11 AM, aditi hilbert  wrote:
>>
>>> Hi all,
>>>
>>> We have been adding a lot of features and functionality in Apache Mynewt
>>> recently. Sample apps make it easy to see how to use them; so adding some
>>> sample apps would be much appreciated. Here's an initial list of sample
>>> apps that we could add. Please respond if you wish to contribute one or add
>>> to the list. And I think we should add a README.md for every app in the
>>> repo.
>>>
>>> * PWM - control LED brightness
>>> * ADC, UART - read voltage on ADC, print value to UART
>>> * ADC, I2C - read out an ADC over I2C
>>> * Expose a resource by enabling a CoAP server
>>> * CoAP, LoRa - enable CoAP client on one LoRa node, CoAP server on
>>> another, retrieve a resource value
>>> * Cycle through available power states (deep sleep, low power etc.)
>>> * Sensor - change sampling rate
>>> * Sensor - read multiple I2C sensors simultaneously
>>> * Sensor - trigger a notification when a threshold is crossed
>>> * Logging, Sensor - enable FCB to log timestamped sensor data
>>> * MMC, SPI, stats - write system stats to the card, read back
>>> * testutil - adding a test for a package in sim using the testutil
>>> framework
>>> * sensor, testutil - how to add a test for a sensor HW using the testutil
>>> framework
>>>
>>> thanks,
>>> Aditi
>