<?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>pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/53375/pc-ble-driver-connectivity-increase-mtu-size</link><description>Looks like pc-ble-driver connectivity (hex file) firmware is limited to MTU of 250 via NRF_SDH_BLE_GATT_MAX_MTU_SIZE. We need to use MTU 515 to match what is supported by most recent Android mobile devices. What is the simplest way to recompile the connectivity</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 15 Jun 2020 12:55:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/53375/pc-ble-driver-connectivity-increase-mtu-size" /><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/255024?ContentTypeID=1</link><pubDate>Mon, 15 Jun 2020 12:55:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9ebc0fd-ef53-42f1-93fb-37e08c6b562b</guid><dc:creator>benjamin.forest</dc:creator><description>&lt;p&gt;I think it does not works with SDK16. pc-ble-driver-py is stuck to softdevice api 5.&lt;br /&gt;I had to use SDK15.3 and follow more or less this &lt;a href="https://jimmywongiot.com/2020/06/03/how-to-compile-the-ble_connectivity-hex-and-run-with-nrf-connect-desktop/"&gt;link to had a working connectivity firmware&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/253771?ContentTypeID=1</link><pubDate>Mon, 08 Jun 2020 11:41:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d252877b-1257-47b2-920a-ffab68a0d427</guid><dc:creator>benjamin.forest</dc:creator><description>&lt;p&gt;Thanks a lot for your answer, I didn&amp;#39;t saw it. It explains things. But As far as I understood, pre-compiled connectivity firmware is limited to an MTU of 250. Do you confirm ? IIs there a way to contourn this limitation ?&lt;br /&gt;&lt;br /&gt;All the best,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/249248?ContentTypeID=1</link><pubDate>Mon, 11 May 2020 14:58:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f4f2906-d295-4e68-aafc-89901bd345c5</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;pc-ble-driver-py is using&amp;nbsp;&lt;span&gt;SD API v5. SDK 16 connectivity&amp;nbsp;project cannot be used with pc-ble-driver-py .use e.g. &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py/blob/master/pc_ble_driver_py/examples/serial_port_enum.py"&gt;serial_port_enum.py&lt;/a&gt;&amp;nbsp;to flash the pre-compiled connectiviy firmware.&lt;/span&gt;&lt;span&gt;E.g.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="text"&gt;python serial_port_enum.py NRF52 COM42&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/248666?ContentTypeID=1</link><pubDate>Thu, 07 May 2020 09:30:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2bcf70b4-7cbd-41f4-994d-fd59cc53d3d3</guid><dc:creator>CheMax</dc:creator><description>&lt;p&gt;for SDK16 version is this patch not relevant anymore? or is it still necessary to apply it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/248648?ContentTypeID=1</link><pubDate>Thu, 07 May 2020 08:49:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4881a56d-6de8-4412-b856-0eeb176592cc</guid><dc:creator>benjamin.forest</dc:creator><description>&lt;p&gt;Hi, thanks for this answer.&lt;/p&gt;
&lt;p&gt;I have the exact same problem using SDK 16, and pca10040 devkit. I tried to compile connectivity uart example, then ran it without success (ie pc-ble-driver-py says Failed to open. Error code: NRF_ERROR_TIMEOUT), Am I missing something ? Is there still a patch or something to apply on this sdk version ? Launching it with debugger it did not crash with error about ram section for soft device too small, is this normal ?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;All the best,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/217008?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2019 08:59:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f0639c5f-7852-4742-9f0f-1e55755c3fca</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;For pc-ble-driver&amp;nbsp;I believe&amp;nbsp;you should actually use the&amp;nbsp;&lt;span&gt;pca10056\ser_s140_usb_hci project, also for the dongle. The firmware(after being patched) has this&amp;nbsp;BOARD_DETECTION&amp;nbsp;functionality were it&amp;#39;s using the qspi to detect if it&amp;#39;s running on the DK or the dongle automatically.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/215998?ContentTypeID=1</link><pubDate>Mon, 21 Oct 2019 15:33:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f485734d-c2aa-4d71-9cac-8fc9c1c81765</guid><dc:creator>figsys100</dc:creator><description>&lt;p&gt;Thanks! I am trying to build pca10059\ser_s140_usb_hci\ses (USB Dongle) with no changes in the patched SDK and am encountering the following error:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;Building ‘ble_connectivity_s140_usb_hci_pca10059’ from solution ‘ble_connectivity_s140_usb_hci_pca10059’ in configuration ‘Debug’

..

Compiling ‘main.c’
main.c
&amp;#39;BSP_QSPI_SCK_PIN&amp;#39; undeclared (first use in this function)
in expansion of macro &amp;#39;QSPI_PIN_SCK&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_SCK&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
each undeclared identifier is reported only once for each function it appears in
in expansion of macro &amp;#39;QSPI_PIN_SCK&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_SCK&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
&amp;#39;BSP_QSPI_CSN_PIN&amp;#39; undeclared (first use in this function); did you mean &amp;#39;QSPI_PIN_CSN&amp;#39;?
in expansion of macro &amp;#39;QSPI_PIN_CSN&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_CSN&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
&amp;#39;BSP_QSPI_IO0_PIN&amp;#39; undeclared (first use in this function)
in expansion of macro &amp;#39;QSPI_PIN_IO0&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_IO0&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
&amp;#39;BSP_QSPI_IO1_PIN&amp;#39; undeclared (first use in this function)
in expansion of macro &amp;#39;QSPI_PIN_IO1&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_IO1&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
&amp;#39;BSP_QSPI_IO2_PIN&amp;#39; undeclared (first use in this function)
in expansion of macro &amp;#39;QSPI_PIN_IO2&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_IO2&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
&amp;#39;BSP_QSPI_IO3_PIN&amp;#39; undeclared (first use in this function)
in expansion of macro &amp;#39;QSPI_PIN_IO3&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_PIN_IO3&amp;#39;
in expansion of macro &amp;#39;NRFX_QSPI_DEFAULT_CONFIG&amp;#39;
in expansion of macro &amp;#39;NRF_DRV_QSPI_DEFAULT_CONFIG&amp;#39;
Compiling ‘SEGGER_RTT.c’
Build failed&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;ble_connectivity\pca10056\ser_s140_usb_hci\ses builds fine.&lt;/p&gt;
&lt;p&gt;Have not tried using other compilers.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver connectivity increase MTU size</title><link>https://devzone.nordicsemi.com/thread/215897?ContentTypeID=1</link><pubDate>Mon, 21 Oct 2019 11:39:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85bf8f39-c8c6-47d0-bff8-90206e9e3a9c</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]What is the simplest way to recompile the connectivity with the increased MTU? [/quote]
&lt;p&gt;&amp;nbsp;Download SDK 15.3, apply the patch found &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/master/hex"&gt;here&lt;/a&gt;&amp;nbsp;(nRF5_SDK_15.3.0_connectivity.patch). Then find the project in SDK_folder\examples\connectivity\ble_connectivity, change the value of &lt;span&gt;NRF_SDH_BLE_GATT_MAX_MTU_SIZE in&amp;nbsp;&lt;/span&gt;sdk_config.h, and compile the project.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>