Re: 2nd UART on NRF52DK

Thanks marko! we got it up and running! Cheers, - Andrew - On Wed, Feb 1, 2017 at 3:13 PM, marko kiiskila wrote: > Hi Andrew, > > > On Feb 1, 2017, at 12:01 PM, Andrew Tam wrote: > > > > Hi Marko, > > > > I've followed what you did in the Arduino Primo bsp

Re: 2nd UART on NRF52DK

Hi Andrew, > On Feb 1, 2017, at 12:01 PM, Andrew Tam wrote: > > Hi Marko, > > I've followed what you did in the Arduino Primo bsp file to setup the UART1 > pins. Looks like my project will compile without errors, But I was unable > to see anything coming over the UART1 TX. Is

BLE HCI support on NRF52DK

Hi, I've spent some time trying to get nRF52832 DK running the 'blehci' code communicating with Xubuntu 16.10 (under VMware) with not much luck. I'm currently running the following development setup: $ git status On branch develop Your branch is up-to-date with 'origin/develop'. $ go version

Creating branch for 1.0.0 beta2 release

Hello: Just a heads up. I am going to create the 1.0.0 beta 2 release branch.

Re: git for all next directories

Yes it can, and it can be un-needlesly complicated if not done right - and so that's why I floated the question, as it seems that it is implicit in the design of the way that newt produces a software part that it should be traceable. I would think, it needs the specific git commands - the

Re: [RFC] Using BLE device address in API

Hi, I created pull request which contains patch that introduces ble_addr_t type and makes public API use it: https://github.com/apache/incubator-mynewt-core/pull/173 In most cases internals are not updated since this in some cases requires a lot of additional work and can be done later. Apart

Re: git for all next directories

> In project.yml you specify what git tag to use when you’re pulling in from those Related request, being able to specify a commit hash, rather than just tags, in project.yml. Useful for the mynewt-core repo when test bleeding edge on develop, but would also come in very handy for my own repos.

Re: git for all next directories

I would recommend doing what David does. I see you having 2 options for dealing with stuff under repos: 1. freeze your project.yml, and check it in to you SCM, along with other packages you’ve created. In project.yml you specify what git tag to use when you’re pulling in from those

Re: git for all next directories

I'm no git expert, as anyone on this list can attest to, but here's one of the ways I have dealt with this issue: The repos/ directory contains repos that are already under git, and that (for the most part) I'm not making changes to. Where MY changes happen is under the 'apps', 'targets' and

RE: git for all next directories

I certainly struggle to understand git all the time and I'm likely to be wrong here, but can't a git repository have sub-projects within the larger super-project? ALan -Original Message- From: Neilh [mailto:neil...@biomonitors.com] Sent: Wednesday, February 01, 2017 9:36 AM To:

git for all next directories

Hi Just got a dumb question to ask - I'm working through the tutorials and its well explained the standard SCM/git is on "myproj/repos/apache-mynewt-core ((mynewt_1_0_0_b1_tag))]$" However, after the basic tutorial, with a working "newt" environment, I need to have the whole sandbox from