Re: OS event queue changes

Really like this change Chris. I think its going to make it way easier to create task-less portable modules. On 11/8/16, 5:36 PM, "Christopher Collins" wrote: >Hello all, > >Recently a pretty big change was made to Mynewt's event queue model. >The Mynewt documentation

newtmgr changes

Folks, As part of our teamwork up to the 1.0 release, we are refactoring newtmgr. One of the pieces of this work was to get newtmgr to use cbor instead of json for encoding. This allows several things 1. more efficient encoding of hash values. Previoulsly these were base-64 encoded.

Re: Removing os_error_t

+1 for this idea. I like the idea of a package that holds error codes. Regarding error codes type, I don¹t have a strong opinion. My preference would be enums because my IDE can help me and the compiler can help a bit. Paul On 9/11/16, 10:44 AM, "Sterling Hughes" wrote:

Re: Mynewt system initialization

Thanks Chris, I think this is a great step in the right direction. I¹m looking forward to seeing it. Just a few quick questions/comments about sysinit. Would you expect that everyone that writes a new core package, would add their init code to sys/sysinit package and include their package in

blenano

All, I have been adding split image to ble-nano. What I found what that there is something happening with MK20 USB daughter board. When I have the BLE module plugged into the daughter module, I am not able to use newtmgr commands with slinky. However, when I unplug the module and wire

split image checkin on develop

I just checked in the split image code on develop. This involves changes to apache-mynewt-core as well as a newt and newtmgr. Generally, the should not affect any functionality or configuration of single image builds. However, a few imgmgr and bootutil APIs have changed in non-backward

Re: split image design

in >libraries where we create tasks, I assume we take a pointer to the >stacks by default, and we don’t place them in .bss ourselves? > >Sterling > >On 20 Jul 2016, at 14:27, p...@wrada.com wrote: > >> Update. >> >> This effort is ongoing on a private bra

split image configuration comments please.

I've tested a simple split image build with newt and I can load both images and have the bootloader boot the loader and then the loader boot and verify the split image. The loader application has a special call to loader_go that checks to see if its meant to run a split app or not. The main

Split Image Build Dependencies Design

Just a note to the list to get feedback on the split image and build dependencies. Feedback would be great, but I also just want to get this out there for understanding (myself mostly as its hurting my head). All if this stuff is buried in newt, so the user won't have to understand much of

Re: split image design

to get newt put back together, sort out how to debug this kind of thing, and most importantly, write an real “loader app” that can download split images via bluetooth and net_mgr. Paul On 6/27/16, 2:37 PM, "p...@wrada.com" <p...@wrada.com> wrote: >Im on to how to implement

Re: debugging with Go using gdb

Sorry Šone correction. When you launch GDB from your mynewt project folder, you have to give it the full path to newt $gdb $GOPATH/bin/newt On 7/1/16, 4:37 PM, "p...@wrada.com" <p...@wrada.com> wrote: > >Just thought I'd share my debug experience with the newt to

debugging with Go using gdb

Just thought I'd share my debug experience with the newt tool using gdb. First, if you are a OS developer, you are probably not messing with newt so there isn't much use for this tutorial; you may want to ignore this. But if you are changing the newt or newtmgr code, this may be helpful. You

Re: Using the ADC on nrf52dk

I just pulled from develop and my version does not have hal_adc support for the nrf52. I looked in the following place and didn’t see a hal_adc.c file. $ ls repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/ hal_cputime.c hal_gpio.c hal_system.c hal_uart.c hal_flash.c hal_os_tick.c

Re: Arduino Zero/M0 Pro default serial connection changed

The Edbg serial port build into the arduino zero debug is a cdc serial port (not FTDI). Linux and Mac should have support but Windows requires some additional drivers > On Jun 30, 2016, at 10:20 AM, marko kiiskila wrote: > > Hi Todd, > > my MAC is using USB CDC driver for

Re: split image design

iti >> On Jun 24, 2016, at 3:18 PM, will sanfilippo <wi...@runtime.io> wrote: >> >> My expectation would be that the bootloaders would be locked down and >>thus not upgradeable in the field… >> >> Will >>> On Jun 24, 2016, at 2:04 PM, p...@wrad

Re: split image design

;Comments/questions in-line. > >> On Jun 22, 2016, at 7:58 PM, p...@wrada.com wrote: >> >> Here is a high level functional spec for the split image feature. It >>include a motivation, overview of design decisions, and a set of >>functional changes that need to happ

Re: split image to increase application storage space.

upgrade the upgrade code >independently? Sorry if this is obvious and I am not quite getting it :-) > >> On Jun 21, 2016, at 12:31 PM, p...@wrada.com wrote: >> >> I¹m working on split image feature and I think I just have one more >>major design issue to consider,

Re: Board Support Tutorial

