<?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>Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/88274/custom-nrf5340-board-in-ncs</link><description>Last year i asked about a custom nRF5340 board when using NCS V1.7.0 and the comment was to just copy the entire nRF5340DK into my custom board folder and modify the names to match my board. 
 With V1.9.1 and VSC with the option to &amp;quot;Create a New Board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 Oct 2023 14:23:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/88274/custom-nrf5340-board-in-ncs" /><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/451768?ContentTypeID=1</link><pubDate>Mon, 23 Oct 2023 14:23:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c2e1296-d8eb-41c2-a65b-bc85a24d738f</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hello Conner,&lt;/p&gt;
&lt;p&gt;I assumed this was somewhat taken care of in this case so I haven&amp;#39;t looked into it further unfortunately.&amp;nbsp;As this case is a bit old it might be preferable to create a new one. Though have a look at &lt;a href="https://www.zephyrproject.org/event/nordic-semiconductor-webinar-adding-custom-boards-in-nrf-connect-sdk/"&gt;this webinar&lt;/a&gt; about this very topic coming out on Wednesday. It might be it will answer all your questions about it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/450417?ContentTypeID=1</link><pubDate>Sun, 15 Oct 2023 14:30:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a73f3aa7-2ac3-4b7a-97f0-ce8172a02664</guid><dc:creator>cldelahan</dc:creator><description>&lt;p&gt;I wanted to see if there has been any progress on this? My current solution is still to do what @MartKano recommended below, and simply add an empty block.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;This problem seems to be that after creating a new board of type nrf5340_cpuapp (nonsecure), there is an out-of-the-box issue with the device tree labeling.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/431699?ContentTypeID=1</link><pubDate>Mon, 19 Jun 2023 10:10:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5bdd4352-a2b3-4c46-8df9-9ab04eb2963a</guid><dc:creator>Martdur</dc:creator><description>&lt;p&gt;I&amp;#39;ve got the same compilation error. I add some lines to define sram0_shared and now it complies:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;/ {
	model = &amp;quot;XX&amp;quot;;
	compatible = &amp;quot;XX,XX-v1-0-0&amp;quot;;

    chosen {
        zephyr,sram = &amp;amp;sram0;
        zephyr,flash = &amp;amp;flash0;
        zephyr,code-partition = &amp;amp;slot0_partition;
        zephyr,ipc_shm = &amp;amp;sram0_shared; 
    };
	
    reserved-memory {
        #address-cells = &amp;lt;1&amp;gt;;
        #size-cells = &amp;lt;1&amp;gt;;
        ranges;


        //sram0_ns: image_ns@20000000 {
            /* Non-Secure image memory */
        //};
        sram0_shared: memory@20070000 {
            /* SRAM allocated to shared memory */
            reg = &amp;lt;0x20070000 0x10000&amp;gt;;
        };
    };
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Hope that&amp;#39;s helped.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/371426?ContentTypeID=1</link><pubDate>Wed, 08 Jun 2022 13:16:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6aecf93-14a3-40c1-8c9b-72531d829201</guid><dc:creator>Elfving</dc:creator><description>[quote user="WesC"]Sorry for the delay[/quote]
&lt;p&gt;Hehe yeah likewise.&lt;/p&gt;
[quote user="WesC"]&lt;p&gt;but i changed my environment to just use NCS 1.9.1 and Toolchain 1.9.1&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;Gotya. From the log it looks like that didn&amp;#39;t get updated completely.&lt;/p&gt;
[quote user="WesC"]&lt;p&gt;if i make no modifications to the custom generated DTS file it will not compile because there are DT nodes with Aliases that are used in main.c&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;You can for instance run the button example on a custom 52840 board by copying contents of the nrf52840dk dts file. And you can run hello world on a default custom 5340 board. Getting the alias in the&amp;nbsp;nrf5340 dts etc however is a bit more complex,&amp;nbsp;as there are several files that needs to be renamed and modified.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I believe &lt;a href="https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-3-ncs-v1-4-0#h11sk6ks1jkp1figkuq6gxw1m1rctdp0"&gt;this guide by Simon mentions everything you need to know though &lt;/a&gt;(see section 2.2), as well as what the different files are for. I just tried it myself along with the button example, and the build works fine. I haven&amp;#39;t tried it in NCS 2.0 yet though.&lt;/p&gt;
&lt;p&gt;Do the steps mentioned in the guide work for you?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/370996?ContentTypeID=1</link><pubDate>Mon, 06 Jun 2022 18:53:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:938c143c-f5b4-4a77-9707-35dbfbd85425</guid><dc:creator>WesC</dc:creator><description>&lt;p&gt;So I moved to NCS V2.0.0&lt;/p&gt;
&lt;p&gt;I started by creating a new board and locating the board directory outside of NCS.&amp;nbsp; I then added some elements of the nrf5340_cpuapp_common_ns.dts to my Custom5340_cpuapp_ns.dts.&amp;nbsp; I have attached my custom dts for reference.&amp;nbsp; Here is the error I get.&lt;pre class="ui-code" data-mode="text"&gt;Found host-tools: zephyr 0.14.1 (C:/Users/Wes/ncs/toolchains/v2.0.0/opt/zephyr-sdk)
-- Found dtc: C:/Users/Wes/ncs/toolchains/v2.0.0/opt/bin/dtc.exe (found suitable version &amp;quot;1.4.7&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;)
-- Found toolchain: zephyr 0.14.1 (C:/Users/Wes/ncs/toolchains/v2.0.0/opt/zephyr-sdk)
-- Found BOARD.dts: C:/Users/Wes/Documents/Nordic/MyProjects/boards/arm/custom5340_cpuapp_ns/custom5340_cpuapp_ns.dts
-- Found devicetree overlay: c:/Users/Wes/Documents/Nordic/MyProjects/SterlingMed/nrf5340dk_nrf5340_cpuapp_ns.overlay
devicetree error: /ipc/ipc0: undefined node label &amp;#39;sram0_shared&amp;#39;
CMake Error at C:\Users\Wes\ncs\v2.0.0\zephyr\cmake\modules\dts.cmake:213 (message):
  gen_defines.py failed with return code: 1
