<?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>MPC5xxx中的主题 Re: linking single elf file for multiple bootloader and applicationn</title>
    <link>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041949#M27263</link>
    <description>&lt;P&gt;okay , which one of these options will allow me to debug the other projects?&lt;/P&gt;</description>
    <pubDate>Tue, 11 Feb 2025 17:33:41 GMT</pubDate>
    <dc:creator>Tarek72</dc:creator>
    <dc:date>2025-02-11T17:33:41Z</dc:date>
    <item>
      <title>linking single elf file for multiple bootloader and applicationn</title>
      <link>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041323#M27256</link>
      <description>&lt;P&gt;I'm currently trying to get a bootmanager/ bootloader/application to be linked as a single .elf file for the MPC5748G.&lt;/P&gt;&lt;P&gt;There are some issues that I'm a little confused about, and I would be very grateful if you could provide any guidance with regard to them.&lt;/P&gt;&lt;P&gt;The plan is to always boot the bootmanager and then jump to the application or the application according to the value of some flag. How to combine all 3 software entities into one instead of flashing each one on its own and I manage to do that would I be able to access the code of bootloader or application after jumping.&lt;/P&gt;&lt;P&gt;I have already defined different start and end addresses of each entity in the linker file and developed the jumping mechanism&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 02:26:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041323#M27256</guid>
      <dc:creator>Tarek72</dc:creator>
      <dc:date>2025-02-11T02:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: linking single elf file for multiple bootloader and applicationn</title>
      <link>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041706#M27260</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/246289"&gt;@Tarek72&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can see two basic options:&lt;/P&gt;
&lt;P&gt;1. Generate binary files for additional projects (bootmanager, bootloader) using this method:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Generate-S-Record-Intel-HEX-Binary-file/ta-p/1105838" target="_blank"&gt;https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Generate-S-Record-Intel-HEX-Binary-file/ta-p/1105838&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;And then import them to your application like this:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Link-a-binary-file-s-into-the-application-project-using/ta-p/1111536" target="_blank"&gt;https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Link-a-binary-file-s-into-the-application-project-using/ta-p/1111536&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;When you build the application, it will contain all the images. &lt;/P&gt;
&lt;P&gt;2. I don't know what kind of tools you use, but if it is S32 Design Studio and Pemicro, you can simply specify here which additional object files should be loaded with the project:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1739270151657.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/323399iB633E4AA05BDD5A5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="lukaszadrapa_0-1739270151657.png" alt="lukaszadrapa_0-1739270151657.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 10:38:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041706#M27260</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-02-11T10:38:01Z</dc:date>
    </item>
    <item>
      <title>Re: linking single elf file for multiple bootloader and applicationn</title>
      <link>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041949#M27263</link>
      <description>&lt;P&gt;okay , which one of these options will allow me to debug the other projects?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 17:33:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2041949#M27263</guid>
      <dc:creator>Tarek72</dc:creator>
      <dc:date>2025-02-11T17:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: linking single elf file for multiple bootloader and applicationn</title>
      <link>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2042303#M27265</link>
      <description>&lt;P&gt;Take a look at:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Debug-multiple-elf-files-in-S32-Design-Studio-with-GDB/ta-p/1121160" target="_blank"&gt;https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Debug-multiple-elf-files-in-S32-Design-Studio-with-GDB/ta-p/1121160&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 06:59:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-applicationn/m-p/2042303#M27265</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-02-12T06:59:55Z</dc:date>
    </item>
  </channel>
</rss>

