This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
manual:ports:tricore_tc3 [2022/11/07 12:23] voorburg [Post-process the Motorola S-record] |
manual:ports:tricore_tc3 [2023/09/18 11:29] (current) voorburg [Post-process the Motorola S-record] |
||
---|---|---|---|
Line 58: | Line 58: | ||
Eclipse CDT based IDEs include a configuration option, where you can configure a command to run as a post-build step. This is the ideal location to call the batch-file: | Eclipse CDT based IDEs include a configuration option, where you can configure a command to run as a post-build step. This is the ideal location to call the batch-file: | ||
+ | |||
+ | {{:manual:ports:tricore_tc3_postbuild_step.png|}} | ||
+ | |||
+ | This approach works for version 1.9.8 and newer of the AURIX Development Studio. Older versions (e.g. 1.7.2) of the AURIX Development Studio have a problem with the post-build steps. Whatever command you enter will result in a build error. | ||
+ | |||
+ | Luckily, there is a simple workaround for this. At the end of a build, the AURIX Development Studio calls the tool "elfsize" to print size information about the firmware's ROM and RAM usage. You can hijack its command to additionally call the "postbuild.bat" batch-file. Simply change the Print Size command line pattern from: | ||
+ | <code> | ||
+ | ${COMMAND} ${INPUTS} ${FLAGS} | ||
+ | </code> | ||
+ | |||
+ | to: | ||
+ | |||
+ | <code> | ||
+ | ${COMMAND} ${INPUTS} ${FLAGS} && ${ProjDirPath}/Cmd/postbuild.bat "${BuildArtifactFileBaseName}.srec" | ||
+ | </code> | ||
+ | |||
+ | {{:manual:ports:tricore_tc3_postbuild_hack.png|}} | ||
+ | |||
+ | When the calling of the "postbuild.bat" batch-file is properly configured, you can see the following output in the Console-window at the end of the build: | ||
+ | |||
+ | {{:manual:ports:tricore_tc3_postbuild_console.png|}} | ||