Re: FCC Pre-scan

Hi Jitesh, On 9 Jun 2017, at 7:27, Jitesh Shah wrote: > Great! > So then ble_ll_reset() followed by ble_phy_disable() should take care of > most cases, right? > > As far as giving back control to the nimBLE stack is concerned - that > probably won't be necessary. FCC is a pretty controlled

Re: segger jlink

faster to communicate and has a better flow then a mailing list thats why i asked in the first place pierre On 30 May 2017, at 21:19, Sterling Hughes <sterling.hughes.pub...@gmail.com> wrote: Hi Jacob, I agree. Some of the Mynewt core devs have an IRC culture, but most use less open

Re: segger jlink

Hi Jacob, I agree. Some of the Mynewt core devs have an IRC culture, but most use less open, more ..friendly.. communications tools like Slack. I’m looking up to see if there is a Slack->IRC gateway, which might make it easier. Alternatively, what do folks think of just pointing people to

Re: [VOTE] Graduation of podling Apache Mynewt to Top Level Project

the Apache Mynewt Project: *Justin Mclean” <jmcl...@apache.org> *P. Taylor Goetz” <ptgo...@apache.org>, *Greg Stein <gst...@apache.org>, *Jim Jagielski <j...@apache.org>, *Sterling Hughes <sterl...@apache.org>, *Marko Kiiskila <ma...@apache.org>, *will sanfilippo <w

Re: Question about MyNewt FCC Certification

Hi Lm, At runtime we can offer commercial help with certification for Apache Mynewt - don't hesitate to reach out if you'd like some help! Generally what I'd say is that it's up to you to decide whether or not you've made significant enough changes to the software on the device such that it

Re: DC/DC regulator enable for nrf52. Where should it go?

> NOTE: I will comment on this in the hal_system_init() function, but this > function will be called by both the bootloader and the app. If there is a > case where doing something twice is undesirable that will have to be dealt > with by anyone adding code to hal_system_init(). > >

Re: Use of os_error_t and OS_OK

I don’t think we ever came to agreement, and things are a bit of a mishmash. Ben brings up a good point. Mynewt wide, in my view: * os_error is a relic, and sys/defs codes should be used. * All functions should return “int” and not “os_error_t” or a specific error type. * 0 and -1 are

Re: mynewt, build on ubuntu

I believe just making this -1 should also fix the problem for now (and we should update the code.). But I’ll let Chris chime in. I’d change it to -1 for now. Best, Sterling On 8 Apr 2017, at 12:58, Sterling Hughes wrote: We just noticed this the other day, we have not tested on a 32-bit

Re: mynewt, build on ubuntu

We just noticed this the other day, we have not tested on a 32-bit ubuntu vm, just the 64-bit vms, as all our stuff is 64-bit here. It’s a bug. Can you try building newt with a 64-bit GOARCH? I think it’s GOARCH=amd64. If you use a 64-bit ubuntu vm, that should work too. sterling On 8

Re: DC/DC regulator enable for nrf52. Where should it go?

Hi, Couple of thoughts: - I think this function/syscfg belongs in the MCU definition, as a configuration item that can be controlled by the BSP. - I think it should be called as early as possible, so probably hal_bsp_init(). - It’s a bid odd that hal_bsp_init() is the same for bootloader

