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


SystemWorkBench Includes problem on Linux - OK on Windows (From a CubeMX project)

Hello,
Generating exactly the same code on Windows (CubeMX -> AC6) works but not on Linux, the same process results in many complains from the compiler
about many ‘unknown type name xxxx’ !
Is the problem in CubeMX ? Seems not as the includes defining the names types *are well* in the code but seem to be skipped/not seen by Eclipse/gcc ?
Example:
stm32h7xx_hal_mdam.h cannot compile because of:

HAL_StatusTypeDef HAL_I2C_Mem_Read_DMA(I2C_HandleTypeDef *hi2c, uint16_t DevAddress, uint16_t MemAddress, uint16_t MemAddSize, uint8_t *pData, uint16_t Size);

~~<span style="color”><span style="color”><span style="color”><span style="color”><span style="color”> In file included from /home/jea/ws_stm32/H7_UART6/Inc/stm32h7xx_hal_conf.h”>309:0,

from /home/jea/ws_stm32/H7_UART6/Drivers/STM32H7xx_HAL_Driver/Inc/stm32h7xx_hal.h:48,
from /home/jea/ws_stm32/H7_UART6/Drivers/CMSIS/Device/ST/STM32H7xx/Include/stm32h7xx.h:180,
from /home/jea/ws_stm32/H7_UART6/Drivers/STM32H7xx_HAL_Driver/Inc/stm32h7xx_hal_def.h:48,
from /home/jea/ws_stm32/H7_UART6/Drivers/STM32H7xx_HAL_Driver/Inc/stm32h7xx_hal_uart.h:47,
from ../Src/uartmessage.c:3:
/home/jea/ws_stm32/H7_UART6/Drivers/STM32H7xx_HAL_Driver/Inc/stm32h7xx_hal_mdma.h:231:1: error: unknown type name ‘HAL_LockTypeDef’
HAL_LockTypeDef Lock;

/home/jea/ws_stm32/H7_UART6/Drivers/STM32H7xx_HAL_Driver/Inc/stm32h7xx_hal_mdma.h:631:1: error: unknown type name ‘HAL_StatusTypeDef’
HAL_StatusTypeDef HAL_MDMA_Init(MDMA_HandleTypeDef *hmdma);

BUT “HAL_LockTypeDef Lock” is defined in “stm32h7xx_hal_def.h” which is well included at the beginning of “stm32h7xx_hal_mdam.h” and all the include
access paths are there in the project !?

So, gcc is going crazy ?

Thanks,
J.

I use CubeMX generated projects on Linux with SystemWorkbench, they work fine.

From memory there are two ways to include the firmware (as references or copied into your project - just checked in CubeMX Project Menu, Project Settings, Code Generator tab)... I use the copy method and that seems to work ok.


 

Newest Forum Posts

  1. Монтаж камина с грилем в Москве - установка и барбекю by KpddomErorb, 2025-05-10 18:28
  2. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  3. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  4. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  5. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  6. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  9. Build a project in "release" mode by tang, 2025-02-20 10:36
  10. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35

Last-Modified Blogs