Re: iOS newtmgr app evaluation

Perhaps it's a limitation of the group mailing list ... no images here either, but not a huge problem. For the firmware uploading process, what I don't like today is the very manual process that requires some previous knowledge. You first have to upload your image, then reset, then select the

Re: nrf52dk hal_bsp_init() and sensor device creation

I agree with Marko and I did try initializing the devices using the init callback in os_dev_create(). This kind of helps in removing the dummy functions. The fix required changing the data structure for the sensor_mgr sensor list to be a singly linked list. I am going to open a PR soon with

Re: nrf52dk hal_bsp_init() and sensor device creation

Hi, I did find it a bit odd to see these device initializations in nrf52dk BSP, without matching dependency/syscfg variable declarations in there. I think what I’d want is to have BSP have the device creation only if the board has the particular device on it. And if it has the device creation,

Re: iOS newtmgr app evaluation

Wow. What an Amazing dashboard view. I didnt even know all these stats were in there. Thanks! On Wed, Apr 26, 2017 at 11:15 AM, aditi hilbert wrote: > Hi Kevin, > > I am very interested in evaluating this. I do not have any Swift > experience but I am always working on

Re: Problems with erasing flash on nordic devices

On Fri, May 05, 2017 at 05:58:52PM -0700, Jacob Rosenthal wrote: > Thats basically what Im saying. Though if you just do #2 I wont need a > separate erase command. It'll erase and disconnect the first time, but not > the second time. Ill get an erase command for free. I don't think that will

Re: Problems with erasing flash on nordic devices

Thats basically what Im saying. Though if you just do #2 I wont need a separate erase command. It'll erase and disconnect the first time, but not the second time. Ill get an erase command for free. On Fri, May 5, 2017 at 5:41 PM, will sanfilippo wrote: > 1) Add a command to

Re: Problems with erasing flash on nordic devices

Jacob: I think we might be talking past each other here. I do understand that the code is auto-erasing on upload. Let’s face it: if you want to upload a new image you are gonna have to erase the one that is there. Sure, there may be a case where it is not there or is already the one you want,

Re: Problems with erasing flash on nordic devices

Im not erasing. It is auto erasing on upload. So I cant upload. On Fri, May 5, 2017 at 5:32 PM, will sanfilippo wrote: > BTW: there is an image list command that will tell you if there is an > image that you need to erase. >

Re: Problems with erasing flash on nordic devices

So I left something out of my proposed work-around. The code would have to be modified such that if the page/sector was already erased the image upload would not blindly erase it. BTW: there is an image list command that will tell you if there is an image that you need to erase. > On May 5,

Re: Problems with erasing flash on nordic devices

Any thoughts on this? Also, Theres a simple solution while a more complex one is discussed. The current code erases every time no matter what, theres even a code comment there about it.

Re: nrf52dk hal_bsp_init() and sensor device creation

This is my fault most likely ... the goal at the driver level was indeed to init with a known default config, but obviously if people think a different solution is better there's no reason not to change it! K. On 05/05/17 20:39, Vipul Rahane wrote: I do not know the reason why it is done

Re: nrf52dk hal_bsp_init() and sensor device creation

I do not know the reason why it is done the way it is but I think you are right, the reason might have been to initialize with a default config. > On May 4, 2017, at 3:45 PM, Jacob Rosenthal wrote: > > On Thu, May 4, 2017 at 3:39 PM, Vipul Rahane

MYNEWT-526: Gap params update succeeds, but times out immediately after

Hi, I created pull request which includes solution for MYNEWT-526 and few minor fixes: https://github.com/apache/incubator-mynewt-core/pull/257 This is not a fix, more like a workaround for a known problem in older versions of TI CC254x which cannot apply connection parameters after update if