Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


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

Hello,

After upgrading the System Workbench to V2.5.0, I get some “builtin-declaration-mismatch” warnings.
Example:
../../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.

Thanks

France

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.

Thanks

France

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.

Bernard


 

Newest Forum Posts

  1. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  2. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  3. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  4. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  5. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  6. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  8. Build a project in "release" mode by tang, 2025-02-20 10:36
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35
  10. Fail to debug in Win 11 C/C++ by mortenlund, 2024-12-26 20:27

Last-Modified Blogs