Re: Trying to build simple ble application fails

[Szymon Janc]

Hi,

What version do you use? This setting was defunct in NimBLE 1.5 ?
Also please share your repo and target configuration

newt info
newt target show ble_tgt1



On Tue, 11 Jun 2024 at 05:59, Ujjval Rathod 
wrote:

> Hi,
>
> When I try to build a simple BLE application it fails with following error
>
>
> *Building target targets/ble_tgt1Error: Config for package
> @apache-mynewt-nimble/nimble/transport: setting BLE_HCI_EVT_BUF_SIZE does
> not have required value field*
>
> What is this error and how to solve this? Internet search did not have that
> much content.
>
> Regards,
> Ujjval
>


-- 
pozdrawiam
Szymon K. Janc

Re: Personal Feedback on your last vote

[Szymon Janc]

Hi,

Yeah, I've noticed that. I think this is due to how gmail handles
email threads with same topic...
On our next voting I'll make sure to change voting topic a bit so that
gmail clients are not confused



On Wed, 17 Apr 2024 at 13:06, Christofer Dutz  wrote:
>
> Hi all,
>
> while reviewing your projects latest activity as part of preparing for 
> tonight's board meeting I was first puzzled that despite the result 
> mentioning 4 binding +1 votes, I actually only found 1.
> A bit later did I find that the votes were cast in the DICSUSS thread.
>
> In the future please pay a bit more attention to which thread you post your 
> votes in. (They belong in the VOTE thread)
>
> Chris



--
pozdrawiam
Szymon K. Janc

CVE-2024-24746: Apache NimBLE: Denial of service in NimBLE Bluetooth stack

[Szymon Janc]

Severity: important

Affected versions:

- Apache NimBLE through 1.6.0

Description:

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Apache 
NimBLE. 

Specially crafted GATT operation can cause infinite loop in GATT server leading 
to denial of service in Bluetooth stack or device.

This issue affects Apache NimBLE: through 1.6.0.
Users are recommended to upgrade to version 1.7.0, which fixes the issue.

Credit:

Iván Arce from Quarkslab Vulnerability Reports team (reporter)

References:

https://mynewt.apache.org/
https://www.cve.org/CVERecord?id=CVE-2024-24746

[ANNOUNCE] Apache Mynewt 1.12.0 and Apache Mynewt NimBLE 1.7.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.12.0 and Apache Mynewt NimBLE 1.7.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The Apache Mynewt NimBLE is Bluetooth Low Energy 5 stack from Apache Mynewt.
It implements both host and controller in radio vendor independent manner.
Although part of Mynewt project it can be easily ported to other operating
systems thanks to Nimble Porting Layer (NPL).

The releases are available here:
https://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.12.0

Release notes for Apache Mynewt NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.7.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
https://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.12.0-rc1 and Apache NimBLE 1.7.0-rc1

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.12.0-rc1 and Apache NimBLE 1.7.0-rc1 is now closed.
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Jerzy Kasenberg (binding)
+1 Łukasz Rymanowski (binding)
+1 Vipul Rahane (binding)
+1 Andrzej Kaczmarek (binding)

Total: +4 binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon K. Janc

[DISCUSS] Release Apache Mynewt 1.12.0-rc1 and Apache NimBLE 1.7.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.12.0 and Apache NimBLE 1.7.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon K. Janc

[VOTE] Release Apache Mynewt 1.12.0-rc1 and Apache NimBLE 1.7.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.12.0 and Apache NimBLE 1.7.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.

Apache NimBLE is Bluetooth Low Energy 5.4 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki: https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.12.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.7.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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * Fedora Linux 38

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.7.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 2c2d990a96541a9688a5f0d5b5005ed37c6cd082
core:
  repos: https://github.com/apache/mynewt-core
  commit c95f54c3e7a90005e54e27c225fee89294b4b2f7
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 3a5cfeb31a36847f727f77046cd52cdeb177029c
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 2462905c1ba4542676592bdb2a5df4d5e441b153
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 675452b62822efd3e3fd28ac55eb166baf8461f4

In addition, the following newt and newtmgr convenience binaries are available:
  linux:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newt-bin-linux-1.12.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newtmgr-bin-linux-1.12.0.tgz

  osx:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newt-bin-osx-1.12.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newtmgr-bin-osx-1.12.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newt-bin-windows-1.12.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.12.0/rc1/apache-mynewt-newtmgr-bin-windows-1.12.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 K. Janc

Re: Interest in an Apache IoT Track at EclipseCon EU in Mainz (Germany) later this year?

[Szymon Janc]

Hi Chris,

I've submitted a proposal for CoC EU talk discussing Mynewt current
state and plans for future.

I could do similar talk in EclipseCon if there will be interest, maybe
focusing more on parts that are useful for other projects like NimBLE
stack or mcumgr.

On Thu, 4 Jan 2024 at 14:04, Christofer Dutz  wrote:
>
> Hi folks,
>
> I was contacted by some of my friends in the IoT Space at the Eclipse 
> Foundation.
>
> They are planning this year's EclipseCon to work closer together with the 
> other foundations in this space and proposed an Apache IoT Track in paralel 
> to the EclipseCon. This will be happening in Mainz in Germany I think 4 weeks 
> before Community Over Code NA.
>
> I promised to reach out to the projects I know at Apache that count to the 
> IoT space.
>
> I really liked the idea of networking with the other foundation's projects as 
> I think this is something happening far too little.
>
> So would you folks be interested in submitting talks and attending such a 
> conference?
>
> Also the CFP for CoC EU in Bratislava is only open for a few more days and so 
> far the IoT related submissions have been ... let's say ... less than I was 
> hoping for.
>
> So if you folks are planning on submitting: Do your track-chair (me) a favor 
> and don't submit on the last day ... it's always a hastle to whip up a 
> schedule if you can't do it in an orderly way, but get "shot by what's there" 
> on the last day.
>
> Looking forward to feedback,
>
> Chris
>
> PS: Please keep me In CC as I'm not subscribed here.



-- 
pozdrawiam
Szymon K. Janc

Re: Some question about Mynewt nimBLE

[Szymon Janc]

Hello Clint,

> This is Clint, focus on firmware development on keyboard and mouse. I have 
> some questions about mynewt nimBLE protocol stack, please help me a little 
> bit, thanks in advance!
> Q1: for BT controller usage, does nimBLE support Nordic chip nRF52840?

Yes, nRF52840 is fully supported

> Q2. if I use desktop as BT host usage, can I develp a web app which use 
> nimBLE host source code? And the web app is used to connect desktop and 
> keyboard (worked as BT controller), then I can use the web app to do 
> key/macro configuration of the keyboard.

I'm not sure if I correctly understand your question, but you may use
NimBLE host source code as long as you comply with Apache License,
Version 2.0 [1]


[1] https://www.apache.org/licenses/LICENSE-2.0

-- 
pozdrawiam
Szymon K. Janc

renaming main() to mynewt_main()

[Szymon Janc]

Hi,

There is a pending PR that aim to improve our support for simulated
environment.
It main goal is to remove explicit call to mcu_sim_parse_args() which
resulted in
recursive call to main() function.

Mentioned PRs are:
https://github.com/apache/mynewt-core/pull/3024
https://github.com/apache/mynewt-blinky/pull/19

Note that not updating your application to mynewt_main() shouldn't cause any
issues but we recommend to move to mynewt_main() after mentioned PRs are
merged.

-- 
pozdrawiam
Szymon K. Janc

[ANNOUNCE] Apache Mynewt 1.11.0 and Apache Mynewt NimBLE 1.6.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.11.0 and Apache Mynewt NimBLE 1.6.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The Apache Mynewt NimBLE is Bluetooth Low Energy 5 stack from Apache Mynewt.
It implements both host and controller in radio vendor independent manner.
Although part of Mynewt project it can be easily ported to other operating
systems thanks to Nimble Porting Layer (NPL).

The releases are available here:
https://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.11.0

Release notes for Apache Mynewt NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.6.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
https://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.11.0-rc1 and Apache NimBLE 1.6.0-rc1

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.11.0-rc1 and Apache NimBLE 1.6.0-rc1 is now
closed.
The release has passed this step of the process. The vote breakdown is as
follows:

+1 Fabio Utzig (binding)
+1 Łukasz Rymanowski (binding)
+1 Vipul Rahane (binding)
+1 Andrzej Kaczmarek (binding)

Total: +4 binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon K. Janc

[VOTE] Release Apache Mynewt 1.11.0-rc1 and Apache NimBLE 1.6.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.11.0 and Apache NimBLE 1.6.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.

Apache NimBLE is Bluetooth Low Energy 5.4 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.11.0+Test+Results
  2. Manual execution of the NimBLE test plan:

https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:

https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.6.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 both releases was executed via "newt test
all"
 with no failures. This testing was performed on the following
platforms:
   * Fedora Linux 38

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.6.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 223f0b3f8859c77cc0a41038a21e8d0f348e992e
core:
  repos: https://github.com/apache/mynewt-core
  commit 6de871dfa7306a06df4219470205af69c569c0d9
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 2215fc6201d7c7c376b9d6733bd35a10b5691aae
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 5086b90977bc0782b1f36eaebacabeb694d19cb5
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit df0718d7eacf414b2f4ed1e28f866250d92cadcb

In addition, the following newt and newtmgr convenience binaries are
available:
  linux:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newt-bin-linux-1.11.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newtmgr-bin-linux-1.10.0.tgz


  osx:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newt-bin-osx-1.11.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newtmgr-bin-osx-1.11.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newt-bin-windows-1.11.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.11.0/rc1/apache-mynewt-newtmgr-bin-windows-1.11.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 K. Janc

Re: Can't compile unittests

[Szymon Janc]

Hi,

`newt test` is using native target which is 32bit, so it requires support
for 32bit binaries, does WSL2 support it?
As a starter make sure you have gcc-multilib installed

On Fri, 14 Apr 2023 at 10:53, Jan Clement 
wrote:

> Hello,
>
> > looks like WSL toolchain misconfiguration...
> anything i can do to compile on WSL? I really need the tests working.
>
> Thanks
>
>
> Am 14.04.2023 um 10:32 schrieb Szymon Janc:
> > Hi,
> >
> > OK, so we were able to reproduce this on WSL, yet all is fine on native
> > linux (including Ubuntu 22.04)
> > Not sure what is going on though, looks like WSL toolchain
> > misconfiguration...
> >
> > Also, that `newt info` output is awkward (all repos showing same
> > non-upstream sha). How did you set that up?
> >
> >
> > On Wed, 12 Apr 2023 at 15:37, Jan Clement  >
> > wrote:
> >
> >>> Which Linux is this? It looks like it is toolchain issue..Welcome to
> >> Ubuntu 22.04.2 LTS (GNU/Linux
> >> 5.15.90.1-microsoft-standard-WSL2 x86_64)
> >>
> >> i am using WSL on Win10
> >>
> >>> Also, could you do `newt info` and show result?
> >> Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48
> >>
> >> Repository info:
> >>   * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.1, (dirty: local changes)
> >>   * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.0, (dirty: local changes)
> >>   * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.0, (dirty: local changes)
> >>   * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0,
> (dirty:
> >> local changes)
> >>   * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac
> >> (dirty: local changes)
> >>
> >>
> >> on Windows I can build for mys target with no problems, but native
> >> builds are not working due to POSIX issues..
> >>
> >> Thank you for your time.
> >>
> >>
> >>
> >> Mit freundlichen Grüßen
> >>
> >> Jan Clement
> >>
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure
> >> cm-electronics
> >> Salzstrasse 9
> >> 79098 Freiburg, Germany
> >>
> >> +49 761 45894342
> >> i...@cm-electronics.de
> >> www.cm-electronics.de
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> >> Freiburg i. Br. PR700214
> >>
> >> Am 12.04.2023 um 11:48 schrieb Szymon Janc:
> >>> Hi,
> >>>
> >>> Which Linux is this? It looks like it is toolchain issue..
> >>> Also, could you do `newt info` and show result?
> >>>
> >>>
> >>> On Tue, 11 Apr 2023 at 16:26, Jan Clement <
> jan.clem...@cm-electronics.de
> >>>
> >>> wrote:
> >>>
> >>>> Hi there,
> >>>>
> >>>> I am trying to compile and use mynewt unittests. I am not able to
> >>>> compile under Linux, it gets stuck at some C makros. Here is the
> compile
> >>>> output i got from newt build tool:
> >>>>
> >>>>
> >>>>> Testing package libs/xxx/selftest
> >>>>> In file included from
> >>>> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
> >>>>>from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
> >>>>>from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> >>>>> /usr/include/stdint.h:276:17: error: missing binary operator before
> >>>> token "("
> >>>>> 276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
> >>>>> | ^
> >>>>> In file included from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> >>>>> /usr/include/string.h:36:43: error: missing binary operator before
> >> token
> >>>> "("
> >>>>>  36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
> >>>>> |   ^
> >>>>> /usr/include/string.h:53:71: error: missing ')' after "defined"
> >>>>>  53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >>>> (__GLIBC_USE (ISOC2X))
> &g

