<?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>S32GのトピックRe: ATF Build Parameters-FIP_QSPI_OFFSET</title>
    <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653271#M3249</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We are not understanding the overall request. We do apologize.&lt;/P&gt;
&lt;P&gt;What information are you looking for on regards of "&lt;SPAN&gt;FIP_ QSPI_ OFFSET, FIP_ MMC_ OFFSET, FIP_ MEMORY_ OFFSET&lt;/SPAN&gt;"?&lt;/P&gt;
&lt;P&gt;We do see they are used under the file you are referring to.&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2023 17:41:52 GMT</pubDate>
    <dc:creator>Daniel-Aguirre</dc:creator>
    <dc:date>2023-05-18T17:41:52Z</dc:date>
    <item>
      <title>ATF Build Parameters-FIP_QSPI_OFFSET</title>
      <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653185#M3242</link>
      <description>&lt;P&gt;My NXP friends:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; In the ATF source code, I couldn't find any information about make FIP_ QSPI_ OFFSET, FIP_ MMC_ OFFSET, FIP_ MEMORY_ OFFSET, Can you tell me why? Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2023-05-18 22-14-43.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/223826i3CE065E6C53B2FA1/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2023-05-18 22-14-43.png" alt="Screenshot from 2023-05-18 22-14-43.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2023-05-18 22-16-20.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/223827iCC1F0F33DF287D92/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2023-05-18 22-16-20.png" alt="Screenshot from 2023-05-18 22-16-20.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 14:21:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653185#M3242</guid>
      <dc:creator>Coco111</dc:creator>
      <dc:date>2023-05-18T14:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: ATF Build Parameters-FIP_QSPI_OFFSET</title>
      <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653271#M3249</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We are not understanding the overall request. We do apologize.&lt;/P&gt;
&lt;P&gt;What information are you looking for on regards of "&lt;SPAN&gt;FIP_ QSPI_ OFFSET, FIP_ MMC_ OFFSET, FIP_ MEMORY_ OFFSET&lt;/SPAN&gt;"?&lt;/P&gt;
&lt;P&gt;We do see they are used under the file you are referring to.&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 17:41:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653271#M3249</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2023-05-18T17:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: ATF Build Parameters-FIP_QSPI_OFFSET</title>
      <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653432#M3255</link>
      <description>I have read the Linux BSP user manual and do not quite understand the functions of these three macros. Therefore, I looked at the specific code in the ATF source code, but I found that there is no corresponding C code to handle these three macros</description>
      <pubDate>Fri, 19 May 2023 01:58:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653432#M3255</guid>
      <dc:creator>Coco111</dc:creator>
      <dc:date>2023-05-19T01:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: ATF Build Parameters-FIP_QSPI_OFFSET</title>
      <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653950#M3273</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thanks for your feedback. As said in the BSP Reference Manual:&lt;/P&gt;
&lt;P&gt;"For QSPI boot, configure TF-A to read the FIP image from a defined QSPI offset."&lt;/P&gt;
&lt;P&gt;"For SD/eMMC boot, configure TF-A to read the FIP image from a defined SD/eMMC offset."&lt;/P&gt;
&lt;P&gt;"Configure TF-A to read the FIP image from a defined memory address instead of reading it from the boot source storage (QSPI or MMC)."&lt;/P&gt;
&lt;P&gt;These options should let you have control over where you want the ATF to be looking for the FIP image, depending on which interface you want to search over (QSPI, MMC or SRAM).&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2023 17:14:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1653950#M3273</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2023-05-19T17:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: ATF Build Parameters-FIP_QSPI_OFFSET</title>
      <link>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1654121#M3283</link>
      <description>&lt;BR /&gt;Thank you for your reply. I understand</description>
      <pubDate>Sat, 20 May 2023 07:10:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/ATF-Build-Parameters-FIP-QSPI-OFFSET/m-p/1654121#M3283</guid>
      <dc:creator>Coco111</dc:creator>
      <dc:date>2023-05-20T07:10:29Z</dc:date>
    </item>
  </channel>
</rss>

