• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 26 subscribers
  • Views 186 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288982
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

MDBT42Q BLE not advertising when using simple SDK ble examples

user116018

Hi everyone, and thanks for all the help provided on this site !

I have tried to flash a MDBT42Q using the nrf82832-DK (PCA10040) and it works fine for simple peripheral examples (like GPIOs, entering sleep modes...).

But when I try to upload ble-peripheral examples such as ble-blinky or ble-app-uart the upload goes fine, but the device doesn't seem to advertise any data.
I have tried to change the NRF_SDH_CLOCK_LF_SRC parameter to 0 and the NRF_SDH_CLOCK_LF_ACCURACY  parameter to 1 as described in this topic, but with no success.

Has anyone managed to make the MDBT42Q work with the ble_app_uart example ?

FYI : I am using Segger Embedded Studio v6.30 and the nrf SDK v17.1.0.

Thanks a lot for your help !

Parents
  • 0

    Hi Vidar,

    Thank you very much for your precise and prompt reply !
    I have switched back to Segger V 5.70 that I used previously and commented out the line you suggested, but still with no luck.

    I went a bit further though : when debugging, I get the error "app: ERROR 7 [NRF_ERROR_INVALID_PARAM]" when calling nrf_sdh_enable_request().
    According to this topic it might be related to the fact that I changed the NRF_SDH_CLOCK_LF_SRC to 0 ("RC") but I should also have changed the values of NRF_SDH_CLOCK_LF_RC_TEMP_CTIV and NRF_SDH_CLOCK_LF_RC_CTIV. 
    The problem is that I don't know to what values I should put those. Any idea ?

    I will look further and upload any findings in here.

    Thanks again for your support !

  • +1 in reply to user116018

    Ok, new update,

    I found this topic which indicated the following values for the parameters :

    NRF_SDH_CLOCK_LF_RC_CTIV=16 and NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=2

    I changed it like this in the sdk_config.h file, and it worked !

    So to sum up the changes I had to make for it work :

    1. Use Segger version 6.20 or older
    2. Comment out the line APP_ERROR_HANDLER(p_event->data.error_communication);
    3. Change NRF_SDH_CLOCK_LF_SRC to 0 and NRF_SDH_CLOCK_LF_ACCURACY to 1 to activate the internal oscillator
    4. Change NRF_SDH_CLOCK_LF_RC_CTIV=16 and NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=2
Reply
  • +1 in reply to user116018

    Ok, new update,

    I found this topic which indicated the following values for the parameters :

    NRF_SDH_CLOCK_LF_RC_CTIV=16 and NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=2

    I changed it like this in the sdk_config.h file, and it worked !

    So to sum up the changes I had to make for it work :

    1. Use Segger version 6.20 or older
    2. Comment out the line APP_ERROR_HANDLER(p_event->data.error_communication);
    3. Change NRF_SDH_CLOCK_LF_SRC to 0 and NRF_SDH_CLOCK_LF_ACCURACY to 1 to activate the internal oscillator
    4. Change NRF_SDH_CLOCK_LF_RC_CTIV=16 and NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=2
Children
No Data
Related
Terms of service