Thursday, February 22nd 2018, 11:50am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Aug 16th 2017

Posts: 14


Friday, December 1st 2017, 10:48am

[SOLVED] Object bin file created with SES is too big...

Hi there,

I did compile a project for STM32F746NG using internal and external flash. Anyway, the additional .bin file created seems to be to big, i.e. the .elf is around 2.9MB and the .bin file is 2.12GB. When I try to load it with J-Link, the J-Link crashes.
Any suggestions?

Thanks in advance,


Super Moderator

Date of registration: Jan 2nd 2017

Posts: 716


Friday, December 1st 2017, 10:58am

Hello Victor,

Thank you for your inquiry.

The problem with bin files is that they fill up any memory gaps.
So if you use internal flash at 0x0 and external flash at e.g. 0x40... this memorygap gets filled up with 0xFF.
That is why you suddenly get several GB data instead of just a couple of MB.

We suggest using either hex or srec/mot as additional output format as these formats act "smarter".

Best regards,



Date of registration: Aug 16th 2017

Posts: 14


Friday, December 1st 2017, 11:28am

Hello Nino,

Thank you for the fast response. This makes sense as the internal flash is on 0x0800 0000 and the QSPI is on 0x9000 0000. I'll use .hex file as output.

Consider the thread solved.