Re: [apache/incubator-mynewt-core] PIC32 port (#218)

Hi Julian, On 31 Mar 2017, at 1:54, Julian Ingram wrote: Hi Marko, The Microchip license: /*- * * Copyright (c) 2014, Microchip Technology Inc. and its subsidiaries ("Microchip") * All rights reserved. * This

Re: newt debug .img or elf?

When running on a physical device you need the image version to load, for development we just use 0.0.0 Sterling > On Mar 29, 2017, at 7:45 AM, Kevin Townsend wrote: > > Was the build process recently updated to output .elf instead of .img? > > I'm on 1.0.0 for

Re: Docker latest is still on newt version 1.0.0-b2

There shouldn’t be an incompatible changes between b2 and rc1 — we’re actually looking at updating the newt in docker to b2 right now. The release just passed incubator vote this weekend :) On 20 Mar 2017, at 12:48, Simon Ratner wrote: Hi devs, Just did `docker pull mynewt/newt:latest` and

Re: STM32F3 Discovery blinky tutorial error

Hi Pradeep, On 20 Mar 2017, at 6:07, Fabio Utzig wrote: On Mon, Mar 20, 2017, at 09:09 AM, Pradeep Sanjeewa wrote: Hi Fabio Utzig, I thought MIPS port is already implemented. Imagination Technologies ci40 board is already ported to mynewt which has a MIPS mcu. Isn't it? Correct me if I'm

Re: What is the different between drivers and hal module?

Belongs in drivers IMO. Cool! Having a LCD driver would be awesome, and I’d love to get a GFX library into (or compatible with) Mynewt as well. On 16 Mar 2017, at 6:47, Fabio Utzig wrote: I believe the agreed on convention is that the "hal" directory contains SOC drivers that are available

Re: Newtmgr over BLE

Hi Jacob, Chris has been working on getting the Mynewt stack working in a cross platform way. You can see some of his progress here: * https://github.com/ccollins476ad/incubator-mynewt-core/tree/nativehost/apps/blehostd/src *

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Louie, Excellent! We’d love the port when you’re done. That usually means a crash of some type has occurred? Can you attach a debugger, you should be able to see a stack trace (similarly - if you can get the console attached, it should *fingers-crossed* dump to console.)

Changes to newt - and Fun with Jerryscript

Howdy, I thought I’d play around with getting Jerryscript up and running with Mynewt. Generally, it was a painless endeavor, however, I needed to make a few changes to newt: - If the src/ext directory of a SDK package doesn’t exist, ignore it when recursively processing includes. - When

Re: ADC on Arduino Primo

/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 2017, at 14:35, Jacob Rosenthal wrote: Thanks again David for your example. Ive taken liberally from there and put together what

Re: newt size improvements

We do! Sterling Sent from my iPhone > On Feb 28, 2017, at 12:21 AM, Michał Narajowski > wrote: > > Hi Simon, > > could you give us more info about your setup, so we can reproduce the > problem? I don't think Mynewt supports Windows. > > Michał > >

Re: Having trouble, where to turn?

This was thumb typing: I was going to say "with James pace, happy to help." But Aditi beat me to it: you are in good hands! ;-) Sent from my iPhone > On Feb 24, 2017, at 7:40 PM, Sterling Hughes > <sterling.hughes.pub...@gmail.com> wrote: > > Hi tharon, > &

Re: ADC on Arduino Primo

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

Re: Script for merging PRs to Mynewt

original message to log > 4) Extra error checkings > > https://gist.github.com/utzig/e582bb2d4cc0128bb01ba5f4b7866711 > > On Mon, Feb 20, 2017, at 01:22 PM, Sterling Hughes wrote: >> Hi, >> >> For others who are merging PRs from GH, I wanted to share what I wa

Script for merging PRs to Mynewt

Hi, For others who are merging PRs from GH, I wanted to share what I was doing: #1 - I have setup the following remotes [~/dev/mynewt/core]$ git remote -v github https://github.com/apache/incubator-mynewt-core (fetch) github https://github.com/apache/incubator-mynewt-core (push) origin

Re: [DISCUSS] [VOTE] Release Policy for Apache Mynewt

Hi, 1. We might want to explicitly define the meaning of "releases that are still supported" (mentioned under Release Schedule); for instance, is it only the current major release, or one or two prior releases as well? The section on Backwards Compatibility talks about active and deprecated

serial library and termios

Hey, I’m looking at adding “serial” support to mynewt as a side project. As I would typically see this architected, it would look like: — console | serial | pty — tty — uart Where the tty support is below the console and serial port, and handles things like flow control and terminal ready.

Re: Can't build blinky app on macOS Sierra

Yup, unfortunately nothing for that. Mac makes you code sign gdb when running sim. If you run on physical hardware, you don’t need to codesign the binary. Sterling On 9 Feb 2017, at 20:50, Denis Magda wrote: Hi Marko, cd $GOPATH/src/newt/mynewt.apache.org/newt git checkout

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

+1 from me On 8 Feb 2017, at 13:22, Szymon Janc wrote: Hi Chris, On 8 February 2017 at 19:58, Christopher Collins wrote: On Wed, Feb 08, 2017 at 08:49:26AM -0800, Christopher Collins wrote: I don't have any hardware available at the moment, but I will try running this

Re: [SensorAPI] Few Questions wrt Sensors

Hi Kevin, On 3 Feb 2017, at 23:43, Kevin Townsend wrote: Hi Vipul, On 04/02/17 01:08, Vipul Rahane wrote: Hello All, I will be taking over SensorAPI stuff from Sterling. Kevin: TSL2561 Driver and LSM303 Driver that you have implemented are pretty good and I used both of them. I saw the

Re: [jira] [Created] (MYNEWT-576) Update apps that use newtmgr framework to explicitly set the event queue with mgmt

Reporter: Wanda Chiu >Assignee: Sterling Hughes >Priority: Trivial > Fix For: v1_0_0_rel > > > The tutorial to enable Newt Manager in Any App indicates that the app must > call the mgmt_evq_set to specify the event queue that mgmt

Re: newNewt

Hi Neil, Sounds like a fun project! I’ll let Marko or the Linaro folks chime in on the K64F, however, I wanted to point to the excellent article the code coup guys wrote on running Mynewt with Eclipse: https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse/ Sterling On 25 Jan 2017, at

Re: push more often (was: [01/50] incubator-mynewt-core git commit: ...)

On 23 Jan 2017, at 23:41, Greg Stein wrote: commit 1 of 50 ?? This says to me: push more often. How can the mynewt community review your work, if you never push it? :-) as pointed out, it’s bringing the sensors_branch up to date: Vipul has started working on it, and I brought it up to

Docker container

Hey, I’ve been noticing a bunch of issues cropping up recently with our Docker container, that seem to center around unusable speed of compilation. I’m wondering if there is a way to speed this up? If we can’t speed up docker-container based compilation: I think we need to de-emphasize it,

Re: State of 1.0.0 beta/rc, develop branch

Hi Simon, IMO we’re probably going to roll b2 off develop. There have been a fair number of stability improvements. While its a fairly large scope of change between betas, its probably the right decision. Prior to b2, either this week or next, we should create a 1.0 branch that b2 is

Re: How to change the CPU time frequency of mynewt and nimble stack

Hi Jiacheng, You need to update your newt tool along with the new develop. Best, Sterling On 10 Jan 2017, at 16:46, WangJiacheng wrote: Hi, Will, I need more help, I have an error message when compile the target. I’m currently working on the release branch, so upgrade to dev branch by:

Re: macOS Sierra Support

ord". DSimmons-Pro:apache-mynewt-core dsimmons$ MacOS Sierra v10.12.2 (16C67) dg On Jan 10, 2017, at 12:45 PM, Sterling Hughes <sterl...@apache.org> wrote: Hi, On the latest develop with the latest macOS Sierra and homebrew, If I have a target: targets/slim_slinky app=apps/slin

macOS Sierra Support

Hi, On the latest develop with the latest macOS Sierra and homebrew, If I have a target: targets/slim_slinky app=apps/slinky bsp=hw/bsp/native build_profile=debug (used to be optimized :-) And I try and build: $ newt run slim_slinky Error: In file included from

Re: Compile and build time, any way to speed up?

This is awesome, timing on the new build (after a clean): Target successfully built: targets/nrf52 real0m6.327s user0m26.972s sys 0m9.276s $ newt target show nrf52 targets/nrf52 app=apps/slinky bsp=hw/bsp/nrf52dk build_profile=debug 6 seconds for a full build. Not bad!

Re: Sensor API Helper Functions

Hi Kevin, On 23 Dec 2016, at 15:26, Kevin Townsend wrote: I'm probably getting ahead of myself diving into this before the sensor API is nailed down, but if we wanted to add some generic helper functions that make use of the sensor API, what would be a good location or what to organize them

Re: [SensorAPI] Default Sensor Config

It’s an interesting thought, as you point out there are kinda two things at work here. 1- A driver needs to be “config’ed” by default, and where the driver init is called is not the right place to do that. 2- The driver doesn’t have any user specific data to call, there should be a

Re: newt build error

Hi Alan, The new PDK now works. @wes3 added some commits to support the BSP. Sterling On 23 Dec 2016, at 12:00, Alan Graves wrote: Hi dev, For my environment I'm running Ubuntu 16.x in a VMWare environment under Windows 7. I also have Go 1.6 installed and working. The problem is that I've

Re: Schedule task with strict fixed timing and variable workload

+1 for PWM support, but as a driver, not HAL. https://issues.apache.org/jira/browse/MYNEWT-525 Sterling On 28 Dec 2016, at 10:11, David G. Simmons wrote: +1 on PWM. dg On Dec 26, 2016, at 2:14 PM, will sanfilippo wrote: I think there was some discussion re: HAL PWM but

Re: Schedule task with strict fixed timing and variable workload

+1 - I agree with this thread. https://issues.apache.org/jira/browse/MYNEWT-522 On 26 Dec 2016, at 10:26, Kevin Townsend wrote: Hi Will, Thanks for the feedback. 1) Unless you are the highest priority task, other tasks can run which could cause delays, and thus you are not waking up at the

Re: newt build error

Hi Alan, What go version are you using? Also, what branch is the mynewt source that you’re trying to compile? For me: $ pwd /Users/sterling/dev/go/src/mynewt.apache.org/newt/newt $ git status On branch develop $ go version go version go1.7.4 darwin/amd64 $ We’ve dropped support in mynewt

Re: how to use include path in myNewt

Hi Then, It may be useful to look at how we bundle chip vendor SDKs when looking at incorporating this project. If there are an additional set of options that would help make this easy to work with newt, don’t hesitate to suggest them. We want to make this easy. Here is a pkg.yml file

Re: WIP: sensor API

/sensor/src/sensor_shell.c#L38 I got into "Segmentation Fault" when running it with simulation (native pc). On 13/12/2016 12:51, Sterling Hughes wrote: Hi, I’ve added initial support for a sensors API to mynewt in a branch off develop called “sensors_branch.” You can find a full

WIP: sensor API

Hi, I’ve added initial support for a sensors API to mynewt in a branch off develop called “sensors_branch.” You can find a full diff here, or pull the source code directly: https://github.com/apache/incubator-mynewt-core/compare/develop...sensors_branch I’ll caveat that this API needs

Re: System init and OS eventq ensure

Hi, On Dec 11, 2016, at 10:55 AM, Christopher Collins wrote: On Sun, Dec 11, 2016 at 10:11:44AM -0800, will sanfilippo wrote: Personally, I keep wanting to try and have the OS start up right away. I wonder if this could solve the problem that Sterling raised (no

yield() and os_eventq_run()

Hi, As a part of developing the sensor interface, I want to register a “listener” on the event queue: listener.sl_sensor_type = type; listener.sl_func = sensor_shell_read_listener; listener.sl_arg = rc = sensor_register_listener(sensor, ); if (rc != 0) { goto

Re: System init and OS eventq ensure

packages handle this is they enqueue the startup event > when their event queue is assigned. This happens automatically when you > call os_eventq_designate(); the last parameter is the event to enqueue > immediately. > > Chris > >> On Sat, Dec 10, 2016 at 11:30:27AM -0800, Sterling Hughes wr

GDB + SIM broken with macOS sierra

I’m wondering if anyone else has seen this / worked around it? I can run SIM directly from command line, or under LLDB, but GBD seems to be broken? Sterling

Re: Subscription Request and Question.

+1 I think even a PSK example would be helpful. On the NRF52, I think it would be practical to run DTLS over the transport, even if a bit heavyweight. It would be great to have an example of that. Speaking of this, I was wondering if folks had experience with embedded TLS libraries.

Re: Subscription Request and Question.

On 3 Dec 2016, at 6:38, Kevin Townsend wrote: On 03/12/16 11:54, Tim Hutt wrote: Android and iOS don't allow you to specify the keys used by BLE's native encryption, but there is nothing stopping you using BLE as an insecure transport and implementing your own encryption on top of it (well

Re: HEX DEBUG output in newtmgr

captured here: https://issues.apache.org/jira/browse/MYNEWT-497 i don’t see a reason to print both hex and decimal, although if someone cares, retaining it as an option seems fine. i agree that default should be hex. On 30 Nov 2016, at 8:52, Kevin Townsend wrote: Hi Christopher, The

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

+1 binding On 30 Nov 2016, at 5:39, David G. Simmons wrote: +1 On Nov 29, 2016, at 9:30 PM, Christopher Collins wrote: [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't object [ ] -1 Do not release this package because... -- David G.

Re: Initial FAT support

I agree — the license seems perfectly acceptable for ASF releases, but it is non-standard. It’s like somebody modified a BSD license to be a MIT license. +/*/ +/ FatFs - Generic FAT file system module R0.12b

Re: Sensor Drivers and File Location

/drivers/sensors/ contain individual sensor drivers organized by manufacturer, that create their own device APIs, but also can register with the sensor API in hw/sensors. Sterling On 10 Nov 2016, at 15:42, Sterling Hughes wrote: Hi Kevin, I have some thoughts, but I’m not sure they all directly

Re: Sensor Drivers and File Location

Hi Kevin, I have some thoughts, but I’m not sure they all directly address your concerns :-) More details on directory re-org and drivers below, but I wanted to mention upfront: I really think its worth thinking through the sensor api you mention in your PS, and then doing the directory org

