Re: mynewt roadmap and future

[Aditi Hilbert]

Hi Mike,

We used Mynewt OS + NimBLE in our first connected product offering at Juul
Labs. We decided to use it on our next connected device as well. In the
process we worked on and submitted PRs for the NimBLE controller + host
code that runs on a new Dialog chip. We hope to get that Bluetooth SIG
certified in the next few months. NimBLE has been ported to Linux,
FreeRTOS, Riot as well - so you have a few options there for the OS.

There’s a mynewt-core release planned in a month or so. The community
should be reviewing and resolving most of the outstanding PRs before that.

I should admit Juul getting “right-sized” earlier this year has limited our
activity somewhat, but we are still quite active with patches and PRs to
the mynewt suite of modules when we need them. I urge other companies who
have adopted Mynewt to speak to their experience in this thread. Slack is
the other forum where a lot of technical conversations happen.

thanks,
Aditi

On Mon, Nov 23, 2020 at 11:09 AM Mike Grobler 
wrote:

> PAX Labs has used mynewt for one of its nRF based products.  We are
> contemplating using mynewt on a new product, but before we commit, we would
> like to understand the future of mynewt.
>
> Please would someone provide a knowledgeable mynewt contact with whom we
> could have a quick 30-min meeting?
>
> --
> _
> Mike Grobler
> Firmware
> PAX Labs <https://pax.com/>
>
> mike.grob...@pax.com
>


-- 
Aditi Hilbert
Juul Labs <https://www.juullabs.com/> | 560 20th Street, San Francisco, CA
94107 |
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>[image:
photo juul labs_sig2_zpsb4y2zjwf.jpg] <https://www.juul.com>
This message and any files transmitted with it may contain information
which is confidential or privileged. If you are not the intended recipient,
please advise the sender immediately by reply e-mail and delete this
message and any attachments without retaining a copy thereof.

Re: NimBLE Stack Integration Support

[Aditi Hilbert]

Also, you need to complete your mailing list subscription by responding to
the email you get when you send the first subscribe email. Otherwise
someone in the committee has to manually approve each of your emails to the
dev@ group.

Welcome to the Mynewt community!
Aditi

On Tue, May 12, 2020 at 7:30 PM Aditi Hilbert 
wrote:

> Hi Anil,
>
> What is your board? What OS is it running? Have you checked the basic
> documentation to get you started with NimBLE and Mynewt OS on supported
> boards:
> http://mynewt.apache.org/latest/tutorials/ble/ble.html
>
> If you have to port to some other OS examples are here
> https://github.com/apache/mynewt-nimble/tree/master/porting/examples
>
> thanks,
> aditi
>
> On Tue, May 12, 2020 at 6:38 AM Anilkumar Jena 
> wrote:
>
>> Hello Sir,
>> I am planning to integrate and use NimBLE Host stack in
>> my Board. Could you please guide me the process of NimBLE stack integration
>> to the board? I am planning to use this for one of our Automotive
>> Infotainment device.
>>
>> Best Regards,
>> Anil Kumar Jena
>> Technical Lead,
>> HCL Technologies Ltd
>> ::DISCLAIMER::
>> 
>> The contents of this e-mail and any attachment(s) are confidential and
>> intended for the named recipient(s) only. E-mail transmission is not
>> guaranteed to be secure or error-free as information could be intercepted,
>> corrupted, lost, destroyed, arrive late or incomplete, or may contain
>> viruses in transmission. The e mail and its contents (with or without
>> referred errors) shall therefore not attach any liability on the originator
>> or HCL or its affiliates. Views or opinions, if any, presented in this
>> email are solely those of the author and may not necessarily reflect the
>> views or opinions of HCL or its affiliates. Any form of reproduction,
>> dissemination, copying, disclosure, modification, distribution and / or
>> publication of this message without the prior written consent of authorized
>> representative of HCL is strictly prohibited. If you have received this
>> email in error please delete it and notify the sender immediately. Before
>> opening any email and/or attachments, please check them for viruses and
>> other defects.
>> 
>>
>
>
> --
> Aditi Hilbert
> Juul Labs <https://www.juullabs.com/> | 560 20th Street, San Francisco,
> CA 94107 |
>
> <https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>
> <https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>[image:
> photo juul labs_sig2_zpsb4y2zjwf.jpg] <https://www.juul.com>
> This message and any files transmitted with it may contain information
> which is confidential or privileged. If you are not the intended recipient,
> please advise the sender immediately by reply e-mail and delete this
> message and any attachments without retaining a copy thereof.
>


