Re: Cannot resolve dependency

The trailing space was it, thanks! I figured it would be something simple like that. *Greg Strange * Software Engineering Program Lead *Synapse Product Development* A Cambridge Consultants Company mail 1511 6th Ave Suite 400, Seattle, WA 98101 direct 206-832-1269 ext. 3505 <206-832-1269,3505> |

Re: Cannot resolve dependency

On Fri, Jun 09, 2017 at 05:59:26PM -0700, Christopher Collins wrote: > By the way, there is an unfortunate bug in the current version of newt. > The dependency resolution error message gets the depender name wrong; it > prints the dependee package instead! I forgot to mention that this bug has

Re: Cannot resolve dependency

Hi Greg, On Fri, Jun 09, 2017 at 05:47:11PM -0700, Greg Strange wrote: > Hi, > > I'm new to mynewt. I went through the quick start and have successfully > installed mynewt, and have built and run the blinky project targeted to a > NRF52 board. > > As a next step I decided to copy the ble

Re: Cannot resolve dependency

the space between os and “ > On 10 Jun 2017, at 01:47, Greg Strange wrote: > > Hi, > > I'm new to mynewt. I went through the quick start and have successfully > installed mynewt, and have built and run the blinky project targeted to a > NRF52 board. > > As a next step I

Cannot resolve dependency

Hi, I'm new to mynewt. I went through the quick start and have successfully installed mynewt, and have built and run the blinky project targeted to a NRF52 board. As a next step I decided to copy the ble peripheral sample project into my own apps directory as a starting point for a simple BLE

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 wrote: > It seems like the best/quickest solution is to not erase the empty area. >

Re: BLE connection timeout

Hey, Thank you for the quick response. I went for option 1) and disabled the DATA_LEN_EXT feature, which seems to fix the timeout when connecting to my Z5. Good to hear that there is already a fix for this, I'm looking forward to a merge into master! (FYI I could also reproduce the issue on a

Re: os_tick_idle on pic32

Hi Francois, > On Jun 9, 2017, at 10:16 AM, François Berder wrote: > ... > > However this approach does not work on PIC32. Interrupts cannot wake up > the CPU if they are disabled. Hence, the CPU would be stuck in idle mode indeed, this is why this was placed in MCU

os_tick_idle on pic32

Hello, I am currently trying to implement os_tick_idle for the pic32mz2048efg100 of the wifire board. I looked at other implementations, especially the one for nrf51xxx. It seems that on ARM cortex M processors, interrupts are still able to wake up the cpu even if the "cspid i" instruction

Re: BLE connection timeout

Jan: I am not 100% sure but we have seen issues with certain phones due to how the nimble stack controller starts some LL control procedures. This has been addressed in a development branch but I do not think it has been merged into the master branch yet (it will in the upcoming release). I

BLE connection timeout

Hey, I've just been getting started with mynewt and build a small program that is very similar to the bleprph example provided by you. The board is a readbear blend v2 (based on the nRF52832 chipset) and I have the latest development of mynewt-core installed. However, it seems like the connection