Re: Mynewt system initialization

Hello all, This is a follow-up email regarding Mynewt system initialization. I took all of your feedback (very helpful, thanks!) and did some more thinking. As always, all comments, criticisms, and suggestions are appreciated. Thanks, Chris ### Recap Proposal: 1. Move system

Re: [jira] [Commented] (MYNEWT-368) Change logging format

In the 16-bit case I don't understand why you would ever reset the index to 0. So long as the value is increasing, you will always have 32k entries prior to wrap. I don't see why you'd care that it starts at a given number. Sterling > On Sep 1, 2016, at 2:28 PM, Ray Suorsa (JIRA)

Re: [jira] [Commented] (MYNEWT-368) Change logging format

Hello Peter, Sorry, I did am not copied on the ticket and so I did not receive a notification. The main reason behind adding an index was indicating the order of entries logged in a millisecond. If the timestamp is the same which could be the case if we log at a lower level than the

Re: nmgr, shell vs ble host

> On Sep 1, 2016, at 9:36 AM, Sterling Hughes wrote: > > Yeah - for sure libraries should be able to use tasks (just like > newtmgr and shell do today.) I'm more thinking as maintainers of > core, which method do we prefer for standard libraries. > > Does anyone disagree

Re: Setting connection parameters

Hmm well I didn't get the ble_gap_update_params() version to work, but I did get ble_l2cap_sig_update() to work! The key is to *not* enabled the BLE_LL_CFG_FEAT_CONN_PARAM_REQ feature. If I had that enabled, the slave sent an L2CAP Connection Parameter Update Request, and the master replied with