nrf52 connectivity example with Yggdrasil

[Wojtek]

I am trying to use my nRF52-DK with Yggdrasil.

I took example from here: *\nRF5_SDK_11.0.0_89a8197\examples\ble_central_and_peripheral\ble_connectivity\pca10040\ser_s132_uart\arm5_no_packs* and succesfully compiled it in SES. I also changed pins to use segger-uart pins on nRF52-DK, but I am not able to connect from Yggdrasil. Any hints? App seems to run fine (no hardfaults etc), and it waits for packets from UART (separate bytes are received when i start Yggdrasil, but no packets are recognized)

[Bjørn Inge]

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.

[Wojtek]

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...

[Bjørn Inge]

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.

[Wojtek]

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!