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: Docker container

I do like the idea of the docker btw. Even without newt compile, one thing I was hoping to use it for was newtmgr for bluetooth transport as apparently this is unsupported on osx atm (though I cant find a link to why.. anyone?) On Sun, Jan 22, 2017 at 12:40 PM, Sterling Hughes <

Re: [ATTENTION] incubator-mynewt-core git commit: os; spin up OS before calling. main() gets called in context of main task.

Looks like this breaks splitty as app, bleprph as loader Error: Syscfg ambiguities detected: Setting: OS_MAIN_TASK_PRIO, Packages: [apps/bleprph, apps/splitty] Setting history (newest -> oldest): OS_MAIN_TASK_PRIO: [apps/splitty:10, apps/bleprph:1, kernel/os:0xfe] Setting

newtmgr firmware update with BLE transport

Anybody used the ble transport for newtmgr image update? Im told it doesnt work in osx, anyone have a link to an open issue? I havent gotten in linux docker or native yet either. nrf51 16kbram, bleloader with splitty app, all upstream sources, newtmgr with serial confirmed working dfu service

Re: Tutorial problem with the Docker Container

Whats the easy way to get 'develop' in the docker? On Fri, Jan 20, 2017 at 9:34 AM, Christopher Collins wrote: > On Fri, Jan 20, 2017 at 11:55:59PM +0800, Li-Chun Ko wrote: > > As an update, the Docker Container works well with the "./newt test all" > > commend. > > Great

Re: Newtmgr over BLE

Or at least the newtmgr code as a dependency ;) On Wed, Jan 25, 2017 at 6:52 AM, David G. Simmons wrote: > ook at this app ... >

Re: ADC on Arduino Primo

On Feb 17, 2017, at 3:47 PM, Jacob Rosenthal <jakerosent...@gmail.com> > wrote: > > > > OK.. nevermind. Im just pasting code in all the wrong places and > confusing > > myself. I > > > > Thoughts on hosting myadc package on github to keep the user

Re: ADC on Arduino Primo

David, some questions about your recent adc tutorial. First off, thanks for pushing code for me to think about and learn about the newt stack from It seems like your tutorial is more about writing a NEW adc driver rather than utilizing the existing mynewt-nordic driver. For me anyway, a tutorial

Re: ADC on Arduino Primo

, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > David, some questions about your recent adc tutorial. > > First off, thanks for pushing code for me to think about and learn about > the newt stack from > > It seems like your tutorial is more about writing a NEW adc driver

Re: ADC on Arduino Primo

instead of my_adc would start me down a better path. also there is a missing include in main.c #include "myadc/myadc.h" #include Sorry for the noise. Thanks for the example! I think I can figure out how to alter this into an nrf51 version now. On Fri, Feb 17, 2017 at 4:15 PM, Jacob

Hackillinois this weekend in Urbana IL

Hey newt folks, Im mentoring at https://hackillinois.org/ this weekend on bluetooth and embedded in general ~1000 Students will create and contribute to open source projects all weekend starting friday. Im not sure what skill levels and languages Ill have available to me, but if anyone has ideas

Config id package

Im trying to build a DIS service with identification strings like bsp and app name from config/id package with conf_get_value I think Im using the api correctly? char *val; int rc; uint16_t uuid16; char tmp_buf[32 + 1]; ///hwid is only one that needs some tmp buffer

Re: newtmgr over serial hanging

I can shell to both boards and send and receive characters, so I know uart is ok. And the target syscfg are identical, as are the targets I believe, heres a recursive target diff, looks like just names Jacobs-MacBook-Air:mynewt-button-example jacobrosenthal$ diff -r targets/split-tinyble/

Re: externalized nrf5 adc include

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, at 3:30 PM, Jacob Rosenthal &l

Re: Single Bank firmware update (ie nordic vendor style dfu)

n generating the sysinit_app() > function, the tool excluded packages which are not explicitly referenced > in the app's dependency tree. This is wrong; all packages should get > initialized in the second stage app. > > Thanks, > Chris > > > On Fri, Jan 13, 2017

