<?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>Trouble generating NFC T4T messages in Zephyr</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90635/trouble-generating-nfc-t4t-messages-in-zephyr</link><description>I&amp;#39;m attempting to create an NFC type 4 message to allow certain information to be read using a phone or other NFC reader. I&amp;#39;ve studied a number of examples, but none that does exactly what I want, i.e. Type 4 text records. The nearest I&amp;#39;ve found is the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 03 Aug 2022 23:57:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90635/trouble-generating-nfc-t4t-messages-in-zephyr" /><item><title>RE: Trouble generating NFC T4T messages in Zephyr</title><link>https://devzone.nordicsemi.com/thread/379994?ContentTypeID=1</link><pubDate>Wed, 03 Aug 2022 23:57:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0b7cacbb-e631-4490-ab5a-1aa9de1fadfb</guid><dc:creator>Frog</dc:creator><description>&lt;p&gt;Further update: I&amp;#39;ve resolved this; it turns out that calling&lt;/p&gt;
&lt;div style="background-color:#1e1e1e;color:#d4d4d4;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;
&lt;div&gt;&lt;span style="color:#dcdcaa;"&gt;nfc_t4t_ndef_rwpayload_set()&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;with a buffer_length that&amp;#39;s not at least a few bytes more than the actual length of the NDEF message causes the problem.&amp;nbsp; I haven&amp;#39;t got to the bottom of exactly how many bytes extra are needed, but with a message of about 120 bytes I have found that specifying 256 bytes (in my case the size of the available buffer rather than the content) is successful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Trouble generating NFC T4T messages in Zephyr</title><link>https://devzone.nordicsemi.com/thread/379990?ContentTypeID=1</link><pubDate>Wed, 03 Aug 2022 23:10:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50ba8095-bad1-4d99-8059-1f232850a6d7</guid><dc:creator>Frog</dc:creator><description>&lt;p&gt;Update: I&amp;#39;m using an iPhone 12 and have installed the slightly more helpful NXP TagInfo app.&amp;nbsp; This tells me &amp;#39;No NDEF Records&amp;#39;, although reading the device using the ACR122 reader and script tool outputs what appears to be valid NDEF records.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1659568218216v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I know that this isn&amp;#39;t much to go on but it&amp;#39;s all I have at this point.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>