ANNA B402 EVK: BLE Blinky example from NRF5 SDKv17 not advertising

I’m not sure if I’m posting in the right forum, but since the EVK-ANNA-B402 uses the nRF52833, I thought this might be the place for questions related to it.

Steps followed to compile and flash the "ble_app_blinky_pca10040_s132" on EVK-ANNA-B402

1.Downloaded custom board support file for the EVK-ANNA-B402 found in the u-blox short range GitHub repository :https://github.com/u-blox/u-blox-sho-OpenCPU.

2.Open the project in SEGGER embedded studio , select options,Select the Common configuration, select code, select Preprocessor and select Preprocessor definitions.

3.Modified the "BOARD_" definition to define the BOARD_CUSTOM.

4.Built the code," Downloaded ble_app_blinky_pca10040_s132.elf ", Verified "ble_app_blinky_pca10040_s132.elf".

with NRF connect app on mobile phone and PC , device name "Nordic-blinky" not advertised.

Please let me know what are the configuration steps i am misssing for EVK-ANNA-B402 to get the BLE working

Parents
  • Hi,

    From what I can see, the ANNA-B402 does not have a 32.768 kHz crystall mounted. That is OK, but the SDK exmaples are configured for a crystal, so you need to modify the project's sdk_config.h as explained in this post to use the internal LFRC instead.

  • Hi Einar,

    Thanks for the response.

    I have checked schematic and board of ANNA-B402 EVK that I am using has external 32.768KHz crystal. Checked individually for both LFRC and XTAL settings in sdk_config.h, no BLE advertised to NRF connect on mobile or on Laptop.

    I am using:
    ble_app_uart example from NRF5 SDK V17.1.0
    Soft device S113 v7.2.0
    SEGGER embedded studio v5.42a
    Renamed this file to custom_board.h and used with preprocessor definition BOARD_CUSTOM.

    Here is a screenshot of the section placement macros:



    Could you please point me to something that I may be missing to configure.

Reply
  • Hi Einar,

    Thanks for the response.

    I have checked schematic and board of ANNA-B402 EVK that I am using has external 32.768KHz crystal. Checked individually for both LFRC and XTAL settings in sdk_config.h, no BLE advertised to NRF connect on mobile or on Laptop.

    I am using:
    ble_app_uart example from NRF5 SDK V17.1.0
    Soft device S113 v7.2.0
    SEGGER embedded studio v5.42a
    Renamed this file to custom_board.h and used with preprocessor definition BOARD_CUSTOM.

    Here is a screenshot of the section placement macros:



    Could you please point me to something that I may be missing to configure.

Children
  • Hi,

    If you are just trying to run the sample on the board there is no need to adjsut the section placement macros. Use the onces from the unmodified example. However, I suspect you are looking for the preprocessor defines? These are set under "Preprosessor" which is one step down in the menue from "Linker", where you are in this screenshot.

    I would suggest that you try the beacon sample first. This does not use any GPIO's, so as long as the LF clock configuration is correct it will work on any board even if you build with the DK board file. I did not find a clear indication that the EVK has the crystal in place, but the module does not. As using the internal LFRC will work regardless I suggest you test with that first as shown in my previous post. With this change, it should run on any board.

  • Hi Einar,

    this is the screenshot for preprocessor defines under "common" configuration:

    Preprocessor defines

    this is the screenshot for config_sdk.h setting for clock source:




    According to schematic of EVK ANNA B402, external crystal of 32.768KHz is present, also checked on the EVK ANNA B402 PCB it is present. However as suggested by you, I have used internal crystal LFRC as shown in the config_sdk.h file setting above.



    https://content.u-blox.com/sites/default/files/EVK-ANNA-B4_UserGuide_UBX-21008123.pdf

    Still doesn't advertise, please advise if something else is missing to configure.



  • Hi,

    I see. Did you test the beacon sample also? does it still not advertise? Then the next step is to start debugging. And the first part of that is to build a debug build (select "Debug" from the build configuration drop-down) and observe the UART log (for that you need to either use your own board fiels or adjust the DK board file so that the UART pins match your hardware). What do you see in the log? If logging is difficult, you can also just start a debug session, reset and let the applicaiton run for a while before pausing. What do you see then?

Related