<?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>Gazelle &amp;amp; NRF 52840</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127587/gazelle-nrf-52840</link><description>I am trying to evaluate the NRF 52840 using the Gazell protocol. 
 I need some secured link between 2 devices with a low latency, and authentified (so no one can replace one of the devices, inject etc). But I also need some communication in both ways</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Mar 2026 10:02:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127587/gazelle-nrf-52840" /><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564172?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2026 10:02:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1eee063c-5c13-4cff-b2ae-919c3552167f</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Sorry, you are right. I was under the impression it was, but it&amp;#39;s been a while since I worked on Gazell so my memory proved me wrong.&lt;/p&gt;
&lt;p&gt;The GZP API doesn&amp;#39;t provide a specific high-level function for host-to-device encrypted data because it uses the underlying Gazell ACK mechanism. For encrypted host-to-device communication, you need to manually encrypt the ACK payload data before calling nrf_gzll_add_packet_to_tx_fifo() on the host. So maybe that can help.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564145?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2026 08:23:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfa056e0-c5b9-4503-a6fd-e7507d1c5582</guid><dc:creator>Samuel01</dc:creator><description>&lt;p&gt;If you have a look at the gzp.h, you will see for the host the functions&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;&lt;span&gt;gzp_crypt_user_data_received and&amp;nbsp;&lt;/span&gt;&lt;/span&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;gzp_crypt_user_data_read.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;span&gt;And for the device the function&amp;nbsp;&lt;/span&gt;&lt;/span&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;gzp_crypt_data_send.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;But there is no send function for the host, or attach_payload function.&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564130?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 19:29:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc623fe1-78c4-4288-bc6d-2426ee3b2fe8</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I honestly don&amp;#39;t understand, I can&amp;#39;t imagine that it&amp;#39;s encrypted only one way.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I assume you have a gazell host that is receiving data and a gazell device transmitting data, all communication&amp;nbsp;should be done&amp;nbsp;on pipe1 that is encrypted after gazell pairing. The gazell device is the one that need to initiate all communication. The gazell host can at any time prepare data to be sent on pipe1 back to the gazell device, but the only way it can be sent from the host to the device, is by the gazell device transmitting a packet which indirectly will then fetch the packet from the gazell host.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564115?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 15:29:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ca96738-2007-4246-9058-643e859b44c8</guid><dc:creator>Samuel01</dc:creator><description>&lt;p&gt;Yes it&amp;#39;s also what I found, only 1 pipe is encrypted, so it&amp;#39;s not possible to have encrypted or at least authentified communication in both directions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564114?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 15:10:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba60185e-45f4-43aa-8a00-fff7137a6cc5</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;If I remember correctly then you can use pipe1 for encrypted data and pipe2-7 for unencrypted data. While pipe0 is used for pairing and key exchange.&lt;/p&gt;
&lt;p&gt;Kenenth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564103?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 13:09:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f103b62b-ad33-44a2-bc59-db744e4283b4</guid><dc:creator>Samuel01</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks for your reply, I have already checked this documentation. Unfortunately, when I try to communicate in encrypted way, there is no function available to add a payload to the ack. It seems this payload is used for key exchange.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazelle &amp; NRF 52840</title><link>https://devzone.nordicsemi.com/thread/564101?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 13:01:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0727b46f-e8d8-41d0-a3d7-15edb1572f12</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can read more about how the Gazell transport layer works here:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/gazell/gzll.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/gazell/gzll.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can read more about how the Gazell pairing library ensure secure wireless link between two devices here:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/gazell/gzp.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/gazell/gzp.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s fully possible to meet your requirements using Gazell pairing.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>