S110 v7.0 available this week. What do you guys think?

RE: S110 v7.0 available this week. What do you guys think?

Andrew Fernandes — Wed, 02 Jul 2014 19:50:06 GMT

Thank you, thank you, thank you!

Bare-metal development is soooo much nicer on Linux and Mac! I've written device drivers for Windows... and I can't thank you enough!

(And on a business side, this makes product development using the nRF51 a MUCH easier thing... leading to higher sales for Nordic!)

RE: S110 v7.0 available this week. What do you guys think?

Carles — Wed, 02 Jul 2014 10:18:37 GMT

We are currently actively working on multiplatform support, including OS X and Linux. Expect good things to come soon.

RE: S110 v7.0 available this week. What do you guys think?

Knut Eldhuset — Fri, 27 Jun 2014 05:42:35 GMT

The S110 v7.0 is still Peripheral only, afaik. I guess you could somehow use the multi-activity feature to implement a Central.

RE: S110 v7.0 available this week. What do you guys think?

steven — Fri, 27 Jun 2014 01:35:21 GMT

It looks very good which can support "Multi-acivity concurrency for Bluetooth Smart and 2.4GHz protocols great".

Do you have any sample to implement it . like nRFready Smart Remote 2 Multi-Protocol Advanced Navigation Remote Control Reference Design

RE: S110 v7.0 available this week. What do you guys think?

Konstantin K — Wed, 25 Jun 2014 23:03:56 GMT

Why are there many of the same include files in the DFU example directory as in the S110 7.0 include directory? Also, some of the files don't match. For example, nrf_mbr.h must be included from the DFU example directory because the one in the S110 7.0 include directory is different. But if I exclude S110 7.0 include directory, then other files are missing.

Seems like DFU example used to be a stand-alone and somewhere those files got offsync. Is there a plan to reconcile and move DFU example into the SDK?

Thanks!

RE: S110 v7.0 available this week. What do you guys think?

Øyvind — Wed, 25 Jun 2014 15:14:04 GMT

Yes, that is correct. Or more correctly, broadcaster and slave concurrently. It will not allow two advertisers running at the same time.

RE: S110 v7.0 available this week. What do you guys think?

Joe Merten — Wed, 25 Jun 2014 09:21:09 GMT

Feature Request:

Please add a Api call to determine the count of available tx buffers e.g. like sd_ble_tx_buffer_count_get_available()

I'd noticed the currently proposed way to determine the available tx buffers as described here and here. But for my opinion, this is a very less comfortable and also error-prone way. I think, the Softdevice could handle this much better, isn't it?

RE: S110 v7.0 available this week. What do you guys think?

jwlock — Wed, 25 Jun 2014 04:45:07 GMT

In the release notes, I found that "The SoftDevice now supports broadcasting while in a connection (DRGN-810, DRGN-4008)."

Does this mean that S110 v7.0 can now support broadcaster and peripheral roles concurrently?

RE: S110 v7.0 available this week. What do you guys think?

Firek — Wed, 07 May 2014 14:53:32 GMT

For Me Gazell doesn't work in Multi-acivity concurrency mode. I've posted at https://devzone.nordicsemi.com/index.php/concurrent-api-s110-7-0-0-3-alpha

RE: S110 v7.0 available this week. What do you guys think?

ovrebekk — Tue, 06 May 2014 12:21:13 GMT

Hi Vaio

The overall DFU solution consists of two parts: The Master Boot Record (MBR) built into S110 v7.0.0 or later, and a bootloader in application space. The only role of the MBR is to copy a new SD image into the SD region, or to copy a bootloader image into the bootloader region. It is up to the bootloader to actually transfer new images into the nRF51 device (allowing you to design the bootloader freely depending on your application requirements, hcoiose the transport layer freely and so on).
Please refer to chapter 3 of the nRF51822 migration white paper to see which revisions you should use with v7 of the S110: Title

The same revision that require version 2 of the PS and RM are the ones guaranteed to work with S110 v7 or later.

The maximum size of the application when not using banked DFU is simply the total flash size, minus the size of the SoftDevice and the bootloader (S110 v7 is 84kB, bootloader is typically 8-16kB). This means that the application will be erased when you update the SD, and you will have to restore it afterwards.

