Re: Blinky on nRF52 DEV via Black Magic Probe: SIGSEGV in os_pkg_init

Marcos Scheeren writes: > Back in February (about Feb 21, if you dig under the mailing lists > archives) I ran into some issues trying to flash a NRF5182xxAA 16KB > RAM with a Black Magic Probe.. > > I only got it running after some binary file tweaking with >

Re: Blinky on nRF52 DEV via Black Magic Probe: SIGSEGV in os_pkg_init

Christopher Collins writes: >> Program received signal SIGSEGV, Segmentation fault. >> os_pkg_init () at repos/apache-mynewt-core/kernel/os/src/os.c:223 >> >> >> I stepped through the code and I end up inside `os_start' which appears >> to only have `assert(0)' as its

Re: Blinky on nRF52 DEV via Black Magic Probe: SIGSEGV in os_pkg_init

Hi Peter, On Fri, Jun 16, 2017 at 04:10:52PM -0700, Peter Jones wrote: > It's very likely that I'm doing something wrong so I'm reaching out for > help. All I want to do right now is to get Blinky working on an nRF52. > > I followed the tutorial and built the boot loader and blinky. I then >

Blinky on nRF52 DEV via Black Magic Probe: SIGSEGV in os_pkg_init

It's very likely that I'm doing something wrong so I'm reaching out for help. All I want to do right now is to get Blinky working on an nRF52. I followed the tutorial and built the boot loader and blinky. I then created an image so the boot loader would be happy about the magic number. I used

Apache Mynewt podling graduation on vote on dev@mynewt.incubator.apache.org

The Apache Mynewt podling team is pleased to announce that the project is currently undergoing voting for graduation to TLP on the dev@mynewt.incubator.apache.org <mailto:dev@mynewt.incubator.apache.org> mailing list. Subsequent to successful voting on dev@ list, it will be put to

dev on Raspberry Pi 3

.yml to use 0-dev (latest from master) as the version. newt install 6. Change to use sim-armv7 as your architecture modify the following lines repos/apache-mynewt-core/hw/bsp/native/bsp.yml bsp.arch: sim-armv7 bsp.compiler: compiler/sim-armv7 7. Build and run 'my_blinky_sim' newt

Joining your dev team

emphasis on platform independence. After reviewing your web-site, it is obvious that your currently dev team leaders are experienced and have put together a solid dev process for a BLE protocol stack. I have some business related questions: 1. Do you currently have end customers using the mynewt

Re: Stuck with the tutorial with MyNewt 1.0.0-dev

:Re: Stuck with the tutorial with MyNewt 1.0.0-dev Resent-From:lm.c...@free2move.se Date: Sun, 4 Dec 2016 11:03:47 -0800 From: aditi hilbert <ad...@runtime.io> To: dev@mynewt.incubator.apache.org CC: Lm Chew <lm.c...@free2move.se>, Meili Yeo <meili@free

Stuck with the tutorial with MyNewt 1.0.0-dev

Dear support, I'm new to MyNewt. Since the new update(1.0.0-dev), the file name/naming have been changed while the tutorial not updated. So far i managed to figure out until the tutorial below: http://mynewt.apache.org/develop/network/ble/ini_stack/ble_parent_ini/ Do you have any updated

dev

Hello all, I wanted to send a quick note about the planned 1.0.0 beta 1 release. The pre-release branch has the following name: 1_0_0_b1_dev This branch has been created in the following repos: incubator-mynewt-blinky incubator-mynewt-core incubator-mynewt-newt

Blinky using latest dev branch errors

I'm working through the documentation, in an effort to update it all in preparation for the beta release, and the STM32 Blinky will not build in the dev branch: ... Linking blinky.elf Error: /Users/dsimmons/dev/myproj/bin/stmf3_blinky/libs/os/os.a(os_arch_arm.o): In function `os_arch_os_init

Re: Is anyone out there still using a nrf52 Preview (stress on the word Preview!) Dev kit?

My vote would be to remove it to push people to production parts and kits. Le vendredi 23 septembre 2016, will sanfilippo <wi...@runtime.io> a écrit : > Hello: > > The first dev kits produced by nordic which used the nrf52 were called > Preview Development Kits. They have a PC

Is anyone out there still using a nrf52 Preview (stress on the word Preview!) Dev kit?

Hello: The first dev kits produced by nordic which used the nrf52 were called Preview Development Kits. They have a PCA of 10036 on them (the large white label on the debugger chip contains the PCA). Just as an FYI: PCA 10028: nrf51DK PCA 10036: nrf52PDK *** Preview Dev Kit *** PCA 10040

Re: Reminder to vote for 0.9.0-rc3 on the dev list

HI, > This is just a friendly reminder - if you are an IPMC member with a > binding vote, could you please carry your vote for 0.9.0-rc3 over to the > gen list? I’m just looking at it now. BTW sometime it can help to say what the difference from the last RC is, if for instance the only

Re: Running Newt on nrf51 boards with 0.9.0 and 0-dev

u.com> wrote: > > On 06/03/2016 07:32 AM, Wayne Keenan wrote: >> Hi Will, >> >> Ok, thanks for letting me know. Boards 2&3 are 'hidden' behind the mbed >> CMSIS-DAP interface and I also didn't want to resort to using additional >> h/w (a non-dev user

Re: Running Newt on nrf51 boards with 0.9.0 and 0-dev

On 06/03/2016 07:32 AM, Wayne Keenan wrote: Hi Will, Ok, thanks for letting me know. Boards 2&3 are 'hidden' behind the mbed CMSIS-DAP interface and I also didn't want to resort to using additional h/w (a non-dev user wouldn't have) in order to erase or program them; prior to programming b

Re: Running Newt on nrf51 boards with 0.9.0 and 0-dev

Hi Will, Ok, thanks for letting me know. Boards 2&3 are 'hidden' behind the mbed CMSIS-DAP interface and I also didn't want to resort to using additional h/w (a non-dev user wouldn't have) in order to erase or program them; prior to programming board 1 am using: JLinkExe -device nrf51 -if

Running Newt on nrf51 boards with 0.9.0 and 0-dev

Hi, I've been trying to get the bletiny and bleprph apps running on a few types of nrf51 boards but not having much luck. The 3 types are: 1. PCA1 - QFAA G0 (The stubby little USB dingle with the built-in Jsegger J-link) 2. PCA10024 - QFAA G0 (The mbed enabled board, using a hex file )

[Dev][GSoC:2016]MYNEWT-118:Android or iOS application to interact with devices/boards powered by Mynewt OS and BLE stack (Nimble)

Hi all, I am a 3rd year computer engineering undergraduate from University of Moratuwa,Sril Lanka.I am interested in above project.I have been researching about bluetooth api of Android. Please let me know how to proceed with this project.

Re: confirm subscribe to dev@mynewt.incubator.apache.org

On 22/01/2016 1:30 PM, dev-h...@mynewt.incubator.apache.org wrote: Hi! This is the ezmlm program. I'm managing the dev@mynewt.incubator.apache.org mailing list. I'm working for my owner, who can be reached at dev-ow...@mynewt.incubator.apache.org. To confirm that you would like

Re: who has subscribed to dev@

Hi Greg, Justin - Can you please add me as a moderator of the dev and commit lists? thanks, aditi > On Nov 6, 2015, at 1:52 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > > Yes, you can send an email to {listtname}-l...@mynewt.incubator.apache.org > <mailto:l...@mynewt