<?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>NFC type 4 Write</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22248/nfc-type-4-write</link><description>Hi all, 
 I am trying to study the NFC type 4 write and how use the values received. 
 I cant find where can I see the data I am receiving when I write to a nRF52 tag using a smartphone (in code), I just can see it reading back the tag using the a smartpone</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 23 May 2017 18:26:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22248/nfc-type-4-write" /><item><title>RE: NFC type 4 Write</title><link>https://devzone.nordicsemi.com/thread/87447?ContentTypeID=1</link><pubDate>Tue, 23 May 2017 18:26:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:666ae5bf-8367-46a2-8db5-68c754fc1ad8</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Yes, the message buffer will be filled with old/garbage data. You need to use the NLEN field to get the valid data from buffer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NFC type 4 Write</title><link>https://devzone.nordicsemi.com/thread/87446?ContentTypeID=1</link><pubDate>Tue, 23 May 2017 15:31:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfe3e59c-675e-4ad0-9732-8d02e49c308c</guid><dc:creator>Arepa</dc:creator><description>&lt;p&gt;Hi Jørgen,
I checked it, now I am receiving the data I wrote, but always on the first write I received corrupt data (always the same message possibly the last message default data on the buffer?)&lt;/p&gt;
&lt;p&gt;update: I fixed it reading the m_ndef_msg_buf when it match with the expected data  in NLEN field&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NFC type 4 Write</title><link>https://devzone.nordicsemi.com/thread/87445?ContentTypeID=1</link><pubDate>Tue, 23 May 2017 10:52:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:064f7f6f-0ae6-4f51-9d1b-25e1ef2b163f</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;When the NDEF buffer is updated (written), you will get a &lt;code&gt;NFC_T4T_EVENT_NDEF_UPDATED&lt;/code&gt; event in &lt;em&gt;nfc_callback&lt;/em&gt;. Typically, this will happen two times, as described in &lt;a href="https://devzone.nordicsemi.com/question/115902/nfc_t4t_event_ndef_updated-gets-fired-twice-per-nfc-write/?answer=116781#post-id-116781"&gt;this answer&lt;/a&gt;. The data will be available in the NDEF message buffer given to the function &lt;code&gt;nfc_t4t_ndef_rwpayload_set&lt;/code&gt;, which in the writable NDEF message example corresponds to &lt;code&gt;m_ndef_msg_buf&lt;/code&gt;. The first two bytes of the buffer, the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v13.0.0/nfc_type4tag_dox.html?cp=4_0_0_3_24_4_0#nfc_t4t_ndef_file_format_dox"&gt;NLEN field&lt;/a&gt;, contains the length of the data.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>