-- 
Aditi Hilbert
Juul Labs <https://www.juullabs.com/> | 560 20th Street, San Francisco, CA
94107 |
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>[image:
photo juul labs_sig2_zpsb4y2zjwf.jpg] <https://www.juul.com>
This message and any files transmitted with it may contain information
which is confidential or privileged. If you are not the intended recipient,
please advise the sender immediately by reply e-mail and delete this
message and any attachments without retaining a copy thereof.

Re: NimBLE Stack Integration Support

[Aditi Hilbert]

Hi Anil,

What is your board? What OS is it running? Have you checked the basic
documentation to get you started with NimBLE and Mynewt OS on supported
boards:
http://mynewt.apache.org/latest/tutorials/ble/ble.html

If you have to port to some other OS examples are here
https://github.com/apache/mynewt-nimble/tree/master/porting/examples

thanks,
aditi

On Tue, May 12, 2020 at 6:38 AM Anilkumar Jena  wrote:

> Hello Sir,
> I am planning to integrate and use NimBLE Host stack in my
> Board. Could you please guide me the process of NimBLE stack integration to
> the board? I am planning to use this for one of our Automotive Infotainment
> device.
>
> Best Regards,
> Anil Kumar Jena
> Technical Lead,
> HCL Technologies Ltd
> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or may contain
> viruses in transmission. The e mail and its contents (with or without
> referred errors) shall therefore not attach any liability on the originator
> or HCL or its affiliates. Views or opinions, if any, presented in this
> email are solely those of the author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification, distribution and / or
> publication of this message without the prior written consent of authorized
> representative of HCL is strictly prohibited. If you have received this
> email in error please delete it and notify the sender immediately. Before
> opening any email and/or attachments, please check them for viruses and
> other defects.
> 
>


-- 
Aditi Hilbert
Juul Labs <https://www.juullabs.com/> | 560 20th Street, San Francisco, CA
94107 |
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>[image:
photo juul labs_sig2_zpsb4y2zjwf.jpg] <https://www.juul.com>
This message and any files transmitted with it may contain information
which is confidential or privileged. If you are not the intended recipient,
please advise the sender immediately by reply e-mail and delete this
message and any attachments without retaining a copy thereof.

Re: Blog post on selecting hardware for embedded protocol adapters ...

[Aditi Hilbert]

Hi Chris,

Very interesting read and a very useful project with numerous applications.
Thanks for integrating with Apache Mynewt. I think you picked the right
software elements, hardware, transport choices.

thanks,
Aditi

On Thu, Apr 16, 2020 at 12:10 AM Christofer Dutz 
wrote:

> Hi folks,
>
> sorry for cross-posting, but I think this might be interesting for some of
> you.
>
> I just published my first blog article on selecting the hardware for my
> current project of “Securing PLCs via embedded Open-Source protocol
> adapters“.
>
> Here I’ll be porting Apache PLC4X drivers to the C language and creating
> an Apache MyNewt integration to build open-source protocol adapters for
> securing the communication with industrial PLCs. But at the start I needed
> to select the hardware I would be using to do this. Being completely new in
> this area it was quite a task to compile that feature comparison matrix,
> that’s currently still on the PLC4X page, but hopefully will move to the
> MyNewt page some time soon:
>
> https://cwiki.apache.org/confluence/display/PLC4X/Creating+a+version+of+PLC4X+drivers+that+work+on+Apache+MyNewt
> Hope the one or the other might get some new info’s from it.
>
> Have fun reading:
>
> https://blog.codecentric.de/en/2020/04/selecting-hardware-embedded-development-open-source-protococol-adapters/
>
> Chris
>


-- 
Aditi Hilbert
Juul Labs <https://www.juullabs.com/> | 560 20th Street, San Francisco, CA
94107 |
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>
<https://www.juulvapor.com/skin/frontend/juul/live/images/juul-labs-logo.jpg>[image:
photo juul labs_sig2_zpsb4y2zjwf.jpg] <https://www.juul.com>
This message and any files transmitted with it may contain information
which is confidential or privileged. If you are not the intended recipient,
please advise the sender immediately by reply e-mail and delete this
message and any attachments without retaining a copy thereof.

Re: Blinky targets do not load

[Aditi Hilbert]

The docs got updated yesterday with this. I tested using the —HEAD flag to 
install openocd and run Blinky on nRF52DK.

Aditi

> On Jan 29, 2019, at 3:46 AM, Fabio Utzig  wrote:
> 
> On Fri, Jan 25, 2019, at 6:39 PM, Simon Ratner wrote:
>> Correct, the version of openocd in homebrew does not work with nRF52. 
> 
> I just tried building with:
> 
> $ brew install --HEAD open-ocd
> 
> Tested it on the Nordic PCA10056 (nrf52840-pdk), and it works.
> 
> Fabio