Re: Can't compile unittests

[Szymon Janc]

Hi,

OK, so we were able to reproduce this on WSL, yet all is fine on native
linux (including Ubuntu 22.04)
Not sure what is going on though, looks like WSL toolchain
misconfiguration...

Also, that `newt info` output is awkward (all repos showing same
non-upstream sha). How did you set that up?


On Wed, 12 Apr 2023 at 15:37, Jan Clement 
wrote:

> > Which Linux is this? It looks like it is toolchain issue..Welcome to
> Ubuntu 22.04.2 LTS (GNU/Linux
> 5.15.90.1-microsoft-standard-WSL2 x86_64)
>
> i am using WSL on Win10
>
> > Also, could you do `newt info` and show result?
> Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48
>
> Repository info:
>  * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.1, (dirty: local changes)
>  * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.0, (dirty: local changes)
>  * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.0, (dirty: local changes)
>  * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0, (dirty:
> local changes)
>  * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac
> (dirty: local changes)
>
>
> on Windows I can build for mys target with no problems, but native
> builds are not working due to POSIX issues..
>
> Thank you for your time.
>
>
>
> Mit freundlichen Grüßen
>
> Jan Clement
>
>
> Clement, Mastalerz & Partner, Elektroingenieure
> cm-electronics
> Salzstrasse 9
> 79098 Freiburg, Germany
>
> +49 761 45894342
> i...@cm-electronics.de
> www.cm-electronics.de
>
> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> Freiburg i. Br. PR700214
>
> Am 12.04.2023 um 11:48 schrieb Szymon Janc:
> > Hi,
> >
> > Which Linux is this? It looks like it is toolchain issue..
> > Also, could you do `newt info` and show result?
> >
> >
> > On Tue, 11 Apr 2023 at 16:26, Jan Clement  >
> > wrote:
> >
> >> Hi there,
> >>
> >> I am trying to compile and use mynewt unittests. I am not able to
> >> compile under Linux, it gets stuck at some C makros. Here is the compile
> >> output i got from newt build tool:
> >>
> >>
> >>> Testing package libs/xxx/selftest
> >>> In file included from
> >> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
> >>>   from
> >> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
> >>>   from
> >> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> >>> /usr/include/stdint.h:276:17: error: missing binary operator before
> >> token "("
> >>>276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
> >>>| ^
> >>> In file included from
> >> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> >>> /usr/include/string.h:36:43: error: missing binary operator before
> token
> >> "("
> >>> 36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
> >>>|   ^
> >>> /usr/include/string.h:53:71: error: missing ')' after "defined"
> >>> 53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >> (__GLIBC_USE (ISOC2X))
> >>>|
> >>   ^
> >>> /usr/include/string.h:53:72: error: missing binary operator before
> token
> >> "ISOC2X"
> >>> 53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >> (__GLIBC_USE (ISOC2X))
> >>>|
> >>^~
> >>> /usr/include/string.h:185:30: error: missing ')' after "defined"
> >>>185 |  || defined (__GLIBC_USE (LIB_EXT2)) || defined
> (__GLIBC_USE
> >> (ISOC2X)))
> >>>|  ^
> >>> /usr/include/string.h:185:31: error: missing binary operator before
> >> token "LIB_EXT2"
> >>>185 |  || defined (__GLIBC_USE (LIB_EXT2)) || defined
> (__GLIBC_USE
> >> (ISOC2X)))
> >>>|   ^~~~
> >>> /usr/include/string.h:194:52: error: missing ')' after "defined"
> >>>194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
> >> || defined (__GLIBC_USE (ISOC2X))
> >>>|^
> >>> /usr/include/string.h:194:53: error: missing binary operator before
> >> token "LIB_EXT2"
> >>

Re: Problem with Return Code

[Szymon Janc]

Hi,

Yes, those are Mynewt "init" functions (note that those are not called
explicitly in Mynewt code).
If you call those (I'd assume on non-Mynewt NimBLE port?) and need error
checking than I think we would have to
split those into BLE API calls and wrappers for Mynewt init calls.



On Wed, 8 Feb 2023 at 04:27, Harish Kalla (MS/EDL1-SDS)
 wrote:

> Hi,
>
> We are implemented NimBLE stack protocol for mobile communication.
>
>
>
> While diagnostic checking faced issue with GAP and GATT initialization
> functions.
>
>
>
> ble_svc_gap_init() and ble_svc_gatt_init() api functions doesn’t return
> the error state, internally assert function is being called on failure. How
> to check the status of BLE stack for any system errors?
>
>
>
>
>
> Best regards,
>
> Harish Kalla
> ​
>


-- 
pozdrawiam
Szymon K. Janc

Re: Error while following the ble application

[Szymon Janc]

Hi,

This looks like issue with toolchain (I recall some versions were broken,
eg on Ubuntu).
My suggestion would be to use one from
https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads

On Wed, 1 Mar 2023 at 11:41, Ujjval Rathod 
wrote:

> Hi,
>
> I was following the ble application guide and got the below error message.
> I tried ignoring the error by commenting out some lines but next up another
> similar error popped up..!
>
> Anyone has idea what could be wrong?
>
> Error: repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c: In
> function 'value_to_pretty':
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:305:50: error:
> "/*" within comment [-Werror=comment]
>   305 | cbor_value_get_raw_integer(it, );/* can't fail */
>   |
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:308:33: error:
> expected ')' before 'PRIu64'
>   308 | if (fprintf(out, "%" PRIu64, val) < 0)
>   | ^~~
>   | )
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:308:31: error:
> spurious trailing '%' in format [-Werror=format=]
>   308 | if (fprintf(out, "%" PRIu64, val) < 0)
>   |   ^
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:313:19: error:
> 'val' undeclared (first use in this function)
>   313 | if (++val) {/* unsigned overflow may
> happen */
>   |   ^~~
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:313:19: note:
> each undeclared identifier is reported only once for each function it
> appears in
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:314:38: error:
> expected ')' before 'PRIu64'
>   314 | if (fprintf(out, "-%" PRIu64, val) < 0)
>   |  ^~~
>   |  )
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:314:36: error:
> spurious trailing '%' in format [-Werror=format=]
>   314 | if (fprintf(out, "-%" PRIu64, val) < 0)
>   |^
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:323:11: error:
> expected expression before '/' token
>   323 | }*/
>   |   ^
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:358:29: error:
> expected ')' before 'PRIu64'
>   358 | if (fprintf(out, "%" PRIu64 "(", tag) < 0)
>   | ^~~
>   | )
> repos/apache-mynewt-core/encoding/tinycbor/src/cborpretty.c:358:27: error:
> spurious trailing '%' in format [-Werror=format=]
>   358 | if (fprintf(out, "%" PRIu64 "(", tag) < 0)
>   |   ^
> cc1: all warnings being treated as errors
>
> Regards,
> Ujjval
>


-- 
pozdrawiam
Szymon K. Janc

Migration from Travis CI to Github Action

[Szymon Janc]

Hello,

We started a migration from Travis CI to Github Actions (ASF Infra decided
to drop Travis support).
Expect CI hiccups in upcoming days.

-- 
pozdrawiam
Szymon K. Janc

Re: newtmgr OTA error: slice bounds out of range [:-62]

[Szymon Janc]

Hi,

We are able to reproduce this on newtmgr master (1.11-dev), will try to fix
this before next release

On Fri, 16 Sept 2022 at 03:22, Mo Chen  wrote:

> Hi there,
>
> I encountered errors when using mynewt to DFU OTA.
>
> Environment:
> Intel Macbook pro
> MacOS: Monterey 12.5.1
>
> newt version: 1.10.0
> newtmgr version: tried with v1.10.0 and v1.9.0. Neither works with the same
> error.
>
> Any clues or help are highly appreciated!
>
>
> error message:
>
> mndrive@Mos-MBP-MnDRIVE ~ % newtmgr image upload -c testbrd
>
> /Users/xxx/Documents/Mynewt/test/bin/targets/testbrd/app/apps/testbrd/testbrd.img
>
>  0 / 163232 [--]
>   0.00%panic:
> runtime error: slice bounds out of range [:-62]
>
>
> goroutine 1 [running]:
>
> mynewt.apache.org/newtmgr/nmxact/xact.encodeUploadReq({0x451a240
> 
> ?,
> 0xc000304320?}, {0xc2e140?, 0x42bd8c6?, 0x5ba48ab08a0c882f?}, 0x98?,
> {0xc00038?, 0x0?, 0x421300?}, 0x0, ...)
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:120
> +0x146
>
> mynewt.apache.org/newtmgr/nmxact/xact.findChunkLen({0x451a240
> ,
> 0xc000304320}, {0xc2e140, 0x20, 0x20}, 0x0?, {0xc00038, 0x27da0,
> 0x27da1}, 0x0, ...)
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:139
> +0x131
>
> mynewt.apache.org/newtmgr/nmxact/xact.nextImageUploadReq({0x451a240
> 
> ,
> 0xc000304320}, 0x0?, {0xc00038, 0x27da0, 0x27da1}, 0x0, 0x0?)
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:177
> +0x1eb
>
> mynewt.apache.org/newtmgr/nmxact/xact.(*ImageUploadCmd).Run(0xc32200,
> {0x451a240, 0xc000304320})
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:353
> +0x24e
>
>
> mynewt.apache.org/newtmgr/nmxact/xact.(*ImageUpgradeCmd).runUpload(0xc32100
> ,
> {0x451a240, 0xc000304320})
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:510
> +0x1cb
>
> mynewt.apache.org/newtmgr/nmxact/xact.(*ImageUpgradeCmd).Run(0x7ff7bfeffbe5
> ?,
> {0x451a240?, 0xc000304320?})
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/nmxact/xact/image.go:536
> +0x6a
>
> mynewt.apache.org/newtmgr/newtmgr/cli.imageUploadCmd(0xc0001f4c80?,
> {0xc0001ad920?, 0x3?, 0x3?})
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/newtmgr/cli/image.go:212
> +0x30b
>
> github.com/spf13/cobra.(*Command).execute(0xc0001f4c80, {0xc0001ad830,
> 0x3,
> 0x3})
>
> /Users/mndrive/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:830
> +0x663 
>
> github.com/spf13/cobra.(*Command).ExecuteC(0xccaf00)
>
> /Users/mndrive/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
> +0x2ee 
>
> github.com/spf13/cobra.(*Command).Execute(...)
>
> /Users/mndrive/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
>
> main.main()
>
>
> /Users/mndrive/Downloads/apache-mynewt-newtmgr-1.10.0/newtmgr/newtmgr.go:111
> +0x16f
>
>
>
> --
> Mo Chen
>


-- 
pozdrawiam
Szymon K. Janc

Re: Why Does Newt Invoke Compiler Backend Directly?

[Szymon Janc]

Hello Jeffrey,

newt takes compiler configurations from core repository "compilers/foo" and
invokes whatrever is provided there.

However, we have seen issues with Coverity Scan in the past and to
workaround this we added --executeShell option to newt build and test
commands.
If I recall correctly it has something to do with Go "os/exec" using
clone() instead of fork() but don't remember details anymore..
With that option compiler is invoked via shell and it seems to fix the
issue.

BTW we have coverity scan run every two weeks on upstream repositories:
https://scan.coverity.com/projects/apache-mynewt-core

Instructions on how this is set up this are on wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Static+code+analysis

I've just tested this with latest Coverity Scan and it seems to work OK:
Emitted 502 C/C++ compilation units (100%) successfully
502 C/C++ compilation units (100%) are ready for analysis


On Sat, 3 Dec 2022 at 00:30, Jeffrey Thalhammer
 wrote:

