Re: newtmgr image upload nrf51dk disconnects with reason=8

supervision_timeout = 300 appears to have done it! Any good way to find the existing params change just the 1 I actually want to change? Maybe nrf51 devices should look up supervision_timeout and either send an error code or even request parameter update automatically? static int

Re: newtmgr image upload nrf51dk disconnects with reason=8

Not sure I am answering the right question here as I am sort of jumping in the middle, but with the NRF51 when you erase the flash the CPU is halted. At least, that is what the documentation states. The joy :-) > On Apr 20, 2017, at 4:16 PM, marko kiiskila wrote: > > Does

Re: newtmgr image upload nrf51dk disconnects with reason=8

Hello: They are both related (in a way). When you increase the slave latency the supervision timeout sort of increases along with it (in a manner so speaking). The minimum supervision timeout is this: (1 + connSlaveLatency) * connInterval * 2. So if you increase the slave latency you need to

Re: newtmgr image upload nrf51dk disconnects with reason=8

I believe the setting to tweak is the slave latency, and have some empirical evidence to back that up. Increasing supervision timeout doesn't help if the timeout is at the link manager level (because of a blocking call, say), while increasing slave latency allows the peripheral to take more than

Re: newtmgr image upload nrf51dk disconnects with reason=8

Hi Jacob, On Thu, Apr 20, 2017 at 02:21:01PM -0700, Jacob Rosenthal wrote: > I think the default intervals are here, which should be sufficiently over > 20ms > /** 30 ms. */ > #define BLE_GAP_ADV_FAST_INTERVAL1_MIN (30 * 1000 / BLE_HCI_ADV_ITVL) > //48 > > /** 60 ms. */ > #define

Re: newtmgr image upload nrf51dk disconnects with reason=8

Not sure about the advertising interval part but you can update the connection parameters using ble_gap_update_params() function. bletiny does have an example in case you would want to check that out. Also, after reading a bit, it seems that it’s up to the central whether to accept the

Re: newtmgr image upload nrf51dk disconnects with reason=8

I took out the interrupts and it the disconnect still happens actually. Random googling found this: https://devzone.nordicsemi.com/question/1183/nrf51822-flash-erase-error/?answer=1281#post-id-1281 "If you need to also erase pages while in a connection, you need to make sure the connection

Re: newtmgr image upload nrf51dk disconnects with reason=8

Im not sure that params on connect is available in osx/ios and certainly not in webbluetooth so I cant even prototype that fix. Thus it also seems like a bad long term solution. Could I do a parameter update from device in bleprph/blesplit? Is it actually necessary to disable interrupts during

Re: newtmgr image upload nrf51dk disconnects with reason=8

You can find the settings that I used for the newtmgr in : ~/go/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/linux/hci.go 129 func (h *HCI) Connect(pd *PlatData) error { 130 h.c.Send( 131 cmd.LECreateConn{ 132 LEScanInterval:0x0004, // N x

Re: newtmgr image upload nrf51dk disconnects with reason=8

Hello Jacob, You can try increasing the supervision timeout in the BLE settings, that’s what I needed to do to get the newtmgr working in Go. Regards, Vipul Rahane > On Apr 20, 2017, at 11:16 AM, Jacob Rosenthal wrote: > > Indeed the disconnect is a result of the

dev on Raspberry Pi 3

Hi, I jotted the major steps to duplicate what I did, in case there are others interested in this. 1. Download rasbian image https://www.raspberrypi.org/downloads/raspbian/ and follow instructions on how to get it to microSD card. 2. Boot the system, set up networking. 3. Install golang

Re: [DISCUSS] Release policy update for handling feature branches

Hi, On Friday, 14 April 2017 21:07:04 CEST will sanfilippo wrote: > I think you are correct about this. Someone needs to determine which pull > requests against master need to get merged into the various branches. > > On Apr 14, 2017, at 11:54 AM, aditi hilbert wrote: > > > >