Call Stack (most recent call first):
  C:\Users\Wes\ncs\v2.0.0\zephyr\cmake\modules\zephyr_default.cmake:121 (include)
  C:\Users\Wes\ncs\v2.0.0\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:51 (include)
  C:\Users\Wes\ncs\v2.0.0\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:76 (include_boilerplate)
  c:\Users\Wes\Documents\Nordic\MyProjects\SterlingMed\build_test\CMakeLists.txt:4 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: &amp;#39;c:\Users\Wes\ncs\toolchains\v2.0.0\opt\bin\cmake.EXE&amp;#39; &amp;#39;-DWEST_PYTHON=c:\Users\Wes\ncs\toolchains\v2.0.0\opt\bin\python.exe&amp;#39; &amp;#39;-Bc:\Users\Wes\Documents\Nordic\MyProjects\SterlingMed\build_test&amp;#39; &amp;#39;-Sc:\Users\Wes\Documents\Nordic\MyProjects\SterlingMed&amp;#39; -GNinja -DBOARD=custom5340_cpuapp_ns -DNCS_TOOLCHAIN_VERSION:STRING=NONE &amp;#39;-DBOARD_ROOT:STRING=c:/Users/Wes/Documents/Nordic/MyProjects;c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution;c:/Users/Wes/ncs/v2.0.0/zephyr/samples/bluetooth/peripheral_hr&amp;#39; -DCONF_FILE:STRING=c:/Users/Wes/Documents/Nordic/MyProjects/SterlingMed/prj.conf -DDTC_OVERLAY_FILE:STRING=c:/Users/Wes/Documents/Nordic/MyProjects/SterlingMed/nrf5340dk_nrf5340_cpuapp_ns.overlay
The terminal process terminated with exit code: 1.&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;my DTS:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;
/dts-v1/;
#include &amp;lt;nordic/nrf5340_cpuappns_qkaa.dtsi&amp;gt;