> Hello Newt devs!
>
> I'm experimenting with Newt using the blinky project as described here<
> https://mynewt.apache.org/latest/get_started/project_create.html>.
> Building on linux, using gcc.
>
> I have noticed that Newt directly invokes the compiler backend `cc1`
> rather than the more customary `gcc` frontend.  Unfortunately, this breaks
> some static analysis tools.
>
> Can you help me understand why Newt works this way? Could it be made to
> (optionally) use the `gcc` frontend instead?
>
> Thanks!
>
> Jeffrey Thalhammer
>
>

-- 
pozdrawiam
Szymon K. Janc

Re: NimBLE help with pairing and security

[Szymon Janc]

Hi,

On Thu, 1 Sept 2022 at 17:01, Henry Hunt  wrote:

> Hi everyone,
>
> I’m working on a BLE peripheral using the NimBLE stack running on an
> ESP32. I’m really struggling to get pairing/bonding/security to work how
> I need and was hoping I could get some help here.
>
> The key requirements in question are as follows:
> - A central must be bonded in order for it to be able to interact with
> any of the peripheral’s characteristics in any way.
> - Only one central can be bonded, and that bonded central is the only
> one that is allowed to be connected to the peripheral (I have a button
> to delete the bond so that a new central can bond).
>
> This is supposed to work exactly like a smartwatch or wireless keyboard:
> you must pair it with your phone; nothing else except your phone can
> then access it; and you have to unpair it to use it with another phone.
>
> So my question is how do I implement this with the NimBLE stack and what
> is the best approach to enforcing these security requirements?
>
> Here are two approaches that I have been trying to make work:
> 1) Call ble_gap_security_initiate() in the BLE_GAP_EVENT_CONNECT event
> to explicitly ensure that connections are secure whenever they are
> started. I've been having multiple issues with this from the Android
> point-of-view, such as it asking for pairing when connecting but already
> paired, getting pairing-related dialogs show multiple times, and having
> to tap the device in Android Settings multiple times to get the pairing
> pin dialog to open. Overall I don’t have much confidence in this due to
> all of the issues I’ve experienced, and a lack of understanding of how
> it, and the bond restoration process in general, works.
> 2) Security is not explicitly requested and the device simply doesn’t
> respond to characteristic interactions unless the connection is secure.
> To interact with the characteristics, you must first pair it manually
> (e.g. in Android Settings or within a companion app that would be
> developed). The biggest difficulty I have with this is that I need to
> terminate any connection that does not successfully bond or restore a
> bond. I can use ble_store_read_our_sec() to check if there is a bond for
> the current connection, but I haven’t found a way to determine if that
> bond fails to actually restore. I’m left with using timers to terminate
> the connection if the BLE_GAP_EVENT_ENC_CHANGE event isn't received in a
> certain amount of time. Another thing I tried was to use directed
> advertising but iOS doesn’t support that.


This double pairing dialog on Android seems to be Android issue as this
happens with other BLE stacks too.
While sending SecurityRequest on connection is fine I suggest other design
on peripheral device.

Set required security on GATT characteristic (eg BLE_GATT_CHR_F_READ_ENC)
and when peer reads/write
to it it will get ATT error due to insufficient security. Most (all?) BLE
stacks will in such case start pairing (or enable
encryption if already bonded) and re-try GATT operation.


> An additional complexity is that things need to work with RPA addresses,
> as at least iOS uses them when advertising, and I would like to use
> privacy on the peripheral.
>
> So, how should I do this? There is limited information and questions on
> the internet regarding NimBLE pairing and security. I’ve been trawling
> through the NimBLE source code and the source code of other BLE
> libraries even, trying to figure out how to get this working. So I’m
> really hoping I can get some help here.
>

Upstream NimBLE host stack requires Privacy 1.2 support in controller as
RPA resolving and generation is implemented
only in NimBLE controller. In such case using privacy requires to pass
proper own_addr type with value +2 (ie 0x02 if using
public addr or 0x03 if static random addr is used). Unfortunately setting
custom local IRK currently required using
ble_hs_pvcy_set_our_irk() which is private function
(src/ble_hs_pvcy_priv.h). This is something we plan to improve
when have some spare time...

You are using ESP32 port which has own controller AFAIR without privacy 1.2
support, I think ESP32 has some
modifications on top of NimBLE to handle privacy in host. Since this isin't
upstream code you should ask in fork community.

There were some interest in adding host based privacy support to NimBLE but
it seems like it never ended in creating a PR.
See https://github.com/apache/mynewt-nimble/issues/897 for some details.

-- 
pozdrawiam
Szymon K. Janc

Re: nrf5340 DK ADC driver

[Szymon Janc]

Hello Mo,

nRF5340 MCU is using adc_nrf52 driver (as it is nrfx based)

See  
https://github.com/apache/mynewt-core/blob/master/hw/mcu/nordic/nrf5340/pkg.yml#L58

On Tue, 24 May 2022 at 21:19, Mo Chen  wrote:
>
> Hi all,
>
> I am developing using the nrf5340DK pca10095.
>
> I noticed that in the @apache-mynewt-core/hw/drivers/adc/ folder, there is
> no nrf53 series driver included.
>
> In this case, do I use the adc_nrf52 files instead? Are they compatible
> with the nrf53?
>
> Thanks,
>
>
> --
> Mo Chen



-- 
pozdrawiam
Szymon K. Janc

Upcoming Apache Mynewt 1.11

[Szymon Janc]

Dear Apache Mynewt Community,

This email is to give you a heads up that we are going to make next
release (1.11) soon.
Tentative 1.11-rc1 release date is 29th July.

If there are any features or bug fixes you are working on (and want them to be
part of 1.11 release) do not hesitate to send pull requests!

Please note that this will be coordinated with NimBLE 1.6 release.

-- 
pozdrawiam
Szymon K. Janc

Re: error using newt new command

[Szymon Janc]

Hello Chen,


Yes,  this is unfortunately bug in 1.10 release
Please use "shallow" option when creating new project:
newt new --shallow=0 myproj


On Thu, 19 May 2022 at 04:43, Mo Chen  wrote:

> Hi all,
>
> I got the following error when trying the "newt new myproj" command.
>
> It seems like the version 1.10.0 is not recognized in git? Would you
> please help fix this?
>
> Thanks,
>
> platform: MacOS 12.4
> Mynewt version: 1.10.0
>
> *mndrive@Mos-MacBook-Pro Mynewt % newt new myproj*
>
> *Downloading project skeleton from apache/mynewt-blinky...*
>
> *Downloading repository mynewt-blinky (commit: master) from
> https://github.com/apache/mynewt-blinky.git
> *
>
> *WARNING: Creating a shallow clone by default. To unshallow repository
> later use "git fetch --unshallow".*
>
> *Error: error: pathspec 'mynewt_1_10_0_tag' did not match any file(s) known
> to git*
>
> --
> Mo Chen
>


-- 
pozdrawiam
Szymon K. Janc

[ANNOUNCE] Apache Mynewt 1.10.0 and Apache Mynewt NimBLE 1.5.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.10.0 and Apache Mynewt NimBLE 1.5.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The Apache Mynewt NimBLE is Bluetooth Low Energy 5 stack from Apache Mynewt. 
It implements both host and controller in radio vendor independent manner. 
Although part of Mynewt project it can be easily ported to other operating 
systems thanks to Nimble Porting Layer (NPL).

The releases are available here:
https://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.10.0

Release notes for Apache Mynewt NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.5.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
https://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.10.0-rc1 and Apache NimBLE 1.5.0-rc1

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.10.0-rc1 and Apache NimBLE 1.5.0-rc1 is now closed. 
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Szymon Janc (binding)
+1 Jerzy Kasenberg (binding)
+1 Łukasz Rymanowski (binding)
+1 Vipul Rahane (binding)
+1 Andrzej Kaczmarek (binding)
+1 Michał Narajowski (binding)
+1 Will Sanfilippo (binding)
+1 Miguel Azevedo

Total: +7 binding and +1 non-binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

Re: [VOTE] Release Apache Mynewt 1.10.0-rc1 and Apache NimBLE 1.5.0-rc1

[Szymon Janc]

+1 (binding)

There are couple of issues mentioned in release notes but those can be
fixed in point release.


On Mon, 25 Apr 2022 at 00:45, Szymon Janc  wrote:

> Hello all,
>
> I am pleased to be calling this vote for the source release of
> Apache Mynewt 1.10.0 and Apache NimBLE 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.
>
> Apache NimBLE is Bluetooth Low Energy 5.3 stack from Apache Mynewt.
>
> This release is coordinated release of Apache Mynewt and NimBLE. Future
> NimBLE releases may be released separately depending on needs.
>
> For full release notes for both Mynewt and NimBLE, please visit the Apache
> Mynewt Wiki:
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes
>
> Apache Mynewt and Apache NimBLE release candidates were 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.10.0+Test+Results
>   2. Manual execution of the NimBLE test plan:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
>  The test results can be found at:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+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 both releases was executed via "newt
> test all"
>  with no failures. This testing was performed on the following
> platforms:
>* Fedora Linux 35
>
> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/
> https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.5.0/rc1/
>
> The commits under consideration are as follows:
> blinky:
>   repos: https://github.com/apache/mynewt-blinky
>   commit d2dcd79fb9fad8fb6cb63b0e338cb81b995fc0f9
> core:
>   repos: https://github.com/apache/mynewt-core
>   commit 71c228891d02891a6be765d53e7a3874edc59074
> newt:
>   repos: https://github.com/apache/mynewt-newt
>   commit 874afdfa6f4738646bad29d9d7119a68dc7b0128
> newtmgr:
>   repos: https://github.com/apache/mynewt-newtmgr
>   commit c3cc444a278471b5ca5293607526e05295ded0e4
> nimble:
>   repos: https://github.com/apache/mynewt-nimble
>   commit 21d59b8b40c232d6746778dda6b91cf0c0edba83
>
> In addition, the following newt and newtmgr convenience binaries are
> available:
>   linux:
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-linux-1.10.0.tgz
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-linux-1.10.0.tgz
>
>   osx:
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-osx-1.10.0.tgz
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-osx-1.10.0.tgz
>
>   windows:
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-windows-1.10.0.tgz
>
> https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-windows-1.10.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



-- 
pozdrawiam
Szymon K. Janc

[VOTE] Release Apache Mynewt 1.10.0-rc1 and Apache NimBLE 1.5.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.10.0 and Apache NimBLE 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.

Apache NimBLE is Bluetooth Low Energy 5.3 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki: https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.10.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * Fedora Linux 35

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.5.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit d2dcd79fb9fad8fb6cb63b0e338cb81b995fc0f9
core:
  repos: https://github.com/apache/mynewt-core
  commit 71c228891d02891a6be765d53e7a3874edc59074
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 874afdfa6f4738646bad29d9d7119a68dc7b0128
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit c3cc444a278471b5ca5293607526e05295ded0e4
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 21d59b8b40c232d6746778dda6b91cf0c0edba83

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-linux-1.10.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-linux-1.10.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-osx-1.10.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-osx-1.10.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newt-bin-windows-1.10.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.10.0/rc1/apache-mynewt-newtmgr-bin-windows-1.10.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

[DISCUSS] Release Apache Mynewt 1.10.0-rc1 and Apache NimBLE 1.5.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.10.0 and Apache NimBLE 1.5.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

Re: programming the net core on the nrf5340 dk

[Szymon Janc]

Hello Manish,

You can check wiki
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177047756

Note that support for nRF5340 improved a lot on master branch, I'll update
wiki before release but current version should give you some hints anyway
on how things work.


On Sat, 12 Mar 2022 at 18:54, manish  wrote:

> Hi,
>
> I am trying out mynewt on the nrf5340-dk on linux.
> I followed the nrf52 blinky tutorial here
> https://mynewt.apache.org/latest/tutorials/blinky/nRF52.html and could
> program the app core using jlinkexe and see the output.
>
> However I am not able to figure out how to program the net core. I repeated
> the above process with the net core bsp but that doesn't seem to work.
>
> Also, can someone please explain to me how to run the bluetooth stack on
> the net core and another application on the app core communicating with it.
>
> Thanks
> Manish
>


-- 
pozdrawiam
Szymon K. Janc

Re: Request for documents

[Szymon Janc]

Hi,

Please check https://mynewt.apache.org/ and
https://cwiki.apache.org/confluence/display/MYNEWT/

On Thu, 20 Jan 2022 at 09:25, Aman saeed  wrote:

