Attachments (0)
Nordic Case Info
  • Case ID: 103546
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

connectivity app not working with PCA10000

Cyril Hruscak

Hi,

I'm using nRF51 BLE driver on PC to simulate BLE peripheral using PCA10000 v2.2 dongle. I need to add some functionality to the default connectivity app. So I compiled the connectivity example from SDK. But the example is not working. The UART interrupts don't seem to be called. Any idea what could be wrong?

BTW Simple UART example is working as expected.

I'm using SDK 5.1.0.36092 and SoftDevice v6.0.0

  • 0

    The interrupt is called, but it seems the connectivity app waits for special byte value (0xC0) first which BLE driver does not send. Is this correct? If yes, how do I need to modify connectivity app to work with BLE driver library?

  • 0

    After some tests it seems BLE Driver uses UART Transport Layer H4 and not Three-way Transport Layer as implemented in the SDK. Can somebody confirm that? If this is true, is there a chance to get new version of BLE Driver in the near future which is compatible with the SDK?

  • 0

    The SDK connectivity source supports more than one transport protocols, and BLE Driver has chosen one of these.

    Update: Version 0.1.0 of BLE Driver uses a variant of SDK Serialization that was not released publicly by SDK at the time. Next release of BLE Driver will be using serialization code that is available in SDK release 6, and the build procedure will be described in the doc.

  • 0 in reply to Bjørn Inge

    I've looked in the readme doc file and also in the sources of connectivity app, but I can't find out how to compile it to be compatible with current BLE driver. Is there some define I have to set?

  • 0 in reply to Bjørn Inge

    The doc of version 0.1.0 did not properly describe the steps to compile the connectivity firmware, I've updated the answer accordingly.

Terms of service