Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


moving porject cause different hex

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

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.