<?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: Question about S32G3 Multi-Boot Bootloader Creation</title>
    <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044259#M12646</link>
    <description>&lt;P&gt;hi,&lt;SPAN&gt;apMike&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I suggest you try the version of BSP42, there is&amp;nbsp;&lt;SPAN&gt;a known issue as described in&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://jira.sw.nxp.com/browse/ALB-11457" target="_self" rel="nofollow noopener noreferrer"&gt;ALB-11457&lt;/A&gt;&lt;SPAN&gt;, and it has been resolved in Linux BSP42. The root cause lies in the bootloader de-initializes (in SysDal) the peripheral clocks before starting the applications, but s32_io_setup() is called without any prior initialization of the SDHC clocks from ATF. The description is shown in the BSP42 release note:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Joey_z_0-1739512566390.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/323945i3E66C3F27D6DA3B5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Joey_z_0-1739512566390.png" alt="Joey_z_0-1739512566390.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The easiest solution to fix this issue is recommending use BSP&amp;gt;=42. If continue working with BSP41, you can refer to these public&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://github.com/nxp-auto-linux/arm-trusted-firmware/commit/65b7b8c54f9ea952bcc35e87791b2edc17fd7688" target="_self" rel="nofollow noopener noreferrer"&gt;commits&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;to modify ATF code.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Hope it can help you.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Joey&lt;/P&gt;</description>
    <pubDate>Fri, 14 Feb 2025 05:59:38 GMT</pubDate>
    <dc:creator>Joey_z</dc:creator>
    <dc:date>2025-02-14T05:59:38Z</dc:date>
    <item>
      <title>Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2043304#M12634</link>
      <description>&lt;P&gt;Hi, all.&lt;/P&gt;&lt;P&gt;I am using the &lt;STRONG&gt;S32G399ARDB3 board&lt;/STRONG&gt; and creating a &lt;STRONG&gt;multi-boot Blob Image for the M7 core and A53 core&lt;/STRONG&gt;.&lt;BR /&gt;I used the &lt;STRONG&gt;GoldVIP-1.12 version&lt;/STRONG&gt; with the &lt;STRONG&gt;Bootloader_S32G3XX_ASR_4.4_M7 example&lt;/STRONG&gt;, and I modified the boot source information based on the following:&lt;/P&gt;&lt;H3&gt;A53:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Reset Handler Address:&lt;/STRONG&gt; 0x34302000&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Load Image Address:&lt;/STRONG&gt; 0x342F8000&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Image Size (size of fip.s32):&lt;/STRONG&gt; 1,189,472 bytes&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;M7:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Reset Handler Address:&lt;/STRONG&gt; 0x34420010&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Load Image Address:&lt;/STRONG&gt; 0x34420000&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Image Size (size of pfe-master.bin):&lt;/STRONG&gt; 1,090,300 bytes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I generated the &lt;STRONG&gt;bootloader.bin&lt;/STRONG&gt; using the &lt;STRONG&gt;S32DS IVT Configuration Tool&lt;/STRONG&gt; and created the Blob Image.&lt;BR /&gt;I uploaded the image using &lt;STRONG&gt;S32 FlashTool&lt;/STRONG&gt; with the following configuration:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Destination:&lt;/STRONG&gt; FLASH&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Algorithm:&lt;/STRONG&gt; MX25UW51245G&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I flashed the images to the following addresses:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;0x0:&lt;/STRONG&gt; Blob Image&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;0x100000:&lt;/STRONG&gt; fip.bin&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;0x300000:&lt;/STRONG&gt; pfe-master.bin&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;After flashing, I powered on the device, but the boot process stopped at the following log without any further response.&lt;/P&gt;&lt;H3&gt;Minicom log:&lt;/H3&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;==============================================================&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; &lt;SPAN class=""&gt;ComDal_Init&lt;/SPAN&gt;() done.&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Bootloader initialization complete.&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application &lt;SPAN class=""&gt;0&lt;/SPAN&gt; image fragment &lt;SPAN class=""&gt;0&lt;/SPAN&gt; of size &lt;SPAN class=""&gt;1189504&lt;/SPAN&gt; was loaded from QSPI, address &lt;SPAN class=""&gt;0x100000&lt;/SPAN&gt;.&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application &lt;SPAN class=""&gt;0&lt;/SPAN&gt; image fragment &lt;SPAN class=""&gt;0&lt;/SPAN&gt; was loaded in &lt;SPAN class=""&gt;16.57&lt;/SPAN&gt; milliseconds. bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application A53_0 was loaded.&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application &lt;SPAN class=""&gt;1&lt;/SPAN&gt; image fragment &lt;SPAN class=""&gt;0&lt;/SPAN&gt; of size &lt;SPAN class=""&gt;1090304&lt;/SPAN&gt; was loaded from QSPI, address &lt;SPAN class=""&gt;0x300000&lt;/SPAN&gt;.&lt;BR /&gt;bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application &lt;SPAN class=""&gt;1&lt;/SPAN&gt; image fragment &lt;SPAN class=""&gt;0&lt;/SPAN&gt; was loaded in &lt;SPAN class=""&gt;15.494&lt;/SPAN&gt; milliseconds. bootloader &lt;SPAN class=""&gt;0x2&lt;/SPAN&gt; Application M7_0 was loaded. ============================================================== &lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;Could you help me figure out the possible cause and how to resolve this issue?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 09:32:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2043304#M12634</guid>
      <dc:creator>apMike</dc:creator>
      <dc:date>2025-02-13T09:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2043365#M12636</link>
      <description>&lt;P&gt;Hi，&lt;SPAN&gt;apMike&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Thank you for contacting us.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Could you tell me the version of the BSP? Where did you get your&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;pfe - master.bin&lt;/CODE&gt;&lt;SPAN&gt;? According to your log, the bootloader successfully loaded the A - core and M - core binary files. There might be some initialization conflicts in the multi - core system or tf-a is not working.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Did you refer to AN13750 when you started dual core？&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Joey&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 10:35:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2043365#M12636</guid>
      <dc:creator>Joey_z</dc:creator>
      <dc:date>2025-02-13T10:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044118#M12644</link>
      <description>&lt;P&gt;Hi Joey_z ,&lt;/P&gt;&lt;P&gt;Thank you for your interest in my question.&lt;BR /&gt;I am using &lt;STRONG&gt;BSP version 41.0&lt;/STRONG&gt;, and the pfe-master.bin was built using &lt;STRONG&gt;MasterProject_RDB3&lt;/STRONG&gt; from &lt;STRONG&gt;PFE-DRV_S32G_M7_MCAL_1.3.0&lt;/STRONG&gt;. When building the pfe-master.bin file, I referred to &lt;STRONG&gt;S32G_PFE_Master_Slave_Demo_V2_2023_5_23_Eng&lt;/STRONG&gt; and set &lt;STRONG&gt;SLAVE_DRIVER=TRUE&lt;/STRONG&gt; in the &lt;STRONG&gt;Makefile&lt;/STRONG&gt;. Additionally, I commented out &lt;STRONG&gt;Eth_43_PFE_PreInit(NULL_PTR)&lt;/STRONG&gt; in &lt;STRONG&gt;src/sample_app_ethswt_initialization.c&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;As you mentioned, I followed &lt;STRONG&gt;AN13750&lt;/STRONG&gt; for multi-core booting, and it was working well previously.&lt;/P&gt;&lt;P&gt;Please let me know if you need any additional information!&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 02:35:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044118#M12644</guid>
      <dc:creator>apMike</dc:creator>
      <dc:date>2025-02-14T02:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044259#M12646</link>
      <description>&lt;P&gt;hi,&lt;SPAN&gt;apMike&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I suggest you try the version of BSP42, there is&amp;nbsp;&lt;SPAN&gt;a known issue as described in&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://jira.sw.nxp.com/browse/ALB-11457" target="_self" rel="nofollow noopener noreferrer"&gt;ALB-11457&lt;/A&gt;&lt;SPAN&gt;, and it has been resolved in Linux BSP42. The root cause lies in the bootloader de-initializes (in SysDal) the peripheral clocks before starting the applications, but s32_io_setup() is called without any prior initialization of the SDHC clocks from ATF. The description is shown in the BSP42 release note:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Joey_z_0-1739512566390.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/323945i3E66C3F27D6DA3B5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Joey_z_0-1739512566390.png" alt="Joey_z_0-1739512566390.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The easiest solution to fix this issue is recommending use BSP&amp;gt;=42. If continue working with BSP41, you can refer to these public&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://github.com/nxp-auto-linux/arm-trusted-firmware/commit/65b7b8c54f9ea952bcc35e87791b2edc17fd7688" target="_self" rel="nofollow noopener noreferrer"&gt;commits&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;to modify ATF code.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Hope it can help you.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Joey&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 05:59:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044259#M12646</guid>
      <dc:creator>Joey_z</dc:creator>
      <dc:date>2025-02-14T05:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044347#M12647</link>
      <description>&lt;P&gt;Hi, Joey_z&lt;BR /&gt;Thank you for your response! I'll try it as you suggested.&lt;BR /&gt;By the way, do you have any examples or documents that I can refer to for running A53 as PFE-Master and M7 as PFE-Slave?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 07:38:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044347#M12647</guid>
      <dc:creator>apMike</dc:creator>
      <dc:date>2025-02-14T07:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: Question about S32G3 Multi-Boot Bootloader Creation</title>
      <link>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044454#M12649</link>
      <description>&lt;P&gt;&lt;FONT size="4"&gt;hi,&lt;SPAN&gt;apMike&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="4"&gt;Thank you for your reply.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can refer to Chapter 7.3.1.4.1 “PFE Slave driver configuration” of the&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;BSP_User_Manual&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;to use PFE as a Slave in the A core. In addition, if the PFE Slave in the A core is working properly, you can refer to these links:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;A href="https://community.nxp.com/t5/NXP-Designs-Knowledge-Base/S32G-PFE-M-Master-A-Slave-Simple-Demo/ta-p/1637946" target="_blank" rel="noopener"&gt;S32G PFE_M_Master_A_Slave_Simple_Demo - NXP Community&lt;/A&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;A href="https://community.nxp.com/t5/NXP-Designs-Knowledge-Base/S32G-PFE-master-slave-scenarios-configurations/ta-p/1822007" target="_blank"&gt;S32G PFE master/slave scenarios configurations - NXP Community&lt;/A&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;FONT size="5"&gt;However, the document in the link is not an official document, it is for reference only, and we cannot provide any further support for it.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;FONT size="5"&gt;Hope it can help you.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;FONT size="5"&gt;BR&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;FONT size="5"&gt;Joey&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 09:49:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Question-about-S32G3-Multi-Boot-Bootloader-Creation/m-p/2044454#M12649</guid>
      <dc:creator>Joey_z</dc:creator>
      <dc:date>2025-02-14T09:49:56Z</dc:date>
    </item>
  </channel>
</rss>