> Hello dear sir:
> I need a document on the supported functionalities of Apache Mynewt, like
> the design of Apache Mynewt, process/thread management, CPU scheduling,
> memory management, synchronization mechanisms, etc.
>
> regards
> Aman Saeed
>


-- 
pozdrawiam
Szymon K. Janc

Re: Examples won't build on MacOS Monterey 12.2.1

[Szymon Janc]

Hi,

Unfortunately this is due to latest MacOS no longer support 32bit binaries
so native and test won't work.
You should stil be able to develop for HW targets though.

At some point (see [1]) one could fallback to Xcode 9 to get 32bit support
but I'm not sure if this is stil possible with latest MacOS...

[1] https://github.com/apache/mynewt-core/issues/1685


On Sun, 27 Feb 2022 at 05:02, Mo Chen  wrote:

> Hi all,
>
> I installed the latest version of Mynewt, 1.9.0 and the environment needed
> following the guidance on the website. However, the examples wont' build on
> MacOS Monterey 12.2.1.
>
> It shows the following error:
>
> Error: ld: warning: The i386 architecture is deprecated for macOS (remove
> from the Xcode build setting: ARCHS)
>
>
>
> I tried to uninstall gcc-11 and installed GCC-6 (gcc-5 is no long supported
> by MacOS later than v11) and changed the Compilier.yml settings to:
>
>
> compiler.path.cc.DARWIN.OVERWRITE:
> "gcc-6"compiler.path.as.DARWIN.OVERWRITE: "gcc-6”
>
>
> The same error still shows up.
>
> Any suggestions?
>
> Thanks,
>
> --
> Mo Chen
>


-- 
pozdrawiam
Szymon K. Janc

Upcoming Apache Mynewt 1.10

[Szymon Janc]

Dear Apache Mynewt Community,

It has been a year since last Apache Mynewt release. This email is to give
you a heads up that we are going to make next release (1.10) soon.
Tentative 1.10-rc1 release date is 28th March.

If there are any features or bug fixes you are working on (and want them to
be
part of 1.10 release) do not hesitate to send pull requests!

Please note that this will be coordinated with NimBLE 1.5 release.

-- 
pozdrawiam
Szymon K. Janc

Re: Confusion about BLE_LL Files

[Szymon Janc]

Hello Armin,

ble_ll_* files are BLE controller implementation, AFAIK idf is using only
host part

On Sun, 24 Oct 2021 at 23:31, Hamar Armin  wrote:

> Morning Everyone,
>
> Just a question the ble_ll_conn.c files are the controller or not? As I
> work currently on a idf project and that seems to use the nimble ble.
> Now we wanted to debug some stuff which happens in regards to the bounding
> and search in side the code base and found ble_ll_conn.c where the said
> code would be.
> Now the problem we have is that we can see the file in gdb but we can't
> step into it or mention a line there.
>
> I suspect this code would run on the CPU? Or is my assumption wrong?
>
> Thanks for any answer.
>
> Best regards,
> Armin
>
>
> ___
> Diese Nachricht und allf?llige angeh?ngte Dokumente sind vertraulich und
> nur f?r den/die Adressaten bestimmt. Sollten Sie nicht der beabsichtigte
> Adressat sein, ist jede Offenlegung, Weiterleitung oder sonstige Verwendung
> dieser Information nicht gestattet. In diesem Fall bitten wir, den Absender
> zu verst?ndigen und die Information zu vernichten. F?r ?bermittlungsfehler
> oder sonstige Irrt?mer bei ?bermittlung besteht keine Haftung.
> ___
> This message and any attached files are confidential and intended solely
> for the addressee(s). Any publication, transmission or other use of the
> information by a person or entity other than the intended addressee is
> prohibited. If you receive this in error please contact the sender and
> delete the material. The sender does not accept liability for any errors or
> omissions as a result of the transmission. Please consider your
> environmental responsibility before printing this e-mail.
>


-- 
pozdrawiam
Szymon K. Janc

Re: subscribe

[Szymon Janc]

Hi,

NimBLE supports multiple operating systems and is build differently (in
OS-specific way) depending on selected OS.

newt is tool for building Apache Mynewt OS (and thus also NimBLE on
Mynewt). You need to setup development environment.
To do so please check http://mynewt.apache.org/latest/get_started/index.html
. You'll find instructions there for setting up
development environment on your PC as well as building your first Mynewt
project. You can also find some tutorials showing
on how to build and run Mynewt on some popular boards.



On Mon, 4 Oct 2021 at 17:30, yu zhigang  wrote:

> hello,
> can i build mynewt-nimble by newt commands ? when i am trying to create
> a target (for blehr), how to set the target.bsp field in the target.yml ?
> The demo can only be built by makefile
> under apache-mynewt-nimble/porting/examples/linux currently .
>
> thanks,
> gavin
>


-- 
pozdrawiam
Szymon K. Janc

Re: Crash due to concurrent access

[Szymon Janc]

Hi,

On Wednesday, 18 August 2021 21:38:32 CEST Jeremy Cole-Baker wrote:
> Hi,
> 
> We are using Nimble BLE on an Espressif ESP32 project. We are getting
> frequent crashes due to invalid memory access. It looks like a race
> condition / threading issue to me, but I can't find much info about using
> Nimble from different threads (i.e. different tasks in FreeRTOS).
> 
> Here's a typical crash log:
> 
> 0x4012773f: put_le16 at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/porting/nimble/s
> rc/endian.c:24 0x400e77c5: ble_hs_hci_cmd_send at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/nimble/host/src/
> ble_hs_hci_cmd.c:77 0x400e7819: ble_hs_hci_cmd_send_buf at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/nimble/host/src/
> ble_hs_hci_cmd.c:122 0x400e3611: ble_hs_hci_cmd_tx at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/nimble/host/src/
> ble_hs_hci.c:304 0x400e386b: ble_hs_hci_util_read_rssi at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/nimble/host/src/
> ble_hs_hci_util.c:96 0x400e1709: ble_gap_conn_rssi at
> C:/Users/Jeremycb/esp-idf/components/bt/host/nimble/nimble/nimble/host/src/
> ble_gap.c:5906 0x400dc0d5: RSSIUpdateTask at
> C:\Users\Jeremycb\esp\wireless-controller\build/../components/wc_bluetooth/
> wc_ble_services.c:369 0x40092e39: vPortTaskWrapper at
> C:/Users/Jeremycb/esp-idf/components/freertos/port/xtensa/port.c:168
> 
> It looks like a bad pointer (NULL) passed to "put_le16".
> 
> I've seen 3 different call paths, 2 from my own tasks and one from the task
> used to start / run Nimble. They all converge at the function
> "ble_hs_hci_cmd_send_buf", which then calls "ble_hs_hci_cmd_send"
> 
> "ble_hs_hci_cmd_send" uses "ble_hci_trans_buf_alloc", but looking at the
> code for the "BLE_HCI_TRANS_BUF_CMD" option, there is only one buffer
> available, and the comments say that "The controller will only allow one
> outstanding command". Thus it returns NULL if called from different
> threads, and results in the crash.
> 
> Looking through the call paths, I see that we can get there two ways:
> "ble_hs_hci_cmd_tx" (called from our code and many other places) or
> "ble_hs_flow_tx_num_comp_pkts" (called from flow event callback, from BLE
> host task).
> 
> I looked for a mutex, and found that "ble_hs_hci_cmd_tx" locks
> ble_hs_hci_mutex, whereas "ble_hs_flow_event_cb" (called by BLE host task)
> locks ble_hs_mutex (different).
> 
> Our code is calling "ble_gap_conn_rssi" and "ble_gap_adv_rsp_set_fields" on
> different tasks / threads, which ultimately call "ble_hs_hci_cmd_tx".
> 
> So, it looks like it's NOT SAFE to call these functions on another thread.
> This looks like a bug, otherwise how would these functions be used?
> 

For the record, this will be handled by
https://github.com/apache/mynewt-nimble/pull/1012

-- 
pozdrawiam
Szymon Janc

Re: Support for csi data and iq samples

[Szymon Janc]

Hello Kaj-Sören,

> Hello mynewt team,
> 
> we are interested in using NimBLE in combination with a Dialog DA14695. For
> our application it is essential that we can obtain some data from the
> bluetooth hardware, like csi data and iq samples. Is this already supported
> by NimBLE? If not is there a plan to support this in the future?

We have tentative plans to add support for Direction Finding but no ETA (the 
DKs with antennas array are not that easy to get...). Probably first on Nordic 
HW due to open HW specs though. That would allow you to enable transmission 
and reception of CTE (which gives basically IQ data of packet extension) via 
HCI interface.

However, if you're willing to work on that we would gladly do code/arch review 
:-)

-- 
pozdrawiam
Szymon Janc

[ANNOUNCE] Apache Mynewt 1.9.0 and Apache NimBLE 1.4.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.9.0 and Apache NimBLE 1.4.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The releases are available here:
https://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.9.0

Release notes for Apache NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.4.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
https://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.9.0-rc1 and Apache NimBLE 1.4.0-rc1

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.9.0-rc1 and Apache NimBLE 1.4.0-rc1 is now closed. 
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Łukasz Rymanowski (binding)
+1 Vipul Rahane (binding)
+1 Will Sanfilippo (binding)
+1 Miguel Azevedo

Total: +3 binding and +1 non-binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.9.0-rc1 and Apache NimBLE 1.4.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.9.0 and Apache NimBLE 1.4.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

travis issues on github

[Szymon Janc]

Hello,

Just a heads up that CI on github is having some issues now.
This is due to planned shutdown of travis-ci.org and migration to travis-ci.com

https://issues.apache.org/jira/browse/INFRA-21358

-- 
pozdrawiam
Szymon K. Janc

Upcoming Apache Mynewt 1.9

[Szymon Janc]

Dear Apache Mynewt Community,

It has been almost a year since last Apache Mynewt release. This email is
to give you a heads up that we are going to make next release (1.9) in early
February (tentative rc1 date is ~10th February).

If there are any features or bug fixes you are working on (and want them to be
part of 1.9 release) do not hesitate to send pull requests!

Please note that this will be coordinated with NimBLE 1.4 release

-- 
pozdrawiam
Szymon K. Janc

Re: Using the LE Coded phy on an nRF52840 HCI mode with a Linux host

[Szymon Janc]

Hi Valens,

Yes, Coded PHY and advertising extensions are fully supported by nimble.
You need to enable and tune them in your project syscfg.yml file.
This is a sample  config I use for testing with most features enabled
   BLE_EXT_ADV: 1
   BLE_EXT_ADV_MAX_SIZE: 1650
   BLE_HCI_EVT_LO_BUF_COUNT: 16
   MSYS_1_BLOCK_COUNT: 160
   MSYS_1_BLOCK_SIZE: 256
   BLE_LL_CFG_FEAT_DATA_LEN_EXT: 1
   BLE_LL_CFG_FEAT_LE_2M_PHY: 1
   BLE_LL_CFG_FEAT_LE_CODED_PHY: 1
   BLE_LL_CFG_FEAT_LL_PRIVACY: 1
   BLE_LL_CONN_INIT_MAX_TX_BYTES: 251
   BLE_LL_CONN_INIT_SLOTS: 4
   BLE_LL_DTM: 1
   BLE_LL_DTM_EXTENSIONS: 1
   BLE_LL_VND_EVENT_ON_ASSERT: 1
   BLE_MAX_CONNECTIONS: 5
   BLE_MAX_PERIODIC_SYNCS: 5
   BLE_MULTI_ADV_INSTANCES: 5
   BLE_PERIODIC_ADV: 1
   BLE_PERIODIC_ADV_SYNC_TRANSFER: 1
   BLE_VERSION: 51

As for PCA10059, it is compatible with PCA10056 (with exception of LED
and buttons)
so the build for PCA10056 should work on nRF52840 dongle.

Also I'm not sure if USB support went in before 1.8 was tagged so you
may have to use master branch instead of release.

On Fri, 25 Sep 2020 at 00:56, Valens D'Silva
 wrote:
