Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » moving porject cause different hex
 
Thread actions
Print this page
  • Print all pages

    • moving porject cause different hex

    Posted by ftoffolon on 2015-12-10 12:48

    Dear all,

    I'm working with STM32F205 microcontroller and usually develop on different PC, with different project path. Actually I've developped a bootloadable program where the application part is signed througth CRC. I've noticed that in different PC I've different CRC and different HEX and BIN file, with the same source/toolchain/optimizaiotn and project settings. If I put the project on same path in both PC, CRC match.

    The application is based on Cube project. In first times I've seen some path strings inside compiled file and removing the "assert" option on Cube that strings never come inside code.

    Anyone has some ideas/suggestion to understand moving source path cause differences on compilation ?

    Best regards
    Fabio

    Reads: 9270
    Posted by diabolo38 on 2015-12-12 16:08

    check hex or bin file dif with an hex (hxd for instance) you'll see where is the difference and it shal giev uou some hint at the reason.
    it's hapen that file name date or time are comming from library or debug macro
    argv0 the program name could include project path for instance.
    All this can prevent to rebuild twice the same binary even on same machine same place.