Re: [incubator-mynewt-blinky] Git Push Summary

Is the idea to merge these from develop or master? I think we should probably merge develop->master now, prior to branching anything. We should only be branching releases off of master (which I’m assuming is the intention.) Sterling On 10 Nov 2016, at 3:36, ccoll...@apache.org wrote:

Re: Angled-brackets vs. quotes in #include directives

Hi, On 7 Nov 2016, at 19:04, Christopher Collins wrote: On Mon, Nov 07, 2016 at 09:45:48AM -0800, marko kiiskila wrote: On Nov 7, 2016, at 8:43 AM, Christopher Collins wrote: Is there a particular reason that you would prefer this? By my reading of the standard, using

Re: newt and newtmgr versions

Hi Kevin, On 7 Nov 2016, at 9:02, Kevin Townsend wrote: I'm just migrating over to develop for mynewt-core and the newt tools repos, and noticed the following after updating the command line tools from develop: - 'newt version' -> returns 0.9.0 in develop, this should probably be 0.10.0 to

Re: Angled-brackets vs. quotes in #include directives

On 4 Nov 2016, at 16:34, Christopher Collins wrote: > Hello all, > > We've been a bit inconsistent with our use of angled-brackets vs. quotes > in #include directives. There is a simple rule for this one: use > quotes for user headers; angled-brackets for headers supplied by the >

