<?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 SW-LL peripheral: link becomes unresponsive after MTU exchange when host is a Windows 10/11 BLE central</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128142/nrf54l15-dk-sw-ll-peripheral-link-becomes-unresponsive-after-mtu-exchange-when-host-is-a-windows-10-11-ble-central</link><description>Hi, 
 
 I&amp;#39;m running into what looks like a software link-layer issue on the nRF54L15-DK that I&amp;#39;d like a second pair of eyes on. The same firmware works end-to-end with iOS / Android centrals but consistently fails post-MTU with Windows 10/11 centrals</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 10:43:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128142/nrf54l15-dk-sw-ll-peripheral-link-becomes-unresponsive-after-mtu-exchange-when-host-is-a-windows-10-11-ble-central" /></channel></rss>