<?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 ATT TX meta</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/107366/unable-to-allocate-att-tx-meta</link><description>Hi, 
 
 custom board with 52832 and st lsm6dsr sensor. Notify data 100 times / second. 
 
 Occasionally I got this warning: 
 [00:00:10.303,985] &amp;lt;wrn&amp;gt; bt_att: Unable to allocate ATT TX meta 
 [00:00:10.303,985] &amp;lt;wrn&amp;gt; bt_gatt: No buffer available to send</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Jan 2024 11:47:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/107366/unable-to-allocate-att-tx-meta" /><item><title>RE: Unable to allocate ATT TX meta</title><link>https://devzone.nordicsemi.com/thread/464365?ContentTypeID=1</link><pubDate>Tue, 16 Jan 2024 11:47:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74b1fc95-642c-48e8-a174-cbd59cc68387</guid><dc:creator>kfcube</dc:creator><description>&lt;p&gt;Hi Susheel, the size is 24 bytes per event. I will check the sample. Thanks a lot.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to allocate ATT TX meta</title><link>https://devzone.nordicsemi.com/thread/464312?ContentTypeID=1</link><pubDate>Tue, 16 Jan 2024 08:23:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f0be8cc-2583-4a6f-a6f0-449e1f21a9f9</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;What is the size of the sensor data you send per event? I think the DATA_LENGTH_MAX can be bigger. Check if you can calibrate some of the configs as compared to the &lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/main/samples/bluetooth/throughput/prj.conf"&gt;throughput sample&lt;/a&gt;&amp;nbsp;where we have configured parameters to send data as fast as possible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to allocate ATT TX meta</title><link>https://devzone.nordicsemi.com/thread/464185?ContentTypeID=1</link><pubDate>Mon, 15 Jan 2024 13:14:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:20c2f468-6ed8-47f2-89bd-c5f440b8c342</guid><dc:creator>kfcube</dc:creator><description>&lt;p&gt;Susheel,&lt;/p&gt;
&lt;p&gt;Thanks for your reply. Sorry I can&amp;#39;t attach my project but I can tell you what I did. I read sensor data(24 bytes including acce and gyro 6 float numbers) using timer with 100 times / second and notify the mobile app through ble. Sometime I got -12 error (not enough core) then I opened log and found those two warnings.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;All I want to know, is which configuration is for the ATT Tx meta buffer? There are so many configuration items.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Also, is there anything wrong with my configuration above? Actually I tried a lot of time by increasing one by one. Initially there are lots of -12 and now only several in a minute.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;Dragon Ji&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to allocate ATT TX meta</title><link>https://devzone.nordicsemi.com/thread/464178?ContentTypeID=1</link><pubDate>Mon, 15 Jan 2024 12:57:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6175b2cc-483c-41cf-9f0d-d8a152a5726b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Can you help me reproduce this error?&lt;/p&gt;
&lt;p&gt;Can you attach your project here?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>