<?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のトピックWhy did it influence the kernel boot on s32g3 after modifying linker_ram.ld</title>
    <link>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1672447#M3737</link>
    <description>&lt;P&gt;Hello, I am adding more code to ipcf sample, and run binary by startm7 under uboot, at same time updated&amp;nbsp;linker_ram.ld file below,&lt;/P&gt;&lt;P&gt;int_sram_no_cacheable : ORIGIN = 0x34600000, LENGTH = 0x00100000 /* 1MB, needs to include int_results */&lt;BR /&gt;ram_rsvd2 : ORIGIN = 0x34700000, LENGTH = 0x0 /* End of SRAM */&lt;/P&gt;&lt;P&gt;and lead to kernel booting hang up, how to correct this info ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2023 07:12:02 GMT</pubDate>
    <dc:creator>fengxianeric</dc:creator>
    <dc:date>2023-06-20T07:12:02Z</dc:date>
    <item>
      <title>Why did it influence the kernel boot on s32g3 after modifying linker_ram.ld</title>
      <link>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1672447#M3737</link>
      <description>&lt;P&gt;Hello, I am adding more code to ipcf sample, and run binary by startm7 under uboot, at same time updated&amp;nbsp;linker_ram.ld file below,&lt;/P&gt;&lt;P&gt;int_sram_no_cacheable : ORIGIN = 0x34600000, LENGTH = 0x00100000 /* 1MB, needs to include int_results */&lt;BR /&gt;ram_rsvd2 : ORIGIN = 0x34700000, LENGTH = 0x0 /* End of SRAM */&lt;/P&gt;&lt;P&gt;and lead to kernel booting hang up, how to correct this info ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 07:12:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1672447#M3737</guid>
      <dc:creator>fengxianeric</dc:creator>
      <dc:date>2023-06-20T07:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Why did it influence the kernel boot on s32g3 after modifying linker_ram.ld</title>
      <link>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1672788#M3755</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It has nothing to do, the kernel just pass the code to core M if you don;t have space it simple hangs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 14:14:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1672788#M3755</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2023-06-20T14:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: Why did it influence the kernel boot on s32g3 after modifying linker_ram.ld</title>
      <link>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1673101#M3770</link>
      <description>&lt;P&gt;Thanks caring，&lt;/P&gt;&lt;P&gt;Kernel booted by A53 and app imgs built for m7 core run by uboot.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 01:25:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Why-did-it-influence-the-kernel-boot-on-s32g3-after-modifying/m-p/1673101#M3770</guid>
      <dc:creator>fengxianeric</dc:creator>
      <dc:date>2023-06-21T01:25:19Z</dc:date>
    </item>
  </channel>
</rss>