Re: Single Bank firmware update (ie nordic vendor style dfu)

.org> wrote: > On Tue, Jan 17, 2017 at 05:47:49PM -0700, Jacob Rosenthal wrote: > > Thanks Chris! Tried some more with the new upstreamed code but a few > > more issues... > > > > > > Still had to add the serial transport to bleprph, not sure if you left

Re: Firmware update with MyNewt

without > going through newtmgr command? > > Thank you. > > Regards, > > Then Yoong Ze > > > On 18/1/2017 2:22 PM, Jacob Rosenthal wrote: > >> Youll find another thread (now poorly) titled "Single Bank firmware update >> (ie nordic vendor style

Re: issue with FCB reboot logs

This comes up a lot Ive noticed, at least with nrf51. I was thinking that the bsp could expose an erase for newtmgr for the cases when it does On Tue, Feb 28, 2017 at 12:24 PM, marko kiiskila wrote: > > > On Feb 28, 2017, at 7:59 AM, Christopher Collins >

Re: Hackillinois this weekend in Urbana IL

o add a driver for a sensor (or sensors). > > Let us know how it goes! > > > On Feb 22, 2017, at 1:34 PM, Jacob Rosenthal <jakerosent...@gmail.com> > wrote: > > > > Hey newt folks, > > > > Im mentoring at https://hackillinois.org/ this weekend on bluetooth

Re: ADC on Arduino Primo

uff: > > https://github.com/runtimeinc/mynewt_nordic > > The hope is to merge the repo into core once Nordic relicenses their SDK. > > Sterling > > > On 28 Feb 2017, at 20:03, Jacob Rosenthal wrote: > > This arrived today with b3be6f034169efaa53511b9da0905c4bba014608 >>

Re: ADC on Arduino Primo

/jacobrosenthal/mynewt-nrf51-adc-driver https://github.com/jacobrosenthal/mynewt-nimble-services/ tree/master/services/battery Thanks all! On Mon, Feb 20, 2017 at 10:19 PM, Sterling Hughes < sterling.hughes.pub...@gmail.com> wrote: > Hi Jacob, > > This is awesome. > > On 20 Feb

Re: Single Bank firmware update (ie nordic vendor style dfu)

of the failed attempt since I have the shell? On Thu, Jan 12, 2017 at 7:51 PM, Christopher Collins <ccoll...@apache.org> wrote: > On Thu, Jan 12, 2017 at 07:06:37PM -0700, Jacob Rosenthal wrote: > > Still ok... and Im able to interact with shell over serial and I think > i

Re: Single Bank firmware update (ie nordic vendor style dfu)

log on shell shows lots of these 9050:[0] rsn:SOFT, cnt:1, img:0.0.0.0 On Thu, Jan 12, 2017 at 8:28 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > All newtmgr commands on serial are hanging indefinitely. > Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newtmgr -c ser

Re: Single Bank firmware update (ie nordic vendor style dfu)

turned off a ton more bluetooth shit for more ram both still hang: newtmgr -c serial1 logs log_list newtmgr -c serial1 image list but log in shell now has: newtmgr 4976:Dumping log reboot_log On Thu, Jan 12, 2017 at 8:33 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > log

Single Bank firmware update (ie nordic vendor style dfu)

On low flash devices like nrf51822 FLASH_AREA_IMAGE_1 equal to FLASH_AREA_IMAGE_0 is improbable, which means dual bank is likewise improbable and as a result we've talked previously about how to shrink FLASH_AREA_IMAGE_1 down to a stub. However, my current understanding is newtmgr/imagemgr

Re: Removing or shrinking flash areas

I think deps are a part of the story, but yeah the goal is to successfully get a target bsp back to 1 larger flash image, or as many as the common set of deps require but shrunk way down. On Fri, Dec 30, 2016 at 2:32 PM, Christopher Collins wrote: > nted to remove

