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

nRF52 DK P0.30 to ground?

Jean

Hi,

I cannot find my nRF52 (PCA100040 / SD132) when scanning for devices from my nRF Master Control Panel on my Android Phone.

In these two posts (post1 and post2), people mention that connecting P0.30 to ground is necessary in order to see the nRF51 DK board when scanning. [EDIT] I just found this post which seems to indicate that the connection to ground is only specific to Master Control Panel. Unfortunately my MCP (v4.0.5) does not seem to have a Help > Supported Hardware section and I cannot check for more information there.

I have a few questions :

  • is this P0.30 to ground connection only necessary for MCP or also for any other BLE scanner?

  • I cannot see the Help > Supported Hardware section on my MCP app (Android phone). Is this information provided somewhere else (eg in the infocenter site or in the nRF51 Series Ref. Manual)?

  • do we also need to connect nRF52 DK's GPIO pin 30 to ground?

Thanks

  • 0

    Hi jean.

    Only is necessary when you use MCP in a pc, for mobile device isn´t necessary.

    I have just tried it and my mobile device detects my board. If your mobile device doesn´t detect it, maybe is because after 3 minutes, your board doesn´t send more advertise, with what example are you testing MCP? or if you are using your own code, try to use an example.

    If you want to see how works mcp, you can find information on your mobile device in:

    • options > settings > (section "About") > tutorial
    • options > settings > (section "About") > question&answer

    Hope this can help you.

    Javier.

  • 0 in reply to Javier

    Thanks Javier. I'd love to use MCP from my computer but unfortunately it does not seem that it has been ported to Linux yet. I was trying to get this code running. I was able to modify for my nRF52 PCA10040 and compile and flash it, but then I am unable to detect any signal with the MCP Android app. That's where I am at right now. I will try to find another basic nRF52 BLE advertizing code example and try again. Thanks for your help.

  • 0 in reply to Javier

    Try with some simple example, maybe "ble_app_uart".

  • 0

    Hi,

    When using Master Control Panel on a PC you will need a "connectivity device" (DK or dongle) connected to the PC to provide BLE capabilities for MCP. "Supported hardware" in the MCP help files is for what hardware is supported as a "connectivity device". MCP (both for pc and smartphone app) can be used to communicate with any BLE device in the other end.

    The "connect P0.30 to GND" is only for the connectivity device, and only if it is an nRF51 DK. This is because of an issue when using the connectivity software on the nRF51 DK.

    We do have a new tool similar to MCP which is for both GNU/Linux, OSX and Windows. Currently it is in development, you can read about it as well as download the current version from the New Bluetooth Smart tool from Nordic blogpost. Do note that just as for MCP you will need a connectivity device.

    I recommend that you have a look at our newest SDK, which can be downloaded from developer.nordicsemi.com. The latest version at the time of writing is SDK 11, which is for both nRF51 and nRF52. See the introduction and the getting started guide on our infocenter.

    Regards, Terje

  • 0 in reply to tesc

    Hi Terje, thanks for your recommendations.

    I only have a nRF52 DK, PCA10040 V0.9.0 and, if I understand correctly the release note , nRF5 SDK v11.0.0 is not compatible with this board. So I'll stick to nRF52 SDK v0.9.2 for the moment.

    As for the new MCP, it's a good news that it is now available on Linux but it seems that it does not work yet for nRF52 DK.

    In any case you answered my question that the P0.30 to GND "bridge" is only required for nRF51, but not for nRF52. Thanks.

Related
Terms of service