<?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 NXP, Linker scripts, and MCUxpresso extension for VS Code in MCUXpresso for VSCode</title>
    <link>https://community.nxp.com/t5/MCUXpresso-for-VSCode/NXP-Linker-scripts-and-MCUxpresso-extension-for-VS-Code/m-p/2383718#M562</link>
    <description>&lt;P&gt;Edit: Currently hand editing the linker scripts and it works, but wondering if there isn't something "better" i should be doing.&lt;/P&gt;&lt;P&gt;I am trying to use the 256KB secondary SRAM region (m_data2 in the linker scripts) as my .bss segment&lt;/P&gt;&lt;P&gt;Normally, I'd just edit the linker scripts for my projects and go from there. That's what I do on my STM32 environments.&lt;/P&gt;&lt;P&gt;But before I go and start ripping up project files, are the contents of the ./armgcc folder under the project regenerated ever? (I doubt it, I just want to check my assumptions)&lt;/P&gt;&lt;P&gt;And also, if they are regenerated, or otherwise, is there a better way to use the secondary 256KB SDRAM region on my chip? By default it seems it's not mapped to any region in my code.&lt;/P&gt;</description>
    <pubDate>Sun, 21 Jun 2026 07:44:18 GMT</pubDate>
    <dc:creator>litch</dc:creator>
    <dc:date>2026-06-21T07:44:18Z</dc:date>
    <item>
      <title>NXP, Linker scripts, and MCUxpresso extension for VS Code</title>
      <link>https://community.nxp.com/t5/MCUXpresso-for-VSCode/NXP-Linker-scripts-and-MCUxpresso-extension-for-VS-Code/m-p/2383718#M562</link>
      <description>&lt;P&gt;Edit: Currently hand editing the linker scripts and it works, but wondering if there isn't something "better" i should be doing.&lt;/P&gt;&lt;P&gt;I am trying to use the 256KB secondary SRAM region (m_data2 in the linker scripts) as my .bss segment&lt;/P&gt;&lt;P&gt;Normally, I'd just edit the linker scripts for my projects and go from there. That's what I do on my STM32 environments.&lt;/P&gt;&lt;P&gt;But before I go and start ripping up project files, are the contents of the ./armgcc folder under the project regenerated ever? (I doubt it, I just want to check my assumptions)&lt;/P&gt;&lt;P&gt;And also, if they are regenerated, or otherwise, is there a better way to use the secondary 256KB SDRAM region on my chip? By default it seems it's not mapped to any region in my code.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jun 2026 07:44:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-for-VSCode/NXP-Linker-scripts-and-MCUxpresso-extension-for-VS-Code/m-p/2383718#M562</guid>
      <dc:creator>litch</dc:creator>
      <dc:date>2026-06-21T07:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: NXP, Linker scripts, and MCUxpresso extension for VS Code</title>
      <link>https://community.nxp.com/t5/MCUXpresso-for-VSCode/NXP-Linker-scripts-and-MCUxpresso-extension-for-VS-Code/m-p/2384667#M564</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/263939"&gt;@litch&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Which chip you are using?&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Harry&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 03:48:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-for-VSCode/NXP-Linker-scripts-and-MCUxpresso-extension-for-VS-Code/m-p/2384667#M564</guid>
      <dc:creator>Harry_Zhang</dc:creator>
      <dc:date>2026-06-23T03:48:39Z</dc:date>
    </item>
  </channel>
</rss>

