<?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>Data Length Update on nRF7002-DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124833/data-length-update-on-nrf7002-dk</link><description>I am using the nRF7002-DK to implement a BLE interface. I need to send packets &amp;gt; 23 bytes through a notification characteristic. I am currently using nRF Connect on an android device to connect to it In my prj.conf file I have the following: 
 
 CONFIG_BT_BUF_CMD_TX_SIZE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Oct 2025 12:46:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124833/data-length-update-on-nrf7002-dk" /><item><title>RE: Data Length Update on nRF7002-DK</title><link>https://devzone.nordicsemi.com/thread/550900?ContentTypeID=1</link><pubDate>Wed, 08 Oct 2025 12:46:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b28db66-7a62-49b9-8ede-8f23d97788ed</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;The RADIO peripheral is only available to the network core, so any application that relies on the RADIO must have firmware running on the network core. In the case of Bluetooth, the&amp;nbsp;bluetooth host typically runs on the application core, while the&amp;nbsp;bluetooth controller resides on the network core (&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf53/features_nrf53.html#bluetooth_low_energy"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf53/features_nrf53.html#bluetooth_low_energy&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;The throughput sample is for for the application core, but uses sysbuild (see&amp;nbsp;&lt;a id="" href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/&lt;/a&gt;) to also include&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/ipc_radio/README.html"&gt;ipc_radio&lt;/a&gt;&amp;nbsp;in the build. Both the app and network core will be programmed when you click &amp;quot;flash&amp;quot;.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re using our VS Code extension to build your project, you can&amp;nbsp;see&amp;nbsp;which projects are included in the build from the APPLICATIONS view.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Data Length Update on nRF7002-DK</title><link>https://devzone.nordicsemi.com/thread/550895?ContentTypeID=1</link><pubDate>Wed, 08 Oct 2025 12:32:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7ebeb52-8012-4203-9d53-bc6ca8065ed4</guid><dc:creator>Ted Jones</dc:creator><description>&lt;p&gt;Thanks Vidar.&amp;nbsp; I appreciate your quick response but I am still a little confused.&amp;nbsp; In the case of the throughput example is the entire code base being built for the network core?&amp;nbsp; I am building my application for the application core, I am not sure what needs to be built/flashed to the&amp;nbsp;network core.&amp;nbsp; I will need to support both BLE and WiFi.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Data Length Update on nRF7002-DK</title><link>https://devzone.nordicsemi.com/thread/550893?ContentTypeID=1</link><pubDate>Wed, 08 Oct 2025 11:59:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df8c3458-e37a-44d9-9995-0b68018e6d31</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The radio packet length should be set to the maximum, which is 251 bytes. This allows the entire 247 byte ATT packet to fit into a single on-air packet.&amp;nbsp;Support for the max. radio packet length (default:27)&amp;nbsp;must be&amp;nbsp;enabled in the ipc_radio FW running on the network core like how it&amp;#39;s done in&amp;nbsp;our BLE throughput sample here:&amp;nbsp;&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/main/samples/bluetooth/throughput/sysbuild/ipc_radio/prj.conf#L21-L23"&gt;https://github.com/nrfconnect/sdk-nrf/blob/main/samples/bluetooth/throughput/sysbuild/ipc_radio/prj.conf#L21-L23&lt;/a&gt;. CONFIG_BT_AUTO_DATA_LEN_UPDATE is also enabled by default, which means you to not have to initiate the update yourself.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Data Length Update on nRF7002-DK</title><link>https://devzone.nordicsemi.com/thread/550846?ContentTypeID=1</link><pubDate>Tue, 07 Oct 2025 20:03:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7b75661-b2a8-4de9-a301-0995103513d8</guid><dc:creator>Ted Jones</dc:creator><description>&lt;p&gt;BTW, I tried initiating a data length update from nRF Connect as well, that had the same behavior.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>