<?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>nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101390/nrf5340-ble-full-stack-in-network-core</link><description>hello there was a problem configuring the project. 
 i want build uart central, peripheral project with rpc_host. 
 
 The uart peripheral project built fine with -DCONFIG_BT_RPC_STACK=y, but the uart central project failed to build even with DCONFIG_BT_RPC_STACK</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 18 Apr 2024 08:49:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101390/nrf5340-ble-full-stack-in-network-core" /><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/479364?ContentTypeID=1</link><pubDate>Thu, 18 Apr 2024 08:49:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db213319-3b11-4473-8d0e-5e905b3997ec</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;There are two PRs which should resolve this issue -&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/13837"&gt;PR #13837&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/14063"&gt;PR #14063&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/441021?ContentTypeID=1</link><pubDate>Fri, 11 Aug 2023 20:37:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca026779-008b-4833-8b32-0d2d4965f1ba</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Could you please try to remove (or comment out) configuration options shown below?&lt;br /&gt;-&amp;nbsp;remove (or comment out) &amp;#39;CONFIG_BT_DEVICE_APPEARANCE=833&amp;#39; in samples/bluetooth/rpc_host/prj.conf&lt;br /&gt;-&amp;nbsp;remove (or comment out) &amp;#39;CONFIG_BT_DEBUG_LOG=y&amp;#39; in samples/bluetooth/central_uart/child_image/rpc_host.conf&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/438815?ContentTypeID=1</link><pubDate>Fri, 28 Jul 2023 17:12:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bbeb0280-53fe-4bbc-836a-ffb02abd75a2</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;We are still looking into your problem.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Thank you for your patience.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/437335?ContentTypeID=1</link><pubDate>Wed, 19 Jul 2023 15:01:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c26580c-b72e-4b3c-acc5-8a84e6761d1a</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;To provide a short update, we are looking into your problem. I am expecting to get back to you by the end of next week.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/435421?ContentTypeID=1</link><pubDate>Mon, 10 Jul 2023 08:55:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2913dab-8ad0-48fa-aa0d-f394af58de21</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;I have reported the issue internally. I will get back to you when I get new information.&lt;br /&gt;&lt;br /&gt;Please note that due to vacations and reduced staffing, getting the reply might be delayed. Thank you for your patience and understanding.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/435069?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2023 16:50:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd286091-4c79-4848-953a-acb159f0df15</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;I have tested central_uart sample (building for nrf5340dk_nrf5340_cpuapp) from VS Code with additional Cmake argument&amp;nbsp;&lt;span&gt;-DCONFIG_BT_RPC_STACK=y. I have successfully reproduced the issue with different rpc_host.conf configurations. We will discuss this internally. I will get back to you when I get new information related to your problem.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434563?ContentTypeID=1</link><pubDate>Wed, 05 Jul 2023 01:49:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2447716f-ffc7-449c-907f-1d9771a1a5eb</guid><dc:creator>quae</dc:creator><description>&lt;p&gt;hello dejans.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;i add CONFIG_BT_PERIPHERAL=n&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_BT_PERIPHERAL=n
# Enable the UART driver
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_UARTE0=y
CONFIG_SERIAL=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

# Enable the BLE stack with GATT Client configuration
CONFIG_BT=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y

# Enable the BLE modules from NCS
CONFIG_BT_NUS_CLIENT=y
CONFIG_BT_SCAN=y
CONFIG_BT_SCAN_FILTER_ENABLE=y
CONFIG_BT_SCAN_UUID_CNT=1
CONFIG_BT_GATT_DM=y
CONFIG_HEAP_MEM_POOL_SIZE=2048

# This example requires more workqueue stack
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# Enable bonding
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

# Config logger
# CONFIG_LOG=y
# CONFIG_USE_SEGGER_RTT=y
# CONFIG_LOG_BACKEND_RTT=y
# CONFIG_LOG_BACKEND_UART=n
# CONFIG_LOG_PRINTK=n

