<?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>nfr connect connectivity</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63407/nfr-connect-connectivity</link><description>Hi, 
 We used nRF52840 Dongle to receive BLE peripheral device 240Bytes notification. The connectivity that &amp;quot;Bluttooth low energy&amp;quot; (nRF connect) programmed can received 240Bytes notifications, but &amp;quot;pc-ble-driver-4.1.1\hex\sd_api_v5\connectivity_4.1.1_usb_with_s132_5</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 08 Jan 2021 12:07:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63407/nfr-connect-connectivity" /><item><title>RE: nfr connect connectivity</title><link>https://devzone.nordicsemi.com/thread/288154?ContentTypeID=1</link><pubDate>Fri, 08 Jan 2021 12:07:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee35cb5e-5ebe-4d8c-94d0-7af43e88b0b2</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for sharing!&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nfr connect connectivity</title><link>https://devzone.nordicsemi.com/thread/288144?ContentTypeID=1</link><pubDate>Fri, 08 Jan 2021 11:19:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:adfc12ab-fcc6-43a7-af78-d09bc7af1b7e</guid><dc:creator>jacksong</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;just let someone look here know:&lt;/p&gt;
&lt;p&gt;nRF Connect for Desktop v3.6.0 is equipped with connectivity_4.1.2_1m_with_s132_5.1.0.hex&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;14:12:48.335	Application data folder: C:\Users\Administrator\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
14:13:26.926	Device setup completed
14:13:26.932	Connectivity firmware version: ble-connectivity 4.1.2+Jul-14-2020-05-48-48. SoftDevice API version: 5. Baud rate: 1000000.
14:13:26.973	Opening adapter connected to COM3
14:13:27.944	Successfully opened COM3. Baud rate: 1000000. Flow control: none. Parity: none.
14:13:27.946	Reset performed on adapter COM3
14:13:29.032	Adapter connected to COM3 opened&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nfr connect connectivity</title><link>https://devzone.nordicsemi.com/thread/258630?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 14:15:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03099d02-6ae7-475e-bca5-73642880b02d</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The BLE connectivity firmware currently used by all nRF Connect for Desktop BLE apps should be the one found in connectivity_4.1.1_usb_with_s132_5.1.0_dfu_pkg.zip delivered with &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/v4.1.1/hex/sd_api_v5"&gt;pc-ble-driver v4.1.1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Also, when using the BLE app, it will state in the log what connectivity firmware is used. For the Dongle, this means the corresponding .zip package, as it can only receive firmware using Device Firmware Upgrade (DFU). Note that the connectivity firmware used by nRF Connect (and pc-ble-driver) is a patched version of the serialization example from the nRF5 SDK. Patch files also available from &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/v4.1.1/hex"&gt;pc-ble-driver on github&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>