<?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>AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12931/aes-ccm-can-inptr-outptr</link><description>Hello: 
 I have read the documentation but I cannot determine if INPTR and OUTPTR can be set to the same memory address? I will try it to see what happens but it would be great to know if this is supported. 
 FYI: I want to do on-the-fly packet encryption</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 08 Apr 2016 13:27:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12931/aes-ccm-can-inptr-outptr" /><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49261?ContentTypeID=1</link><pubDate>Fri, 08 Apr 2016 13:27:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbc22c8d-6e51-4678-818e-0dd9613cb294</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;If you set the pointers to the same value, output data will overwrite input data, but it may be that the overwriting happens after data is read, but this has not been verified. Judging by your results, this is not a viable option.&lt;/p&gt;
&lt;p&gt;I discussed this with our R&amp;amp;D engineers and this was their reply:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;For Tx, Radio PACKETPTR should point
to where OUTPTR (encrypted packet)
points to. INPTR (clear text) should
point to a different location.&lt;/p&gt;
&lt;p&gt;For Rx, INPTR should point to where
Radio PACKETPTR points to. OUTPTR
(clear text) should point to a
different location.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;-Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49260?ContentTypeID=1</link><pubDate>Thu, 07 Apr 2016 15:59:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec53be0d-69ab-4e32-9fa4-1f7ec63c294d</guid><dc:creator>will</dc:creator><description>&lt;p&gt;Bjorn:&lt;/p&gt;
&lt;p&gt;Thanks! I will do so... BTW I figured out the answer to my question. You CANNOT set INPTR to OUTPTR. I finally got the LL_START_ENC_RSP correctly encrypted with the proper MIC. I had to set INPTR and OUTPTR to different RAM locations. When they were the same the encryption worked but the MIC was incorrect. I would still like verification from your engineers on this one. Maybe I am not doing something else correctly? Anyway, as I move along I will post other questions on a different thread.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49259?ContentTypeID=1</link><pubDate>Thu, 07 Apr 2016 07:33:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2cdbf2b3-1d78-4584-9e00-ef7778a492fa</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;No problem! Please post them in separate questions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49258?ContentTypeID=1</link><pubDate>Wed, 06 Apr 2016 16:52:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7985e378-9b77-4634-a397-ab9fcabbe208</guid><dc:creator>will</dc:creator><description>&lt;p&gt;Thanks Bjorn. I am having issues getting all this working and I may have quite a few more questions if I cant get it working. Should I post them as separate questions to the forum or just add them to this post?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49257?ContentTypeID=1</link><pubDate>Wed, 06 Apr 2016 11:46:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76e0c869-6e9f-4cfa-93cf-450b7ea17293</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@wes3:(will) I have forwarded this to the R&amp;amp;D guys and will update you as soon as they come back to me.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49256?ContentTypeID=1</link><pubDate>Mon, 04 Apr 2016 15:01:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28aa6055-a974-4259-b0ad-7e684c55b956</guid><dc:creator>will</dc:creator><description>&lt;p&gt;Shoot! I thought I put that in there. I am using the nrf52. I am not using the SDK nor softdevice (writing my own BLE controller code). I will also be porting this code to the nrf51 so if there are any differences I would appreciate it if you pointed those out (I have not read the nrf51 docs yet). Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AES CCM: can INPTR = OUTPTR?</title><link>https://devzone.nordicsemi.com/thread/49255?ContentTypeID=1</link><pubDate>Mon, 04 Apr 2016 14:29:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6539b64d-bcf1-48fe-b8df-f86101833ff8</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Which chip, SDK and SoftDevice  are you using?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>