<?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>Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/94486/switch-between-bluetooth-mesh-and-constant-carrier</link><description>Hi, 
 As part of our production test, we perform a constant carrier test (from Bluetooth DTM sample). But this test is performed after the casing is put on, which means that we are unable to reprogram the device and this test will be part of the application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Mar 2023 10:14:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/94486/switch-between-bluetooth-mesh-and-constant-carrier" /><item><title>RE: Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/thread/413202?ContentTypeID=1</link><pubDate>Fri, 03 Mar 2023 10:14:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:55bac5b2-1502-4379-8c9e-c82a4609fa35</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="ThierryH"]&lt;p&gt;Luckily I found this topic because I have the exact same question as Tim. I do understand the idea behind the bt_disable feature. My concern is the MCU family that I&amp;#39;m using from Nordic...&lt;/p&gt;
&lt;p&gt;Our product uses a nRF5340,&lt;/p&gt;[/quote]
&lt;p&gt;bt_disable() is currently not supported on nRF5340. There is a feature request here for it:&amp;nbsp;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/issues/52907"&gt;https://github.com/zephyrproject-rtos/zephyr/issues/52907&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But&amp;nbsp;your use-case might be solved without using&amp;nbsp;&lt;span&gt;bt_disable().&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Please create a new support case for your use-case.&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/support/add"&gt;https://devzone.nordicsemi.com/support/add&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/thread/413015?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2023 12:40:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4603a96f-54fa-41da-a308-5f54da9a0375</guid><dc:creator>ThierryH</dc:creator><description>&lt;p&gt;Hello Sigurd&lt;/p&gt;
&lt;p&gt;Luckily I found this topic because I have the exact same question as Tim. I do understand the idea behind the bt_disable feature. My concern is the MCU family that I&amp;#39;m using from Nordic...&lt;/p&gt;
&lt;p&gt;Our product uses a nRF5340, so it has two cores, one for the application, the second one is the netcore. If I call bt_disable, this should disable the bt stack on the netcore, but how can I call the required functions on the netcore&amp;nbsp;to start a constant carrier test? My production firmware contains two separate projects, one for the appcore and one for the netcore where I start and stop the carrier test with some &amp;quot;events&amp;quot; over shared memory. But when I use the BT Mesh stack, the netcore contains the child image with that stack, so no idea how I should be able to launch the carrier test with the BT Mesh stack already on the netcore part of the nRF5340...&lt;/p&gt;
&lt;p&gt;Thanks in advance for your assistance...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/thread/398803?ContentTypeID=1</link><pubDate>Fri, 02 Dec 2022 15:12:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ec33147-24ed-412a-954d-5f7cd309a0fb</guid><dc:creator>Sigurd</dc:creator><description>[quote user="tim-remoticom"]Do you have an estimate of when&amp;nbsp;the next NCS will come out?&amp;nbsp;[/quote]
&lt;p&gt;~Mid December, there is already a release&amp;nbsp;candidate ready now (v2.2.0-rc1).&lt;/p&gt;
[quote user="tim-remoticom"]Is there something you can recommend I can do now with the current version of NCS?[/quote]
&lt;p&gt;Another option would be to use the radio in&amp;nbsp;a MPSL timeslot.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/mpsl/doc/timeslot.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/mpsl/doc/timeslot.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/tree/main/samples/mpsl/timeslot"&gt;https://github.com/nrfconnect/sdk-nrf/tree/main/samples/mpsl/timeslot&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/mpsl/timeslot/README.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/mpsl/timeslot/README.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/thread/398763?ContentTypeID=1</link><pubDate>Fri, 02 Dec 2022 12:57:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a32e7ba0-2181-4726-8cee-458a92b5707a</guid><dc:creator>tim-remoticom</dc:creator><description>&lt;p&gt;Hi Sigurd,&lt;/p&gt;
&lt;p&gt;Thanks for your reply.&lt;/p&gt;
&lt;p&gt;Great to hear that this&amp;nbsp;feature will be added. Do you have an estimate of when&amp;nbsp;the next NCS will come out?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Due to our tight release schedule,&amp;nbsp;I don&amp;#39;t think I can wait for this release (deliveries in a few weeks). But we will use this in the future.&lt;/p&gt;
&lt;p&gt;Is there something you can recommend I can do now with the current version of NCS?&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Tim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch between Bluetooth mesh and constant carrier</title><link>https://devzone.nordicsemi.com/thread/398749?ContentTypeID=1</link><pubDate>Fri, 02 Dec 2022 12:00:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a948f336-60ba-4dac-87a9-b40ff8d10771</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;For the upcoming NCS v2.2.0 release we have this in the changelog:&lt;/p&gt;
&lt;h4&gt;Bluetooth LE&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Added:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Support for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;&lt;span&gt;hci_driver_close()&lt;/span&gt;&lt;/code&gt;, so&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a title="(in Zephyr Project v3.2.99)" href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/api/gap.html#c.bt_disable"&gt;&lt;code&gt;&lt;span&gt;bt_disable()&lt;/span&gt;&lt;/code&gt;&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;can now be used to disable the SoftDevice Controller.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The Kconfig option&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a title="(in Kconfig reference v&amp;amp;nbsp;)" href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_UNINIT_MPSL_ON_DISABLE"&gt;&lt;code&gt;&lt;span&gt;CONFIG_BT_UNINIT_MPSL_ON_DISABLE&lt;/span&gt;&lt;/code&gt;&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;that, when enabled, uninitializes the MPSL when&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a title="(in Zephyr Project v3.2.99)" href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/api/gap.html#c.bt_disable"&gt;&lt;code&gt;&lt;span&gt;bt_disable()&lt;/span&gt;&lt;/code&gt;&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;is used. This releases all peripherals used by the MPSL.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>