<?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>Lots of I2C ANACK messages with ATECC508</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84926/lots-of-i2c-anack-messages-with-atecc508</link><description>NCS 1.8.0 
 We have a custom board that uses the ATECC508A on an I2C bus. We are using release 3.3.0 of Microchips library cryptoauthlib which includes zephyr hal support which we have integrated with our application but we see lots of address NACKs while</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Feb 2022 11:22:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84926/lots-of-i2c-anack-messages-with-atecc508" /><item><title>RE: Lots of I2C ANACK messages with ATECC508</title><link>https://devzone.nordicsemi.com/thread/354314?ContentTypeID=1</link><pubDate>Tue, 22 Feb 2022 11:22:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a878239-c349-4a75-88ac-5badbb91bd75</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Ok, I am not familiar with that library, so my recommendation would be to hear Microchip&amp;#39;s thoughts on the issue.&lt;/p&gt;
&lt;p&gt;If you find something that is not working correctly on our side, let me know.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Lots of I2C ANACK messages with ATECC508</title><link>https://devzone.nordicsemi.com/thread/354310?ContentTypeID=1</link><pubDate>Tue, 22 Feb 2022 10:44:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b8a9cf9-70be-42f8-8c07-06872133c5c1</guid><dc:creator>RonanB96</dc:creator><description>&lt;p&gt;Got a logic trace of multiple transactions and it seems all of the ANACKs are coming from the cryptoauthlibs wake-up function.&lt;/p&gt;
&lt;p&gt;It writes 0x01 to address 0x00 to wake up the ATECC508A and then does the write/read so I guess I can ignore those ANACK errors&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1645526621229v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Lots of I2C ANACK messages with ATECC508</title><link>https://devzone.nordicsemi.com/thread/354128?ContentTypeID=1</link><pubDate>Mon, 21 Feb 2022 12:23:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fce51822-62f7-424f-bfd0-3f7232f9285d</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Could I see a logic trace of the I2C lines?&lt;/p&gt;
[quote user=""]The I2C comms has not actually failed&amp;nbsp;so far as we have a high retry count for the ATECC508A configuration.[/quote]
&lt;p&gt;What do you mean by this? Are you able to communicate after a number of retries?&lt;/p&gt;
&lt;p&gt;Have you double checked the voltage, ground and signal levels?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>