Re: [DISCUSS] Proposed changes to mynewt website

Got it - about the tech docs release. How about the website changes? I was proposing we merge that into master for beta. +1 from me, they look great. Sterling

Re: [DISCUSS] Proposed changes to mynewt website

Hi Aditi, On 4 Nov 2016, at 12:50, aditi hilbert wrote: Hi all, Documentation update is going to be a big part of the Apache Mynewt 1.0 release since it is featuring several additions and enhancements. I would like to propose some changes to the landing page and additional links on the

Bundling Atmel support

Hi, I’ve noticed on our site we refer to the Arduino Zero, Zero Pro and M0 Pro as supported platforms, when in fact: Mynewt does not support these platforms out of the box — you need to get support for them from Runtime externally: https://github.com/runtimeinc/mynewt_arduino_zero We’re,

Re: C++ support added to newt

In the case of compiling with newlib, _exit was not being resolved from libc_stubs.c in the BSP. I believe this has to do with link stage, and adding -specs=nosys.specs does the right thing: but I have not tested this. In general, we should probably look to trim down libc_stubs.c. With

C++ support added to newt

Hi, I’ve added C++ support to Newt in the “develop” branch. In order to use C++ with newt, the compiler definition files have a new entry which is: compiler.path.cpp: arm-none-eabi-g++ -x c++ And newt will search every package for files that end with *.cpp, *.cxx, and *.cc. I decided not