>
> Hi,
>
> I am new to Apache and the mynewt-nimble project. I am a little familiar with 
> Zephyr and the nRF52840.
>
> We have an application where I want to use the nRF52840 dongle (PCA10059) in 
> USB HCI mode with a Linux host system (Pi Zero, BLueZ 5.55) which acts as a 
> BLE central. Our application must use LE coded Phy and  tx power settings for 
> max range.
>
> I’ve learn from Zephyr devs that setting LE is currently not supported in HCI 
> mode with their open source stack.
> Does mynewt-nimble support the host system (specifically BLuez and hcitool) 
> setting the LE phy and the tx power level in USB HCI mode?
> I see commands in 
> mynewt-nimble/nimble/include/nimble/hci_common.h
>  but I’ve learnt from Zephyr that doesn’t always mean the feature works as yet
> If the project does support this I’m assuming I would use this tutorial:
> https://mynewt.apache.org/latest/tutorials/ble/blehci_project.html
> Change transport to USB in 
> mynewt-nimble/apps/blehci/syscfg.yml
> Go to file
> Problem: The BSP (PCA10059) is not supported by mynewt-core/hw/bsp.
> Thanks,
> Valens
>
>
>
> Sent from Mail for Windows 10
>


-- 
pozdrawiam
Szymon K. Janc

Re: RAM overflow for nrf51-16Kb target

[Szymon Janc]

Hi,

You probably need to fine tune some of the syscfg values.
I suggest starting with OS_MAIN_STACK_SIZE, by default it is 1024
(4096 bytes) and probably you don't need such a big stack.

newt size (-R) should help you to do further fine tuning if needed.


On Mon, 21 Sep 2020 at 15:41, Sherlock Labs  wrote:
>
> Hi,
> I tried to compile the code following turotial for ibeacon
> https://mynewt.apache.org/latest/tutorials/ble/ibeacon.html
>
> only change was setting target nordic_pca10028-16k, my module has NRF51822
> -QFAAH2 which has 16KB of ram.
>
> on build i get error
> "ble_app.elf section `.bss' will not fit in region `RAM'"
>
> "region RAM overflowed with stack"
>
> "region `RAM' overflowed by 1676 bytes"
>
>
> i see linker has
>
> MEMORY
>
> {
>
>   FLASH (rx) : ORIGIN = 0x8000, LENGTH = 0x1b800
>
>   RAM (rwx) :  ORIGIN = 0x2000, LENGTH = 0x4000
>
> }
>
>
> /* This linker script is used for images and thus contains an image header
> */
>
> _imghdr_size = 0x20;
>
> do we have active support on nimble on nrf51-16Kb or not
>
> Thanks
> Mohit



-- 
pozdrawiam
Szymon K. Janc

Re: Error: 2 mynewt 1.7.0

[Szymon Janc]

Hi Alessandro,

You can confirm only the running image, so you need to reboot your
board after upload, and then confirm if it works ok.
If you reboot again without confirming the image, it will be reverted
back to the old one.

For a disconnection error at the end, could you try getting btmon logs
(on linux) so we can see the reason of disconnection?

On Thu, 16 Apr 2020 at 17:29, Alessandro Amato
 wrote:
>
> Hello, I'm Alessandro from Italy.
>
> Im having trouble with mynewt loaded on an nrf52.
>
> I have followed the tutorial in this page :
> https://mynewt.apache.org/latest/tutorials/devmgmt/ota_upgrade_nrf52.html
> to upgrade my device trought BLE.
>
> During the load of the image i get this : "
>
>  127.32 KiB / 127.43 KiB [==]  99.92% 1.93 
> KiB/s
> Error: disconnected
>
> "
>
> After that, i used the command "newtmgr image list -c mybleprph" and the
> result was:
> "
> Images:
>
>  slot=0
> version: 2.0.1
> bootable: true
> flags: active confirmed
> hash: a5eb7f4bfef07b6441acc7901af074289cbc547b8639a4e0790614f164917998
>  slot=1
> version: 2.0.0
> bootable: true
> flags: pending
> hash: ff4c537c41a6cb53264d54f93e38c368434960fbc43a04a42809d9f6461028ed
> Split status: N/A (0)
> "
>
> So actually my image was uploaded but something wrong happed, because when
> i try to test and reset, my slot 1 image stay on flags: pending anche I
> cant confirm it.
>
> After all of that, I tried to re-upload the image, but now I get Error 2 :
>
> "
>  0 / 130484 [--]   
> 0.00%
> Error: 2
> "
>
> I have even try to erase, but Error 2 block me:
>
> "
> sudo newtmgr image erase -c mybleprph
> Error:2
> "
>
> What can I do?
>
> Regards,
>
> Alessandro.



-- 
pozdrawiam
Szymon K. Janc

[ANNOUNCE] Apache Mynewt 1.8.0 and Apache NimBLE 1.3.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.8.0 and Apache NimBLE 1.3.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The releases are available here:
http://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.8.0

Release notes for Apache NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.3.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.8.0-rc2 and Apache NimBLE 1.3.0-rc2

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.8.0-rc2 and Apache NimBLE 1.3.0-rc2 is now closed. 
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Andrzej Kaczmarek (binding)
+1 Łukasz Rymanowski (binding)
+1 Sterling Hughes (binding)
+1 Vipul Rahane (binding)
+1 Miguel Azevedo

Total: +4 binding and +1 non-binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.8.0-rc2 and Apache NimBLE 1.3.0-rc2

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.8.0 and Apache NimBLE 1.3.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.8.0-rc2 and Apache NimBLE 1.3.0-rc2

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.8.0 and Apache NimBLE 1.3.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.

Apache NimBLE is Bluetooth Low Energy 5.1 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki: https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Comparing to rc1 only licensing issues were sorted out and there were no code
changes.

Apache Mynewt and Apache NimBLE release candidates were 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.8.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.3.0+Test+Results
  3. The full unit test suite for both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * OS X 10.15
   * Fedora Linux 32

Note that this testing is not yet complete and more results will show while
voting is ongoing.

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.3.0/rc2/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 34e9aae78f3ab4a4307bf99b4e25be11060aa526
core:
  repos: https://github.com/apache/mynewt-core
  commit cb9df4273aac1c8e627ff4df67b866ba9a22b018
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 725740e08825a4a15d6270cccd7ff45fdd928312
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 15c6a24d57d6dbdcf33646df365b2c64a12de251
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 97ce3eacaaa79e8ed6cf71717149ced4f5328ee7

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newt-bin-linux-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newtmgr-bin-linux-1.8.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newt-bin-osx-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newtmgr-bin-osx-1.8.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newt-bin-windows-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc2/apache-mynewt-newtmgr-bin-windows-1.8.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: [VOTE] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hi,

On Tuesday, 24 March 2020 13:59:05 CET Justin Mclean wrote:
> Hi,
> 
> > Yeap, this is being fixed in
> > https://github.com/apache/mynewt-core/pull/2248
> Good to know, however I see another possible issue here:
> " The copyright holder assumes no responsibility
>  * for the consequences of use
>  * of such information nor for any infringement of patents or
>  * other rights of third parties which may result from its use.
>  * No license is granted by implication or otherwise under any patent or
>  * patent rights of the copyright holder.”
> 
> That would possibly be against the terms of the Apache license, (see section
> 3 grant of patent license) you may want to check this on legal dicuss.

We clarified this offline with copyright holder that intention was to use 
BSD-3 license and this additional statement can be removed. PR is updated and 
I'll merge once CI is finished.


-- 
pozdrawiam
Szymon Janc

Re: [VOTE] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hi,

On Tuesday, 24 March 2020 12:17:04 CET Justin Mclean wrote:
> Hi,
> 
> >> * Which also seem to have an incorrect headers?
> > 
> > While [15] is indeed odd, what do you mean by incorrect headers in other
> > files?
> 
> 3rd party files shouldn’t have ASF headers on them.

Yeap, this is being fixed in https://github.com/apache/mynewt-core/pull/2248

> > So just to be sure, NOTICE should have listed all 3rd party but APL2
> > licensed code, while LICENCE should list all non-APL code?
> 
> Not quite, if some code in included from an ALv2 project and it has a NOTICE
> file you need to look at it’s NOTICE and include the relevant parts in
> yours. If it doesn’t have a NOTICE file then nothing needs to be done.

Understood. I did some more reading on ASF pages and I think I have good 
understanding now on how this should look.

-- 
pozdrawiam
Szymon Janc

[CANCEL][VOTE] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hello all,

This vote for  Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1 is being 
canceled due to license headers, LICENSE and NOTICE files issues.

Thanks all for your patience. You will be seeing a new [VOTE] thread soon.

-- 
pozdrawiam
Szymon Janc

Re: [VOTE] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hi Justin,

On Thursday, 19 March 2020 03:52:51 CET Justin Mclean wrote:
> HI,
> 
> Sorry but it’s -1 (binding) as LICENSE file are not correct.

Uhm, yeah I'll clean that up and we will do rc2.

> 
> I checked:
> - signatures and hashes are fine
> - Years in NOTICE are incorrect
> - LICENSE for blink is fine, other LICENSE files are not (see below)
> - no unexpected binary files
> - all source file have ASF headers, some of them may incorrect headers
> - did not compile from source
> 
> For apache-mynewt-newtmgr-1.8.0 the LICENSE list a large number of things,
> none of which seem to be actually bundled.
> 
> the same with apache-mynewt-newt-1.8.0. I also note it does bundle some
> files under the go versions libyaml but not the full list mentioned in
> LICENSE.
> 
> A spot check on core LICENSE show some missing or invalid paths e.g
> [1][2][3][4][5][6][7][8][9][10] do these need to be removed from LICENSE?

Some were removed, some renamed, I'll check that.

> It also seems to be missing a number of things as well. This fiile*, [11]
> Android Open Source Project, [12] Dialog Semiconductor, [13] Jan Van
> Winkel*, several file copyright PHYTEC Messtechnik GmbH* e.g [14], several
> files copyright Bosch Sensortec GmbH* eg [15], several file copyright Ac6
> e.g [16], InvenSense, Inc [17] and several file copyright Embedded
> Microprocessor Benchmark Consortium (EEMBC). They are probably others and I
> didn’t;t check any ARM or STMircrocontroller files.

Yes, [15] looks odd with those double licenses although it was clarified for 
header file, but not for .c file in PR [20].

> * Which also seem to have an incorrect headers?

While [15] is indeed odd, what do you mean by incorrect headers in other 
files?

> 
> I did the above check by comparing with the 1.5 release as it's LICENSE file
> is identical, but as the LICENSE file hasn’t changed in 2 year which mean
> there’s probably more to be done and we’ll need to check with an easier
> release (1.3 release?)
> 
> It may also be that NOTICE file are incoresst as I some of teh files added
> are 3rd part file that are Apache licensed.

So just to be sure, NOTICE should have listed all 3rd party but APL2 licensed 
code, while LICENCE should list all non-APL code?

> I didn’t check the binaries.
> 
> Thanks,
> Justin
> 
> 1. hw/bsp/nrf51dk/src/arch/cortex_m0/gcc_startup_nrf51.s
> 2. hw/bsp/stm32l152discovery/src/system_stm32l1xx.c
> 3. hw/bsp/nrf52840pdk/split-nrf52840pdk.ld
> 4. docs/_static/css/bootstrap-3.0.3.min.css
> 5 docs/themes/mynewt/static/js/affix.js
> 6 docs/themes/mynewt/static/js/scrollspy.js
> 7 docs/themes/mynewt/static/fonts/fontawesome-webfont.eot
> 8 docs/themes/mynewt/static/fonts/Inconsolata-Bold.ttf
> 9 docs/themes/mynewt/static/fonts/Lato-Bold.ttf
> 10 hw/mcu/arc/src/ext/sdk
> 11. ./hw/drivers/display/cfb/src/cfb_fonts.c
> 12 ./hw/mcu/dialog/include/DA1469xAB.h
> 13. ./hw/drivers/display/include/display/display.h
> 14. ./hw/drivers/display/cfb/include/display/cfb.h
> 15 ./hw/drivers/sensors/bmp388/src/bmp388_shell.c
> 16../hw/mcu/stm/stm32wbxx/src/ext/Drivers/CMSIS/Device/ST/STM32WBxx/Source/T
> emplates/gcc/linker/stm32wb55xx_flash_cm4.ld 17
> ./hw/drivers/sensors/icp101xx/License.txt
> 18 ./apps/coremark/include/core_portme.h


[20] https://github.com/apache/mynewt-core/pull/1819

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.8.0 and Apache NimBLE 1.3.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.