Removing or shrinking flash areas

I worked with Sterling to shrink the nimble stack for 256k flash devices, but Im starting to cut into pretty basic functionality. Ive noticed that even not using splitty/flash reboot logging those are enable in the bsp I forked (nrf51dk-16kbram) Any guidance on removing or shrinking those? Whats

Re: Removing or shrinking flash areas

I think I want a bootloader, and Im ok with stub solutions 'losing' a little flash space, especially if some other dep might still want a little bit of that space. For nrf51 targets it seems like I just wont have room to split equally at the very least. What other deps use flash areas? My

Re: Removing or shrinking flash areas

I think were on the same page now. We were talking about 'stub' in previous posts, which Im going to you've listed here as 'Single image' The nrf51dk-16kbram Im forking for my target seems set up for Dual bank, with two equal sized flash areas. Sounds like split is what Im actually looking for

Re: Removing or shrinking flash areas

(unduplicated)access to nimble so it could receive bytes via bluetooth in the bootloader without duplicating that code... Whats the newt way :) Thoughts? On Fri, Dec 30, 2016 at 5:13 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > I think I want a bootloader, and Im ok with stub

Re: blecent demo

Oh perfect. I dont particularly care about ans myself, I didnt realize bleprp was an ans client. In the documentation is just says "bleprph: An implementation of a minimal BLE peripheral." If they work together thats enough for me On Tue, Dec 20, 2016 at 1:32 PM, Christopher Collins

Re: ble_gattc_disc_svc_by_uuid problems

Thanks for the quick replies. I changed to repository.apache-mynewt-core: type: github vers: 0-latest user: apache repo: incubator-mynewt-core Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newt run nrf51822xxaa_blecenthr 0.0.0 Compiling main.c Compiling misc.c Compiling

Re: ble_gattc_disc_svc_by_uuid problems

need to upgrade newt as well. You can do that as follows: > > cd $GOPATH && > git checkout develop && > git pull && > go install > > Hopefully that fixes the compile problem. Please report back if you > encounter any issues. > >

ble_gattc_disc_svc_by_uuid problems

Hey all, been working with mynewt for a week or so now, trying to understand the code and slim the nimble stack down for nrf51822qfaa targets. Playing with central role now (modified blecent), and Im having some trouble searching for a single svc by uuid (to save peer struct memory, rather than

Target download pathing issues

Im seeing all sorts of errors with targets on my osx 10.12.3 Some targets cant find download script Error: fork/exec /Users/jacobrosenthal/Downloads/xxx/repos/apache- mynewt-core/hw/bsp/bbc_microbit/microbit_download.sh: no such file or directory and if I ls

Re: Target download pathing issues

In trying to reproduce for Fabio in irc we realized I couldnt run newt scripts at all Jacobs-Air:newt jacobrosenthal$ ./build.sh -bash: ./build.sh: /bin/sh^M: bad interpreter: No such file or directory My line endings got windows-ed at some point Jacobs-Air:apache-mynewt-core jacobrosenthal$

newtmgr image upload nrf51dk disconnects with reason=8

I got a linux partition and newtmgr working finally, However the upload command fails after writing one packet. The logs appear to show BLE_HS_ENOTSUP , but I just cant find where that could becoming from! any help appreciated :) Jacobs-MacBook-Air:chippd3 jacobrosenthal$ newt target show

Re: newtmgr image upload nrf51dk disconnects with reason=8

lers that we have had > issues with. Try disabling Data Length Extension. Set > BLE_LL_CFG_FEAT_DATA_LEN_EXT in net/nimble/controller/syscfg.yml to 0 > > Let us know if that changes anything. > > On Apr 16, 2017, at 6:13 PM, Jacob Rosenthal <jakerosent...@gmail.com> >

Re: newtmgr image upload nrf51dk disconnects with reason=8

You can try increasing the supervision timeout in the BLE settings, > that’s what I needed to do to get the newtmgr working in Go. > > > > Regards, > > Vipul Rahane > > > >> On Apr 20, 2017, at 11:16 AM, Jacob Rosenthal <jakerosent...@gmail.com> > wrote: > >>

