Pierre, All this is great exchange - and we would love it if you could contribute back to the documentation (https://github.com/apache/incubator-mynewt-site, develop branch) :)
We do have a chat channel on irc.freenode.net <http://irc.freenode.net/>, channel name #mynewt. thanks, aditi > On May 31, 2017, at 1:54 AM, Pierre Kircher <pkirc...@me.com> wrote: > > might worth mentioning that just happens in gdb .. > if i use ozone (segger tool) it debugs straight away > > i check those recommendations as soon as im back on the desk > > thanks again > > love the project but could use some more documentation or a chatroom > irc/gitter > > pierre > >> On 30 May 2017, at 18:37, Christopher Collins <ch...@runtime.io> wrote: >> >> Hi Pierre, >> >> First, don't worry about asking a lot of questions. There are probably >> others with the same questions who will benefit from your asking them! >> >> On Tue, May 30, 2017 at 04:32:20PM +0100, Pierre Kircher wrote: >> [...] >>> the breakpoint points on main.c 129 > apps/bleprph/src >>> >>> Reading symbols from >>> /Users/pkircher/dev/puck/bin/targets/bleprph/app/apps/bleprph/bleprph.elf... >>> done. >>> os_tick_idle (ticks=595) at >>> repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200 >>> 200 if (ticks > 0) { >>> Not implemented stop reason (assuming exception): undefined >>> >>> never hits that breakpoint - is that a known issue ? >> >> That is not a known issue. My guess is that the API call immediately >> before that point (ble_gap_adv_set_fields) is failing for some reason. >> One common reason is that the app is trying to put too much data into >> the advertisement. For example, this happens if you are using a very >> long name. I would backtrack a bit; set a breakpoint on >> bleprph_advertise() and see if your app gets there. >> >> FYI, here is the expected sequence of events: >> 1. main() >> 2. bleprph_on_sync() (communication established among host and >> controller). >> 3. bleprph_advertise (called from bleprph_on_sync()). >> >> Chris >
