<?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>Identical code to Peripheral HR Coded sample not working in my own project</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/103091/identical-code-to-peripheral-hr-coded-sample-not-working-in-my-own-project</link><description>Hi, 
 I&amp;#39;ve tested the peripheral_hr_coded sample before; using the VSCode extension, I created a new project and selected &amp;quot;nrf/sampls/bluetooth/periphral_hr_coded&amp;quot; as the template, and the code ran as expected. 
 Now, I want to modify the peripheral_hr_coded</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 Aug 2023 08:05:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/103091/identical-code-to-peripheral-hr-coded-sample-not-working-in-my-own-project" /><item><title>RE: Identical code to Peripheral HR Coded sample not working in my own project</title><link>https://devzone.nordicsemi.com/thread/442705?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2023 08:05:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:079d81b8-b311-4650-b8d2-283ad3dbf38e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Of course. When building BLE applications for the nRF5340, you are building separate&amp;nbsp;FW images for the application core and network core as explained here &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.1/nrf/working_with_nrf/nrf53/nrf5340.html#protocols-and-use-cases"&gt;link&lt;/a&gt;. This happens automatically and is made possible with the SDKs&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.1/nrf/app_dev/multi_image/index.html#multi-image-builds"&gt;Multi-image builds&lt;/a&gt;&amp;nbsp;feature.&amp;nbsp;And since you are building multiple different FW images, there is also a need to be able to change override the default Kconfig symbols for each image individually. This is where the &amp;#39;child_image&amp;#39; folder comes in. In this folder you can place overlays for your child images. Please refer to the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.1/nrf/app_dev/multi_image/index.html#id13"&gt;Image-specific variables&lt;/a&gt;&amp;nbsp;section for more details.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Kconfig symbols in proj.conf file in the root folder&amp;nbsp;will only be applied to the parent FW image (i.e. your application).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Identical code to Peripheral HR Coded sample not working in my own project</title><link>https://devzone.nordicsemi.com/thread/442699?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2023 07:39:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93deecd7-4ea2-4d46-b472-85a455f8836f</guid><dc:creator>Michael Zeng</dc:creator><description>&lt;p&gt;I see, thank you! Do you mind explaining the distinction/relationship between proj.conf in the root folder, the hci_rpmsg.conf in the child_image folder, and Kconfig?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Identical code to Peripheral HR Coded sample not working in my own project</title><link>https://devzone.nordicsemi.com/thread/442686?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2023 06:55:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aedef3cd-1cb3-4fae-a487-73fe0b218617</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Michael,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;W: opcode 0x2036 status 0x01&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;This warning message means that support for the extended advertising feature has not been enabled in the Bluetooth controller running on the network core (hci_rpmsg).&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Opcode 0x2036 corresponds to &amp;#39;BT_HCI_OP_LE_SET_EXT_ADV_PARAM&amp;#39;, and status 0x1 means the opcode was not recognized by the controller. Except from BT core spec., vol 1, part F:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span&gt;&lt;strong&gt;2.1 UNKNOWN HCI COMMAND (0x01)&lt;/strong&gt;&lt;br /&gt;The Unknown HCI Command error code indicates that the Controller does not&lt;br /&gt;understand the HCI Command packet opcode that the Host sent. The opcode&lt;br /&gt;given might not correspond to any of the opcodes specified in this document,&lt;br /&gt;or any vendor-specific opcodes, or the command may have not been&lt;br /&gt;implemented.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;To fix this, copy the &amp;#39;child_image&amp;#39; folder from the peripheral_hr_code sample to your project source directory and do a pristine build. The child image folder contains the&amp;nbsp;hci_rpmsg.conf overlay which will be applied to your controller build and enable support for advertising extensions.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Vidar&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>