<?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>Issues on Pairing LESC with Just Works</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99555/issues-on-pairing-lesc-with-just-works</link><description>Hi! I&amp;#39;m using the nRF52-DK development kit to implement secure communications via Bluetooth Low Energy (BLE) on Zephyr. I&amp;#39;m trying to pair an nRF52-DK with my smartphone via LE Secure Connections with Just Works (BLE Security Mode 1 Level 2). However</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 May 2023 11:59:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99555/issues-on-pairing-lesc-with-just-works" /><item><title>RE: Issues on Pairing LESC with Just Works</title><link>https://devzone.nordicsemi.com/thread/424516?ContentTypeID=1</link><pubDate>Tue, 09 May 2023 11:59:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17293c79-f565-42dd-bd87-cd07dd198892</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The LESC pairing procedure is CPU intensive (specifically the&amp;nbsp;Diffie–Hellman key exchange), and this is done in a priority lower than the main thread. When you have a main loop without any sleep, this will consume all available CPU time, and leave no time for lower priority tasks. This is also a bad idea for other reasons, as the CPU will never sleep and the current consumption will be high. You can keep the main loop if you like, but then you need to add a k_sleep() or similar.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>