<?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: GPIO vs Secure GPIO in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/GPIO-vs-Secure-GPIO/m-p/950896#M37784</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Randa,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to the architecture of normal GPIO, all digital IO pins states are readable through normal GPIO module from the GPIO read path, independent of which function is chosen for this pin(UART,SPI,I2C,etc). As a result, there is a possibility of leaking information from secure resource.&lt;/P&gt;&lt;P&gt;The &lt;A href="https://www.nxp.com/docs/en/application-note/AN12326.pdf"&gt;application note&lt;/A&gt;&amp;nbsp;for secure gpio will provide the details of what it entails such as the secure gpio mask that is implemented in order to turn on and off the state of this peripheral.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Have a great day!&lt;/P&gt;&lt;P&gt;Sabina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Oct 2019 18:57:02 GMT</pubDate>
    <dc:creator>Sabina_Bruce</dc:creator>
    <dc:date>2019-10-23T18:57:02Z</dc:date>
    <item>
      <title>GPIO vs Secure GPIO</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/GPIO-vs-Secure-GPIO/m-p/950895#M37783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One of the security features offered by the LPC55S6x is Secure GPIO. In the user manual is it given some insights about its configuration. Meanwhile, I was not able to see what this&amp;nbsp;"type"&amp;nbsp;of GPIO is&amp;nbsp;additionally adding comparing to the "causal" GPIO. What do &lt;STRONG&gt;Secure&lt;/STRONG&gt; mean in this context?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2019 09:50:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/GPIO-vs-Secure-GPIO/m-p/950895#M37783</guid>
      <dc:creator>randa_zarrouk</dc:creator>
      <dc:date>2019-10-22T09:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO vs Secure GPIO</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/GPIO-vs-Secure-GPIO/m-p/950896#M37784</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Randa,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to the architecture of normal GPIO, all digital IO pins states are readable through normal GPIO module from the GPIO read path, independent of which function is chosen for this pin(UART,SPI,I2C,etc). As a result, there is a possibility of leaking information from secure resource.&lt;/P&gt;&lt;P&gt;The &lt;A href="https://www.nxp.com/docs/en/application-note/AN12326.pdf"&gt;application note&lt;/A&gt;&amp;nbsp;for secure gpio will provide the details of what it entails such as the secure gpio mask that is implemented in order to turn on and off the state of this peripheral.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Have a great day!&lt;/P&gt;&lt;P&gt;Sabina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Oct 2019 18:57:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/GPIO-vs-Secure-GPIO/m-p/950896#M37784</guid>
      <dc:creator>Sabina_Bruce</dc:creator>
      <dc:date>2019-10-23T18:57:02Z</dc:date>
    </item>
  </channel>
</rss>