Apache NimBLE is Bluetooth Low Energy 5.1 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki: https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.8.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.3.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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * OS X 10.15
   * Fedora Linux 32

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.3.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 51fdaca7faffd9ff37df1b1d11f11007fc30c8cd
core:
  repos: https://github.com/apache/mynewt-core
  commit fce93de30559adcb9bbaa1807ace31a16505c988
newt:
  repos: https://github.com/apache/mynewt-newt
  commit ab96a8ac29568516dddf56af00bab856ebd93e18
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 199917cf7f3ff8443697ef03d67bb0459ba8339c
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 47cf31f687a5e56dd831f8387c9574f38bda0191

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newt-bin-linux-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newtmgr-bin-linux-1.8.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newt-bin-osx-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newtmgr-bin-osx-1.8.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newt-bin-windows-1.8.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.8.0/rc1/apache-mynewt-newtmgr-bin-windows-1.8.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

[DISCUSS] Release Apache Mynewt 1.8.0-rc1 and Apache NimBLE 1.3.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.8.0 and Apache NimBLE 1.3.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

Re: Issues with MSYS2 and pacman for newt on Windows

[Szymon Janc]

Hi,

On Thursday, 5 March 2020 20:08:01 CET Dhara Solanki wrote:
> Hello,
> 
> I am having issues with installing MSYS2 from the repo.
> I got another version from SourceForge, but when I issue command 'pacman
> -Syuu', it says Synchronizing database and then nothing else.
> 
> After this if I issue any pacman command, it gets stuck saying 'Cannot
> unlock database'.
> 
> I have tried more things to move past but unable to.
> 
> Was wondering if you have any other suggestions for using mynewt on Windows
> platform, or you suggest to move to MAC maybe?

I'm using 64bit version from https://www.msys2.org/ and it seems to work just 
fine under Windows 10.

-- 
pozdrawiam
Szymon Janc

Re: Simplifying Mynewt repo dependencies

[Szymon Janc]

Hi,

Great! And yes, I've read the whole email:-)

On Wed, 22 Jan 2020 at 16:04, Christopher Collins 
wrote:

> Hi Szymon,
>
> On Wed, Jan 22, 2020 at 12:33:21PM +0100, Szymon Janc wrote:
> > Hi Chris,
> >
> > Yes! Let's simplify this as much as possible.
> > Do I get this correctly that change we could (if want to) get rid of
> > release branches and just freeze master during release?
>
> Thanks for reading.  Yes, that is correct.  Branching is permitted but
> not required.
>
> Chris
>


-- 
pozdrawiam
Szymon K. Janc

Re: mynewt create-image no work at windows

[Szymon Janc]

Hi,

So I was able to bisect this to

commit e3fdcd68c9ed6fa58a6b68bbf3c45a780c57ab40 (refs/bisect/bad)
Author: Christopher Collins 
Date:   Mon Aug 5 11:15:33 2019 -0700

create-image: Generate a .hex file

Create a `.hex` equivalent of the `.img` file.  This feature used to be
present but was inadvertently removed at some point.




On Mon, 18 Nov 2019 at 10:21, Szymon Janc  wrote:

> Hi Jezus,
>
> Yes, I've been able to reproduce this and this indeed looks like false
> error message.
>
>
> On Fri, 15 Nov 2019 at 23:13, J. Ipanienko 
> wrote:
>
>> Hi there,
>>
>> good new
>>
>> create-image does image, error printing but image creating
>>
>> command which no work is:
>> MYNEWT /home/ipan/dev/myproj> newt run bluepill_blinky 0
>> Error: arm-none-eabi-objcopy: error: the input file
>> 'H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.img'
>> is empty
>>
>> I may load image with out error:
>> MYNEWT /home/ipan/dev/myproj> newt load bluepill_blinky 0
>> Loading app image into slot 1
>> MYNEWT /home/ipan/dev/myproj>
>>
>> then debug:
>> MYNEWT /home/ipan/dev/myproj> newt debug bluepill_blinky
>>
>> best lack
>> ipan
>>
>> > Sent: Thursday, November 14, 2019 at 11:13 PM
>> > From: "Jezus Ipanienko" 
>> > To: dev@mynewt.apache.org
>> > Subject: mynewt create-image no work at windows
>> >
>> > Welcome there,
>> >
>> > I have bluepill modul and I learned mynewt supporting it.
>> > I new at mynewt.
>> > I try newt release 1.7, work good.
>> > How I try build newt.exe at git master I have newt version 1.8.0-dev
>> >
>> > MYNEWT /home/ipan/dev/myproj> newt version
>> > Apache Newt
>> >Version: 1.8.0-dev
>> >   Git Hash: unknown
>> > Build Date: unknown
>> >
>> > How I try do:
>> > newt.exe create-image bluepill_blinky 0.0.0
>> > it do error:
>> > ...
>> > Linking
>> H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.elf
>> > Error: arm-none-eabi-objcopy: error: the input file
>> 'H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.img'
>> is empty
>> >
>> > version 1.7 do image, version 1.8 do not image
>> >
>> >
>> > I am interesting if newt version 1.7 work on mynewt-core master (no 1.7
>> release)?
>> >
>> > I have:
>> > MYNEWT /home/ipan/dev/myproj> go version
>> > go version go1.13.3 windows/amd64
>> > MYNEWT /home/ipan/dev/myproj> arm-none-eabi-gcc --version
>> > arm-none-eabi-gcc.exe (GNU Tools for Arm Embedded Processors
>> 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
>> >
>> > best luck
>> > ipan
>> >
>>
>
>
> --
> pozdrawiam
> Szymon K. Janc
>


-- 
pozdrawiam
Szymon K. Janc

Re: mynewt create-image no work at windows

[Szymon Janc]

Hi Jezus,

Yes, I've been able to reproduce this and this indeed looks like false
error message.


On Fri, 15 Nov 2019 at 23:13, J. Ipanienko 
wrote:

> Hi there,
>
> good new
>
> create-image does image, error printing but image creating
>
> command which no work is:
> MYNEWT /home/ipan/dev/myproj> newt run bluepill_blinky 0
> Error: arm-none-eabi-objcopy: error: the input file
> 'H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.img'
> is empty
>
> I may load image with out error:
> MYNEWT /home/ipan/dev/myproj> newt load bluepill_blinky 0
> Loading app image into slot 1
> MYNEWT /home/ipan/dev/myproj>
>
> then debug:
> MYNEWT /home/ipan/dev/myproj> newt debug bluepill_blinky
>
> best lack
> ipan
>
> > Sent: Thursday, November 14, 2019 at 11:13 PM
> > From: "Jezus Ipanienko" 
> > To: dev@mynewt.apache.org
> > Subject: mynewt create-image no work at windows
> >
> > Welcome there,
> >
> > I have bluepill modul and I learned mynewt supporting it.
> > I new at mynewt.
> > I try newt release 1.7, work good.
> > How I try build newt.exe at git master I have newt version 1.8.0-dev
> >
> > MYNEWT /home/ipan/dev/myproj> newt version
> > Apache Newt
> >Version: 1.8.0-dev
> >   Git Hash: unknown
> > Build Date: unknown
> >
> > How I try do:
> > newt.exe create-image bluepill_blinky 0.0.0
> > it do error:
> > ...
> > Linking
> H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.elf
> > Error: arm-none-eabi-objcopy: error: the input file
> 'H:/msys64/home/ipan/dev/myproj/bin/targets/bluepill_blinky/app/apps/blinky/blinky.img'
> is empty
> >
> > version 1.7 do image, version 1.8 do not image
> >
> >
> > I am interesting if newt version 1.7 work on mynewt-core master (no 1.7
> release)?
> >
> > I have:
> > MYNEWT /home/ipan/dev/myproj> go version
> > go version go1.13.3 windows/amd64
> > MYNEWT /home/ipan/dev/myproj> arm-none-eabi-gcc --version
> > arm-none-eabi-gcc.exe (GNU Tools for Arm Embedded Processors
> 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
> >
> > best luck
> > ipan
> >
>


-- 
pozdrawiam
Szymon K. Janc

newt upgrade (install, sync) fails on mcuboot repo

[Szymon Janc]

Hello,

Due to recent changes in mcuboot git (use of submodules) you may hit issues 
with newt upgrade|install|sync commands. There is a short term hotfix merged 
into newt master to workaround this.

Since this is also affecting new users we may need to release newt 1.7.1 (only 
newt tool) in next few days to address this issue.


-- 
pozdrawiam
Szymon Janc

packed structs for HCI

[Szymon Janc]

Hi,

This is something I was working on few past few weeks: using packed structs 
for building and parsing HCI commands in NimBLE stack. For easier transition
I decided to have one big commit affecting both controller and host (mind the 
size of change!:).

In general this follows similar changes done already for SMP and ATT. Packed 
structs are used for accesing and creating protocol ordered data. While 
parsing, unchanged data is passed up in stack as much as possible, so there 
are some API constifications required due to that.

As usual, rule of thumb is that protocol data is accessed via packed structs, 
and host ordered (parsed) data is (if needed) passed as unpacked structs. 

I decided to leave unit tests "as is", which means some defines were moved 
there and tests are stil using byte-by-byte parsing and contructions. I think 
this is fine since it provides additional cross checking for implemention :)

There are serveral benefits of this approach:
 - less source code - 4470 insertions(+), 6137 deletions(-)
 - easy to map where host and controller use same command/event
 - last but not least, less code size. Sample numbers for optimized build with
   most features enabled:
  nimble_controller.a 55602 -> 55246
  nimble_host.a   68001 -> 65285


Note that while PR is ready to be merged (no regressions in our tests), there 
is stil place for improvements: using packed structs for ACL, HCI transports, 
some cleanups in generic code for HCI handling etc. This will be work on later 
on.

PR implementing this is pending review at
https://github.com/apache/mynewt-nimble/pull/507

Comments are welcome.

-- 
pozdrawiam
Szymon Janc

Re: getting rid of ble_hs_dbg.c

[Szymon Janc]

Hi,

On Monday, 23 September 2019 15:52:45 CEST Łukasz Rymanowski wrote:
> Hi
> 
> On Mon, 23 Sep 2019 at 15:34, Andrzej Kaczmarek <
> 
> andrzej.kaczma...@codecoup.pl> wrote:
> > Hi,
> > 
> > On Wed, Sep 11, 2019 at 3:40 PM Szymon Janc 
> > 
> > wrote:
> > > Hi,
> > > 
> > > Since we have BLE_MONITOR support which is far superior copmaring to
> > > ble_hs_dbg.c... how about getting rid of that file?
> > 
> > I'm all for it and also for removing other "decoders" we have - these are
> > likely not up to date with new features anyway.
> > 
> > > Are there any active users relying on HCI events debugging via logs?
> > 
> > I never used it since it's just hard to follow - this was main reason why
> > monitor interface was added to make analyzing HCI stream much easier.
> 
> I agree, however we need a way to grab HCI logs not only on Linux machines.
> Maybe we could have some tool for Windows and maybe Macs which would store
> logs from monitor interface?
> Such logs could be easily read by btmon or wireshark.

PR removing protocol logs:
https://github.com/apache/mynewt-nimble/pull/581

-- 
pozdrawiam
Szymon Janc

getting rid of ble_hs_dbg.c

[Szymon Janc]

Hi,

Since we have BLE_MONITOR support which is far superior copmaring to 
ble_hs_dbg.c... how about getting rid of that file?

Are there any active users relying on HCI events debugging via logs?

-- 
pozdrawiam
Szymon Janc

draft for Mynewt Board Report for September 2019

[Szymon Janc]

Hi,

This is draft for September Board Report.
Any comments/additions?
 


## Description:
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:
None.

## Activity:
- Work on release 1.7.0 in August 2019
- NimBLE 1.2 stack release at same time
- BT SIG qualification done for NimBLE 1.2
- Community work in several areas including test facilities

## Health report:
- Users questions and contributor's pull requests are quickly dealt with
- It's been a long time since any PMC members have been voted in


## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aditi Hilbert on Wed Jun 21 2017

## Committer base changes:
- Currently 31 committers
- 1 new commiter voted (Amr Bekhit) on Jun 2019

## Releases:
- Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0 released August 4th

## Mailing list activity:

- Mailing list activity seeing new users and responders to questions asked
 (esp. questions from newcomers)
- Mailing list exchanges are mostly around NFC, BLE (and BLE mesh), test
facilities and LoRa
- Mailing list activity has dropped compared to last quarter
- Slack activity is up and more users have joined

## GitHub Issues activity:
- Issue types seen include change/feature requests, bug reports,
 contributions/PR, Q


-- 
pozdrawiam
Szymon Janc

Re: Deprecate "install" and "sync" commands?

[Szymon Janc]

Hi Chris,

Yes!  I'm also for option 3. Lets deprecate for next (1.8) release (make
those print proper warning info when used) and just remove for 1.9.




