STM32MP1 support available in SW4STM32

   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 download a short video showcasing this on the ac6-tools website (registration required).

System Workbench for STM32

"builtin-declaration-mismatch" warnings after update to V2.5.0


After upgrading the System Workbench to V2.5.0, I get some “builtin-declaration-mismatch” warnings.
../../eCos_install/include/unistd.h:267:13: warning: declaration of ‘int execve(const char*, char**, char**)’ conflicts with built-in declaration ‘int execve(const char*, char* const*, char* const*)’ -Wbuiltin-declaration-mismatch

I compile with the eCos library, Is there a way to disable these warnings.



Hi Guy,

There are two solutions:

  1. Add -Wno-builtin-declaration-mismatch in the Other flags setting of the MCU GCC Compiler Miscellaneous tab
  2. Correct the eCos declarations to match the standard confused

The first solution is simple, but may mask real errors. The second is longer but safer; however you will have to correct eCos code after each eCos update (unless you are able to submit the correction to eCos...), something that would be simpler if you manage the eCos code under SVN or GIT as updates will retain your corrections.

Hope this helps,

Bernard (Ac6)

Thanks Bernard for the help,

maybe something linked to:
When I highlight an included file, for ex: and then press F3, the system opens the AC6 included file, I would like the eCos file.
It is possible to disable the link to the AC6 include.



Hi Guy,

For the order of includes, go in project properties >> C/C++ General >> Paths and Symbols >> Includes; there you will see all include files directories, in the order they are searched. Ensure the eCos directories are there, probably before all others.

Also it’s possible that some symbols have to be defined for the content of the eCos files to be visible; try to set these in the Symbols tab.