Re: Benchmarking of Real-Time Operating Systems for Internet of Things Devices

[aditi hilbert]

Hi Julien,

Just curious how your project is coming along. Have you decided on the 
benchmark metrics?

thanks,
Aditi 


> On Sep 21, 2018, at 1:08 AM, Julien Gomez  
> wrote:
> 
> Hello Aditi,
> 
> Thank you for your advices. I've already joined the Slack ;-) It's nice to 
> see a dev community with a modern communication channel.
> 
> Can you give more information or references about HAL performance - latency 
> and throughput of peripheral access?
> 
> Regards,
> 
> Julien
> 
> 
> Le 20/09/18 à 19:00, aditi hilbert a écrit :
>> Hi Julien and Trong-Vu,
>> 
>> Thanks for wanting to include Apache Mynewt in a comparative benchmarking 
>> across different RTOS!
>> 
>> There are lots of standard metrics that benchmark an OS kernel. Commercial 
>> RTOS such as ThreadX or Micrium tout these stats often - interrupt latency, 
>> context switching time, memory allocation/deallocation etc. These are 
>> interesting, but going beyond the kernel is probably more useful such as HAL 
>> performance - latency and throughput of peripheral access. People are also 
>> interested in power consumption/current draws for some basic operations both 
>> at kernel level and esp. at network protocol level e.g. message tx/rx etc. I 
>> am sure others in the community would have a lot of suggestions.
>> 
>> Have you joined the Mynewt workspace on Slack?
>> https://join.slack.com/t/mynewt/shared_invite/enQtMTkwMTg1ODM1NTg5LTY0ZjgxNmFjNzBjZmRlZDdlYmM4MGUzNDdkNDQ1NDE0OWRlYWE4ODM1OWQ1Mjg1YmM1NDJmODNkNDA4NGJmODY
>> 
>> thanks,
>> aditi
>> 
>>> On Sep 20, 2018, at 7:45 AM, Julien Gomez 
>>>  wrote:
>>> 
>>> Hello Apache Mynewt community !
>>> 
>>> We are two students of the Université catholique de Louvain from Belgium 
>>> and we work on our master thesis. The thesis is called "Benchmarking of 
>>> Real-Time Operating Systems for Internet of Things Devices" and is about 
>>> comparing the different implementations of open-source RTOS's currently 
>>> available on the market.
>>> 
>>> In broad outline, we are planning to analyze the scheduling, switching 
>>> context, memory management and/or any relevant metric dependant of the 
>>> operating system.
>>> 
>>> Another goal is to compare networking performances or implementations of 
>>> the various stacks available. We have currently no concrete planning for 
>>> this part.
>>> 
>>> This project will be open source (because we <3 the open source).
>>> 
>>> Here are some questions we have for you:
>>> - "What would you like to see in this benchmarking project?";
>>> - "What RTOS should we benchmark?";
>>> - "What metric should we consider?".
>>> 
>>> We'd love to hear your recommandations or any help you can provide us with.
>>> 
>>> Also if you are interested about how the project will evolve, we'll be glad 
>>> to update you on our progress.
>>> 
>>> If the project gain lot of interests, we will probably create a 
>>> communication channel like Slack or Gitter.
>>> 
>>> Sincerely,
>>> Julien Gomez and Trong-Vu Tran
>>> 
> 

Re: Linux port of NimBLE BLE Stack question

[aditi hilbert]

Hi Husam,

Have you checked out the port already available?
https://github.com/apache/mynewt-nimble/tree/master/porting/npl/linux 


thanks,
aditi

> On Nov 1, 2018, at 11:00 AM, Husam Elfadil  wrote:
> 
> Dear NimBLE Support,
> 
> I read about the NimBLE BLE stack and it looks interesting. I'm trying to 
> port it to Linux and just play with it a little bit and see how it works. 
> However, I had trouble in getting started with the porting process as there 
> is not much information on how to do it for Linux. Could you briefly give a 
> steps to do the porting of the stack to Linux and run some of your sample 
> apps. Please not that I'm working with a 64-bit Ubuntu 18.04. I appreciate 
> your help.
> 
> Best Regards,
> Husam

Re: [VOTE] Release Apache Mynewt 1.5.0-rc1

[aditi hilbert]

+1 (binding)

Aditi

