<?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>Unable to allocate TX context ENOBUFS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96578/unable-to-allocate-tx-context-enobufs</link><description>I am trying to call bt_gatt_notify_cb() from a for loop which occurs within a workqueue thread. 
 The work is submitted periodically through an interrupt call. 
 
 This works just fine while testing on the LightBlue app on an iOS device. However, when</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Feb 2023 13:33:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96578/unable-to-allocate-tx-context-enobufs" /><item><title>RE: Unable to allocate TX context ENOBUFS</title><link>https://devzone.nordicsemi.com/thread/409610?ContentTypeID=1</link><pubDate>Mon, 13 Feb 2023 13:33:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a1765ed4-1da2-44a9-9344-0ffbed71b110</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The only reason you should see these -ENOBUFS error messages should be because the devices transmit faster than the buffers are able to clear on either side. Seeing as you&amp;#39;re not seeing this when using iOS devices (where MTU size is restricted to 184 IIRC) I think the throughput of 244 bytes fill up the buffers quicker than they are emptied. The best way to solve this would be to add a check that there are available buffers before sending the next packet(s). You can try tweaking the parameters as well to see if that helps at all, for example the event length&amp;nbsp; and latency numbers.&lt;/p&gt;
&lt;p&gt;I can also recommend checking out this throughput blog post over at Novel Bits where they do some testing finding the best throughput for a BLE application on nRF52840 devices:&amp;nbsp;&lt;a href="https://novelbits.io/bluetooth-5-speed-maximum-throughput/"&gt;https://novelbits.io/bluetooth-5-speed-maximum-throughput/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>