<?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>LPC MicrocontrollersのトピックLPC66S69 : Secure GPIO output</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983181#M38769</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;Do I understand right and when GPIO pin from Bank 0 is marked as secure, it is not only not possible to read it state from NonSecure world but also is not possible to set output state ?&lt;/P&gt;&lt;P&gt;in UM it is not so clear about output behaviour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idea is to close control access to some GPIO pins what configured as output.&lt;/P&gt;&lt;P&gt;Is this possible ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way what peripheral block of LPC can be use in similar ways like AIPS in K82 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have RTOS tasks what running in nonsecure world with User privileges and I would like to limit set of peripherals&lt;/P&gt;&lt;P&gt;what can be accessed with User privileges . For K82 it was easy to done by using dynamic tables what update AIPSx gates at the same time as MPU tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But how in this MCU I can limit access of User task to one FLEXCOMM interface only ?&lt;/P&gt;&lt;P&gt;When task context is in -&amp;gt; eanble access with User privileges , when&amp;nbsp; out - disable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Oct 2019 08:38:13 GMT</pubDate>
    <dc:creator>EugeneHiihtaja</dc:creator>
    <dc:date>2019-10-30T08:38:13Z</dc:date>
    <item>
      <title>LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983181#M38769</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;Do I understand right and when GPIO pin from Bank 0 is marked as secure, it is not only not possible to read it state from NonSecure world but also is not possible to set output state ?&lt;/P&gt;&lt;P&gt;in UM it is not so clear about output behaviour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idea is to close control access to some GPIO pins what configured as output.&lt;/P&gt;&lt;P&gt;Is this possible ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way what peripheral block of LPC can be use in similar ways like AIPS in K82 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have RTOS tasks what running in nonsecure world with User privileges and I would like to limit set of peripherals&lt;/P&gt;&lt;P&gt;what can be accessed with User privileges . For K82 it was easy to done by using dynamic tables what update AIPSx gates at the same time as MPU tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But how in this MCU I can limit access of User task to one FLEXCOMM interface only ?&lt;/P&gt;&lt;P&gt;When task context is in -&amp;gt; eanble access with User privileges , when&amp;nbsp; out - disable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Oct 2019 08:38:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983181#M38769</guid>
      <dc:creator>EugeneHiihtaja</dc:creator>
      <dc:date>2019-10-30T08:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983182#M38770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp;&lt;SPAN style="color: #646464; background-color: #ffffff;"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="320103" data-username="yevgen.gyl@solita.fi" href="https://community.nxp.com/people/yevgen.gyl@solita.fi" style="color: #3d9ce7; background-color: #ffffff; border: 0px; font-weight: 600; text-decoration: none; font-size: 11.9994px;"&gt;Eugene Hiihtaja&lt;/A&gt;&lt;SPAN style="background-color: #ffffff; color: #646464; "&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; color: #646464; "&gt;1) "&lt;SPAN style="color: #51626f;"&gt;Do I understand right and when GPIO pin from Bank 0 is marked as secure, it is not only not possible to read it state from NonSecure world but also is not possible to set output state ?&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; color: #646464; "&gt;-&amp;gt; If the GPIO config as secure state, yes, only CPU-S can read it. The CPU-S can config it, CUP-NS can't.&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;About the secure GPIO, the main function is when one pin is configured as peripheral pin, for example UART pin,&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;and the config the UART in secure state, then the avoid CPU-NS read the GPIO state, only CPU-S can access it.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;About the detail introduction of Secure GPIO,&amp;nbsp; you can have a look at this application note:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN12326.pdf" title="https://www.nxp.com/docs/en/application-note/AN12326.pdf"&gt;https://www.nxp.com/docs/en/application-note/AN12326.pdf&lt;/A&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;2) About the freeRTOS question, you can take a new ticket in this thread:&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://community.nxp.com/space/2023"&gt;MQX Software Solutions&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2019 08:45:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983182#M38770</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2019-10-31T08:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983183#M38771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello !&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;I need to separate pins from group 0 to secure and nonsecure accesible.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;I undestand if individuals pins marked as secure they can be read/write via SGPIO only.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Remains one will be accessed from NonSecure world as usually.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Is this right way to split GPIO0 pins for Secure and Nonsecure groups ?&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2019 10:54:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983183#M38771</guid>
      <dc:creator>EugeneHiihtaja</dc:creator>
      <dc:date>2019-10-31T10:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983184#M38772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Hello &lt;A _jive_internal="true" data-content-finding="Community" data-userid="320103" data-username="yevgen.gyl@solita.fi" href="https://community.nxp.com/people/yevgen.gyl@solita.fi"&gt;Eugene Hiihtaja&lt;/A&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;From your description , I think your requirement is not SGPIO function,&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;it should be TrustZone . The implementation of ARM TrustZone for CPU0 involves using address bit 28 to divide the address space into potential secure and non-secure regions.&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;In Table 5 of UM,&amp;nbsp; provides details of the addresses for APB peripherals. APB peripherals have both secure and non-secure access possibilities.&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P style="background: white;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #51626f;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P style="background: white;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #51626f;"&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/92152iF9B8D8BEDE089462/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;So we can only set the whole GPIO to secure space or Non-secure, can't split GPIO0 pins for Secure and Nonsecure groups.&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Nov 2019 03:11:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983184#M38772</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2019-11-05T03:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983185#M38773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&amp;nbsp;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;But I can see separate peripheral called&amp;nbsp; HS Secure GPIO. I assume some individual pins start to belong to Secure GPIO and controlled from secure world and remains one can be controlled via NonSecure world by using GPIO peripherals.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;And TZ configuration will be done accordingly.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Also GPIO releated to peripherals will be added to Secure domain for avoid any read from NonSecure side.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Or how it works ?&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Nov 2019 09:05:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983185#M38773</guid>
      <dc:creator>EugeneHiihtaja</dc:creator>
      <dc:date>2019-11-05T09:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: LPC66S69 : Secure GPIO output</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983186#M38774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Eugene,&lt;/P&gt;&lt;P&gt;OK, I know your meaning.&lt;/P&gt;&lt;P&gt;Yes, you can set some of the GPIO as secure GPIO, some as normal GPIO.&lt;/P&gt;&lt;P&gt;About how to config them as secure GPIO, please refer to the AN12326 I mentioned before.&lt;/P&gt;&lt;P&gt;And also there is Secure GPIO demo under SDK, this demo just config one pin as Secure GPIO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2019 07:46:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC66S69-Secure-GPIO-output/m-p/983186#M38774</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2019-11-07T07:46:03Z</dc:date>
    </item>
  </channel>
</rss>

