Programming External Device wilth Peripheral UART (nRF Connect SDK)

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Mon, 13 Jun 2022 11:24:31 GMT

The solution... use nrf5 SDK instead

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Mon, 13 Jun 2022 11:23:44 GMT

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.

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

Sigurd — Mon, 13 Jun 2022 11:00:59 GMT

[quote user="AntMAN"]It was my (lack of) understanding that the Connect SDK did not require programming the soft device... is this correct?[/quote]

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

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Mon, 13 Jun 2022 10:15:19 GMT

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?

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

Sigurd — Mon, 13 Jun 2022 09:09:46 GMT

[quote user="AntMAN"] 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:[/quote]

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

[quote user="AntMAN"]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.[/quote]

Yes, I agree.

[quote user="AntMAN"]If I run the debug,[/quote]

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

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Mon, 13 Jun 2022 08:59:14 GMT

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.

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Mon, 13 Jun 2022 08:19:11 GMT

If I run the debug, i do get warning messages, but... these are exactly the same as what I see when I run the program on the nRF52DK. The only difference is it doesnt want to run. Everything seems to be set up correclty (as far as I can tell),

The program displays 'problems'upon build:

[{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 124,
	"startColumn": 4,
	"endLineNumber": 124,
	"endColumn": 11
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 154,
	"startColumn": 4,
	"endLineNumber": 154,
	"endColumn": 11
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 171,
	"startColumn": 4,
	"endLineNumber": 171,
	"endColumn": 11
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 217,
	"startColumn": 3,
	"endLineNumber": 217,
	"endColumn": 10
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 247,
	"startColumn": 4,
	"endLineNumber": 247,
	"endColumn": 11
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 270,
	"startColumn": 3,
	"endLineNumber": 270,
	"endColumn": 10
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 275,
	"startColumn": 3,
	"endLineNumber": 275,
	"endColumn": 10
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 286,
	"startColumn": 3,
	"endLineNumber": 286,
	"endColumn": 10
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 405,
	"startColumn": 2,
	"endLineNumber": 405,
	"endColumn": 9
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 469,
	"startColumn": 4,
	"endLineNumber": 469,
	"endColumn": 11
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 594,
	"startColumn": 2,
	"endLineNumber": 594,
	"endColumn": 9
},{
	"resource": "/c:/nordic/myapps/peripheral_uart/src/main.c",
	"owner": "C/C++",
	"code": "54",
	"severity": 8,
	"message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
	"source": "C/C++",
	"startLineNumber": 632,
	"startColumn": 4,
	"endLineNumber": 632,
	"endColumn": 11
},{
	"resource": "/c:/ncs/v2.0.0/zephyr/CMakeLists.txt",
	"owner": "nrf-connect",
	"severity": 4,
	"message": "__ASSERT() statements are globally ENABLED",
	"source": "cmake",
	"startLineNumber": 1803,
	"startColumn": 1,
	"endLineNumber": 1803,
	"endColumn": 2147483647
},{
	"resource": "/c:/ncs/v2.0.0/zephyr/modules/hal_nordic/nrfx/Kconfig",
	"owner": "nrf-connect",
	"severity": 4,
	"message": "NRFX_UARTE0 (defined at C:\\ncs\\v2.0.0\\zephyr\\modules\\hal_nordic\\nrfx\\Kconfig:347,",
	"source": "kconfig",
	"startLineNumber": 347,
	"startColumn": 1,
	"endLineNumber": 347,
	"endColumn": 2147483647
}]

And the debug console displays the following errors:

Error: c:/ncs/toolchains\v2.0.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-nm-no-py.exe failed! statics/global/functions may not be properly classified: Error: spawn c:/ncs/toolchains\v2.0.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-nm-no-py.exe ENOENT
    Expecting `nm` next to `objdump`. If that is not the problem please report this.
Error: objdump failed! statics/globals/functions may not be properly classified: Error: spawn c:/ncs\toolchains\v2.0.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-objdump-no-py.exe ENOENT    ENOENT means program not found. If that is not the issue, please report this problem.Launching gdb-server: "C:\\Program Files\\SEGGER\\JLink\\JLinkGDBServerCL.exe" -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device nRF52832_xxAA -select usb=483019567 -rtos "C:\\Program Files\\SEGGER\\JLink\\GDBServer\\RTOSPlugin_Zephyr.dll"
    Please check TERMINAL tab (gdb-server) for output from C:\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe

Again, the same messages are generated for each build (nRF52 DK & DVK-BL652).

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

Sigurd — Fri, 10 Jun 2022 11:06:33 GMT

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

[quote user="AntMAN"]I am struggling to find out what the CONFIG_BOARD_ENABLE_DCDC option is doing. Could you please explain?[/quote]

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?

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Fri, 10 Jun 2022 11:01:52 GMT

Hi, upon further inspection I can see that the DVK-BL652 does have an external crystal. 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.

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

That being said, I have tried turning off the DCDC mode board option (thereby modifying 'peripheral_uart\BL652_DVK\zephyr\.config'). The result remains unchanged.

I should add: when inspecting SIO_17 & SIO_18, I would expect to see the flashing of LEDS as on the nRF52DK (P0.17 & P0.18). As I am not seeing this, it would infer that the device is not running the program. Would you agree?

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

AntMAN — Fri, 10 Jun 2022 09:35:03 GMT

Hi, thanks for getting back so quickly. Yeah, okay... i think you're right about the extern crystal. But, DCDC components? Not sure what this is, having a look.

RE: Programming External Device wilth Peripheral UART (nRF Connect SDK)

Sigurd — Fri, 10 Jun 2022 09:02:38 GMT

Hi,

I'm thinking either

1) The module does not have external LF crystal. In that case, set this config:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

2) The module does not have DCDC components. In that case, try setting this:

CONFIG_BOARD_ENABLE_DCDC=n