<?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 Re: Firmware and bootloader binary file issues in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1686577#M23934</link>
    <description>&lt;P&gt;I have find a document dealing with this topic:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/13290/1/ANxxxx_Fill_Pattern_feature_DRAFT.pdf" target="_blank"&gt;https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/13290/1/ANxxxx_Fill_Pattern_feature_DRAFT.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jul 2023 11:11:41 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2023-07-12T11:11:41Z</dc:date>
    <item>
      <title>Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1674859#M23855</link>
      <description>&lt;P&gt;If you do firmware and check the internal flash, the picture below appears. However, if you build it as a binary file, you get the same result as the picture on the right.&lt;BR /&gt;Is there a reason for this or is there any way I can fix it?&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pyi285_1-1687510399549.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/228999i87EF9FE8FF52E754/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pyi285_1-1687510399549.png" alt="pyi285_1-1687510399549.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;pyi285_1-1687510399549.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pyi285_2-1687510427258.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/229000i6F1AD1976B05647C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pyi285_2-1687510427258.png" alt="pyi285_2-1687510427258.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;pyi285_2-1687510427258.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;1. The difference between the two pictures is that the FF part is displayed as 00. Please explain the reason.&lt;BR /&gt;2. Please explain if there is any other way to solve the binary file problem.&lt;BR /&gt;3. Finally, looking at the address 00000, what exactly does the first line of the 015A000 part do?&lt;BR /&gt;#mpc5674f #bootloader # Binary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2023 08:55:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1674859#M23855</guid>
      <dc:creator>pyi285</dc:creator>
      <dc:date>2023-06-23T08:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1677692#M23880</link>
      <description>&lt;P&gt;&lt;BR /&gt;I am not sure what you are trying to compare as you are loking for different addresses 0x0001_0000 vs 0x0000_0000.&lt;/P&gt;
&lt;P&gt;Anyway these are two booting address options from following sets:&lt;BR /&gt;0x0000_0000&lt;BR /&gt;0x0000_4000&lt;BR /&gt;0x0001_0000&lt;BR /&gt;0x0001_C000&lt;BR /&gt;0x0002_0000&lt;BR /&gt;0x0003_0000&lt;/P&gt;
&lt;P&gt;and pattern on that address in Reset Configuration Half Word&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_0-1687941714201.png" style="width: 670px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/229822iE969B86FEBA55754/image-dimensions/670x947?v=v2" width="670" height="947" role="button" title="davidtosenovjan_0-1687941714201.png" alt="davidtosenovjan_0-1687941714201.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;davidtosenovjan_0-1687941714201.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 08:42:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1677692#M23880</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-06-28T08:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685764#M23926</link>
      <description>&lt;P&gt;In the first question, do you know why the values stored in the board's flex memory and changed to binary files are different when building as a binary file in CodeWarrior?&lt;BR /&gt;ex)&lt;BR /&gt;Flex status saved on board after firmware&lt;BR /&gt;015A0000 00010110 FFFFFFFF FFFFFFFF&lt;BR /&gt;When you open a binary file after building it as a binary file&lt;BR /&gt;015A0000 00010110 00000000 00000000&lt;BR /&gt;Is there any way to solve the result where FFFFFFFF FFFFFFFF should come out as 00000000 00000000?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 12:09:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685764#M23926</guid>
      <dc:creator>pyi285</dc:creator>
      <dc:date>2023-07-11T12:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685774#M23927</link>
      <description>&lt;P&gt;Are you using .elf/.srec file what usual practice, then only used address ranges are included in the file. Check whether mentioned area is defined in the linker command file.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 12:25:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685774#M23927</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-07-11T12:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685775#M23928</link>
      <description>If so, is there any way to float it with an F other than 0?</description>
      <pubDate>Tue, 11 Jul 2023 12:28:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1685775#M23928</guid>
      <dc:creator>pyi285</dc:creator>
      <dc:date>2023-07-11T12:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1686577#M23934</link>
      <description>&lt;P&gt;I have find a document dealing with this topic:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/13290/1/ANxxxx_Fill_Pattern_feature_DRAFT.pdf" target="_blank"&gt;https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/13290/1/ANxxxx_Fill_Pattern_feature_DRAFT.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 11:11:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1686577#M23934</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-07-12T11:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware and bootloader binary file issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1686955#M23938</link>
      <description>#pragma fill_alignment_data_with_FF on&lt;BR /&gt;&lt;BR /&gt;Can you tell me where to put this?&lt;BR /&gt;I would be very grateful if you could attach a picture&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Jul 2023 01:16:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Firmware-and-bootloader-binary-file-issues/m-p/1686955#M23938</guid>
      <dc:creator>pyi285</dc:creator>
      <dc:date>2023-07-13T01:16:11Z</dc:date>
    </item>
  </channel>
</rss>

