This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Connect Desktop Bluetooth low energy app with PCA10056

I am interested in having nRF Connect Desktop Bluetooth low energy app work with my PCA10056.  From:

https://devzone.nordicsemi.com/f/nordic-q-a/40155/custom-board-support-for-nrf-connect

The BLE app will only work with specific dev kits under specific circumstances.  From my understanding of the response in the link, it should work with the PCA10056 board on the nRF USB port (other then the USB attached jtag port which it will work on) with the firmware:

\examples\connectivity\ble_connectivity\pca10056\ser_s140_usb_hci\

installed.  Is this suppose to be the case?  When trying to open the port I get the error:

ERROR Unsupported device with serial number 'CD57CF158FCF' and traits ["serialport"]

Does the example require modification to work with the Bluetooth low energy app?  I am using app version V3.3.0 and SDK version 15.2.  For my situation I am not interested in it working on the JTAG USB port.  The port does enumerate properly on my PC as nRF52 USB CDC Connectivity and is seen by the Bluetooth low energy app, it just cannot connect to it.

Thank you for your help.

Parents
  • Hi,

    The connectivity firmware used by nRF Connect is slightly modified compared to the stock serialization firmware in the SDK (see this patch).

    You can flash the connectivity hex from pc-ble-driver repository (connectivity_4.1.1_usb_with_s132_3.1.0.hex) to your board, and it should work with the nRF_USB port of the PCA10056 board. As far as I know, nRF Connect currently only supports up to softdevice API v3.

    Best regards,
    Jørgen

  • Thank you for your reply,

    The connectivity_4.1.1_usb_with_s132_3.1.0.hex does work on the nRF_USB port as you said using the PCA10056 board. We are very interested in using it as the start of a project. We are working with SES as our build and development environment. Our immediate goal is to be able to build a file equivalent to connectivity_4.1.1_usb_with_s132_3.1.0.hex using SES. We could then modify it for the specifics of our board. Our ultimate goal is to have our board work as a dongle for the Desktop nRF Connect Bluetooth Low Energy app by making it look like the PCA10056. Is being able to build a file equivalent to connectivity_4.1.1_usb_with_s132_3.1.0.hex using SES something that can be readily done? I see a completely different build system then SES being described in the GIT repo and we would not want to switch development environment. If we can, is having our board work with the BLE app by appearing as the PCA10056 demo board something that seems feasible?

    Thank you for your help.

Reply
  • Thank you for your reply,

    The connectivity_4.1.1_usb_with_s132_3.1.0.hex does work on the nRF_USB port as you said using the PCA10056 board. We are very interested in using it as the start of a project. We are working with SES as our build and development environment. Our immediate goal is to be able to build a file equivalent to connectivity_4.1.1_usb_with_s132_3.1.0.hex using SES. We could then modify it for the specifics of our board. Our ultimate goal is to have our board work as a dongle for the Desktop nRF Connect Bluetooth Low Energy app by making it look like the PCA10056. Is being able to build a file equivalent to connectivity_4.1.1_usb_with_s132_3.1.0.hex using SES something that can be readily done? I see a completely different build system then SES being described in the GIT repo and we would not want to switch development environment. If we can, is having our board work with the BLE app by appearing as the PCA10056 demo board something that seems feasible?

    Thank you for your help.

Children
No Data
Related