<?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: SREC Decompilation in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SREC-Decompilation/m-p/776008#M47221</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm not sure if I understand your question? But the S-Records only contain the code and constant data (see &lt;A class="link-titled" href="https://mcuoneclipse.com/2012/09/27/s-record-intel-hex-and-binary-files/" title="https://mcuoneclipse.com/2012/09/27/s-record-intel-hex-and-binary-files/"&gt;S-Record, Intel Hex and Binary Files | MCU on Eclipse&lt;/A&gt; ), so all what you would get from a reverse engineering standpoint is an array of hexadecimal values. If you now the memory map, you can transform this with a disassembler into assembly code with no symbol/variable information: you only will see absolute addresses.&lt;/P&gt;&lt;P&gt;You will not get to the level of C code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Nov 2017 19:54:50 GMT</pubDate>
    <dc:creator>BlackNight</dc:creator>
    <dc:date>2017-11-14T19:54:50Z</dc:date>
    <item>
      <title>SREC Decompilation</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SREC-Decompilation/m-p/776007#M47220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #646464; background-color: #f2f2f5; font-size: 14px;"&gt;Hi, We're new to Kinetis and Motorola S-Record&amp;nbsp;files and are working with FOTA for software updates. Our FOTA tool uses srec files generated through the KDS Cross ARM GNU Create Flash Image option. I just wanted to ask whether we'll be able to decompile our srec file into its original .c files once we compile it?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 18:35:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SREC-Decompilation/m-p/776007#M47220</guid>
      <dc:creator>jennifervolk</dc:creator>
      <dc:date>2017-11-14T18:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: SREC Decompilation</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SREC-Decompilation/m-p/776008#M47221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm not sure if I understand your question? But the S-Records only contain the code and constant data (see &lt;A class="link-titled" href="https://mcuoneclipse.com/2012/09/27/s-record-intel-hex-and-binary-files/" title="https://mcuoneclipse.com/2012/09/27/s-record-intel-hex-and-binary-files/"&gt;S-Record, Intel Hex and Binary Files | MCU on Eclipse&lt;/A&gt; ), so all what you would get from a reverse engineering standpoint is an array of hexadecimal values. If you now the memory map, you can transform this with a disassembler into assembly code with no symbol/variable information: you only will see absolute addresses.&lt;/P&gt;&lt;P&gt;You will not get to the level of C code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 19:54:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SREC-Decompilation/m-p/776008#M47221</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2017-11-14T19:54:50Z</dc:date>
    </item>
  </channel>
</rss>

