<?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 used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125470/nrf54l15-dk-used-with-bluez-connecting-to-other-peripheral-ble-devices-automatic-disconnection-after-connection</link><description>After using the official example hci_uart with the nRF54L15-DK, it is configured as an HCI controller. I used bluetoothctl commands like scan on and connect to scan for peripheral devices (dual-mode Bluetooth headphones and a BLE debug assistant in peripheral</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Nov 2025 14:44:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125470/nrf54l15-dk-used-with-bluez-connecting-to-other-peripheral-ble-devices-automatic-disconnection-after-connection" /><item><title>RE: nRF54L15-DK used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/thread/553843?ContentTypeID=1</link><pubDate>Mon, 10 Nov 2025 14:44:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75cc89c1-76d7-42c0-944c-5566888b74d9</guid><dc:creator>JONATHAN LL</dc:creator><description>&lt;p&gt;Happy to help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15-DK used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/thread/553815?ContentTypeID=1</link><pubDate>Mon, 10 Nov 2025 13:00:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e0e9ca4-880c-47be-939a-93021c4f4902</guid><dc:creator>Tinao</dc:creator><description>&lt;p&gt;Right, thank you for your response.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15-DK used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/thread/553814?ContentTypeID=1</link><pubDate>Mon, 10 Nov 2025 12:48:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92426190-7732-4a18-8e43-d06b31d3db59</guid><dc:creator>JONATHAN LL</dc:creator><description>[quote user="Tinao"] Do I need to modify the board hardware before attaching the attenuator externally, or can I connect it directly to the SMA structure?[/quote]
&lt;p&gt;You dont need to do any other modifications to the Kit, if you have something that can connect directly to the SWF connector then that is fine.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;We use one of these SWF connectors &lt;a href="https://mou.sr/3JVISeN"&gt;MM8130-2600RA2&lt;/a&gt;, so if you find a connector\adapter for that then that is fine.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15-DK used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/thread/553757?ContentTypeID=1</link><pubDate>Mon, 10 Nov 2025 03:34:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:985842c1-d80c-4d9d-bc15-1bfd11db862c</guid><dc:creator>Tinao</dc:creator><description>&lt;p&gt;Thank you very much for your response. I&amp;#39;ve also tried other approaches. When I use another nRF54L15-DK as the BLE peripheral, it maintains a stable connection. I suspect the initial unstable connection might have occurred because the tool didn&amp;#39;t exchange data after establishing the connection, causing it to be deemed useless and subsequently disconnected. I&amp;#39;m using NCS version 3.1.1. However, I&amp;#39;d like to consult you on another issue: if I want to change the PHY channel during the connection process&amp;mdash;such as switching between PHY Coded S2 or S8&amp;mdash;I&amp;#39;ve found that attempting to negotiate this change via HCI commands doesn&amp;#39;t always succeed. I suspect this is due to RSSI. I plan to attach an external attenuator via the SMA port to adjust the RSSI value and improve the success rate of changing PHY Coded S2/S8. Do I need to modify the board hardware before attaching the attenuator externally, or can I connect it directly to the SMA structure?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15-DK used with BlueZ, connecting to other peripheral BLE devices, automatic disconnection after connection</title><link>https://devzone.nordicsemi.com/thread/553728?ContentTypeID=1</link><pubDate>Sat, 08 Nov 2025 01:43:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3bd15ea6-c86f-44d6-b515-4d96b73f0a70</guid><dc:creator>JONATHAN LL</dc:creator><description>[quote user=""]However, when I use nRF Connect for mobile as the host device to connect to the nRF54L15-DK, the connection remains stable. Why is that?[/quote]
&lt;p&gt;Do you have to option to test on another device? Could be that the computers BLE and the DK maybe has some issues. So if you can test on another computer or with another external BLE device on the computer to see if issue presist?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;What version of NCS are you using?&lt;br /&gt;&lt;br /&gt;Have you tested another sample also, to see if it also has the same issue?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>