Ive also got a DIS thats a good candidate and a very simple polled button.
https://github.com/jacobrosenthal/mynewt-nimble-services/tree/master/services
On Wed, Mar 1, 2017 at 9:53 AM, Sterling Hughes <
sterling.hughes.pub...@gmail.com> wrote:
> :-)
>
> Definitely the battery service.
:-)
Definitely the battery service. Unfortunately we can’t accept the
nrf51-adc-driver, yet. The Nordic SDK drivers it relies on are not
(yet) BSD licensed. I believe that Nordic was looking into this.
We’d be happy to merge it into the runtime repository where we’re
keeping the non-BSD
This arrived today with b3be6f034169efaa53511b9da0905c4bba014608
and I updated both my nrf51 version of davids adc driver and my battery
service. I think its pretty clean and 'newty' Again, any code review
welcome, and if you think any of it fits in core I can PR
Hi Jacob,
This is awesome.
On 20 Feb 2017, at 14:35, Jacob Rosenthal wrote:
Thanks again David for your example. Ive taken liberally from there
and put
together what seems like a working nrf51 driver. Any input accepted.
https://github.com/jacobrosenthal/mynewt-nrf51-adc-driver
and used it
Thanks again David for your example. Ive taken liberally from there and put
together what seems like a working nrf51 driver. Any input accepted.
https://github.com/jacobrosenthal/mynewt-nrf51-adc-driver
and used it in a ble battery service, again any input happily accepted.
Sent from my iPad
> On Feb 17, 2017, at 6:15 PM, Jacob Rosenthal wrote:
>
> OK no wait I think Im understanding.. It IS using the nrf52 driver and not
> duplicating..
That's correct.
>
> Because of the driver style abstraction my_adc is an 'nrf52 water level
>
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 from having to
generate those files? Then you're just editing the main.c of bleprph for
the task.
I do think a name change to nrf52_water or something
OK no wait I think Im understanding.. It IS using the nrf52 driver and not
duplicating..
Because of the driver style abstraction my_adc is an 'nrf52 water level
driver(sensor?)' (maybe a name change?)
I guess I have issue with exposing a bunch of board specific stuff into to
the main.c. Though
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
To answer my own question, yes, I am correct in assuming that! I just had to
keep moving the wire from pin to pin until I found the one that ADC0
referenced, but the same driver for the ADC that worked on the NRF52DK board
works just fine on the Arduino Primo. I'll be writing up a blog post
10 matches
Mail list logo