> On Oct 23, 2018, at 7:20 AM, Szymon Janc  wrote:
> 
> Hello all,
> 
> I am pleased to be calling this vote for the source release of
> Apache Mynewt 1.5.0.
> 
> Apache Mynewt is a community-driven, permissively licensed open source
> initiative for constrained, embedded applications. Mynewt provides a
> real-time operating system, flash file system, network stacks, and
> support utilities for real-world embedded systems.
> 
> For full release notes, please visit the Apache Mynewt Wiki:
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes
> 
> This release candidate was tested as follows:
>  1. Manual execution of the Mynewt test plan:
> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test
> +Plan
> The test results can be found at:
> https://cwiki.apache.org/confluence/display/MYNEWT/1.5.0+Test+Results
> 
> Note that this testing is not yet complete and more results will show 
> while voting is ongoing.
> 
>  2. The full unit test suite for this release was executed via "newt
> test all" with no failures.  This testing was performed on the
> following platforms:
>   * OS X 10.13
>   * Fedora Linux 28
> 
> 
> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.5.0/rc1/
> 
> The commits under consideration are as follows:
> blinky:
>  repos: https://github.com/apache/mynewt-blinky
>  commit a94cfa402da18a305db2ea9afa3771ead69968fe
> core:
>  repos: https://github.com/apache/mynewt-core
>  commit e311e78e59e71aae72679b76baea8fd9e2aa18e8
> newt:
>  repos: https://github.com/apache/mynewt-newt
>  commit d8b903e11abbfe854e6601de016e755ad307a2b0
> newtmgr:
>  repos: https://github.com/apache/mynewt-newtmgr
>  commit d38f17df9143be4729f33572fa78fe276ac09af7
> 
> In addition, the following newt convenience binaries are available:
>  linux: https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.5.0/
> rc1/apache-mynewt-newt-bin-linux-1.5.0.tgz
>  osx: https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.5.0/rc1/
> apache-mynewt-newt-bin-osx-1.5.0.tgz
>  windows: https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.5.0/
> rc1/apache-mynewt-newt-bin-windows-1.5.0.tgz
> 
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/mynewt/KEYS
> 
> The vote is open for at least 72 hours and passes if a majority of at
> least three +1 PMC votes are cast.
> 
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
> 
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes.
> 
> A separate [DISCUSS] thread will be opened to talk about this release
> candidate.
> 
> -- 
> pozdrawiam
> Szymon Janc
> 
> 

Re: newtmgr

[aditi hilbert]

Hi Timo,

That is correct - currently, newtmgr is only point to point capable. It is 
possible to extend it to work over mesh and that would be useful ... but such 
functionality is not planned for a release yet.

thanks,
aditi

> On Aug 7, 2018, at 4:55 AM, Timo Kolthoff  wrote:
> 
> Hi,
> 
> Is it correct that newtmgr is only ble point to point capable, so no
> ble mesh support? Is it something that has been concidered or possible
> to be implemented?
> 
> This implies that there will not be support for log fetching,
> statistics or software upgrading in a ble mesh network? Is this
> something that will be solved in the mesh networking specifications?
> 
> If so, does anybody know when one could expect a release of this
> functionality?
> 
> /BR

Re: Hello!

[aditi hilbert]

Welcome to the Apache Mynewt community, Mehul! 

Aditi

> On Jul 17, 2018, at 8:21 PM, Mehul Hirpara  
> wrote:
> 
> Hello There,
> 
> 
> This is Mehul Hirpara from Ineda Systems Pvt Ltd, Hyderabad, India and I am 
> joining the community as a user and contributor of NimBLE.
> 
> 
> Thanks & Regards,
> 
> Mehul Hirpara
> 
> 
> 
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed. If 
> you have received this email in error please notify the system manager. This 
> message contains confidential information and is intended only for the 
> individual named. If you are not the named addressee you should not 
> disseminate, distribute or copy this e-mail. Please notify the sender 
> immediately by e-mail if you have received this e-mail by mistake and delete 
> this e-mail from your system. If you are not the intended recipient you are 
> notified that disclosing, copying, distributing or taking any action in 
> reliance on the contents of this information is strictly prohibited.

Re: [VOTE] Release Apache Mynewt 1.4.1-rc1

[aditi hilbert]

+1 binding

