<?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>S32 Design Studio中的主题 Re: S32DS Post-build step</title>
    <link>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/754223#M2669</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lutz,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I didn't find way how to execute post-build after .hex file dump. I'll put feature request for S32DS - In my opinion the post-build step should be really "post-build".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a workaround you can include hex file dump into your post build .bat file like this (I'm not sure if you are using ARM S32DS - for Power it is similar):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;arm-none-eabi-objcopy -O ihex&amp;nbsp; project.elf&amp;nbsp; &amp;nbsp;project.hex&lt;/P&gt;&lt;P&gt;your_post_build_commands&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Dec 2017 08:48:07 GMT</pubDate>
    <dc:creator>jiri_kral</dc:creator>
    <dc:date>2017-12-04T08:48:07Z</dc:date>
    <item>
      <title>S32DS Post-build step</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/754222#M2668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want execute a *.bat file after building the *.hex image.&lt;/P&gt;&lt;P&gt;When I use the the *.bat file in the Post-build steps, then the *.bat file is executed before the hex-file is created.&lt;/P&gt;&lt;P&gt;How can I start the *.bat file after building the *.hex image automatic in the build process?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR Lutz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2017 12:05:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/754222#M2668</guid>
      <dc:creator>koehlerl</dc:creator>
      <dc:date>2017-12-01T12:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: S32DS Post-build step</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/754223#M2669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lutz,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I didn't find way how to execute post-build after .hex file dump. I'll put feature request for S32DS - In my opinion the post-build step should be really "post-build".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a workaround you can include hex file dump into your post build .bat file like this (I'm not sure if you are using ARM S32DS - for Power it is similar):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;arm-none-eabi-objcopy -O ihex&amp;nbsp; project.elf&amp;nbsp; &amp;nbsp;project.hex&lt;/P&gt;&lt;P&gt;your_post_build_commands&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2017 08:48:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/754223#M2669</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2017-12-04T08:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: S32DS Post-build step</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/1315522#M7686</link>
      <description>&lt;P&gt;same question@&lt;SPAN&gt;07-30-2021&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 01:11:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/S32DS-Post-build-step/m-p/1315522#M7686</guid>
      <dc:creator>huigangshi</dc:creator>
      <dc:date>2021-07-30T01:11:01Z</dc:date>
    </item>
  </channel>
</rss>

