nrf52 connectivity example with Yggdrasil

RE: nrf52 connectivity example with Yggdrasil

Wojtek — Sun, 13 Mar 2016 13:35:41 GMT

Ok, I will try to do some research of transmission limits on my own or just try to use 1M if I see lack of performance... Thanks Bjørn, that is everything I wanted to know!

RE: nrf52 connectivity example with Yggdrasil

Bjørn Inge — Sun, 13 Mar 2016 13:23:35 GMT

Yggdrasil, or rather pc-ble-driver, uses HCI UART for the Serialization transport. It is true that HCI UART has more overhead in terms of acking, SLIP escaping and other metadata. This may make the transmission slower, though I'm not sure how much of a bottleneck this incurs in practical use.

RE: nrf52 connectivity example with Yggdrasil

Wojtek — Sat, 12 Mar 2016 15:22:18 GMT

Thank you Bjørn! one more question - does Yggdrasil use RAW UART implementation of serialization, or UART HCI one? I am not sure about difference between these two implementations - HCI one seems more reliable because of ACK's and checksum, but may be slower...

RE: nrf52 connectivity example with Yggdrasil

Bjørn Inge — Fri, 11 Mar 2016 18:55:35 GMT

The serialization included in SDK 11.0.0 is based on version 2.0 of the S130/S132 SoftDevice API, whereas Yggdrasil 0.9.0 is targeted against SoftDevice S130 v1.0. The two version are not compatible, both in terms of API and command opcodes. You will therefore not be able to run Yggdrasil 0.9.0 against a v2.0 connectivity application.

A new release of Yggdrasil is in progress and will be out within a month or two. It will have support for both nRF51 and nRF52 and is targeted against v2 of S130 and S132 SoftDevices.