> On Jun 26, 2018, at 10:58 AM, Sterling Hughes 
>  wrote:
> 
> +1 binding
> 
> On 26 Jun 2018, at 10:45, Fabio Utzig wrote:
> 
>> +1 (binding)
>> 
>> On Fri, Jun 22, 2018, at 11:14 AM, Szymon Janc wrote:
>>> Hello all,
>>> 
>>> I am pleased to be calling this vote for the source release of
>>> Apache Mynewt 1.4.1.
>>> 
>>> Apache Mynewt is a community-driven, permissively licensed open source
>>> initiative for constrained, embedded applications. Mynewt provides a
>>> real-time operating system, flash file system, network stacks, and
>>> support utilities for real-world embedded systems.
>>> 
>>> This is a bugfix only release fixing BLE connection creation in central role
>>> on Nordic nRF51, flashing issues on Nordic nRF52840 and building errors on
>>> Windows for newt and newtmgr tools.
>>> 
>>> For full release notes, please visit the Apache Mynewt Wiki:
>>> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes
>>> 
>>> This release candidate was tested as follows:
>>>  1. Manual execution of the Mynewt test plan:
>>> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test
>>> +Plan
>>> The test results can be found at:
>>> https://cwiki.apache.org/confluence/display/MYNEWT/1.4.1+Test+Results
>>> 
>>> Note that only features affected by bugfixes were tested for this
>>> release. If you feel more testing is needed please provide your results 
>>> here.
>>> 
>>>  2. The full unit test suite for this release was executed via "newt
>>> test all" with no failures.  This testing was performed on the
>>> following platforms:
>>>   * OS X 10.13
>>>   * Ubuntu Linux 18.04
>>> 
>>> 
>>> The release candidate to be voted on is available at:
>>> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.4.1/rc1/
>>> 
>>> The commits under consideration are as follows:
>>> blinky:
>>>  repos: https://github.com/apache/mynewt-blinky
>>>  commit bb43247a7e28a1f5e5d869f1088cb4ae53a1
>>> core:
>>>  repos: https://github.com/apache/mynewt-core
>>>  commit f0ce13e45c51825c35963fb13f2562d5911ef1ed
>>> newt:
>>>  repos: https://github.com/apache/mynewt-newt
>>>  commit ac0db20a10ea042e253012c30b6261d722e11093
>>> newtmgr:
>>>  repos: https://github.com/apache/mynewt-newtmgr
>>>  commit 4d5d517d2a99c2f2c4b322e872714ea702c1a88f
>>> 
>>> In addition, the following newt convenience binaries are available:
>>>  linux: https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.4.1/
>>> rc1/apache-mynewt-newt-bin-linux-1.4.1.tgz
>>>  osx: https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.4.1/rc1/
>>> apache-mynewt-newt-bin-osx-1.4.1.tgz
>>> 
>>> The release candidate is signed with a GPG key available at:
>>> https://dist.apache.org/repos/dist/dev/mynewt/KEYS
>>> 
>>> The vote is open for at least 72 hours and passes if a majority of at
>>> least three +1 PMC votes are cast.
>>> 
>>> [ ] +1 Release this package
>>> [ ]  0 I don't feel strongly about it, but don't object
>>> [ ] -1 Do not release this package because...
>>> 
>>> Anyone can participate in testing and voting, not just committers,
>>> please feel free to try out the release candidate and provide your
>>> votes.
>>> 
>>> A separate [DISCUSS] thread will be opened to talk about this release
>>> candidate.
>>> 
>>> -- 
>>> pozdrawiam
>>> Szymon Janc
>>> 
>>> 

Re: Bluetooth certification

[aditi hilbert]

Hi David,

Runtime has qualified the NimBLE host stack just released (version 1.0.0). The 
QDID is 64 and you can use it for your product listing.
https://launchstudio.bluetooth.com/ListingDetails/59050 


Runtime is in the process of qualifying the Apache Mynewt NimBLE controller for 
nRF52832 and the listing is currently expected sometime in July. 
If the code undergoing testing (version 1.0.0) requires fixes for the 
qualification, there will be a new release.

thanks,
aditi

