BL652 EVK Crystal Problem

RE: BL652 EVK Crystal Problem

shewan — Fri, 13 Apr 2018 10:01:10 GMT

By the way, the BL652 EVK had a 32KHz crystal on board. It is not connected by default, and you will need to bridge SB8 and SB9 to connect it to the module. See page 33 of the user guide assets.lairdtech.com/.../BL652 Dev Kit User Guide.pdf

RE: BL652 EVK Crystal Problem

shewan — Fri, 13 Apr 2018 09:58:03 GMT

BL652 EVK has a 32KHz crystal on board, but it is not connected by default. You will need to bridge SB9 and SB8 to connect it to the module. See the user guide (page 33) here: assets.lairdtech.com/.../BL652 Dev Kit User Guide.pdf

RE: BL652 EVK Crystal Problem

Stian Røed Hafskjold — Fri, 13 Apr 2018 09:02:36 GMT

Ok, I'm glad it worked!

RE: BL652 EVK Crystal Problem

enkavak — Fri, 13 Apr 2018 08:47:17 GMT

Hello Stian,

I fully erased the chip. Now I can debug the code successfully. Thanks a lot.

RE: BL652 EVK Crystal Problem

Stian Røed Hafskjold — Fri, 13 Apr 2018 08:31:32 GMT

Ok, so just to summarize here:

You have a ble_app_uart application with external crystal that runs fine on a pca10040 DK
The ble_app_uart application does not run on the BL652, even if you change to LFRC.
ble_app_blinky does run on the BL652 but debugging is not working.
From the debug window it seems like you are running a bootloader? Since you have code in the 0x7F000 area.

Are you using bootloader? Maybe you flashed the bootloader in an earlier project and that you have never fully erased the chip afterwards? Then the previous values in UICR will redirect to the bootloader region, even though the code you are running now does not use the bootloader.

Try to fully erase the chip. Open a terminal (cmd) and write: nrfjprog --eraseall

What do you mean with "I can not debug the code". Do you get any errors? Are you unable to set breakpoints, or does it never reach the breakpoints you set?

RE: BL652 EVK Crystal Problem

enkavak — Fri, 13 Apr 2018 07:37:40 GMT

Hello Stian

I use the code in the below path.

"nRF5_SDK\examples\peripheral\blinky\pca10040\s132\ses"

When I use "Build and Run", the LEDs are blinking. However, When I use "Build and Debug", I can not debug the code and LEDs are not blinking.

RE: BL652 EVK Crystal Problem

Stian Røed Hafskjold — Fri, 13 Apr 2018 07:30:18 GMT

Then I suspect there's something else going on. Have you tried flashing the blinky example which does not use softdevice? Just to see if it the HW is actually working.

Sorry, didn't mean to debug, just check if the code is not hardfaulting or something.

RE: BL652 EVK Crystal Problem

enkavak — Fri, 13 Apr 2018 07:25:29 GMT

Hello, picben

I set a breakpoint in the main but nothing has changed. I can not debug the code.

I have attached my compiled hex file. How will you debug the code by using hex file?

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_pca10040e_5F00_s112.hex

RE: BL652 EVK Crystal Problem

Stian Røed Hafskjold — Fri, 13 Apr 2018 07:16:36 GMT

Are you not able to set a breakpoint in top of main? You should be able to debug the code even with the wrong LF clock settings. The LF clock is not started until softdevice init.

Maybe you can post your hex file here. Then I can try to debug it and see if it hardfaults.

RE: BL652 EVK Crystal Problem

enkavak — Fri, 13 Apr 2018 05:48:30 GMT

Hello, picben.

LED blinking is not the case since the flashed code is crashes somewhere. If there is another problem, then Why I can not debug the code, step by step?

I think that I have the crystal configuration problem.

Are you using the same SDK and application with me?

I downloaded the "nRF5_SDK_15.0.0_a53641a" and trying to use "ble_app_uart_pca10040_s132” application.

In addition to all, I am using segger embedded studio

Best Regards

RE: BL652 EVK Crystal Problem

picben — Wed, 11 Apr 2018 14:57:27 GMT

Alright, it doesn't look like a clock configuration problem then, I am using the same configuration on a BL652 right now and it's working fine (it's on a custom PCB though, not on the evaluation kit).

I was going to suggest to make sure the SoftDevice is flashed along with the application but looking at your screenshot I think it's the case.

I suggest that you check how the buttons and LEDs pins are mapped on your Evaluation board (SIO_13 to SIO_20 of the BL652) and make sure nothing will go wrong if the application tries to access them maybe.

RE: BL652 EVK Crystal Problem

enkavak — Wed, 11 Apr 2018 14:19:21 GMT

Hello,

I have changed the accuracy to 250ppm and even 500ppm, but nothing has changes. still I can not debug the code.

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

RE: BL652 EVK Crystal Problem

picben — Wed, 11 Apr 2018 14:01:08 GMT

Hi,

The ble_app_uart example from the SDK calls the nrf_sdh_enable_request library function to enable the SoftDevice. This function gets the clock configuration from the sdk_config.h file. Have you tried changing the configuration of the clock directly in the sdk_config.h file ? A cleaner way, if you don't want to modify SDK files directly would be to add a app_config.h in the project and add the USE_APP_CONFIG preprocessor symbol in the compiler options. You then just re-define the options you want in the app_config.h file (in your case NRF_SDH_CLOCK_LF_SRC, NRF_SDH_CLOCK_LF_RC_CTIV, NRF_SDH_CLOCK_LF_RC_TEMP_CTIV and NRF_SDH_CLOCK_LF_ACCURACY). You must set the accuracy to 250ppm (or even 500ppm, according to nRF52832 errata #146) to get a stable BLE connection with the internal RC.

Another thing that you might want to check is the mapping of all I/O used by the ble_app_uart example on your board. I think the UART pins mapping is the same between the nRF52 DK and the BL652 EVK but I'm not so sure about the buttons and LEDs.