In my use case I need to provide the highest throughput that the BLE spec safely allows yet has to be agnostic to which type of hardware device is on the client side. Our current implementation uses a bluetooth classic chipset to transmit data using serial, tftp and ppp services to another device. The data is sent as individual files that are approximately 20-30k a piece. A prototype board we spun uses the da14580 and I was able to download a custom fully hosted image via SPI to the board, but I am now looking at how to transfer data via BLE in the most efficient way possible. I want to move away from having the overhead of tftp and ppp stacks so I just want to send straight data with integrity checking. One would argue it makes sense to just stick with classic Bluetooth for such a situation, but besides being able to send these larger chunks of data, we'd like to be able to create custom profiles for other sensors on the device. Ble chipsets in general also have lower power needs.

Looking at the examples such as throughput_streaming and dsps, this seems to be achieveable, but am I locked into using a diaglog chipset on each end? Meaning is the throughput streaming example using specific murata da14580 features that might not be available on the other end?

Also I noticed that there is no streaming data example for the new SDK. I have been trying to setup the streamdatahd profile located in the 5.0.3 SDK, but have been running into errors. I was successfully able to setup other profiles in the new SDK such as the battery profile, but the steamdata one eludes me. Are there any internal/beta versions of the streaming data example project that have been converted to the new SDK?