# CONFIG_ASSERT=y
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;it compiled well.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;but run my application&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;ble central device print this log infinitely.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;it seem like ble central function not working&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434415?ContentTypeID=1</link><pubDate>Tue, 04 Jul 2023 10:19:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e0f5b2cb-97de-4b67-bbdd-73bc3b476cf2</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;In my tests, I have seen the same error as you if I omit &lt;span&gt;CONFIG_BT_PERIPHERAL=n.&amp;nbsp;&lt;/span&gt;It seems that in your previous configuration (based on my previous reply), you forgot to include CONFIG_BT_PERIPHERAL=n.&amp;nbsp;&lt;br /&gt;Could you include this configuration option and try building again? Do you get the same result after programming the device?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434356?ContentTypeID=1</link><pubDate>Tue, 04 Jul 2023 07:32:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1df6f6af-4d77-4499-bf5e-db179603aef7</guid><dc:creator>quae</dc:creator><description>&lt;p&gt;i&amp;nbsp;tried another way.&lt;/p&gt;
&lt;p&gt;this is my prj.conf.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_BT=y
CONFIG_BT_PERIPHERAL=n
CONFIG_BT_CENTRAL=y
CONFIG_BT_OBSERVER=y
CONFIG_BT_DEVICE_NAME=&amp;quot;Zephyr&amp;quot;
CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_GATT_DM=y
CONFIG_HEAP_MEM_POOL_SIZE=2048
# CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_GATT_DM_DATA_PRINT=y
CONFIG_SETTINGS=y
CONFIG_BT_SETTINGS=y
CONFIG_NRF_RPC_THREAD_STACK_SIZE=2048
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;it is compiled well.&lt;/p&gt;
&lt;p&gt;When I run an application, it starts infinitely.&lt;/p&gt;
&lt;p&gt;ble central not working.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;this is my ble central logs&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;Starting nRF RPC bluetooth host&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;br /&gt;*** Booting Zephyr OS build v3.2.99-ncs2 ***&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434350?ContentTypeID=1</link><pubDate>Tue, 04 Jul 2023 07:03:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6704c5a6-43a9-4a07-85bd-ebd3055560fe</guid><dc:creator>quae</dc:creator><description>&lt;p&gt;hello dejans build failed&lt;/p&gt;
&lt;p&gt;this is my prj.conf child_image/rpc_host.conf.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;# Enable the UART driver
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_UARTE0=y
CONFIG_SERIAL=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

# Enable the BLE stack with GATT Client configuration
CONFIG_BT=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y

# Enable the BLE modules from NCS
CONFIG_BT_NUS_CLIENT=y
CONFIG_BT_SCAN=y
CONFIG_BT_SCAN_FILTER_ENABLE=y
CONFIG_BT_SCAN_UUID_CNT=1
CONFIG_BT_GATT_DM=y
CONFIG_HEAP_MEM_POOL_SIZE=2048

# This example requires more workqueue stack
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# Enable bonding
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

# Config logger
# CONFIG_LOG=y
# CONFIG_USE_SEGGER_RTT=y
# CONFIG_LOG_BACKEND_RTT=y
# CONFIG_LOG_BACKEND_UART=n
# CONFIG_LOG_PRINTK=n

