<?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>Issue with connecting to BLE GATT at NRL54L15</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121879/issue-with-connecting-to-ble-gatt-at-nrl54l15</link><description>Dear Team, 
 I have recently acquired NRF54L15 Development Board for evaluation and from Day 1 experiencing issues with BLE. 
 I am running simple Zephyr-based BLE Peripheral test application from NRF Connect SDK samples which advertises simulated Heart</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 May 2025 11:04:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121879/issue-with-connecting-to-ble-gatt-at-nrl54l15" /><item><title>RE: Issue with connecting to BLE GATT at NRL54L15</title><link>https://devzone.nordicsemi.com/thread/537507?ContentTypeID=1</link><pubDate>Fri, 30 May 2025 11:04:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:226e9b04-6742-47cf-8e93-830ab03d1c11</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Alex,&lt;/p&gt;
&lt;p&gt;Since you do not know what is happening in your device or the peer device during the &amp;quot;sluggish&amp;quot; connection, I strongly recommend you to get &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE"&gt;air sniffer log&amp;nbsp;&lt;/a&gt;and also the serial logs from your nrf device to get the context in which there are any issues. With the given information, it is not possible to get a proper debugging direction.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>