• State Verified Answer
  • Replies 12 replies
  • Subscribers 74 subscribers
  • Views 5002 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 256087
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problems using nRFConnect with nRF52840 Dongle - No connection

daubsi

My nRF52840 arrived yesterday and I started playing around with it. It is immediately recognized y nRFConnect v3.5 BLE App v2.4.0. The firmware on the device is 4.1.2 Jul 14th 2020.

I am reproducing exactly this example How to use nRF52840 USB Dongle and nRF Connect for emulating a BLE peripheral

The advertised device can be found on iOS's nRF Connect App as well as with Android. The advertised name of the nRF52 is correctly received. However neither can I connect nor read the advertised services. Both apps show "No service" in the pre-connection phase. When I try to connect with iOS I immediately get the following error:

As you can see the smart phone seems to be "somewhat" connected (background of picture). The app on the phone still says "Connecting...". Some seconds later the connection terminates.

On Android I get "Error 133 (0x85): GATT Error" but nothing more.

The behavior is consistent whether running the nRF Connect tool on Linux or on Windows. The error is the same.

I also tried adding a HRS in the tool and use the nRF Toolbox on the phone to see whether this works. Here, the nRF52840 isn't even found but the app just said "Scanning".

What am I missing?

Parents
  • 0

    Hi

    First off, the reason we're seeing this error in the BLE app on nRFConnect for Desktop, seems to be due to a bug where the app doesn't handle the PHY request properly. We will provide a fix for this in an upcoming version of the Bluetooth Low Energy app.

    As for the application you are flashing onto your Dongle. You can use the .hex files located in the particular example paths for a "complete .hex file with both SoftDevice and application (I.E. nRF5_SDK_17.0.0_9d13099\examples\ble_peripheral\ble_app_hrs\hex), or if you want to make changes to the example projects, you have to add both the application hex and SoftDevice hex into the Programmer app and write this to the Dongle. 

    If the Flash start address is not correct, you can check out the Adjustment of RAM and Flash memory guide we have here, in order to edit the Flash and RAM start addresses to match the SoftDevice you're using. You can alternatively find older SoftDevices to match the memory of your application in older SDK versions.

    As for the information in the nRFConnect log, what details are you referring to here? If you write the ble_app_hrs_pca10059_s140.hex you should see what SoftDevice version/ID is added in the log. This seems not to go for all Softdevices though. I don't think there is a problem with your board.

    Best regards,

    Simon

Reply
  • 0

    Hi

    First off, the reason we're seeing this error in the BLE app on nRFConnect for Desktop, seems to be due to a bug where the app doesn't handle the PHY request properly. We will provide a fix for this in an upcoming version of the Bluetooth Low Energy app.

    As for the application you are flashing onto your Dongle. You can use the .hex files located in the particular example paths for a "complete .hex file with both SoftDevice and application (I.E. nRF5_SDK_17.0.0_9d13099\examples\ble_peripheral\ble_app_hrs\hex), or if you want to make changes to the example projects, you have to add both the application hex and SoftDevice hex into the Programmer app and write this to the Dongle. 

    If the Flash start address is not correct, you can check out the Adjustment of RAM and Flash memory guide we have here, in order to edit the Flash and RAM start addresses to match the SoftDevice you're using. You can alternatively find older SoftDevices to match the memory of your application in older SDK versions.

    As for the information in the nRFConnect log, what details are you referring to here? If you write the ble_app_hrs_pca10059_s140.hex you should see what SoftDevice version/ID is added in the log. This seems not to go for all Softdevices though. I don't think there is a problem with your board.

    Best regards,

    Simon

Children
No Data
Related
Terms of service