<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: A71CH on Raspberry Pi3: I2C errors in Secure Authentication</title>
    <link>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906535#M70</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that the problem you are experiencing it's similar to this one&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/477378"&gt;https://community.nxp.com/thread/477378&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please check that thread and verify if that it's helpful for you?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Estephania&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 May 2019 16:35:46 GMT</pubDate>
    <dc:creator>stephanie_m</dc:creator>
    <dc:date>2019-05-01T16:35:46Z</dc:date>
    <item>
      <title>A71CH on Raspberry Pi3: I2C errors</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906534#M69</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello to the NXP Community team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am reaching you because I am running into troubles while trying to interface the A71CHARD demo board to my Raspberry Pi3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is what I did already:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;modified the A71CH Makefile to build for the Raspberry Pi&lt;/LI&gt;&lt;LI&gt;deactivated the i2c interface of the Pi3 which&amp;nbsp;yielded a 'Read Block not supported' upon launching the demos&lt;/LI&gt;&lt;LI&gt;installed pigpio to run i2c as a bit-banged bus&lt;/LI&gt;&lt;LI&gt;modified&amp;nbsp;&lt;STRONG&gt;/boot/config.txt&lt;/STRONG&gt; with the following&amp;nbsp;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;dtoverlay=i2c-gpio,i2c_gpio_sda=2,i2c_gpio_scl=3,i2c_gpio_delay_us=4&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Details on the Config:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;Linux &amp;lt;GATEWAY_NAME&amp;gt; 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux&lt;/P&gt;&lt;P&gt;pigpio V64&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I could compile the following examples:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;A71CH_i2c_native&lt;/LI&gt;&lt;LI&gt;A71CHlight_i2c_native&lt;/LI&gt;&lt;LI&gt;a71chConfig_i2c_native&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I am running into issues with some of the simple commands responding correctly (e.g.&amp;nbsp;&lt;STRONG&gt;info device, info cnt, info pairs&lt;/STRONG&gt;) but most of them return a 0x7011 or 0x7010 (Write or Read error code), including the i2c native demo, the light i2c native demo and&amp;nbsp;&lt;STRONG&gt;info status, info objects&lt;/STRONG&gt; called from the &lt;STRONG&gt;config interactive console&lt;/STRONG&gt;. After an error code, the normally operational commands return&amp;nbsp;&lt;STRONG&gt;Protocol exception 01 A7&lt;/STRONG&gt; and the A71CH required a softReset to be issued (device hanging). I have tried to look directly at the bus with a logic analyzer but the results are not quite clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached in the following zip:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;the console logs for the different run cases&lt;/LI&gt;&lt;LI&gt;the Saleae analyzer outputs and decoded messages in Hex format (.csv files)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already tried to change the gpio delay &amp;amp; timeout parameters in the&amp;nbsp;&lt;STRONG&gt;dtoverlay&lt;/STRONG&gt; as I think it is certainly related to the implementation of the i2c bus on the Raspberry Pi3 side but without success that far. Do you have any idea what the source of the issue might be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance for your help&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Apr 2019 16:00:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906534#M69</guid>
      <dc:creator>quentincabrol</dc:creator>
      <dc:date>2019-04-23T16:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: A71CH on Raspberry Pi3: I2C errors</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906535#M70</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that the problem you are experiencing it's similar to this one&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/477378"&gt;https://community.nxp.com/thread/477378&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please check that thread and verify if that it's helpful for you?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Estephania&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2019 16:35:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906535#M70</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2019-05-01T16:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: A71CH on Raspberry Pi3: I2C errors</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906536#M71</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Indeed I first followed these steps but in addition to that, the makefile points to an /&lt;STRONG&gt;rsp&lt;/STRONG&gt; folder that is not present in the package and must contain:&lt;/P&gt;&lt;P&gt;- i2c_a7.c leveraging pigpio (not the same as the i2c_a7 provided for the imx platform)&lt;/P&gt;&lt;P&gt;- pigpio.h/c&lt;/P&gt;&lt;P&gt;- types.h&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The pigpio standard library files (on pigpio github) were missing some undeclared defines and I add to edit them so for it to be operational on the pi.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Raspberry allows for a fast and easy testing of the IC that does not require to rebuild a full Yocto (we are working with the i.Mx7 platform). Also it might be helpful for all the A71CH users that the adapted files for a build on Pi be added to one of your future A71CH Software Package releases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the compilation issues observed when using the standard pigpio files:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="AperÃ§u de image.png" src="https://www.linkedin.com/dms/C4D06AQFuxwjv7E1Xuw/messaging-attachmentFile/0?m=AQLLD72FWrawIgAAAWp3zVPNVg4zzjezEmK_c_WdfSRVAivyhlB-ijouBQ&amp;amp;ne=1&amp;amp;v=beta&amp;amp;t=agaQD0XSR2cSI5lphtYBpVl0o2sWQSMpoUW0q-h4M6A#S6528611128778465280_500" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is operational now and I was able to test the different A71CH features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your support&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quentin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 May 2019 09:18:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/A71CH-on-Raspberry-Pi3-I2C-errors/m-p/906536#M71</guid>
      <dc:creator>quentincabrol</dc:creator>
      <dc:date>2019-05-02T09:18:26Z</dc:date>
    </item>
  </channel>
</rss>