Re: i2c hal API issues and possible modifications

I also think the calls to read() and write() should be modified to take a flag, which tells whether or not to generate a STOP. Linux’s I2C APIs take a linked list of commands to pass to the device that encompass an I2C “transaction.” The last element of that generates the STOP. This seems

Re: SystemView with Mynewt

I’ve added a tracking ticket for this to Mynewt Jira (https://issues.apache.org/jira/browse/MYNEWT-430). I think it would be great. Sterling On 6 Oct 2016, at 9:02, Kevin Townsend wrote: Has anyone tried to get Segger's SystemView working with Mynewt? https://www.segger.com/systemview.html

Re: Initial impressions.

PS: https://issues.apache.org/jira/browse/MYNEWT-424 On 6 Oct 2016, at 13:33, Sterling Hughes wrote: Glen thanks for the feedback, much appreciated! I think MCU specific macros make sense to me. Personally, I’m OK going to a schematic and looking up physical pin->port pin mapp

Re: Initial impressions.

Glen thanks for the feedback, much appreciated! I think MCU specific macros make sense to me. Personally, I’m OK going to a schematic and looking up physical pin->port pin mapping, depending on silk screen, but the fact that the arduino zero BSP starts from 32 for PORTB pins, and you can

Re: Improve Unit Tests and Test Suite Output

Hi, I don’t think we planned on providing a mock’ing framework in V1 of Mynewt. The approach to mocking has been to implement the lower layers on sim, and then special case things where it only makes sense for a particular regression or unit test. While you won’t get the control you have

Re: Directory re-org in develop

All the best Wayne On 29 September 2016 at 16:50, Sterling Hughes <sterl...@apache.org> wrote: Hey, On 29 Sep 2016, at 7:42, James Pace wrote: imgmgr, and newtmgr could be broken into a TLD mgmt/ directory. They could also be put into “sys.” Other suggestions? +1 for /mgm

Version on statistics structures

As I’m going through the statistics module and documenting it, one thing that occurs to me is for the case where STATS_NAME_ENABLE = 0, and statistic names are omitted, we should create the statistic name -> number mapping, in the target’s directory, in a machine parseable format (i.e. JSON.)

Re: MIPS port (WIP)

Julian, Awesome!! It would be great to get this into 1.0-beta1 (thinking code complete in 2 weeks) if at all possible. Also, if you’re taking further requests, I’d love to see a PIC32 running Mynewt as well. :-) Sterling On 4 Oct 2016, at 8:00, Julian Ingram wrote: Hello all, I have

