Hello. ST Micro provides a project for a BLDC. They provide a readme with an outline of the process, and simply say to copy over the final binary file to the 3204 without any information on how to make it. I can create the HEX file with uVision 5 and convert this to a BIN using srec_cat. However, the size of the resulting file is over 128k, while the available space on the STEVAL-3204 is only about 42k.
Is there a way to create a much smaller object file, one that I would think has everything not needed stripped out (such as debug code)?
Thank you.
See i.e.:
- "Minimizing code size by eliminating unused functions during compilation"
https://www.keil.com/support/man/docs/armcc/armcc_chr1359124200053.htm
- "Optimizing for code size or performance"
https://www.keil.com/support/man/docs/armclang_intro/armclang_intro_chr1382084370492.htm
- "Methods of reducing debug information in objects and libraries"
https://www.keil.com/support/man/docs/ARMCC/armcc_chr1359124224235.htm
Jeffrs said:However, the size of the resulting file is over 128k, while the available space on the STEVAL-3204 is only about 42k.
The size of a BIN file may not have much of a correlation to the space actually used by the program, depending on aspects like the address mapping of the controller, and/or gaps in the used space. BIN files, by their very nature, cannot usefully represent such gaps. That's why it's almost always better to use HEX files as the flashable file format.
Jeffrs said:Is there a way to create a much smaller object file, one that I would think has everything not needed stripped out (such as debug code)?
Your BIN file is not an object file, so that question makes very little sense. In particular there is no "debug code" left in there to be stripped out.