Skip to main content
turboscrew
turboscrew
Senior III
February 12, 2019
Question

Weird binary size growth

  • February 12, 2019
  • 3 replies
  • 794 views

Has anyone else stumblen on this?

I had a build configuration, and I needed to do another for a different memory area.

I made a new one with a different name based on the existing configuration, and when it compiled and linked, I removed the old one. Then I made another new one but with different linker script for the other memory area. The linker script file is the same for the original configuration and the first new one, and almost same for the second new one - only the memory areas changed.

But when the original configuration produced about 150 kB binary image, the new ones produce over 300 000 kB image.

Also, the binary image seems to have extension .binary (instead of .bin) and it doesn't seem to be changeable. Why? .bin is conventional, and even ST-link SW wants .bin, it doesn't accept .binary extensions.

This topic has been closed for replies.

3 replies

S.Ma
S.Ma
Principal
February 12, 2019

BIN files are a contiguous block of data. No offset, no "holes".

If the new memory mapping configuration is changed, bin file size may as well.

S19 or HEX file size might remain similar as it's using multiple data fragment with absolute address information for each one of them.

For the file extension change, maybe something was incorrectly setup.

turboscrew
turboscrewAuthor
Senior III
February 12, 2019

Yes, but as I mentioned, for the first new configuration, the linker script is the same. For the second new linker script file, only the memory area for the image was changed.

It was done in MEMORY-block. That is: for one image the FLASH was defined to be 0x08020000 and for the other 0x08080000. Both areas are of the same size (3x128kB = 3 sectors).

turboscrew
turboscrewAuthor
Senior III
February 12, 2019

Also one irritatin thing is that you can only browse for the the linker script file - and one file only. And the path become absolute starting from C:\. You can change that to relative by hand-editing the project files. I think you still can't use more than one linker script file.

turboscrew
turboscrewAuthor
Senior III
February 13, 2019

Reverting to previous version and redoing the last changes fixed the size problem, but another problem emerged. FreeRTOS reboots in its initialization. I haven't yet found out the nature of the problem.

Terms & ConditionsAccessibility statement