Re: [DISCUSS] Release Apache Mynewt 1.0.0-b2-incubating-rc1

Hi, > should the NOTICE files be updated with 2017? Yep but not a blocking issue for an incubator vote. Thanks, Justin

Re: sysint() fails

Ok, now I'm very confused ... The newt tool is what is used to BUILD newt apps, etc. The newt-core stuff is what the apps are built out of. So what I'm getting here is that an out-of-date newt tool will build bad mynewt apps, even if all the parts that are used in the app are correct? If

Re: externalized nrf5 adc include

In your pkg.yml file: "@mynewt_nordic/hw/drivers/adc/adc_nrf52" In your source file: #include #include #include "nrf_drv_saadc.h" For an ADC app that (at least used to work) see https://github.com/davidgs/incubator-mynewt-core/blob/adc_demo/apps/nrf52_adc/src/main.c dg > On Feb 7, 2017,

Re: [DISCUSS] Release Apache Mynewt 1.0.0-b2-incubating-rc1

Got it! Thanks for figuring it out. I updated the NOTICE files in develop branch, so they’ll be ready for 1.0.0. I don’t these things are blockers for beta. > On Feb 7, 2017, at 11:15 AM, will sanfilippo wrote: > > The mynewt binary that was committed was built with go

externalized nrf5 adc include

Im not sure how to include, or if nrf adc works. If I add - "@mynewt_nordic/hw/mcu/nordic_sdk" I get: Error: repos/mynewt_nordic/hw/drivers/adc/adc_nrf51/src/adc_nrf51.c:27:21: fatal error: nrf_adc.h: No such file or directory #include Am I missing some other resources in pkg? or is

Re: [VOTE] Release Apache Mynewt 1.0.0-b2-incubating-rc1

+1 to release. Everything I checked seems ok. > On Feb 7, 2017, at 11:25 AM, Padmasheela kiiskila wrote: > > >> [X ] +1 Release this package >> [ ] 0 I don't feel strongly about it, but don't object >> [ ] -1 Do not release this package because… >> > +1 (binding) > >

Re: sysint() fails

Hi David, can you get a backtrace of that crash? Develop branch and the 1.0.0 beta2 release branches have diverged a bit, so we should see what this assert() is about. One issue I ran across a month back with nrf52 and sys/reboot package. The flash area containing FCB was holding some other

Re: [VOTE] Release Apache Mynewt 1.0.0-b2-incubating-rc1

> [X ] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because… > +1 (binding) -Sheela

Re: [VOTE] Release Apache Mynewt 1.0.0-b2-incubating-rc1

> [X ] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because… > +1 (binding) > Hello all, > I am pleased to be calling this vote for the source release of Apache > Mynewt 1.0.0, beta 2. > > Apache Mynewt is a

Re: [VOTE] Release Apache Mynewt 1.0.0-b2-incubating-rc1

On Mon, Feb 06, 2017 at 05:32:55PM -0800, will sanfilippo wrote: > [X] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because… +1 (binding) Chris

Re: [DISCUSS] Release Apache Mynewt 1.0.0-b2-incubating-rc1

The mynewt binary that was committed was built with go version 1.6. There are issues with running go binaries on newer versions of mac osx if they were built with 1.6 so that is the reason it is crashing (I suspect). You need go 1.7 if you are running macOS 10.12 Sierra. > On Feb 7, 2017, at

Re: sysint() fails

Hello David: I did not attempt to re-test all the apps you mentioned below, but bletiny on the nrf52dk is working just fine. Another note: the release is on branch 1_0_0_b2_dev. That is the branch I would use, or check out the tag (mynewt_1_0_0_b2_rc1_tag). Thanks > On Feb 7, 2017, at 8:07

Re: sysint() fails

Hi David, Could your version of the newt tool be out of date? Some backwards compatibility breaking changes were made about two weeks ago. If that isn't the problem, could you grab a backtrace in gdb at the point of the crash ("bt" or "where" in gdb)? Thanks, Chris On Tue, Feb 07, 2017 at

sysint() fails

Having some trouble this morning with the nrf52dk board. 389 sysinit(); (gdb) n Program received signal SIGTRAP, Trace/breakpoint trap. __assert_func (file=file@entry=0x0, line=line@entry=0, func=func@entry=0x0, e=e@entry=0x0) at