<?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>nRF54L15 DK ChannelSounding HCI Command</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126613/nrf54l15-dk-channelsounding-hci-command</link><description>Hello, 
 
 I am developing Channel Sounding related features using nRF Connect SDK (NCS) v3.1.1 and the nRF54L15 Development Kit (DK) , based on Nordic’s official hci_uart sample. I found that the default sample does not support sending Channel Sounding</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 Jan 2026 13:34:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126613/nrf54l15-dk-channelsounding-hci-command" /><item><title>RE: nRF54L15 DK ChannelSounding HCI Command</title><link>https://devzone.nordicsemi.com/thread/559166?ContentTypeID=1</link><pubDate>Tue, 20 Jan 2026 13:34:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:51779687-da1b-483c-b40b-21873d27fe97</guid><dc:creator>Lee1823</dc:creator><description>&lt;p&gt;I would like to express my sincere gratitude for your helpful responses and guidance. By following your recommended steps in order, I have successfully resolved the issue and can now send &lt;strong&gt;Channel Sounding-related HCI commands&lt;/strong&gt; normally without encountering errors.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 DK ChannelSounding HCI Command</title><link>https://devzone.nordicsemi.com/thread/559133?ContentTypeID=1</link><pubDate>Tue, 20 Jan 2026 09:54:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15c0cd86-1fba-4584-8e2e-64f4e3996c6f</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;First you need to enable channel sounding in the controller by setting&amp;nbsp;CONFIG_BT_CTLR_CHANNEL_SOUNDING=y.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Enabling the controller alone isn’t sufficient – the host side must also advertise that it supports Channel Sounding, or the controller will refuse certain CS commands.&amp;nbsp;So you also need to&amp;nbsp;configure&amp;nbsp;CONFIG_BT_CHANNEL_SOUNDING=y on the host to set the channel sounding feature during initialization. Note: If you are using an external host, then you may need to implement the&amp;nbsp;HCI command “LE Set Host Feature” for the Channel Sounding host support bit, this is automatically done for zephyr host when using&amp;nbsp;&amp;nbsp;&lt;span&gt;CONFIG_BT_CHANNEL_SOUNDING=y.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Bluetooth Core Specification states that the host must enable the Channel Sounding Host Support bit before using related commands. If the host issues a CS capability request while that bit is 0, the controller shall respond with Command Disallowed. This design is similar to other features (e.g. LE Privacy, LE Extended Advertising) where the host must opt-in via an HCI command.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kenneth&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>