This is what I know about http://mynewt.apache.org/os/core_os/porting/port_bsp/ From: "David G. Simmons" > Reply-To: > Date: Friday, June 3, 2016 at 10:07 AM To:

Re: [DISCUSS] A users@ mailing list for Apache Mynewt

I¹d prefer to keep them together for now. As this is new, I think that developers are going to learn a lot from the users issues or questions, and vice versa. I agree that this will get too much at some point, but I¹m really getting a lot from seeing the user and developer issues together. On

Re: my newt on STM32091c-eval board

David, I did the BSP for the atmel SAMD21 for arduino_zero (also a cortex M0 SoC). I utilized the driver code from atmel for the hal. Its available in a separate repository ( to preserve the license from Atmel) when you are ready. This tutorial shows you how to get it up and running.

Re: common BSP API,

Fantastic. The more consistent this is the better. On 5/17/16, 6:29 PM, "marko kiiskila" wrote: >Hi, > >I was chatting with Will about this offline; there¹s no header file >describing API exported by BSPs. > >This includes function prototypes like os_bsp_init() (currently

Re: privacy modes for LE

On 5/13/16, 2:43 PM, "will sanfilippo" <wi...@runtime.io> wrote: >Why exactly do you want to store the random, static address? My >understanding is that this is expected to change with rebootsŠ > >> On May 13, 2016, at 1:59 PM, p...@wrada.com wrote: >> &

privacy modes for LE

I'm working on LE privacy modes. I reviewed The soft device from nordic and also zephyr and have the following proposal Privacy API proposal 1. a config for address mode * Identity. * NRPA * RPA 2. A address timeout to rotate NRPA/RPA Initialization - The default

Re: newtmgr protocol, no sequence number

I concur that keeping an 8-byte header is desirable. If we will have only a very few message outstanding why not use 4 bits for the nh_seq. Although I feel 8-bits is probably enough message IDs for a given group (these are small devices after all) It would seem that we should save bits if they

1.0 HAL draft

I'm starting a doc on 1. HAL draft for all of us to contribute to. Right now its a google doc, but it would be better to put someplace that our dev team can all edit. Is there a better place on apache to host this. For now, I post so anyone can comment. My goal is not to discourage or

Re: i2c HAL API

is misfired, you typically cannot issue a start condition, so the read/writes fail. I only tested this condition when there are no suitable pull-ups on the bus. On 4/19/16, 12:13 PM, "marko kiiskila" <ma...@runtime.io> wrote: >Hi Paul, > >> On Apr 19, 2016, at 11

i2c HAL API

All, Please take a look at the i2c HAL api in https://github.com/apache/incubator-mynewt-core/pull/44 I chose a simple blocking API for now to get some I2C functionality fast. Its mostly just read/write, with a few other functions. 1. probe - I found that immediately after writing this

Re: Mynewt for arduino_101 board

I concur with what Chris is saying. This is how we do it for arduino, but its not ideal in my opinion. It worked OK for arduino zero versus Zero Pro, but for your case we are talking about two very different products (arduino and NRF eval board). I wish I had a good answer. One possibility is

hal spi

All, I submitted a pull request for a basic SPI API.I chose the simplest API I could in order to get functionality to build upon with the thinking that we can add APIs in the future without breaking compatibility. Comments are greatly appreciated.

Re: Problem Loading arduino_boot

Nges, The good news is that this shows that you are connecting to the board and issuing commands to the target. The bad news is that the command Œat91samd boot loader 0` is not working on your openocd version. We are using 0.9.0. If you are using 0.8.0, Please upgrade to 0.9.0 and try again.

Re: choosing between FCB and NFFS

I prefer to keep the boot loaders as simple as possible. Unless there is good justification, I think we should move all the boot loaders to the simplest (and smallest) implementation for flash storage that we can and NOT give a choice. As an alternate if we want to keep the functionality is to

Re: Rename newtmgr protocol

I like the idea of having different names. I think nmp is fine for the protocol. On 4/6/16, 7:24 PM, "Christopher Collins" wrote: >Hello all, > >There are two things called "newtmgr": > >1. A simple command-response protocol used for interfacing with mynewt > devices

Re: hal_gpio_toggle() should return changed pin state

Sound good to me > On Apr 6, 2016, at 3:10 PM, will sanfilippo wrote: > > Seems fine to me. > > >> On Apr 6, 2016, at 1:45 PM, Vipul Rahane wrote: >> >> Hello, >> >> Current definition: void hal_gpio_toggle() doesn’t return anything. >> Proposed

Re: PWM API

or duty cycle dynamically in the API but to both. #1. Paul On 3/31/16, 2:33 PM, "will sanfilippo" <wi...@runtime.io> wrote: >Comments… > >> On Mar 31, 2016, at 1:59 AM, Greg Stein <gst...@gmail.com> wrote: >> >> On Mar 30, 2016 11:48 PM, "p...@wrad

include files with the same name

Hi all, Just something I noticed here that I'll pass on to the group. Mynewt has special directory structure to avoid name conflicts with header files. For example, Hal/hal_adc.h And Mcu/hal_adc.h won't conflict because the user has to include the directory name in the path. #include

Re: more ADC hal discussion

Thanks for the reviews. 1) regarding names. I can shorten. I really like having the units in the names, but can shorted to hal_adc_refmv(); hal_adc_bits(); As far as convert. To convert from adc output to molts requires the resolution and the reference voltage. I agree though that This

hal_adc API rev 2

Here iare two hal_adc APIs and underlying implementations to compare. https://github.com/apache/incubator-mynewt-core/pull/23 https://github.com/apache/incubator-mynewt-core/pull/21 Pull21 - this uses a sysid in the hal Api and depends on a the BSP to translate (at runtime) to a driver

Re: pull request for ADC and PWM APIs

;I understand). > >I do wish that some of the API were a bit more abbreviated but that is >only because i dont like typing :-) > >And btw, I am interested in hearing the answer to marko¹s questionŠ > >Will > >> On Mar 23, 2016, at 4:03 PM, marko kiiskila <ma...@runtime.io> wrote

Re: pull request for ADC and PWM APIs

PM, "marko kiiskila" <ma...@runtime.io> wrote: >Good stuff. > >> On Mar 22, 2016, at 5:21 PM, p...@wrada.com wrote: >> >> All, >> >> I'm having so much fun with my newt. Please comment and help me improve >>this work. >> &g

Re: Refactoring of Newt Git Repo

Good. Are there no newty dependencies between them? > On Mar 23, 2016, at 2:19 PM, Sterling Hughes wrote: > > Hi, > > I'm thinking we need to do a little refactoring of the newt git repo. > > Specifically: > > - We should get rid of newtmgr from the newt git repo, it

pull request for ADC and PWM APIs

All, I'm having so much fun with my newt. Please comment and help me improve this work. I've submitted two HAL API pull requests. They are to add new HAL_xxx.h files for two new sets of core functionality: ADC and PWM. When designing these hal_xxx.h interfaces, I considered the APIs from

Re: documentation for code

+1 Great idea. On 3/5/16, 11:46 AM, "Aditi" wrote: > > >On Mar 5, 2016, at 11:10 AM, Sterling Hughes >> We have a regression test framework. Perhaps we can make samples in >>the documentation into regression tests, and mark them with a tag (e.g.

Re: documentation for code

he.org> wrote: > >On 3/4/16 4:42 PM, p...@wrada.com wrote: >> >> I was writing some documentation today for the hal Apis and had a >>feeling that we are making work for ourselves. >> >> Documentation of the interface is important, but I wish we could have

documentation for code

I was writing some documentation today for the hal Apis and had a feeling that we are making work for ourselves. Documentation of the interface is important, but I wish we could have some way to get that from the actual header files. The amount of copying from code to documentation led me

hal organization and multiple smaller packages

Just wanted to pass on some thoughts I had today about the hal ... I was thinking about how much is in a hal, how it will grow over time and how to tell "how complete" a given hal is. And more importantly how to provide simple stuff that does basic HW (like polling GPIO) while allowing

Re: ASF JIRA account

Justin, Can you add me to the list of jira users. I am paufdietrich0 From: aditi hilbert <ad...@runtime.io<mailto:ad...@runtime.io>> Date: Friday, February 5, 2016 at 5:18 PM To: Paul Dietrich <p...@wrada.com<mailto:p...@wrada.com>> Subject: ASF JIRA account Hi Pa

Re: OS time tick initialization

mply pass the priority in the API. Or just >have the BSP program the interrupt priority to 1 less than the lowest >priority. We could also return the interrupt vector used by the BSP to >the OS and have the OS set the priority. > > >> On Feb 3, 2016, at 10:28 AM, p...@wrada.com wrote:

egg file cflags

I was just working on importing an existing code tree into my HW directory for arduino zero. Rather than re-arrange the files, I wanted to pass include directives to the compiler for specific directories. But the only option is relative paths to the compiled file. That cause includes like

Re: OS time tick initialization

Tick for MCU’s which support it; otherwise the bsp >will use a different HAL timer (provided by the MCU). > >Sound good? > >Will > > > >> On Feb 2, 2016, at 2:43 PM, p...@wrada.com wrote: >> >> I¹ll throw in my support as well. >> >>

Re: OS time tick initialization

I¹ll throw in my support as well. Certainly on some processors different timers have different current draw and require different sleep states. For wearables, this is super critical for battery life. I expect that folks will want to use alternate timers for the system tick to maximize battery

Re: OS time tick initialization

One more quick note. I think that there are probably a number of things in the MCU that are good defaults for most folks, but we may want to allow override in the BSP. I wish I had a good list, but I don’t :(. On 2/2/16, 2:43 PM, "p...@wrada.com" <p...@wrada.com> wrote: &