Re: newtmgr image upload nrf51dk disconnects with reason=8

ot sure what that maps to yet though.. On Thu, Apr 20, 2017 at 1:40 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > Is it actually necessary to disable interrupts during the flash erase? > Seems like most hals do it, though maybe not the STM? >

Re: newtmgr image upload nrf51dk disconnects with reason=8

> I believe the setting to tweak is the slave latency, and have some > >>> empirical evidence to back that up. Increasing supervision timeout > doesn't > >>> help if the timeout is at the link manager level (because of a blocking > >>> call, say), while increasin

Re: Console improvements - newtmgr and OIC over shell

I for one am really looking forward to rtt as I dont have serial on several off the shelf devices Im working with. On Wed, Apr 19, 2017 at 1:16 AM, Łukasz Rymanowski < lukasz.rymanow...@codecoup.pl> wrote: > I suggest to create feature branch for that work in this case. I believe > Michal will

Re: Sim Sensor Update

So what are you using simaccel0 for? On Thu, Apr 13, 2017 at 11:58 PM, Vipul Rahane wrote: > d return dummy data which won’t really let you experiment everything but > at the same time let you develop an app which returns some dummy data.

Re: newtmgr image upload nrf51dk disconnects with reason=8

Anyone have thoughts on debugging the scheduler crash? That point gets hit constantly, so breaking there is tough, break commands and logging also appears to mess with bluetooth timing as I cant get a connect when I do that. On Mon, Apr 17, 2017 at 10:49 AM, Jacob Rosenthal <jakeros

Re: newtmgr image upload nrf51dk disconnects with reason=8

On Wed, Apr 19, 2017 at 11:19 AM, marko kiiskila wrote: > Just general comments, I hope I’m not saying things which are > too obvious. > More specific would be even better :) I dont think my gdb is up to par Either g_os_run_list or one of the task structures is getting

Re: newtmgr image upload nrf51dk disconnects with reason=8

OK. thanks, I understand that much better. I totally forgot about increasing the stack size.. Separately I figured out by commenting things out that cbor_encode_text_stringz is what was crashing it, and increased the main stack size. Which makes sense. Now Im back to what started this, with err 8.

newtmgr macos issues: newtmgr Killed: 9 and cgo argument has Go pointer to Go pointer

Looks like xcode 8.3.x breaks newtmgr with "newtmgr Killed: 9" Confirmed fix seems to be just using -ldflags -s on either go build or go install https://github.com/golang/go/issues/19734 Further when I run I get "cgo argument has Go pointer to Go pointer" Googling seems to indicate maybe it

Re: newtmgr image upload nrf51dk disconnects with reason=8

does this. It is lest > > up to the central to use disable connection parameters if it will be > > performing an image upgrade. It sounds like a useful feature, though. > Maybe > > someone can contribute it :). > > > > Chris > > > > On Friday, April 21

Re: newtmgr in nodejs

://nnewtmgr.surge.sh/ which means you can now upload firmware from browser or android on nrf52 devices. nrf51 devices have issues were working on in another thread On Tue, Apr 4, 2017 at 4:16 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > @Sterling Im experimenting with a streams styl

Re: newtmgr image upload nrf51dk disconnects with reason=8

supervision_timeout; uint8_t role; uint8_t master_clock_accuracy; }; As low as 248, or could just round up to 256 (x100) works here as well. On Fri, Apr 21, 2017 at 8:09 AM, Christopher Collins <ch...@runtime.io> wrote: > On Thu, Apr 20, 2017 at 09:43:12PM -0700, Jacob Rosent

Re: Hackillinois this weekend in Urbana IL

> > > On Mar 2, 2017, at 1:04 AM, Jacob Rosenthal <jakerosent...@gmail.com> > wrote: > > > > Hey all, > > > > As is obvious from lack of commits and prs, I talked up mynewt a bit, but > > it wasnt what I was able to focus my mentees on. Next time! &

