<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104665/ncs-zephyr-logging-and-nrfx-logging-conflict</link><description>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&amp;#39;t work because of the relative paths in CMakefiles. 
 set(COMMON_PATH ${CMAKE_CURRENT_LIST_DIR} /../../../common ) include(${COMMON_PATH</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Oct 2023 20:04:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104665/ncs-zephyr-logging-and-nrfx-logging-conflict" /><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/451139?ContentTypeID=1</link><pubDate>Wed, 18 Oct 2023 20:04:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50d7cc32-ba3f-43c2-8dc7-4b6ac1f173db</guid><dc:creator>lvh831</dc:creator><description>&lt;p&gt;Thank you so much for the links to the document. This explains a lot.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/451039?ContentTypeID=1</link><pubDate>Wed, 18 Oct 2023 11:04:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0aefccea-885d-428c-9b45-bde7378f6da7</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;You can see the peripherals which are enabled by default by their node having&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; status = &amp;quot;okay&amp;quot;;&lt;/p&gt;
&lt;p&gt;in the board files:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts"&gt;https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;spi1 {
	status = &amp;quot;disabled&amp;quot;;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/intro-input-output.html#input-files"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/intro-input-output.html#input-files&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/howtos.html#set-devicetree-overlays"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/howtos.html#set-devicetree-overlays&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/450921?ContentTypeID=1</link><pubDate>Tue, 17 Oct 2023 22:50:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7bfbde90-611f-4617-8252-0ddb5eb997c0</guid><dc:creator>lvh831</dc:creator><description>&lt;p&gt;Hi Oivind,&lt;/p&gt;
&lt;p&gt;Could you please elaborate on how to check or disable the peripheral&amp;#39;s node in the devicetree to stop Zephyr from &lt;span&gt;initializing the peripheral&lt;/span&gt;? Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/450519?ContentTypeID=1</link><pubDate>Mon, 16 Oct 2023 11:10:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89a7db7b-1ef9-4d22-895e-6654791204da</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;My pleasure!&lt;/p&gt;
&lt;p&gt;If you are having issues initializing a peripheral using the nrfx api, make sure the peripheral&amp;#39;s node is disabled in the devicetree. This is to stop Zephyr from initializing the peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/450389?ContentTypeID=1</link><pubDate>Fri, 13 Oct 2023 20:21:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b186138b-57db-4dd7-b66b-a8873c583db3</guid><dc:creator>lvh831</dc:creator><description>&lt;p&gt;Wow! that&amp;#39;s so simple and clean. Thank you so much. I wish Nordic zephyr academic (&lt;span&gt;nRF Connect SDK Fundamentals)&amp;nbsp;&lt;/span&gt;includes some examples using nrfx (from nordic) instead of generic drivers from zephyr. Thanks again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs zephyr logging and nrfx logging conflict</title><link>https://devzone.nordicsemi.com/thread/450341?ContentTypeID=1</link><pubDate>Fri, 13 Oct 2023 14:30:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:749dcfc6-ebaf-4876-8563-20db9a4b9d21</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There should be no need to move your project to use the nrfx libraries, and Zephyr already defines NRFX_LOG as LOG: &lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/v3.3.99-ncs1-1/modules/hal_nordic/nrfx/nrfx_log.h"&gt;https://github.com/nrfconnect/sdk-zephyr/blob/v3.3.99-ncs1-1/modules/hal_nordic/nrfx/nrfx_log.h&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To use nrfx libraries just include the header file for the driver and add the config to enable the peripheral.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; #include &amp;lt;nrfx_spim.h&amp;gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a little hard to say why your current setup is not working, since I don&amp;#39;t know exactly what you have changed. Are you using a custom logging implementation?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>