/ {
	model = &amp;quot;Custom5340_cpuapp_ns&amp;quot;;
	compatible = &amp;quot;wescherry,custom5340-cpuapp-ns&amp;quot;;

	chosen {
		zephyr,console = &amp;amp;uart0;
		zephyr,shell-uart = &amp;amp;uart0;
		zephyr,uart-mcumgr = &amp;amp;uart0;
		zephyr,sram = &amp;amp;sram0;
		zephyr,flash = &amp;amp;flash0;
		zephyr,code-partition = &amp;amp;slot0_ns_partition;
	};
	leds {
		compatible = &amp;quot;gpio-leds&amp;quot;;
		led0: led_0 {
			gpios = &amp;lt;&amp;amp;gpio0 28 GPIO_ACTIVE_LOW&amp;gt;;
			label = &amp;quot;Green LED 0&amp;quot;;
		};
		led1: led_1 {
			gpios = &amp;lt;&amp;amp;gpio0 29 GPIO_ACTIVE_LOW&amp;gt;;
			label = &amp;quot;Green LED 1&amp;quot;;
		};
		led2: led_2 {
			gpios = &amp;lt;&amp;amp;gpio0 30 GPIO_ACTIVE_LOW&amp;gt;;
			label = &amp;quot;Green LED 2&amp;quot;;
		};
		led3: led_3 {
			gpios = &amp;lt;&amp;amp;gpio0 31 GPIO_ACTIVE_LOW&amp;gt;;
			label = &amp;quot;Green LED 3&amp;quot;;
		};
	};

	pwmleds {
		compatible = &amp;quot;pwm-leds&amp;quot;;
		pwm_led0: pwm_led_0 {
			pwms = &amp;lt;&amp;amp;pwm0 0 PWM_MSEC(20) PWM_POLARITY_INVERTED&amp;gt;;
		};
	};

	buttons {
		compatible = &amp;quot;gpio-keys&amp;quot;;
		button0: button_0 {
			gpios = &amp;lt;&amp;amp;gpio0 23 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
			label = &amp;quot;Push button 1&amp;quot;;
		};
		button1: button_1 {
			gpios = &amp;lt;&amp;amp;gpio0 24 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
			label = &amp;quot;Push button 2&amp;quot;;
		};
		button2: button_2 {
			gpios = &amp;lt;&amp;amp;gpio0 8 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
			label = &amp;quot;Push button 3&amp;quot;;
		};
		button3: button_3 {
			gpios = &amp;lt;&amp;amp;gpio0 9 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
			label = &amp;quot;Push button 4&amp;quot;;
		};
	};
	aliases {
		led0 = &amp;amp;led0;
		led1 = &amp;amp;led1;
		led2 = &amp;amp;led2;
		led3 = &amp;amp;led3;
		pwm-led0 = &amp;amp;pwm_led0;
		sw0 = &amp;amp;button0;
		sw1 = &amp;amp;button1;
		sw2 = &amp;amp;button2;
		sw3 = &amp;amp;button3;
		bootloader-led0 = &amp;amp;led0;
	};

};

&amp;amp;gpio0 {
	status = &amp;quot;okay&amp;quot;;
};

&amp;amp;gpio1 {
	status = &amp;quot;okay&amp;quot;;
};

&amp;amp;flash0 {
	partitions {
		compatible = &amp;quot;fixed-partitions&amp;quot;;
		#address-cells = &amp;lt;1&amp;gt;;
		#size-cells = &amp;lt;1&amp;gt;;

		boot_partition: partition@0 {
			label = &amp;quot;mcuboot&amp;quot;;
			reg = &amp;lt;0x0 0x10000&amp;gt;;
		};
		slot0_partition: partition@10000 {
			label = &amp;quot;image-0&amp;quot;;
			reg = &amp;lt;0x10000 0x40000&amp;gt;;
		};
		slot0_ns_partition: partition@50000 {
			label = &amp;quot;image-0-nonsecure&amp;quot;;
			reg = &amp;lt;0x50000 0x30000&amp;gt;;
		};
		slot1_partition: partition@80000 {
			label = &amp;quot;image-1&amp;quot;;
			reg = &amp;lt;0x80000 0x40000&amp;gt;;
		};
		slot1_ns_partition: partition@c0000 {
			label = &amp;quot;image-1-nonsecure&amp;quot;;
			reg = &amp;lt;0xc0000 0x30000&amp;gt;;
		};
		scratch_partition: partition@f0000 {
			label = &amp;quot;image-scratch&amp;quot;;
			reg = &amp;lt;0xf0000 0xa000&amp;gt;;
		};
		storage_partition: partition@fa000 {
			label = &amp;quot;storage&amp;quot;;
			reg = &amp;lt;0xfa000 0x6000&amp;gt;;
		};
	};
};