> On Jun 18, 2018, at 2:12 PM, david zuhn  wrote:
> 
> What is the current state of Bluetooth Certification for the MyNewt/NimBLE
> stack?
> 
> I'm looking at the need for certification(s) to get a device to market, and
> using an already FCC certified hardware module (based on nRF52) seems to
> solve one side of the problem.   The software is another case:  I'd love to
> be able to use an already certified version of NimBLE - which should be
> easy enough since I'm not in need of making any changes to the BLE stack at
> all.
> 
> Now I understand why some people go through the pain of the Nordic SDK --
> use of the pre-certified Softdevice looks to make the device certification
> *MUCH* simpler.
> 
> david zuhn
> very early in the startup phase (read: $$$?  what's that?)
> 
> 
> -- 
> The State Belt Railway of California
> zoo @ statebeltrailway.org

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: Sample apps in mynewt-core

[aditi hilbert]

Lukasz,

Yes - great addition!

thanks,
aditi

> On Mar 20, 2018, at 8:16 AM, Lukasz Wolnik <lukasz.wol...@gmail.com> 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 <ad...@runtime.io> 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

Sample apps in mynewt-core

[aditi hilbert]

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: Apache Mynewt release 1.4

[aditi hilbert]

Hi Andrzej.

> On Feb 8, 2018, at 2:29 AM, Andrzej Kaczmarek <andrzej.kaczma...@codecoup.pl> 
> wrote:
> 
> Hi,
> 
> On Thu, Feb 8, 2018 at 12:32 AM, aditi hilbert <ad...@runtime.io> wrote:
> 
>> Hi all,
>> 
>> There has been a lot of feature additions and bug fixes since our last
>> release on Dec 13, 2018.
>> I’d like to propose we try to get a release out in two weeks (Feb 21st).
>> Below are some of the things we have added:
>> 
>> * Fixes for NimBLE 5 and Mesh issues found at upf59 last week
>> * Fixes for NimBLE 5 issues found during BT certification testing
>> 
> 
> Also we'll have support for advertising data fragmentation (i.e.
> AUX_CHAIN_IND) which was successfully tested on UPF59 and hopefully will be
> merged soon: https://github.com/apache/mynewt-core/pull/770
> 
> 
>> * NimBLE port to freeRTOS kernel
>> 
> 
> ​This is actually being worked on in separate repository (mynewt-nimble) so
> we now have two separate repositories with Nimble code. The goal is to have
> mynewt-nimble as the only repository with Nimble code and build Mynewt with
> that code. I think it would make sense to aim for completing this split
> after current release so we can develop Nimble in one place and also start
> raising issues on GitHub for proper repository. If this makes sense, I can
> send separate e-mail for discussion later.
> 

Yes, I agree it makes sense to wait until after 1.4 release. There are a couple 
of 
other modules that are in a similar situation (mcuboot, mcumgr) and we probably 
need 
a plan for the migration/deprecation. For example, make Mynewt use the existing 
Nimble 
code in -core as default in 1.5 but be able to use code in -nimble if so 
configured. 
Then make -nimble default the following release onwards. 

Looking forward to your email!

thanks,
aditi

>> * LoRa enhancements (e.g. config variable to distinguish boards with and
>> without antenna switch)
>> * Support for additional hardware: Cortex M3 (STM32L152), ARCv2
>> architecture
>> * Update supported tools e.g. STM32Cube
>> * Additional sensor support: DRV2605L haptic driver for LRA and ERM
>> * Port of image manager to other non-Mynewt OS
>> * Newt tool bug fixes and minor features
>> 
>> This means we get a release candidate out next week. Can we get one out by
>> Feb 15th?
>> 
>> thanks,
>> Aditi
> 
> 
> ​Best regards,
> Andrzej​

Re: Draft board report

[aditi hilbert]

Hi Justin,

I am doing an Apache Mynewt workshop today at ESC (Embedded Silicon Valley 
Conference) in San Jose. We’ve exhibited Apache Mynewt in action at conferences 
as well such as ARM TechCon (end of Oct) and Bluetooth Asia (end of Sept). 

thanks,
aditi

> On Dec 3, 2017, at 7:05 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Here’s the draft board report can anyone think of anything to add under 
> activity or any other suggestions? Has there been any conference talks or the 
> like? I gave a Mynewt talk at IoT Sydney to 50 or so people but that’s hardly 
> significant news :-)
> 
> 
> Mynewt is a real-time operating system for constrained embedded systems like 
> wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit 
> MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS 
> architectures.
> 
> ## Issues:
> 
> A couple of "category X" files (4-clause BSD files) were found in a release 
> candidate. The issue is being felt with.
> 
> ## Activity:
> - Community work in serval areas including working on new 1.3 releases, 
> improved documentation, updated security libraries and sensor support
> 
> ## Health report
> - PMC and committers are active
> - Users questions and contributor's pull requests are quickly dealt with
> 
> ## PMC changes:
> - Currently 19 PMC members
> - Last PMC addition was everyone on 21st June
> - No new PMC members added this reporting period
> 
> ## Committer base changes:
> - Currently 24 committers
> - One new committer voted on and added since last report
> - Miguel Azevedo on Sun Sep 17 2017
> 
> ## Releases:
> - 1.2 was released on September 12th 2017
> - voting on 1.3 release candidates is currently underway 
> 
> ## Mailing list activity:
> - Mailing list activity is mainly around BLE, Lora and new releases
> - Mailing list activity up slightly over previous 3 months
> - Slack channel activity up significantly and users up 50% from 3 month ago
> 
> ## JIRA activity:
> -  JIRAs activity down over previous 3 month
> 
> Thanks,
> Justin
> 

Next release of Apache Mynewt

[aditi hilbert]

Hi all,

There’s been quite a lot of activity on mynewt-core since the last release. The 
general plan was to do release 1.3 in December but I suggest we release the 
next point release (minor release) sooner than that to keep testing of features 
up to date and encourage adoption of recent features by the community of users.

