Re: segger jlink

[Szymon Janc]

Hi Sterling,

On 30 May 2017 at 22:19, Sterling Hughes
 wrote:
>
> 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 Slack 
> —> if it’s better attended by developers, is it too much of a hurdle even 
> these days?

I can live with Slack as long as IRC gateway is enabled :)


-- 
pozdrawiam
Szymon K. Janc

Re: segger jlink

[Justin Mclean]

Hi,

> Well, I’m on mynewt.slack.com - if you care to be a guinea pig! :-)
> 
> Invite link here: 
> https://join.slack.com/mynewt/shared_invite/MTkwMTg1ODM1NTg5LTE0OTYxNzQ4NzQtZTU1YmNhYjhkMg

You might want to consider adding a room to https://the-asf.slack.com/ ?

Thanks,
Justin

Re: segger jlink

[Sterling Hughes]

Well, I’m on mynewt.slack.com - if you care to be a guinea pig! :-)

Invite link here: 
https://join.slack.com/mynewt/shared_invite/MTkwMTg1ODM1NTg5LTE0OTYxNzQ4NzQtZTU1YmNhYjhkMg


Sterling

On 30 May 2017, at 13:22, Pierre Kircher wrote:


i dont mind using slack ..

a quick chat is just way 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 
 wrote:


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 Slack —> if it’s better attended by developers, is it 
too much of a hurdle even these days?


Sterling

On 30 May 2017, at 12:27, Jacob Rosenthal wrote:

The mailing list has been gracious to help me fix a bunch of stuff 
upstream

and taken my changes, and Ive really enjoyed the tooling on mynewt.

However, no offense to the mynewt core, but I would push back on the 
idea

you have a functioning IRC.

Ive been idling there for well over 6 months and have tried asking
questions there. Any questions there go unanswered, or are told to 
be taken

here.

Further in all that time the room has been absolutely silent because 
the
core team has literally no public discussion there. It would be nice 
to
hear that kind of core discussion that really doesnt happen here 
either...





On Tue, May 30, 2017 at 12:07 PM, aditi hilbert  
wrote:


at exchange - and we would love it if you could contribute back to 
the
documentation (https://github.com/apache/incubator-mynewt-site, 
develop

branch) :)

Re: segger jlink

[Pierre Kircher]

i dont mind using slack ..

a quick chat is just way 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  
> wrote:
> 
> 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 Slack 
> —> if it’s better attended by developers, is it too much of a hurdle even 
> these days?
> 
> Sterling
> 
> On 30 May 2017, at 12:27, Jacob Rosenthal wrote:
> 
>> The mailing list has been gracious to help me fix a bunch of stuff upstream
>> and taken my changes, and Ive really enjoyed the tooling on mynewt.
>> 
>> However, no offense to the mynewt core, but I would push back on the idea
>> you have a functioning IRC.
>> 
>> Ive been idling there for well over 6 months and have tried asking
>> questions there. Any questions there go unanswered, or are told to be taken
>> here.
>> 
>> Further in all that time the room has been absolutely silent because the
>> core team has literally no public discussion there. It would be nice to
>> hear that kind of core discussion that really doesnt happen here either...
>> 
>> 
>> 
>> 
>> On Tue, May 30, 2017 at 12:07 PM, aditi hilbert  wrote:
>> 
>>> at exchange - and we would love it if you could contribute back to the
>>> documentation (https://github.com/apache/incubator-mynewt-site, develop
>>> branch) :)
>>> 



signature.asc
Description: Message signed with OpenPGP

Re: segger jlink

[Sterling Hughes]

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 Slack —> if it’s better attended by developers, is it too 
much of a hurdle even these days?


Sterling

On 30 May 2017, at 12:27, Jacob Rosenthal wrote:

The mailing list has been gracious to help me fix a bunch of stuff 
upstream

and taken my changes, and Ive really enjoyed the tooling on mynewt.

However, no offense to the mynewt core, but I would push back on the 
idea

you have a functioning IRC.

Ive been idling there for well over 6 months and have tried asking
questions there. Any questions there go unanswered, or are told to be 
taken

here.

Further in all that time the room has been absolutely silent because 
the
core team has literally no public discussion there. It would be nice 
to
hear that kind of core discussion that really doesnt happen here 
either...





On Tue, May 30, 2017 at 12:07 PM, aditi hilbert  
wrote:


at exchange - and we would love it if you could contribute back to 
the
documentation (https://github.com/apache/incubator-mynewt-site, 
develop

branch) :)

Re: segger jlink

[Christopher Collins]

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