Programming External Device wilth Peripheral UART (nRF Connect SDK)

I found this in the BL652 datasheet:

So yes, if you build for bl652_dvk board, CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC will bet set to y:

https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/bl652_dvk/bl652_dvk_defconfig#L27

AntMAN said:

I am struggling to find out what the CONFIG_BOARD_ENABLE_DCDC option is doing. Could you please explain?

It enables DCDC mode.https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/power.html?cp=4_2_0_17_0#topic

Have you tried doing any debugging of the sample? Does it get stuck somewhere? Any log output?

Laird provide a jtag programming application note for use with the DVK. However it uses nrf5 SDK, and shows a change required to the s132 soft device. This is similar to what you previously stated. However, I cannot find the options to modify the connect SDK, I'm looking in Kconfig, I assume this is correct? The settings are as follows:

nrf_clock_lf_cfg_t const clock_lf_cfg = 
{
    .source         =   0;
    .rc_ctiv        =   16,
    .rc_temp_ctiv   =   2,
    .accuracy       = NRF_SDH_CLOCK_LF_XTAL_ACCUARCY
}

I have been assuming these settings to be correct, but would like to check. 

AntMAN said:

However, I cannot find the options to modify the connect SDK, I'm looking in Kconfig, I assume this is correct? The settings are as follows:

For nRF Connect SDK you need to set 

# 32kHz clock source
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

If you build for board bl652_dvk, this will already be set for you. https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/bl652_dvk/bl652_dvk_defconfig#L27

AntMAN said:

As for the settings you have mentioned, I have looked at the kconfig - and they already seem to be setup correctly for the corresponding board.

Yes, I agree.

AntMAN said:

If I run the debug,

Have you tired debugging using the Ozone? Do you get the same errors there?

AntMAN said:

However, I cannot find the options to modify the connect SDK, I'm looking in Kconfig, I assume this is correct? The settings are as follows:

For nRF Connect SDK you need to set 

# 32kHz clock source
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

If you build for board bl652_dvk, this will already be set for you. https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/bl652_dvk/bl652_dvk_defconfig#L27

AntMAN said:

As for the settings you have mentioned, I have looked at the kconfig - and they already seem to be setup correctly for the corresponding board.

Yes, I agree.

AntMAN said:

If I run the debug,

Have you tired debugging using the Ozone? Do you get the same errors there?

Hi,

so, I have followed a tutorial for programming using nfr5SDK, this involves programming the softdevice in addition to the example code. This worked! Lovely. It was my (lack of) understanding that the Connect SDK did not require programming the soft device... is this correct? Or was this the step I was missing? 

AntMAN said:

It was my (lack of) understanding that the Connect SDK did not require programming the soft device... is this correct?

Correct. In the nRF5-SDK the SoftDevice .hex need to be flashed together with your application.hex

In nRF Connect SDK, it's all linked into a single .hex file

OK, thanks for clarifying. I will stick with the nrf5 sdk solution. Just need to trasnfer project to nrf52810. Thanks for you quick responses. Unfortunately, there seems to be some issue with the 'connect SDK' setup for BL652.  

The solution... use nrf5 SDK instead