On Mon, 5 Aug 2019 at 18:47, Christopher Collins  wrote:

> Hello all,
>
> The newt tool supports three "project commands":
>
> * install
> * upgrade
> * sync
>
> I always have a hard time remembering the particulars of commands like
> these.  For example, when other package management systems support both
> "update" and "upgrade", I inevitably mix them up.  I propose we remove
> "install" and "sync", reducing the list to just one command.
>
> First, here is a refresher for each of these three commands:
>
> INSTALL: Downloads repos that aren't installed yet.  The downloaded
> version matches what `project.yml` specifies.
>
> UPGRADE: Performs an INSTALL, and then ensures the installed version of
> each repo matches what `project.yml` specifies.  This is similar to
> INSTALL, but it also operates on already-installed repos.
>
> SYNC: Fetches and pulls the latest for each repo, but does not change
> the branch (version).  Only necessary for Mynewt repo versions that
> point to a git branch (e.g., 0.0.0 usually points to "master").
>
> The distinction between these commands is somewhat subtle, so please
> ask if it isn't clear.
>
> I would like to remove INSTALL and SYNC.  I propose we do this as
> follows:
>
> A. Remove SYNC:
> A recent newt change allows us to deprecate SYNC:
> https://github.com/apache/mynewt-newt/pull/312.  With this change,
> `newt upgrade` always grabs the latest commit for repos with
> branch-versions.  So UPGRADE now subsumes SYNC.
>
> B. Remove INSTALL:
> I have never found the INSTALL to be very useful.  I find it easier to
> simply use UPGRADE instead.  It's just my experience, but there is never
> a time when I want to install new repos without updating existing ones.
> If you don't want to upgrade existing repos, then you can just not
> change their versions in `project.yml`.
>
> Alternatively, we don't have to go so far as to deprecate and remove
> these commands.  We could keep them, but just make them synonyms for
> `upgrade`.  This is a less disruptive option.
>
> So I see three options:
>
> 1. Change nothing.
> 2. Make "install" and "sync" synonyms for "upgrade".
> 3. Deprecate "install" and "sync"
>
> My vote is for 3, but I would be happy with 2.
>
> Thoughts?
>
> Chris
>


-- 
pozdrawiam
Szymon K. Janc

[ANNOUNCE] Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The releases are available here:
http://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.7.0

Release notes for Apache NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.2.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team

Re: [RESULT][VOTE] Release Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2

[Szymon Janc]

Hi,

And just to confirm, the resulting vote stil passed with +5 binding votes.

On Friday, 2 August 2019 14:36:19 CEST Szymon Janc wrote:
> Hi Justin,
> 
> Thanks for pointing that, I'll check against PMC list on next vote.
> 
> On Fri, 2 Aug 2019 at 10:53, Justin Mclean  wrote:
> > Hi,
> > 
> > Just a reminder that only PMC members votes are binding on releases.
> > 
> > From what I see Miguel, Martin and  Jerzy are listed as committers on the
> > project not PMC members. [1] (It’s either that or the roster is not up to
> > date.)
> > 
> > I also notice several PMC members are not subscribed to the private list
> > including some of those who voted on this release. All PMC members must be
> > subscribed to the private list, this has been brought up before, so please
> > if you are a PMC member please subscribe.
> > 
> > I'll also note that my email to the private list  on these subjects (and
> > some others) of a month or so ago got no response. Can the PMC please
> > respond.
> > 
> > Thanks,
> > Justin
> > 
> > 1. https://whimsy.apache.org/roster/committee/mynewt
> > 2.
> > https://lists.apache.org/thread.html/d59ccf4a1d3ebb4f874aabf415e3d37e80180
> > 143c7ed5de087985bee@%3Cprivate.mynewt.apache.org%3E


-- 
pozdrawiam
Szymon Janc

Re: [RESULT][VOTE] Release Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2

[Szymon Janc]

Hi Justin,

Thanks for pointing that, I'll check against PMC list on next vote.

On Fri, 2 Aug 2019 at 10:53, Justin Mclean  wrote:

> Hi,
>
> Just a reminder that only PMC members votes are binding on releases.
>
> From what I see Miguel, Martin and  Jerzy are listed as committers on the
> project not PMC members. [1] (It’s either that or the roster is not up to
> date.)
>
> I also notice several PMC members are not subscribed to the private list
> including some of those who voted on this release. All PMC members must be
> subscribed to the private list, this has been brought up before, so please
> if you are a PMC member please subscribe.
>
> I'll also note that my email to the private list  on these subjects (and
> some others) of a month or so ago got no response. Can the PMC please
> respond.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/committee/mynewt
> 2.
> https://lists.apache.org/thread.html/d59ccf4a1d3ebb4f874aabf415e3d37e80180143c7ed5de087985bee@%3Cprivate.mynewt.apache.org%3E
>
>

-- 
pozdrawiam
Szymon K. Janc

[RESULT][VOTE] Release Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2 is now closed. 
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Fabio Utzig (binding)
+1 Miguel Azevedo (binding)
+1 Michał Narajowski (binding)
+1 Łukasz Rymanowski (binding)
+1 Andrzej Kaczmarek (binding)
+1 Martin Turon (binding)
+1 Jerzy Kasenber (binding)
+1 Vipul Rahane (binding)

Total: +8 binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.7.0-rc2 and Apache NimBLE 1.2.0-rc2

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.7.0 and Apache NimBLE 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.

Apache NimBLE is Bluetooth Low Energy 5.0 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.7.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/
Apache+NimBLE+Test+Plan
 The test results can be found at:
 https://cwiki.apache.org/confluence/display/MYNEWT/
NimBLE+1.2.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 both releases was executed via
 "newt test all" with no failures. This testing was performed on the
 following platforms:
   * OS X 10.14
   * Fedora Linux 30

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.2.0/rc2/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 1007e978f2655b3e054099ff8600d147a79b369b
core:
  repos: https://github.com/apache/mynewt-core
  commit b7a5474d569d5b67152d1773627ddda010c080a3
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 80bcba727dfe828dcb1f8da522f0502377d18fd4
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit a222bac117793db7b8444acfb744dcb822a6f448
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 5371a45890604d32564c6384eb00dfee74ee7d13

In addition, the following newt and newtmgr convenience binaries are 
available:
  linux: 
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newt-bin-linux-1.7.0.tgz
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newtmgr-bin-linux-1.7.0.tgz

  osx: 
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newt-bin-osx-1.7.0.tgz
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newtmgr-bin-osx-1.7.0.tgz

  windows:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newt-bin-windows-1.7.0.tgz
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc2/
apache-mynewt-newtmgr-bin-windows-1.7.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

[CANCEL][VOTE] Release Apache Mynewt 1.7.0-rc1 and Apache NimBLE 1.2.0-rc1

[Szymon Janc]

Hello all,

This vote for Apache Mynewt 1.7.0-rc1 and Apache NimBLE 1.2.0-rc1 is being 
cancelled due for the following reasons:
 * we identified critical regression affecting controller which lead to memory 
   corruption and crash. Issue is being track at 
   https://github.com/apache/mynewt-nimble/issues/532 and once fixed rc2 will
   be released

Thanks all for your patience. You will be seeing a new [VOTE] thread
soon.


-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.7.0-rc1 and Apache NimBLE 1.2.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.7.0-rc1 and Apache NimBLE 1.2.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.7.0 and Apache NimBLE 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.

Apache NimBLE is Bluetooth Low Energy 5.0 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future
NimBLE releases may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache
Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.7.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.2.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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * OS X 10.14
   * Fedora Linux 30


The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.1.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 1007e978f2655b3e054099ff8600d147a79b369b
core:
  repos: https://github.com/apache/mynewt-core
  commit b7a5474d569d5b67152d1773627ddda010c080a3
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 80bcba727dfe828dcb1f8da522f0502377d18fd4
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit a222bac117793db7b8444acfb744dcb822a6f448
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 0678bae06ede574a0e6c33acf7a5427a0fcb9efa

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newt-bin-linux-1.7.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newtmgr-bin-linux-1.7.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newt-bin-osx-1.7.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newtmgr-bin-osx-1.7.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newt-bin-windows-1.7.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.7.0/rc1/apache-mynewt-newtmgr-bin-windows-1.7.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

Upcoming Apache Mynewt 1.7

[Szymon Janc]

Dear Apache Mynewt Community,

It has been three months since last Apache Mynewt release. This email is to 
give you a heads up that we are going to make next release (1.7) in July 
(tentative rc1 date is ~10th July).

If there are any features or bug fixes you are working on (and want them to be 
part of 1.7 release) do not hesitate to send pull requests!

Please note that this will be coordinated with NimBLE 1.2 release.

-- 
pozdrawiam
Szymon Janc

Re: Question about FPGA's

[Szymon Janc]

Hi,

It looks like RN-42 is Bluetooth 2.1 chip with high level features like HID
peripheral, so this isn't something you can run Mynewt BLE stack on.

On Fri, 19 Apr 2019 at 02:14, will sanfilippo  wrote:

> Not sure if anyone answered you Rafael but porting the stack to a new
> processor can be tricky depending on what you want to port. The controller
> would be quite tricky but the host would be doable. Not sure if that is
> something you want to explore. I took a quick peek at the RN-42 but could
> not find information about the BLE processor in there… And btw: porting the
> host would mean you would still need some way to send things to the
> controller on that board so probably not what you want.
>
> Will
>
> > On Apr 15, 2019, at 4:08 AM, Rafael A. Becerra 
> wrote:
> >
> > Hi,
> >
> > Im a 5th year computer engineering student and was wondering if you guys
> could give me any insight to this: Currently doing a side project using an
> FPGA(NEXYS 4) with a RN-42 (PMOD BT2) bluetooth module attached via a UART
> port to send data between the fpga to another PC. The RN-42 has an embedded
> bluetooth stack already but if I wanted to, could I replace the that
> bluetooth stack in the RN-42 chip with Apache MyNewt? If I could, what
> would be the best way to go about it?
> >
> >
> > Sincerely,
> >
> > Rafael Becerra
> > Cal Poly Pomona
> >
> > Sent from Mail for
> Windows 10
> >
>
>

-- 
pozdrawiam
Szymon K. Janc

switching to mcuboot

[Szymon Janc]

Hi,

As discussed on several occasions we want to move away from bootutils and
start using mcuboot project directly.

PR implementing this is here https://github.com/apache/mynewt-core/pull/1763
It is not yet ready to be merged due to some issues with tests on mcuboot
side

Open points for this PR which I'd like to get some feedback on:
 - fixing (or removing?) tests that are executed with newt test all
 - should newt create-image default to new image header version (-2 option)
once we switch to mcuboot?
 - which mcuboot version should core track? Since it is external project I
suggest that master
  tracks 1-latest and when we release we stick to latest released version
at that time (eg core 1.7.0 would depend on mcuboot 1.3.0, 1.8 on 1.4.0 if
released etc)


-- 
pozdrawiam
Szymon K. Janc

Re: Removing transient packages from core

[Szymon Janc]

Hi,

Yes, I've started working on that

On Wed, 10 Apr 2019 at 16:55, Sterling Hughes <
sterling.hughes.pub...@gmail.com> wrote:

> Hi Szymon,
>
> Great, while you are looking at this, it would be excellent if you could
> also do:
>
> https://github.com/apache/mynewt-core/issues/1695
>
> It would be good to get time on these changes to stabilize prior to next
> release.
>
> Sterling
>
> On 10 Apr 2019, at 6:17, Szymon Janc wrote:
>
> > Hi,
> >
> > Just a heads up that since we are right after release it is good time
> > to
> > start doing housekeeping :)
> >
> > PR removing transient packages is pending review:
> > https://github.com/apache/mynewt-core/pull/1757
> >
> > Make sure to update your targets when this gets merged!
> >
> > --
> > pozdrawiam
> > Szymon K. Janc
>


-- 
pozdrawiam
Szymon K. Janc

Removing transient packages from core

[Szymon Janc]

Hi,

Just a heads up that since we are right after release it is good time to
start doing housekeeping :)

