ncs zephyr logging and nrfx logging conflict

[lvh831]

I want to use some nrfx samples but when I create a copy of it in vscode, it copies to a specified directory and didn't work because of the relative paths in CMakefiles.

set(COMMON_PATH ${CMAKE_CURRENT_LIST_DIR}/../../../common)
include(${COMMON_PATH}/common.cmake)

I started with a working project using a copy sample shell_module. It works fine, but I want to use libraries from nrfx. So I moved to an adjacent directory of nrfx_saadc.

Once my shell_module is in there, I could use nrfx libraries just like other nrfx samples, but my log module doesn't work. nrfx samples use NRFX_LOG* while zephyr use LOG_*.

When I move a project to ncs/v2.4.2/modules/hal/nordic/nrfx/samples/src/nrfx_saadc and added copy few lines to CMakeLists.txt,

if(DEFINED CUSTOM_BOILERPLATE)
include(${CUSTOM_BOILERPLATE})
return()
endif()

set(COMMON_PATH ${CMAKE_CURRENT_LIST_DIR}/../../../common)
include(${COMMON_PATH}/common.cmake)

GET_DEVICE_CONFIG_FILES(${BOARD} ../boards)

I messed up the logging and can't find the conflict.

Do you know how can I debug this? Thanks.

[Øivind]

Hi,

There should be no need to move your project to use the nrfx libraries, and Zephyr already defines NRFX_LOG as LOG: https://github.com/nrfconnect/sdk-zephyr/blob/v3.3.99-ncs1-1/modules/hal_nordic/nrfx/nrfx_log.h

To use nrfx libraries just include the header file for the driver and add the config to enable the peripheral.

For example, to use the nrfx spim driver for spim2, you would enable CONFIG_NRFX_SPIM2=y and include the header file in your code with:

    #include <nrfx_spim.h>

It's a little hard to say why your current setup is not working, since I don't know exactly what you have changed. Are you using a custom logging implementation?

[lvh831]

Wow! that's so simple and clean. Thank you so much. I wish Nordic zephyr academic (nRF Connect SDK Fundamentals) includes some examples using nrfx (from nordic) instead of generic drivers from zephyr. Thanks again.

[Øivind]

My pleasure!

If you are having issues initializing a peripheral using the nrfx api, make sure the peripheral's node is disabled in the devicetree. This is to stop Zephyr from initializing the peripheral.

[lvh831]

Hi Oivind,

Could you please elaborate on how to check or disable the peripheral's node in the devicetree to stop Zephyr from initializing the peripheral? Thanks.

[Øivind]

You can see the peripherals which are enabled by default by their node having

    status = "okay";

in the board files:

https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts

To change this for your project, add an overlay file to the project folder with the same name as your board, for example nrf52840dk_nrf52840.overlay, which disables the node. For example, to disable spi1:

&spi1 {
	status = "disabled";
};

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/intro-input-output.html#input-files

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/howtos.html#set-devicetree-overlays