# CONFIG_ASSERT=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;build failed log&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;warning: BT_MAX_CONN (defined at&lt;br /&gt;C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf\subsys\bluetooth/Kconfig:14,&lt;br /&gt;C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf\subsys\bluetooth\rpc/Kconfig:170,&lt;br /&gt;subsys/bluetooth/Kconfig:115) was assigned the value &amp;#39;1&amp;#39; but got the value &amp;#39;2&amp;#39;. See&lt;br /&gt;&lt;a href="http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BT_MAX_CONN"&gt;docs.zephyrproject.org/.../kconfig.html&lt;/a&gt; and/or look up BT_MAX_CONN in&lt;br /&gt;the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration&lt;br /&gt;Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;warning: Experimental symbol BT_RPC is enabled.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;warning: user value 1 on the int symbol BT_MAX_CONN (defined at C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf\subsys\bluetooth/Kconfig:14, C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf\subsys\bluetooth\rpc/Kconfig:170, subsys/bluetooth/Kconfig:115) ignored due to being outside the active range ([2, 20]) -- falling back on defaults&lt;/p&gt;
&lt;p&gt;error: Aborting due to Kconfig warnings&lt;/p&gt;
&lt;p&gt;Parsing C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/Kconfig&lt;br /&gt;Loaded configuration &amp;#39;C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig&amp;#39;&lt;br /&gt;Merged configuration &amp;#39;C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/samples/bluetooth/rpc_host/prj.conf&amp;#39;&lt;br /&gt;Merged configuration &amp;#39;C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/subsys/partition_manager/partition_manager_enabled.conf&amp;#39;&lt;br /&gt;Merged configuration &amp;#39;C:/Users/jaesun/Desktop/work/NORDIC/ble_full_stack/central_uart/child_image/rpc_host.conf&amp;#39;&lt;br /&gt;CMake Error at C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/cmake/modules/kconfig.cmake:328 (message):&lt;br /&gt; command failed with return code: 1&lt;br /&gt;Call Stack (most recent call first):&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/cmake/modules/kconfig.cmake:29 (include)&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)&lt;br /&gt; CMakeLists.txt:8 (find_package)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;-- Configuring incomplete, errors occurred!&lt;br /&gt;See also &amp;quot;C:/Users/jaesun/Desktop/work/NORDIC/ble_full_stack/central_uart/build/rpc_host/CMakeFiles/CMakeOutput.log&amp;quot;.&lt;br /&gt;See also &amp;quot;C:/Users/jaesun/Desktop/work/NORDIC/ble_full_stack/central_uart/build/rpc_host/CMakeFiles/CMakeError.log&amp;quot;.&lt;br /&gt;CMake Error at C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/cmake/multi_image.cmake:433 (message):&lt;br /&gt; CMake generation for rpc_host failed, aborting. Command: 1&lt;br /&gt;Call Stack (most recent call first):&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/cmake/multi_image.cmake:163 (add_child_image_from_source)&lt;br /&gt; C:/Users/jaesun/Desktop/work/NORDIC/v2.3.0/nrf/samples/CMakeLists.txt:120 (add_child_image)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;-- Configuring incomplete, errors occurred!&lt;br /&gt;See also &amp;quot;C:/Users/jaesun/Desktop/work/NORDIC/ble_full_stack/central_uart/build/CMakeFiles/CMakeOutput.log&amp;quot;.&lt;br /&gt;See also &amp;quot;C:/Users/jaesun/Desktop/work/NORDIC/ble_full_stack/central_uart/build/CMakeFiles/CMakeError.log&amp;quot;.&lt;br /&gt;FAILED: build.ninja &lt;br /&gt;C:\Users\jaesun\Desktop\work\NORDIC\toolchains\v2.3.0\opt\bin\cmake.exe --regenerate-during-build -SC:\Users\jaesun\Desktop\work\NORDIC\ble_full_stack\central_uart -BC:\Users\jaesun\Desktop\work\NORDIC\ble_full_stack\central_uart\build&lt;br /&gt;ninja: error: rebuilding &amp;#39;build.ninja&amp;#39;: subcommand failed&lt;br /&gt;FATAL ERROR: command exited with status 1: &amp;#39;C:\Users\jaesun\Desktop\work\NORDIC\toolchains\v2.3.0\opt\bin\cmake.EXE&amp;#39; --build &amp;#39;c:\Users\jaesun\Desktop\work\NORDIC\ble_full_stack\central_uart\build&amp;#39;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434242?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2023 13:38:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77c33660-116a-443e-92f0-20697768491b</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;I have reproduced your issue with flash overflow.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I have successfully tested central_uart sample in NCS v2.3.0 with argument&amp;nbsp;-DCONFIG_BT_RPC_STACK=y. The solution for me was to copy the content of prj.conf into rpc_host.conf and disable all options related to logging which are found under &amp;quot;# Config logger&amp;quot; in prj.conf (and rpc_host.conf). Could you please provide information if this works for you as well?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 ble full stack in network core</title><link>https://devzone.nordicsemi.com/thread/434004?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 16:43:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:656ba1a1-1775-4e17-87a6-c31356da1460</guid><dc:creator>quae</dc:creator><description>&lt;p&gt;i can&amp;#39;t upload my log.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;An error occurred. Please try again or contact your administrator.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;this message shown&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>