&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/370692?ContentTypeID=1</link><pubDate>Thu, 02 Jun 2022 12:25:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:45e405c0-c1dd-40e3-8414-c97e4bb71bb5</guid><dc:creator>WesC</dc:creator><description>&lt;p&gt;Sorry for the delay I was working on other things.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So I was working on Main with NCS 1.9.1 toolchain for LE Audio.&lt;/p&gt;
&lt;p&gt;but i changed my environment to just use NCS 1.9.1 and Toolchain 1.9.1&lt;/p&gt;
&lt;p&gt;my custom board directory is created outside of NCS folder&lt;/p&gt;
&lt;p&gt;I was using zephyr/samples/basic/button and created a custom nRF5340_cpuapp_ns board.&lt;/p&gt;
&lt;p&gt;if i make no modifications to the custom generated DTS file it will not compile because there are DT nodes with Aliases that are used in main.c&lt;/p&gt;
&lt;p&gt;if i look at the nRF5340_cpuapp_common.dts and copy elements of that dts into the custom board that have the button nodes and aliases, i get many more error of the type&lt;/p&gt;
&lt;p&gt;C:\Users\Wes\ncs\v1.9.1\zephyr\include\toolchain\gcc.h:61:36: error: static assertion failed: &amp;quot;&amp;quot;&lt;br /&gt; 61 | #define BUILD_ASSERT(EXPR, MSG...) _Static_assert(EXPR, &amp;quot;&amp;quot; MSG)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;also i get this&lt;/p&gt;
&lt;p&gt;CMake Warning at C:\Users\Wes\ncs\v1.9.1\zephyr\cmake\app\boilerplate.cmake:241 (message):&lt;br /&gt; BOARD_ROOT element without a &amp;#39;boards&amp;#39; subdirectory:&lt;/p&gt;
&lt;p&gt;c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution&lt;/p&gt;
&lt;p&gt;Hints:&lt;/p&gt;
&lt;p&gt;- if your board directory is &amp;#39;/foo/bar/boards/&amp;lt;ARCH&amp;gt;/my_board&amp;#39; then add &amp;#39;/foo/bar&amp;#39; to BOARD_ROOT, not the entire board directory&lt;br /&gt; - if in doubt, use absolute paths&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Do i need to modify the boilerplate to look for custom boards in the other directory?&lt;/p&gt;
&lt;p&gt;looking for advice to create a custom board&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/369893?ContentTypeID=1</link><pubDate>Mon, 30 May 2022 07:50:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7313248e-0ba9-4a07-bed6-9f8d6538d7e6</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;&amp;gt;&amp;nbsp;Found Python3: C:/Users/Wes/ncs/v1.9.1/toolchain/opt/bin/python.exe&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;nbsp;Cache files will be written to: C:/Users/Wes/ncs/v1.9.99-dev1/zephyr/.cache&lt;/p&gt;
&lt;p&gt;First of all, it seems to me that you are running the Master branch SDK along with the NCS 1.9.1 toolchain. Is this on purpose?&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;nbsp;BOARD_ROOT element without a &amp;#39;boards&amp;#39; subdirectory&lt;/p&gt;
&lt;p&gt;This also gives the impression that you might have saved the board to another directory, or modified the BOARD_ROOT.&lt;/p&gt;
&lt;p&gt;Are you able to&amp;nbsp;build a basic hello world sample with a new default 5340 board? (ie. nothing added besides what comes with its creation in VSC).&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/369602?ContentTypeID=1</link><pubDate>Wed, 25 May 2022 15:58:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4f69c7a-0a7a-4267-a352-83acf5fed73b</guid><dc:creator>WesC</dc:creator><description>&lt;p&gt;i cannot get it to build.&amp;nbsp; So what i did was create a new board and selsct the nRF5340_cpuapp_ns as the base.&amp;nbsp; I then copied what i thought i would need from the nRF5340_cpuapp_common.dts into my test5340.dts.&amp;nbsp; when i compile i get the following error about a DTS error with sram0_sherd&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;west build --build-dir c:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution\build c:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution --pristine --board test5340_ns -- -DNCS_TOOLCHAIN_VERSION:STRING=&amp;quot;NONE&amp;quot; -DBOARD_ROOT:STRING=&amp;quot;c:/Users/Wes/Documents/Nordic/MyProjects;c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution;c:/Users/Wes/Documents/Nordic/MyProjects/Blog_LowPower;c:/Users/Wes/ncs/v1.9.1/nrf/applications/asset_tracker_v2&amp;quot; -DCONF_FILE:STRING=&amp;quot;c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution/prj.conf&amp;quot;

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution
-- Found Python3: C:/Users/Wes/ncs/v1.9.1/toolchain/opt/bin/python.exe (found suitable exact version &amp;quot;3.8.2&amp;quot;) found components: Interpreter 
-- Cache files will be written to: C:/Users/Wes/ncs/v1.9.99-dev1/zephyr/.cache
-- Zephyr version: 3.0.99 (C:/Users/Wes/ncs/v1.9.99-dev1/zephyr)
-- Found west (found suitable version &amp;quot;0.12.0&amp;quot;, minimum required is &amp;quot;0.7.1&amp;quot;)
CMake Warning at C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\cmake\modules\boards.cmake:85 (message):
  BOARD_ROOT element without a &amp;#39;boards&amp;#39; subdirectory:

  c:/Users/Wes/Documents/Nordic/MyProjects

  Hints:

    - if your board directory is &amp;#39;/foo/bar/boards/&amp;lt;ARCH&amp;gt;/my_board&amp;#39; then add &amp;#39;/foo/bar&amp;#39; to BOARD_ROOT, not the entire board directory
    - if in doubt, use absolute paths