Regards Torbjørn

RE: S110 v7.0 available this week. What do you guys think?

ovrebekk — Tue, 06 May 2014 11:59:45 GMT

Power consumption will definitely go up. You can more or less add the average current of the two protocols together to get the total current draw.

RE: S110 v7.0 available this week. What do you guys think?

ovrebekk — Tue, 06 May 2014 11:58:25 GMT

Gazell is an example of a proprietary 2.4GHz protocol, but it's not the only one.

RE: S110 v7.0 available this week. What do you guys think?

Vaio — Fri, 18 Apr 2014 08:08:35 GMT

The promised features sound awesome, as we were waiting for both (DFU & multi-activity concurrency for BLE & 2.4 GHz protocol).

Reg. DFU, can sbdy state the requirements?

is Softdevice > v7.0 all we need?
is this compatible with all nRF51822 chipsets (we are using nRF51822-QFAA-R at the moment)?
what are the memory requirements for updating DFU & application? (how much memory is left for the actual application, after reserving memory for softdevice (around 80 kB?), and the "new firmware" for DFU?)

Thanks!

RE: S110 v7.0 available this week. What do you guys think?

Marc Nicholas — Tue, 15 Apr 2014 18:14:04 GMT

Hi John,

We're evaluating the 7.0 SDK to migrate to. We're currently using 4.x and had to write things like our own flash storage routines, our own DFU routines, etc.

One thing that's particularly of interest for us is the concurrent Broadcast and Peripheral role.

RE: S110 v7.0 available this week. What do you guys think?

John — Tue, 15 Apr 2014 13:20:16 GMT

I have a question related to the feature mtsunstrum highlights above: Does the ability for peripheral devices to build there own network have any implications on power consumption? Seems like it could potentially take more power to have that capability.

RE: S110 v7.0 available this week. What do you guys think?

mtsunstrum — Sun, 13 Apr 2014 03:18:57 GMT

Looking for clarifications on the v4.1 Bluetooth support ...

Does that mean two S110 devices can exchange data directly between eachother ?

ie. as described in http://www.trustedreviews.com/opinions/bluetooth-4-1-what-is-it-and-why-should-you-care

Improved Data Transfer Bluetooth 4.1 devices can act as both hub and end point simultaneously. This is hugely significant because it allows the host device to be cut out of the equation and for peripherals to communicate independently.

For example, whereas previously a smartwatch would need to talk to your phone to get data from a heart monitor, now the smartwatch and heart monitor can talk directly saving your phone’s battery and then upload their compiled results directly to your phone. This is crucial to the Internet of Things concept: peripherals become independent and can build their own networks before bringing the collation of all their data to you.

RE: S110 v7.0 available this week. What do you guys think?

cocoa — Sat, 12 Apr 2014 11:55:37 GMT

Beautiful thing, but, as usual, no support for OSX or Linux gcc , only windows Keil project. -c

RE: S110 v7.0 available this week. What do you guys think?

aaronxu — Thu, 10 Apr 2014 03:33:24 GMT

Multi-acivity concurrency for Bluetooth Smart and 2.4GHz protocols great!

You mean 2.4Ghz=Gazell?

RE: S110 v7.0 available this week. What do you guys think?

Nguyen Hoan Hoang — Wed, 09 Apr 2014 22:41:58 GMT

Full ota for softdevice is a must. Dfu over serial wire is also very useful.

RE: S110 v7.0 available this week. What do you guys think?

sashi — Wed, 09 Apr 2014 17:10:12 GMT

built in OTA DFU into the softcore would make the setup procedure much simpler as well as reduce code space needed for the DFU. where do I download?

RE: S110 v7.0 available this week. What do you guys think?

Joe Merten — Wed, 09 Apr 2014 16:44:12 GMT

Yep, I'm very interested. I'm curious how Dfu for SoftDevice is working. Currently I'm using the Sdk' Dfu capable bootloader with slightly modifications. But I think, SoftDevice Dfu will only work against SD >= 7.0, isn't it? If so, then I need at least 2 different versions (e.g. 7.0.0 and 7.0.1) to test this feature.