Directory re-org in develop

Howdy, So the directory re-org is now committed in develop: it’s a fairly large, BC breaking set of changes. Please review the new structure, and use this opportunity to discuss anything you don’t like. There are a few directories I did _not_ move, mainly for lack of a good place to put

Re: hal watchdog

and if a system has lots of tasks the idle task may not run for a bit (although 200 msecs is a while). On Sep 22, 2016, at 10:58 PM, Sterling Hughes <sterl...@apache.org> wrote: Hey — A follow up on this, I’ve committed initial support for the Nordic platforms for the watchdog,

Re: newtmgr over Serial

No worries: try setting the feature vs CFLAGS. (Note: all good efforts learning about features will be unfortunately useless, as we’ve changed to sys config in develop :-( ). # clear cflags newt target set bootloader cflags= # set feature newt target set bootloader features=BOOT_SERIAL That

Re: newtmgr over Serial

Hi Kevin, I think (and I’ll let Marko chime in here), you can use the boot_serial package to achieve this (apache-mynewt-core/libs/boot_serial.) It speaks the newtmgr protocol, but doesn’t require the shell task or an image to be programmed. I think it will slightly explode the size of

Re: hal watchdog

Hey — A follow up on this, I’ve committed initial support for the Nordic platforms for the watchdog, along with modifying this API a bit. I made the watchdog expiry a millisecond value (in hal_watchdog_init()), as pretty much every watchdog I’ve seen executes in millisecond resolution. I

Re: Switching to Master

Hi, On 21 Sep 2016, at 8:22, Kevin Townsend wrote: No, you aren't missing anything - we should have added a new pointer for master. Thanks for catching this! For reference, here is the current apache-mynewt-core repository.yml file: repo.name: apache-mynewt-core repo.versions:

Re: Directory re-org conversation

for the BLE stack but we could do it if folks thought it a good idea. On Sep 15, 2016, at 3:50 PM, Sterling Hughes <sterl...@apache.org> wrote: Hey, I wanted to get this kicked off, so we can make the changes fairly quickly after the sterly_refactor merge next week (while still giving

Directory re-org conversation

Hey, I wanted to get this kicked off, so we can make the changes fairly quickly after the sterly_refactor merge next week (while still giving enough time for discussion.) Please take this as a _rough_ first cut proposal. I want people to bikeshed this discussion, mainly because I only want

Merge of sterly_refactor -> develop in _1 WEEK_

Hey, I think sterly_refactor is getting pretty close to ready. Chris & Vipul are working on some final items (updating to Will’s latest SPI changes, and finishing the ADC driver for the STM32F4 boards.) I’d like to merge sterly_refactor into develop in 1 week, this will likely lead to some

sys/defs package; power management

Hey, I’m wondering if we should have a new package called “sys/defs” which contain system wide definitions. Right now there are some definitions which don’t fit cleanly in packages (e.g. error codes require OS package). By having a “sys/defs” package we could put error codes into that

Re: Adding C++ header guards?

I think a temporary exception would be fine: but I’m not sure the impact, perhaps somebody who understands C++ better can chime in. Why are ‘#includes’ _excluded_ from the extern “C” namespace? Is it just to avoid cluttering that namespace? Or are there subtle/nefarious effects? If its

Removing os_error_t

Hey, Across the OS, we have two interfaces: some that use os_error_t, and the other that uses int’s for return codes. Personally, I have never liked using a typedef for an error code (largely as a short hand for an enum.) I like to have a single variable “rc” that I use for error

OS device locking

For reference, the OS device code in sterly_refactor: https://github.com/apache/incubator-mynewt-core/blob/sterly_refactor/libs/os/src/os_dev.c I wanted to document my assumptions on OS device locking for folks, and get input as to whether people agree/disagree that this is the right

Re: Low power design

- (future) Provide a method to newt by which certain tasks memory can be linked earlier in RAM, so that for systems where RAM suspension is desired, a core set of system services can be located there, while other services can be re-initialized in a second phase. - This may cause some

Re: Adding C++ header guards?

PS: if anyone wants to volunteer to do this work, I’m more than happy to cede responsibility :-) On 9 Sep 2016, at 10:08, Sterling Hughes wrote: Hey, In our coding style we’ve agreed to be C++ friendly: https://github.com/apache/incubator-mynewt-core/blob/master/CODING_STANDARDS.md

Re: Low power design

Hi Kevin, On 8 Sep 2016, at 10:41, Kevin Townsend wrote: Hi Sterling, I'm sure it's in the planning, but there should definately be some sort of callback at the BSP level before going into a lower sleep state (deep sleep or halt), as well as after wakeup. This will allow you to configure

Re: [jira] [Commented] (MYNEWT-368) Change logging format

URL: https://issues.apache.org/jira/browse/MYNEWT-368 >>Project: Mynewt >> Issue Type: Bug >> Components: Newtmgr >> Reporter: Sterling Hughes >> Assignee: Peter Snyder >>Fix For: v1_0_0_beta1 >&

Re: nmgr, shell vs ble host

PS: I’d be interested in what Will has to say w.r.t controller, which may be an exception — given that it will have hard timing requirements, and likely need to be a high priority task. My mail was meant to address more “appy” (app-ish?) libraries. On 31 Aug 2016, at 16:14, Sterling Hughes

nmgr, shell vs ble host

Hey, I’ve been wondering how we should handle libraries in the OS, that need to run in a task context, but don’t necessarily need their own _dedicated_ task context. I think right now we have two approaches: - Create a library that takes an event queue, and expects to be called within a

Re: hal watchdog

Hi, 2) When developers create the system and want a HW watchdog, what in the OS tickles the watchdog? Is that done by the sanity task or is it done by the OS in some other manner (os time tick, for example)? Or does the creator of the application need to provide for the tickle? This would