PR removing transient packages is pending review:
https://github.com/apache/mynewt-core/pull/1757

Make sure to update your targets when this gets merged!

-- 
pozdrawiam
Szymon K. Janc

[ANNOUNCE] Apache Mynewt 1.6.0 and Apache NimBLE 1.1.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.6.0 and Apache NimBLE 1.1.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The releases are available here:
http://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.6.0

Release notes for Apache NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.1.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.6.0-rc2 and Apache NimBLE 1.1.0-rc2

[Szymon Janc]

Hello All,

Voting for Apache Mynewt 1.6.0-rc2 and Apache NimBLE 1.1.1-rc2 is now closed. 
The release has passed this step of the process. The vote breakdown is as 
follows:

+1 Fabio Utzig (binding)
+1 Miguel Azevedo (binding)
+1 Michał Narajowski (binding)
+1 Łukasz Rymanowski (binding)
+1 Christopher Collins (binding)
+1 Andrzej Kaczmarek (binding)

Total: +6 binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.6.0-rc2 and Apache NimBLE 1.1.0-rc2

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.6.0 and Apache NimBLE 1.1.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.6.0-rc2 and Apache NimBLE 1.1.0-rc2

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.6.0 and Apache NimBLE 1.1.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.

Apache NimBLE is Bluetooth Low Energy 5.0 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future NimBLE 
releases
may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache 
Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.6.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.1.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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * OS X 10.14
   * Fedora Linux 29


The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.1.0/rc2/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 8cad686874cd2824a5cd483df7254870f8ac5e88
core:
  repos: https://github.com/apache/mynewt-core
  commit eb1d3ec0f486d92887586f60d87f0bb916188515
newt:
  repos: https://github.com/apache/mynewt-newt
  commit da3758b66fa010cd8db7d5ae60a1a9dfaf97db8c
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 06ecbd65d47ca1c52b367d2be7f8c3a69d5bd195
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 223714cb16c255cfa701929c0de6d7579bfd2cdd

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newt-bin-linux-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newtmgr-bin-linux-1.6.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newt-bin-osx-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newtmgr-bin-osx-1.6.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newt-bin-windows-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc2/apache-mynewt-newtmgr-bin-windows-1.6.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

[CANCEL][VOTE] Release Apache Mynewt 1.6.0-rc1 and Apache NimBLE 1.1.0-rc1

[Szymon Janc]

Hello all,

This vote for 1.6.0-rc1 Apache Mynewt and 1.1.0-rc1 Apache NimBLE is being 
cancelled due for the following reasons:
 * newt tool issue on Windows preventing 'newt install' to work
 * openocd not working properly on Windows
 * few issues with STM32 boards
 * NimBLE certification regression on nRF52840

Thanks all for your patience. You will be seeing a new [VOTE] thread soon.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.6.0-rc1 and Apache NimBLE 1.1.0-rc1

[Szymon Janc]

Hello all,

I am pleased to be calling this vote for the source release of
Apache Mynewt 1.6.0 and Apache NimBLE 1.1.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.

Apache NimBLE is Bluetooth Low Energy 5.0 stack from Apache Mynewt.

This release is coordinated release of Apache Mynewt and NimBLE. Future NimBLE 
releases
may be released separately depending on needs.

For full release notes for both Mynewt and NimBLE, please visit the Apache 
Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

Apache Mynewt and Apache NimBLE release candidates were 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.6.0+Test+Results
  2. Manual execution of the NimBLE test plan:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+NimBLE+Test+Plan
 The test results can be found at:
 
https://cwiki.apache.org/confluence/display/MYNEWT/NimBLE+1.1.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 both releases was executed via "newt test all"
 with no failures. This testing was performed on the following platforms:
   * OS X 10.14
   * Fedora Linux 29


The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/
https://dist.apache.org/repos/dist/dev/mynewt/apache-nimble-1.1.0/rc1/

The commits under consideration are as follows:
blinky:
  repos: https://github.com/apache/mynewt-blinky
  commit 8cad686874cd2824a5cd483df7254870f8ac5e88
core:
  repos: https://github.com/apache/mynewt-core
  commit 5ff4c8a05bc102aeaa99b5bcb9409713e473db01
newt:
  repos: https://github.com/apache/mynewt-newt
  commit 8de945675f9b45a014eb5491259f6e0b5b74bcd6
newtmgr:
  repos: https://github.com/apache/mynewt-newtmgr
  commit 06ecbd65d47ca1c52b367d2be7f8c3a69d5bd195
nimble:
  repos: https://github.com/apache/mynewt-nimble
  commit 884a8b088fad4d994750a68f4bad57abe023

In addition, the following newt and newtmgr convenience binaries are available:
  linux: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newt-bin-linux-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newtmgr-bin-linux-1.6.0.tgz

  osx: 

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newt-bin-osx-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newtmgr-bin-osx-1.6.0.tgz

  windows:

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newt-bin-windows-1.6.0.tgz

https://dist.apache.org/repos/dist/dev/mynewt/apache-mynewt-1.6.0/rc1/apache-mynewt-newtmgr-bin-windows-1.6.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

[DISCUSS] Release Apache Mynewt 1.6.0-rc1 and Apache NimBLE 1.1.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.6.0 and Apache NimBLE 1.1.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

Upcoming Apache Mynewt 1.6 release

[Szymon Janc]

Dear Apache Mynewt Community,

It has been three months since last Apache Mynewt release. This email is to 
give you a heads up that we are going to make next release (1.6) in mid March 
(tentative rc1 date is ~10th March).

If there are any features or bug fixes you are working on (and want them to be 
part of 1.6 release) do not hesitate to send pull requests!

-- 
pozdrawiam
Szymon Janc

[ANNOUNCE] Apache Mynewt 1.5.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of Apache Mynewt  
1.5.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The Apache Mynewt release is available here:
http://www.apache.org/dyn/closer.lua/mynewt/apache-mynewt-1.5.0

Release notes are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.5.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team

[RESULT][VOTE] Release Apache Mynewt 1.5.0-rc1

[Szymon Janc]

Hello all,

Voting for Apache Mynewt 1.5.0-rc1 is now closed.  The release has passed this 
step of the process. The vote breakdown is as follows:

+1 Łukasz Rymanowski (binding)
+1 Fabio Utzig (binding)
+1 Vipul Rahane (binding)
+1 Christopher Collins (binding)
+1 Andrzej Kaczmarek (binding)
+1 Aditi Hilbert (binding)
+1 Kevin Townsend


Total: +6 binding, +1 non-binding

Thank you to all who voted.

-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.5.0-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.5.0.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.5.0-rc1

[Szymon Janc]

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

Upcoming Apache Mynewt 1.5 release

[Szymon Janc]

Dear Apache Mynewt Community,

It has already been 3 months since Apache Mynewt 1.4 release. We plan to tag 
1.5.0-rc1 next week so if there are any features that you feel should go in, 
please make sure to merge appropriate PRs in next few days.

-- 
pozdrawiam
Szymon Janc

BLE sample apps removal from core repo

[Szymon Janc]

Hi,

As discussed some time ago, BLE sample apps that were moved to nimble repo are 
going to be removed from core repo. PR implementing this is now under review 
https://github.com/apache/mynewt-core/pull/1310

Please make sure to update your targets.

-- 
pozdrawiam
Szymon Janc

Re: BLE GATT Characteristic ENC AUTHEN and AUTHOR flag meanings

[Szymon Janc]

Hi,

On Tuesday, 17 July 2018 10:59:41 CEST Amr Bekhit wrote:
> Hello,
> 
> Can someone explain (or help point to documentation) the ENC, AUTHEN
> and AUTHOR flags that are used in GATT characteristics? I've noticed
> that using them in combination with the normal READ and WRITE flags
> causes the central to request a pin code when it tries to access the
> characteristic, but other than that, what each flag means and how they
> can be combined together is unclear to me.

ENC means that operation (read or write) on characteristic requires encryption 
(MITM protected or not).

AUTHEN means that operation requires authentication (encryption with MITM 
protected key).

AUTHOR means that operation requires authorization - that gives your 
application means to rejected read/write operation based on your own 
authorization mechanism (eg user pushing a button).


For more details I suggest getting into Bluetooth Core Specification.

-- 
pozdrawiam
Szymon Janc

[ANNOUNCE] Apache Mynewt 1.4.1 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of Apache Mynewt 
1.4.1.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The Apache Mynewt release is available here:
http://www.apache.org/dyn/closer.lua/mynewt/apache-mynewt-1.4.1

Release notes are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.4.1

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team
-- 
pozdrawiam
Szymon Janc

[RESULT][VOTE] Release Apache Mynewt 1.4.1-rc1

[Szymon Janc]

Hello all,

Voting for Apache Mynewt 1.4.1 is now closed.  The release has passed this 
step of the process.  The vote breakdown is as follows:

+1 Christopher Collins (binding)
+1 Fabio Utzig (binding)
+1 Sterling Hughes   (binding)
+1 Aditi Hilbert (binding)
+1 Vipul Rahane (binding)
+1 Andrzej Kaczmarek (binding)
+1 Łukasz Rymanowski (binding)
+1 Sasa Petrovic

Total: +7 binding, +1 non-binding

Thank you to all who voted.
-- 
pozdrawiam
Szymon Janc

[DISCUSS] Release Apache Mynewt 1.4.1-rc1

[Szymon Janc]

Hi all,

This thread is for any and all discussion regarding the release of
Apache Mynewt 1.4.1.  All feedback is welcome.

-- 
pozdrawiam
Szymon Janc

[VOTE] Release Apache Mynewt 1.4.1-rc1

[Szymon Janc]

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: Greetings

[Szymon Janc]

Hi Jeff,

On Friday, 15 June 2018 19:17:07 CEST Jeff Belz wrote:
> All devs:
> 
> Greeting to all of you.I'm really new to mynewt so bear with me as I get
> to know the ropes.
> 
> I have some questions:
> 
>   1.  Newt upgrade seems to not work.  What is the proper way to use this
> command.   I currently have 1.3, but need to update to 1.4 .  I am using
> Windows 10.

Ouch, it looks like 1.4 build is broken on Windows. I'll be doing 1.4.1 point 
release next week so this should be fixed soon.

> 2.  The End goal for me is to use the nimBLE stack on a
> STM32F412., however at the end of the day I have to use TrueStudio for STM
> to write my application code.   Will mynewt compile a library to include
> into project?

You should be able to create package with your lib that can be included into 
project.

> 3.  Any project examples out there that use Eclipes,
> TrueStudio or Keil  and nimBLE?

There is tutorial on how to set up Visual Studio Code for Mynewt [1].
For Eclipse you may check our blog [2] but this was tested on Linux only.


[1] http://mynewt.apache.org/develop/misc/ide.html
[2] https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse/

-- 
pozdrawiam
Szymon Janc

Re: Changing modules in the shell

[Szymon Janc]

Hi Amr,

On Wednesday, 13 June 2018 08:55:11 CEST Amr Bekhit wrote:
> After playing around some more, it appears that this only works when you
> are in the base "shell" module, but not from other sub-modules.

Yes, I think that was the intention that it works from top menu when no 
subshell is selected. Maybe we should update docs to clarify that..

> 
> On Tue, 12 Jun 2018 at 15:08, Amr Bekhit  wrote:
> > Hello all,
> > 
> > Quick intro - I've recently started using mynewt and hoping to use it
> > primarily for the Bluetooth and LoraWAN functionality. I quite like the
> > package and syscfg system in mynewt, I think it's very flexible and I look
> > forward to seeing the project grow. I've managed to make a small
> > contribution (
> > https://github.com/apache/mynewt-core/pull/1180#pullrequestreview-12750593
> > 1) and hope to get involved more.
> > 
> > I have a question regarding shell modules (mynewt master - cloned
> > 2018/06). I've created a new shell module and registered it using
> > shell_register, then set it as the default module
> > using shell_register_default_module. The module works fine and I can
> > access
> > the commands no problem. I can use the select command to to change modules
> > as described in the documentation (
> > https://mynewt.apache.org/latest/os/modules/shell/shell/), but the
> > documentation also states the following:
> > 
> > "To run a command in the shell, you enter the module name and the command
> > name."
> > 
> > I can't seem to get this to work - if the compat module is currently set,
> > and I have a module "gpio" with a command "set", I can't seem to run "gpio
> > set" from within the compat module.
> > 
> > Amr


-- 
pozdrawiam
Szymon Janc