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 two short videos (registration required) highlighting:

System Workbench for STM32


You are viewing a reply to Adding new Include files  

Adding new Include files

France

Hi,

The “could not be resolved” errors are in fact not due to not referencing some files but to reference useless header files... In fact CubeMX provides the header files for all supported chips, not just the one used, and these header files are not protected by #ifdefs inside the file but around the #include that references them...

The net effect is that, by default, System Workbench will see several definitions for, say, SysTick_IRQn, and has no clue to which one is the right one, so the “could not be resolved” message.

To correct that you just have to switch System Workbench to only parse header files that are effectively included in your source files, either globally (in Window >> Preferences >> C/C++ >> Indexer) or just for the current project (in project >> Properties >> C/C++ General >> Indexer and checking the Enable project specific settings checkbox) and uncheck the Index unused headers checkbox.

Detailed explanations are in this FAQ: ((http://www.openstm32.org/tiki-view_faq.php?faqId=4#q21|Why did the IDE complains that SysTick_IRQn can’t be resolved when my project compile cleanly?))

Bernard (Ac6)