Re: newtmgr over serial hanging

/04 14:30:19 [DEBUG] Reading [49 50 48 55 58 73 67 83 82 58 48 120 48 48 52 50 49 48 48 51] from data channel On Sat, Mar 4, 2017 at 2:10 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > I checked out the microbit target in upstream which is probably damn near > identi

Re: newtmgr over serial hanging

, Christopher Collins <ch...@runtime.io> wrote: > On Wed, Feb 22, 2017 at 04:08:00PM -0700, Jacob Rosenthal wrote: > > I can shell to both boards and send and receive characters, so I know > uart > > is ok. > [...] > > Hmm... I don't see any problems with your config.

Re: Newtmgr over BLE

Whats the internal thinking on this? Is it being discussed elsewhere? Is the aforementioned rewrite going on, or delayed so it make sense for me to try to get work on the xpc calls? On Wed, Jan 25, 2017 at 1:07 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > The gatt dependency

newtmgr in nodejs

I started porting newtmgr to node. Ive got Current transports include serial and ble. Current commands include list, test, confirm, reset. https://www.npmjs.com/package/newtmgr Next up, more commands, and some testing webpacking it so I can utilize it front end javascript with webble -- and

Re: iOS newtmgr app evaluation

Id love to take a look as Im some ways away from packaging my javascript through to reactnative or phonegap. Same email. On Tue, Apr 25, 2017 at 11:25 AM, Kevin Townsend wrote: > > If you have the time and interest in evaluating this, and some Swift > experience would be

Re: newtmgr macos issues: newtmgr Killed: 9 and cgo argument has Go pointer to Go pointer

hich might also be what fixed > the issue for me... > > On Tue, Apr 25, 2017, at 03:28 PM, marko kiiskila wrote: > > This happens on my setup as well. > > And passing "-ldflags -s” at go build fixes it. > > > > My golang version is: > > go version go1.

Re: newtmgr macos issues: newtmgr Killed: 9 and cgo argument has Go pointer to Go pointer

Go 1.8.1 was available in homebrew and did indeed fix the "Killed: 9" issue I still have the "cgo argument has Go pointer to Go pointer" On Tue, Apr 25, 2017 at 1:34 PM, Fabio Utzig <ut...@utzig.org> wrote: > I have 8.3.2 too. > > On Tue, Apr 25, 2017,

Re: newtmgr image upload nrf51dk disconnects with reason=8

It seems like the best/quickest solution is to not erase the empty area. That way we dont have to figure out how and when to renegotiate the connection and we also get an erase command for 'free' as the first upload will fail but fail having successfully erased the sector. We need to do several

Re: Writing PWM api, and nrf51 implementation

ead. I am not the best newt tool > person. I can try to take a look at it later today if you cant figure it > out before then. > > > > On May 14, 2017, at 10:00 AM, Jacob Rosenthal <jakerosent...@gmail.com> > wrote: > > > > Good point. Ive obviously seen pwm implem

Re: Writing PWM api, and nrf51 implementation

