Difference in ending of .bin files

[yuri CH]

Posted on March 13, 2018 at 13:07

Hello!

i have been working on an application which allows me to flash a binary file into the MCU memory and thus

updating the firmware application.

When i flash the .bin file using my app i am able to transfer the file but its ending is different from

the one flashed by the 'stm32CubeProgrammer' as shown in the attached snapshot. please note that

besides the ending all other bytes are the same.

i am working with the stm32f7 on IAR embedded workbench version 8.11, the .bin file is created

the IDE's output converter.

What's the meaning of this file ending? is this some sort of checksum? am i doing something wrong?

please advise.

[Pavel A.]

Posted on March 13, 2018 at 16:47

Does your bin file actually end with FF F7 FE EF or 00 00 00 00 ?

(view in a decent binary editor)

-- pa

[yuri CH]

Posted on March 13, 2018 at 17:11

Hi,

it does end with FF F7 FE BF  ...

[Pavel A.]

Posted on March 13, 2018 at 18:13

Then, in your app pad the data up to 64 bytes boundary (it looks so) with 1A, and it will be same as with the 

stm32CubeProgrammer.

-- pa

[Tesla DeLorean]

Posted on March 13, 2018 at 18:42

0x1A (26) is a frequent end-of-file marker, likely to see in X-MODEM type methods as a fill character for 128 or 1KB packets.