A big update this week for our S110 SoftDevice. Full OTA DFU for SoftDevice and Application. Also Multi-acivity concurrency for Bluetooth Smart and 2.4GHz protocols. As Developers working with our products we're interested in your thoughts?
A big update this week for our S110 SoftDevice. Full OTA DFU for SoftDevice and Application. Also Multi-acivity concurrency for Bluetooth Smart and 2.4GHz protocols. As Developers working with our products we're interested in your thoughts?
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.
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.
Regards Torbjørn
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
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?
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?