Re: Is the Arduino "M0" board supported?

Hi Glen, Awesome! The M0 does not have a debug chip on it, so if you have an external JTAG debugger, I believe it will work (or it will be fairly easy for us to support it, if you are determined.) M0 Pro, Zero and Zero Pro all work well, if you want to get going with those. Sterling On

Re: HAL & I2C redux

On 25 Aug 2016, at 14:00, Sterling Hughes wrote: Hi, On 25 Aug 2016, at 9:48, Stéphane D'Alu wrote: Hi, You could want to take a look at others. ChibiOS has a nice and clean API. I have taken a look at quite a few (Zephyr, mbed-hal). I just took a look at ChibiOS: I’ll refer

Re: HAL & I2C redux

Hi, On 25 Aug 2016, at 9:48, Stéphane D'Alu wrote: Hi, You could want to take a look at others. ChibiOS has a nice and clean API. I have taken a look at quite a few (Zephyr, mbed-hal). I just took a look at ChibiOS: I’ll refer to them more in the past. I haven’t paid much attention

Re: HAL & I2C redux

Hi Kevin, On 25 Aug 2016, at 9:49, Kevin Townsend wrote: Although, this will also depend on how things are implemented in the .c code ... I only see the header at present. But from experience some sensors require the stop to be handled differently between multiple read or writes, so it's

HAL & I2C redux

Hi, While we’re doing the HAL changes, I’d like folks to check out the I2C APIs, and provide any comments they have: https://github.com/apache/incubator-mynewt-core/blob/sterly_refactor/hw/hal/include/hal/hal_i2c.h I was relatively happy with these APIs, except for maybe the

  1   2   3   >