Call Stack (most recent call first):
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\cmake\modules\zephyr_default.cmake:121 (include)
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:45 (include)
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:70 (include_boilerplate)
  c:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution\build\CMakeLists.txt:4 (find_package)


-- Board: test5340_ns
-- Found dtc: C:/Users/Wes/ncs/v1.9.1/toolchain/opt/bin/dtc.exe (found suitable version &amp;quot;1.4.7&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;)
-- Found toolchain: gnuarmemb (c:/Users/Wes/ncs/v1.9.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution/boards/arm/test5340_ns/test5340_ns.dts
devicetree error: /soc/peripheral@40000000/ipc0: undefined node label &amp;#39;sram0_shared&amp;#39;
CMake Error at C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\cmake\modules\dts.cmake:212 (message):
  gen_defines.py failed with return code: 1
Call Stack (most recent call first):
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\cmake\modules\zephyr_default.cmake:121 (include)
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:45 (include)
  C:\Users\Wes\ncs\v1.9.99-dev1\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:70 (include_boilerplate)
  c:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution\build\CMakeLists.txt:4 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: &amp;#39;c:\Users\Wes\ncs\v1.9.1\toolchain\opt\bin\cmake.EXE&amp;#39; &amp;#39;-DWEST_PYTHON=c:\Users\Wes\ncs\v1.9.1\toolchain\opt\bin\python.exe&amp;#39; &amp;#39;-Bc:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution\build&amp;#39; &amp;#39;-Sc:\Users\Wes\Documents\Nordic\MyProjects\fund_less2_exer2_solution&amp;#39; -GNinja -DBOARD=test5340_ns -DNCS_TOOLCHAIN_VERSION:STRING=NONE &amp;#39;-DBOARD_ROOT:STRING=c:/Users/Wes/Documents/Nordic/MyProjects;c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution;c:/Users/Wes/Documents/Nordic/MyProjects/Blog_LowPower;c:/Users/Wes/ncs/v1.9.1/nrf/applications/asset_tracker_v2&amp;#39; -DCONF_FILE:STRING=c:/Users/Wes/Documents/Nordic/MyProjects/fund_less2_exer2_solution/prj.conf
The terminal process terminated with exit code: 1.&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom nRF5340 Board in NCS</title><link>https://devzone.nordicsemi.com/thread/369582?ContentTypeID=1</link><pubDate>Wed, 25 May 2022 14:31:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26158384-491d-42c9-9281-87c211bec2cb</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hey Wes,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately, I will have to get back to you next week.&lt;/p&gt;
[quote user=""] I have tried using VSC with the nRF5340 and have been unsuccessful[/quote]
&lt;p&gt;What issues are you running into? Is bt_ready() not &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/80550/custom-board-ncs/334200#334200"&gt;returning like in this case&lt;/a&gt;, or are you not able to build a&amp;nbsp;project with a custom board?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>