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


Syntax for every __weak and __packed

Hi,

Thank you for the feedback.

How did you create your project ? I can’t reproduce your issues (Do you use HAL or Stdperiph and for which target board). SW4STM32 does not redefine the __weak attribute, it is already done in the stm32fYxx_hal_def.h in the HAL_Driver.

#if  defined ( __GNUC__ )
  #ifndef __weak
    #define __weak   __attribute__((weak))
  #endif /* __weak */
  #ifndef __packed
    #define __packed __attribute__((__packed__))
  #endif /* __packed */
#endif /* __GNUC__ */


Regard,
Kevin.
(Ac6)

The project has been generated with STMCubeMX 5.2.0. The MCU is a STM32F103C8T6.
The quotes are present in .mxproject - which I believe is imported by SW4STM32?
Or does STMCubeMX touch the .cproject file directly?

Have you been able to reproduce the issue?

Hi,

Sorry for late answer. I could not reproduce your issue.
If I remember well, STMCubeMX was indeed modifying the .cproject file which means each times you regenerated the project, it sets back the problematic quotes. But I think it was fixed on the latest versions of STMCubeMX.

Regards,
Kevin.

I am using STMCubeMX 5.2.0. That is the latest version. The issue persists. I just created a project for the Nucleo L476RG board. And there are the quotes again. Should I attached a screenshot?

I hope you do not expect to see syntax errors reported by GCC. Instead of being properly escaped, the quotes are stripped at some point and they are not passed to GCC. That of course is a bug in itself (!!!). Anyhow, for the CDT Indexer, the quotes are present, hence it cannot understand the syntax and it cannot properly index the files.

The CDT indexer is still being sabotaged - be it by STMCubeMX or by OpenSTM32. This is harmful to the usability of OpenSTM32.

Right after generating a project for the L476RG Nucleo board with STMCubeMX 5.2.0 with default settings, the file .cproject contains the definitions of packed and weak with quotes in them. That is very very wrong.

Do you have contacts at ST? Do I have to report this to ST?
I vaguely recall, that I already did that and they didn’t care. I have to look through their forums.