• State Suggested Answer
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 4823 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 226941
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Issue with flashing of nRF52810QFAA Device

Umesh

I am facing issue with programming of own developed nRF52810QFAA board. I used Pins 25 (clock) and 26 (data) along with Vcc and Gnd to flash device. I tried with two boards but same issue as mentioned below using Segger while debug mode and using JFlah. Even Erase of Chip is not allowed. Error Is:

Failed to connect to target.
No idcode detected.
Please check connection and Target Interface Type

When checked with DSO for Clock and Data signal,. I observed some data going to controller. Please suggest if any other issue if applicable.

Parents Reply
  • 0 in reply to Umesh

    Thank you! I will discuss your layout/schematic with an HW specialist.

    Just to get me back to speed with your case:

    1. You are able to flash and debug both devices?
    2. Have you enabled DCDC? This should be disabled as you are not using it. Ref. DCDC reference schematic
    3. Have you debugged your code to see when it resets? What error are you receiving?
    4. Please give a current status after the changes you have tried.

    Thanks!
    -Øyvind

Children
  • 0 in reply to Øyvind

    Hello,

    We are able to flash both devices.

    We are using SDK15.2.0 ble_app_blinky example without many modifications. 

    By default DCDC is not enabled & in program we are not enabling it.

    Yes we are able to debug code.

    when program execution of function sd_softdevice_enable start, PC jumps to unknown location. we are using segger studio.

    By default DCDC is not enabled & in program we are not enabling it.

    No any software BLE change is tried.

    Many Thanks

  • 0 in reply to Umesh
    Umesh said:
    when program execution of function sd_softdevice_enable start, PC jumps to unknown location. we are using segger studio.

     Please provide output with an error code from debugging. What location does PC jump to?

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    There is no error but just PC enters to sd_softdevice_enable start and never comes out. If this function comment then continuous reset it observed.

    Could you please provide the work space for this in which BLE is working and DC DC converter is disable as per provide schematic also its using external crystal..

    May be some issue in our work space. We wanted to do this experiment.

    Is it possible to use internal 64MHz clock to run the BLE so that it will be clear the issue which will be related to crystal only.?

    (Note: Our previous working PCB is of 4 layers and this new one is 2 layers)

  • 0 in reply to Umesh
    Umesh said:
    There is no error but just PC enters to sd_softdevice_enable start and never comes out. If this function comment then continuous reset it observed.

     My initial thought is that you have an issue with the 32kHz XTAL, this can cause the sd_softdevice_enable to hang.

    To test this, please edit sdk_config.h to the following:

    / <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// <0=> NRF_CLOCK_LF_SRC_RC 
// <1=> NRF_CLOCK_LF_SRC_XTAL 
// <2=> NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 8
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// <0=> NRF_CLOCK_LF_ACCURACY_250_PPM 
// <1=> NRF_CLOCK_LF_ACCURACY_500_PPM 
// <2=> NRF_CLOCK_LF_ACCURACY_150_PPM 
// <3=> NRF_CLOCK_LF_ACCURACY_100_PPM 
// <4=> NRF_CLOCK_LF_ACCURACY_75_PPM 
// <5=> NRF_CLOCK_LF_ACCURACY_50_PPM 
// <6=> NRF_CLOCK_LF_ACCURACY_30_PPM 
// <7=> NRF_CLOCK_LF_ACCURACY_20_PPM 
// <8=> NRF_CLOCK_LF_ACCURACY_10_PPM 
// <9=> NRF_CLOCK_LF_ACCURACY_5_PPM 
// <10=> NRF_CLOCK_LF_ACCURACY_2_PPM 
// <11=> NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif

    Umesh said:
    Is it possible to use internal 64MHz clock to run the BLE so that it will be clear the issue which will be related to crystal only.?

    As the issue is with sd_softdevice_enable, this clock has not been enabled yet and will not help.

    Umesh said:
    Could you please provide the work space for this in which BLE is working and DC DC converter is disable as per provide schematic also its using external crystal..

     All our BLE examples are working with DCDC converter disabled. Please ensure that the correct SoftDevie Clock Source is set as per my first answer.

    Kind regards,
    Øyvind

Related
Terms of service