<?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>Porting code from S332 V2.0 to V4.0,  BLE_ERROR_NO_TX_PACKETS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24219/porting-code-from-s332-v2-0-to-v4-0-ble_error_no_tx_packets</link><description>With version v2.0 of S332, I checked for a return of BLE_ERROR_NO_TX_PACKET when using the ble_nus_string_send function. I use this test in a routine which writes buffers larger than 20. 
 When I ported to v4.0 of S332 I see that BLE_ERROR_NO_TX_PACKET</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 10 Aug 2017 09:11:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24219/porting-code-from-s332-v2-0-to-v4-0-ble_error_no_tx_packets" /><item><title>RE: Porting code from S332 V2.0 to V4.0,  BLE_ERROR_NO_TX_PACKETS</title><link>https://devzone.nordicsemi.com/thread/95355?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2017 09:11:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e24825e4-b52c-42ee-9b0a-6a9c9a30444b</guid><dc:creator>Ross Belloni</dc:creator><description>&lt;p&gt;Thanks Sigurd!&lt;/p&gt;
&lt;p&gt;Ross&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting code from S332 V2.0 to V4.0,  BLE_ERROR_NO_TX_PACKETS</title><link>https://devzone.nordicsemi.com/thread/95354?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2017 07:52:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b5f0d9e-e470-46ee-a2b7-7c01f63f9109</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In S332 v4.0, &lt;code&gt;BLE_ERROR_NO_TX_PACKETS&lt;/code&gt; has been replaced by &lt;code&gt;NRF_ERROR_RESOURCES&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The application packet concept has been replaced with a dedicated transmission queue for Handle Value Notifications. The number of Handle Value Notifications that can be queued is configured by &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s332.api.v4.0.2/structble__gatts__conn__cfg__t.html?cp=2_3_3_0_0_2_5_4_0"&gt;ble_gatts_conn_cfg_t::hvn_tx_queue_size&lt;/a&gt;. When the queue is full, the &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s332.api.v4.0.2/group___b_l_e___g_a_t_t_s___f_u_n_c_t_i_o_n_s.html?cp=2_3_3_0_0_2_5_2_4#ga313fe43c2e93267da668572e885945db"&gt;sd_ble_gatts_hvx()&lt;/a&gt; function will now return &lt;code&gt;NRF_ERROR_RESOURCES&lt;/code&gt;. &lt;code&gt;BLE_ERROR_NO_TX_PACKETS&lt;/code&gt; / &lt;code&gt;BLE_ERROR_NO_TX_BUFFERS&lt;/code&gt; is no longer used. A &lt;code&gt;BLE_GATTS_EVT_HVN_TX_COMPLETE&lt;/code&gt; event will be issued as soon as the transmission of the notification is complete&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>