Why can the CGMS routines of nRF connect SDK run on the development board, but not on the circuit board designed by myself, even though the chips of both are exactly the same?

RE: Why can the CGMS routines of nRF connect SDK run on the development board, but not on the circuit board designed by myself, even though the chips of both are exactly the same?

Kc Owen — Wed, 31 Jul 2024 01:20:11 GMT

After I added the following two items to prj.conf, the program did run normally.
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_BOARD_ENABLE_DCDC=n

Thanks Einar Thorsrud

RE: Why can the CGMS routines of nRF connect SDK run on the development board, but not on the circuit board designed by myself, even though the chips of both are exactly the same?

Kc Owen — Wed, 31 Jul 2024 01:01:54 GMT

I also found a problem, that is, the example does not run properly on my board in normal mode, but it runs properly in debug mode

RE: Why can the CGMS routines of nRF connect SDK run on the development board, but not on the circuit board designed by myself, even though the chips of both are exactly the same?

Kc Owen — Wed, 31 Jul 2024 00:50:46 GMT

Thank you for your reply. The circuit board I designed does not use a 32.768 kHz crystal oscillator or DC/DC. The applications I used are CGMS examples of two versions of SDK. I am not sure whether they have DC/DC enabled. I guess they should not, because the examples clearly state that power consumption optimization is not performed. I will focus on checking these two issues.

RE: Why can the CGMS routines of nRF connect SDK run on the development board, but not on the circuit board designed by myself, even though the chips of both are exactly the same?

Einar Thorsrud — Tue, 30 Jul 2024 12:20:39 GMT

Hi,

There are two typical issues when using an example application on a custom board:

Example (or the board files you are using) enables the optional 32.768 kHz crystal, but it is not present on the hardware. Try selecting the LFRC by adding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to your prj.conf.
Example (or the board files you are using) enables the DC/DC, but the board is missing the optional DC/DC inductors. Try disabling by adding CONFIG_BOARD_ENABLE_DCDC=n to your prj.conf.

Note that a difference between the nRF5 SDK and nRF Connect SDK is that while the 32.768 kHz is enabled for the development kits in both SDK variants, the DCDC is not enabled by default in the nRF5 SDK.