ordic/hw/drivers/lf_pwm/src/lf_pwm.c:182: undefined reference to `app_timer_init' collect2: error: ld returned 1 exit status On Sun, May 14, 2017 at 9:00 AM, will sanfilippo <wi...@runtime.io> wrote: > Jacob: > > Does the nrf51 have a PWM peripheral? I do not think it does. I looke

Writing PWM api, and nrf51 implementation

Im attempting to write a pwm api and nrf51 driver. Im mostly just stubbing right now based on the adc driver, and have mynewt pwm driver stubbed, and am now stubbing mynewt_nordic/hw/drivers/pwm_nrf51 which includes nrf_drv_pwm.h and nrf_pwm.h from the sdk but thats giving tons of errors. Maybe

Re: newtmgr image upload nrf51dk disconnects with reason=8

This was resolved with https://github.com/apache/incubator-mynewt-core/pull/281 https://github.com/apache/incubator-mynewt-newt/pull/60 On Mon, Apr 24, 2017 at 11:00 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote: > It seems like the best/quickest solution is to not erase the e

Re: bleprph with newmgr over ble - disable uart

If you look at bleprph's pkg.yml by default it already has newtmgr with a ble transport, and no uart/shell transport - "@apache-mynewt-core/mgmt/newtmgr" - "@apache-mynewt-core/mgmt/newtmgr/transport/ble" Now uart isnt disabled though, you edit or in your bsp for a syscfg.yml flag to

Re: Problems with erasing flash on nordic devices

a glance, you are confusing bytes with ints (data is declared as > unsigned int), so for the most part you are comparing uninitialised stack > memory. > > Hth, > > simon > > On Thu, May 25, 2017 at 11:04 PM, Jacob Rosenthal <jakerosent...@gmail.com > > > wrote: &

Re: Problems with erasing flash on nordic devices

On Tue, May 16, 2017 at 5:26 PM, Christopher Collins <ch...@runtime.io> wrote: > On Tue, May 16, 2017 at 05:11:36PM -0700, Jacob Rosenthal wrote: > > Seems like it could go in flash_map? > > > > Its also been requested to also have a function that detects if an area

Re: Writing PWM api, and nrf51 implementation

I know we're chummy with zephyr team. Whats the license issues with bringing something very close to their implementation over? On Mon, May 15, 2017 at 6:23 AM, Cufi, Carles wrote: > Hi Wayne, > > > -Original Message- > > From: Wayne Keenan

Re: Problems with erasing flash on nordic devices

Any thoughts on this? Also, Theres a simple solution while a more complex one is discussed. The current code erases every time no matter what, theres even a code comment there about it.

Re: Problems with erasing flash on nordic devices

Im not erasing. It is auto erasing on upload. So I cant upload. On Fri, May 5, 2017 at 5:32 PM, will sanfilippo wrote: > BTW: there is an image list command that will tell you if there is an > image that you need to erase. >

Re: Problems with erasing flash on nordic devices

Thats basically what Im saying. Though if you just do #2 I wont need a separate erase command. It'll erase and disconnect the first time, but not the second time. Ill get an erase command for free. On Fri, May 5, 2017 at 5:41 PM, will sanfilippo wrote: > 1) Add a command to

Re: iOS newtmgr app evaluation

Wow. What an Amazing dashboard view. I didnt even know all these stats were in there. Thanks! On Wed, Apr 26, 2017 at 11:15 AM, aditi hilbert wrote: > Hi Kevin, > > I am very interested in evaluating this. I do not have any Swift > experience but I am always working on

Re: [SensorAPI] Few Questions wrt Sensors

Im developing some (mostly accelerometer) sensors right now. Power modes were brought up here, and Id love to see more talk about that, and in specific sensor initial config state. It looks like the LSM driver doesnt init the cfg struct in _init, so its presumably the 0 enum values of

Re: nrf52dk hal_bsp_init() and sensor device creation

On Thu, May 4, 2017 at 3:39 PM, Vipul Rahane wrote: > I have been thinking about calling the driver initialization function > directly from the bsp Can you comment on why you're not yet init in the BSP? Im thinking power issues, which is another conversation I started in

Re: nrf52dk hal_bsp_init() and sensor device creation

Hey Vipul et al, Ive been plugging away at a few sensors (bma250, lis2dh) and so taking a much closer look at this now. It seems odd to me that sensors are getting pushed all way down to the BSP, only to be created, but not inited. Also why dont BSP then pickup a dependency on all those

Re: [SensorAPI] Few Questions wrt Sensors

, May 4, 2017 at 3:16 PM, Dave Baker <d...@etacompute.com> wrote: > Don't turn on the gyro unless you really really need it. It's a pig! > Default to accel only is good. > > On May 4, 2017 5:13 PM, "Jacob Rosenthal" <jakerosent...@gmail.com> wrote: > > &g