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

nRF Connect for desktop

Ming

hi,

I want to use the Bluetooth Low Energy in nRF Connect for desktop. But I have no DK or dongle.

When I use my own development board and the MCU is nRF 52832, it can be downloaded, but it can't be connected.

Is the Bluetooth Low Energy function available only for PCA10028, PCA10031, PCA10040, PCA10056 and PCA10100?

and this is log about nRF Connect for Desktop

2019-12-10T06:45:06.755Z INFO Application data folder: C:\Users\XMX\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2019-12-10T06:45:06.825Z DEBUG App pc-nrfconnect-ble v2.3.2 official
2019-12-10T06:45:06.826Z DEBUG App path: C:\Users\XMX\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2019-12-10T06:45:06.826Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2019-12-10T06:45:06.826Z DEBUG nRFConnect path: C:\Users\XMX\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-12-10T06:45:06.826Z DEBUG HomeDir: C:\Users\XMX
2019-12-10T06:45:06.826Z DEBUG TmpDir: C:\Users\XMX\AppData\Local\Temp
2019-12-10T06:51:46.286Z INFO Validating connectivity firmware for device with serial number 000059401308...
2019-12-10T06:51:53.800Z INFO Connectivity firmware is valid.
2019-12-10T06:51:53.801Z ERROR Device with serial number 000059401308 is not in the list of supported JLink devices: PCA10028, PCA10031, PCA10040, PCA10056, PCA10100
      

Best wishes.

Parents
  • +1

    Hi

    You're seeing this error message because the Segger ID doesn't match the Segger IDs for the DKs, so nRFConnect doesn't know what sort of device you're trying to connect. The reason it is like this in the BLE app is that the BLE app requires the device to work with any BLE device, which is why the app is locked to a specific range of Segger IDs.  As far as I know, there are no plans to change this, but we at support rarely know everything about the roadmap.

    If you want to discuss this further, please contact the regional sales manager (RSM) of your area. If you don't know how to contact your RSM, please fill out our Sales Related Questions form to get in touch.

    Best regards,

    Simon

Reply
  • +1

    Hi

    You're seeing this error message because the Segger ID doesn't match the Segger IDs for the DKs, so nRFConnect doesn't know what sort of device you're trying to connect. The reason it is like this in the BLE app is that the BLE app requires the device to work with any BLE device, which is why the app is locked to a specific range of Segger IDs.  As far as I know, there are no plans to change this, but we at support rarely know everything about the roadmap.

    If you want to discuss this further, please contact the regional sales manager (RSM) of your area. If you don't know how to contact your RSM, please fill out our Sales Related Questions form to get in touch.

    Best regards,

    Simon

Children
Related
Terms of service