Some of the features already implemented for the upcoming release 1.3 are 
listed here. It is by no means an exhaustive list, so feel free to add features 
that you are working on but don’t see included.
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Roadmap 


To target an end of Nov release date we would have to release the candidate on 
Nov 27th, if not earlier. Any red flags?

thanks,
aditi

Re: BLE Host - Removing the BLE_GAP_EVENT_CONN_CANCEL event type

[aditi hilbert]

> On Oct 25, 2017, at 6:46 PM, Christopher Collins  wrote:
> 
> On Thu, Oct 19, 2017 at 12:07:58PM -0700, Christopher Collins wrote:
>> On Fri, Oct 13, 2017 at 10:18:14AM -0700, Christopher Collins wrote:
>>> * Because this is an API change, it would be best to introduce it
>>>  slowly.  The `BLE_GAP_CONN_CANCEL` event would be marked deprecated in
>>>  the next release, and then removed entirely in the one after that.
>> 
>> After some discussion in the pull request page
>> (https://github.com/apache/mynewt-core/pull/632), I'm not sure it makes
>> sense to try to slowly "phase out" this behavior.  Since this change
>> represents a change in behavior, rather than the removal of
>> functionality, I don't think there is a good way to deprecate it.  The
>> two basic options are:
>> 
>> 1. Keep deprecated symbols in the code base, but stop using them.  Apps
>> will continue to build without errors, but any app relying on the old
>> behavior will silently break.
>> 
>> 2. Remove unused symbols.  This may introduce build errors for some
>> apps, but at least there is no silent breakage.
>> 
>> We could also try some hybrid approach, e.g., send both types of GAP
>> events when a connection is cancelled.  However, I think this would do
>> more harm than good (and probably introduce some new bugs!).
>> 
>> The release policy document's section on backwards compatibility
>> (https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy#ReleaseandSupportPolicy-BackwardsCompatibility)
>> is pretty clear - if an API change has the potential to break builds,
>> deprecate the old behavior for at least six months before removing it.
>> I think this text needs some additional language for changes such as
>> this one that can't be reasonably phased in.
> 
> I propose we add the following text to the release policy:
> 
>Sometimes it is impossible or impractical to retain a deprecated
>version of an API alongside the new one.  For example, a change to
>a callback function's type, such as the addition of a new parameter,
>is difficult to introduce while still maintaining the old API.  For
>these types of changes, the `deprecated` state can be bypassed.
>Such changes must be voted on by the community before they are
>implemented.
> 

+1

> If there are no objections, I will make this addition to the wiki.
> 
> Thanks,
> Chris

Re: [VOTE] Release Apache Mynewt 1.2.0-rc1

[aditi hilbert]

+1

thanks,
aditi

> On Sep 8, 2017, at 11:54 AM, Szymon Janc  wrote:
> 
> Hello all,
> 
> I am pleased to be calling this vote for the source release of
> Apache Mynewt 1.2.0.
> 
> Apache Mynewt is a community-driven, permissively licensed open source
> initiative for constrained, embedded applications. Mynewt provides a
> real-time operating system, flash file system, network stacks, and
> support utilities for real-world embedded systems.
> 
> For full release notes, please visit the Apache Mynewt Wiki:
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes
> 
> This release candidate was tested as follows:
>  1. Manual execution of the Mynewt test plan:
> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
> The test results can be found at:
> https://cwiki.apache.org/confluence/display/MYNEWT/1.2.0+Test+Results
>  2. The full unit test suite for this release was executed via "newt
> test all" with no failures.  This testing was performed on the
> following platforms:
>   * OS X 10.11.5
>   * Ubuntu Linux 17.04
> 
> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.2.0/rc1/
> 
> The commits under consideration are as follows:
> blinky:
>  repos: https://github.com/apache/mynewt-blinky
>  commit 5ade7990e81ebfb6b9801fd56b7ea32774747ced
> core:
>  repos: https://github.com/apache/mynewt-core
>  commit e511aa733ee0d5740484738036618332ed45475b
> newt:
>  repos: https://github.com/apache/mynewt-newt
>  commit 3a3e87d754e63cbcf2e49b49c20847dc3c19e655
> newtmgr:
>  repos: https://github.com/apache/mynewt-newtmgr
>  commit 8bc55635bbac12c036b25b4968ee0f48c1f06e52
> 
> In addition, the following newt convenience binaries are available:
>  linux: 
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.2.0/rc1/apache-mynewt-bin-linux-1.2.0.tgz
>  osx: 
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.2.0/rc1/apache-mynewt-bin-osx-1.2.0.tgz
> 
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/mynewt/KEYS
> 
> The vote is open for at least 72 hours and passes if a majority of at
> least three +1 PMC votes are cast.
> 
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
> 
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes.
> 
> A separate [DISCUSS] thread will be opened to talk about this release
> candidate.
> 
> Thanks,
> Szymon Janc
> 

Re: Separate repository for NFFS

[aditi hilbert]

> On Aug 31, 2017, at 8:15 AM, David Brown  wrote:
> 
> BTW, can someone please remove the !@#$ Reply-to header in the apache
> mailing lists?  It completely breaks messages that are cross posted,
> effectively stealing all replies from all other mailing lists, as well
> as from anyone that was CC'd that doesn't happen to be on the Apache
> mailing list.
> 
> On Wed, Aug 30, 2017 at 10:08:50PM +0200, Andrzej Kaczmarek wrote:
> 
>> I'm now porting NFFS code to Zephyr and in order to avoid forking this
>> code into two separate projects I'd like to propose to move NFFS code into
>> its own repository (i.e. mynewt-nffs) and basically make it a bit more
>> generic so it can be used by other projects.
> 
> I think this is a good idea.  We'll need to figure out what project to
> host it under.
> 

Just as MCUboot was pulled out into a separate repository hosted under 
runtimeco,
perhaps NFFS could have its own repo there as well? Happy to copy that over.

thanks,
aditi

>> In case of Mynewt, there's not much to do since everything is already
>> implemented and just needs to be copied from one place to another. The API
>> can be polished over time and memory usage (heap vs. static) can be made
>> configurable.
> 
> Mynewt has the distinct advantage of its build system being able to
> pull code in from other repos.  This is nice because it means this
> separation isn't difficult to do.
> 
>> Of course the new repository would be compatible with Mynewt ootb, the
>> changes in code are to make "copying" it to other OS-es as straightforward
>> as possible so code can be updated to new release easily.
> 
> Is your intent then to just drop this code into the Zephyr repository
> (probably under 'ext') and manually keeping it up to date, like is
> done now.
> 
> We should probably bring this up on the Zephyr mailing list as well.
> Unless the Reply-to problem is fixed with the Mynewt mailing lists,
> you should probably just send it to that list (right now, the Mynewt
> mailing list will steal any other address you To or Cc a message to,
> redirecting all replies only to that list).
> 
> David

Re: Mynewt Logo

[aditi hilbert]

I put a .svg image as well at the request of Martin Turon. Please try that.

thanks,
aditi


> On Aug 14, 2017, at 8:58 AM, Fabio Utzig <ut...@apache.org> wrote:
> 
> I tried with the Logo with Apache's Logo at the left but it looks
> distorted for the typical Logo res format on Wikipedia. I tried moving
> the logo to the right where there's a lot of empty space. The result:
> 
> https://en.wikipedia.org/wiki/Apache_Mynewt#/media/File:Apache_Mynewt_Logo.png
> 
> On Mon, Aug 14, 2017, at 12:09 PM, aditi hilbert wrote:
>> I have placed a vector image (with updated feather) for download as well
>> as a .png on the project cwiki:
>> 
>> https://cwiki.apache.org/confluence/display/MYNEWT/Logo
>> <https://cwiki.apache.org/confluence/display/MYNEWT/Logo>
>> 
>> thanks,
>> aditi
>> 
>> 
>>> On Aug 14, 2017, at 7:55 AM, Todd Mitton <mit...@runtime.io> wrote:
>>> 
>>> There's also this svg version. It has the old feather though.
>>> 
>>> http://mynewt.apache.org/img/logo.svg
>>> 
>>> -Todd
>>> 
>>> On Mon, Aug 14, 2017 at 7:38 AM, Alfred Schilken <alf...@schilken.de> wrote:
>>> 
>>>> Hi Justin -  that sounds great!
>>>> 
>>>> Can you tell more ?
>>>> 
>>>> Where and when  - I know, it’s unofficial
>>>> 
>>>> I’m living in Germany - may be I can help somehow.
>>>> 
>>>> Regards
>>>> Alfred
>>>> 
>>>> EDV-Beratung Schilken
>>>> alf...@schilken.de
>>>> www.schilken.de
>>>> mobil: +49 178 1475677
>>>> 
>>>>> Am 14.08.2017 um 15:30 schrieb Justin Mclean <jus...@classsoftware.com>:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> Do we have a hi res vector versions of the logo available anywhere?
>>>>> 
>>>>> I’m going to be speaking at a conference in Germany on Mynewt (not
>>>> officially announced yet) and want to organise some stickers.
>>>>> 
>>>>> Thanks,
>>>>> Justin
>>>> 
>>>> 
>>