<?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>What causes decryption before receiving?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/43656/what-causes-decryption-before-receiving</link><description>Hello, 
 I’m sorry for asking again, but I could need some help again. This is a followup to devzone.nordicsemi.com/.../missing-endcrypt-event. 
 
 I’ve managed to receive and send encrypted link layer PDUs now (by manually triggering the KSGEN task)</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 13 Feb 2019 18:29:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/43656/what-causes-decryption-before-receiving" /><item><title>RE: What causes decryption before receiving?</title><link>https://devzone.nordicsemi.com/thread/170975?ContentTypeID=1</link><pubDate>Wed, 13 Feb 2019 18:29:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6116813-da84-4c8f-bd3f-b2b22fd40d63</guid><dc:creator>Torsten Robitzki</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;thanks a lot for the response. Encryption seems to work pretty well with this workaround.&lt;/p&gt;
&lt;p&gt;best regards,&lt;/p&gt;
&lt;p&gt;Torsten&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What causes decryption before receiving?</title><link>https://devzone.nordicsemi.com/thread/170970?ContentTypeID=1</link><pubDate>Wed, 13 Feb 2019 17:43:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5be8300-6f8e-41f8-b968-7675849dcde4</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I can not find any errata on the CCM module, but&amp;nbsp;there may be some dependencies or sequence of operation that the module requires even though not documented, so I am not terrible surprised if the CCM module must be enabled at the start of the connection event and disabled at the end to work as intended. It&amp;#39;s been implemented in specific to fulfill the Bluetooth requirements, and then some assumption may have been made by the designers on usage and test.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What causes decryption before receiving?</title><link>https://devzone.nordicsemi.com/thread/170828?ContentTypeID=1</link><pubDate>Wed, 13 Feb 2019 11:00:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:807fd5ff-e811-49fb-b026-15f03b280b1c</guid><dc:creator>Torsten Robitzki</dc:creator><description>&lt;p&gt;It turns out, that if I disable and enable the NRF_CCM, when setting up the connection event, I do not run into the error above. I&amp;#39;ve read that sequence in the sources of Zephire (Zephire also resets the NRC_CCM before setting up the transmission).&lt;/p&gt;
&lt;p&gt;I wonder now, if this just hides a bug in my implementation, or if this is really required. Could someone from Nordic please be so kind and confirm, that this resetting of the NRF_CCM is required? Is there any errata for this?&lt;/p&gt;
&lt;p&gt;best regards,&lt;/p&gt;
&lt;p&gt;Torsten&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>