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

Forum List Topic List

[ prev topic | next topic ]  

Error unknown type name 'HAL_LockTypeDef'

Posted by Ellissar on 2018-01-25 11:45

1. I create a project in CubeMX.
2. Imported into SW4STM32.
3. The compilation is completed without errors.
4. I create in the project c-file gyro_l3gd20.с.
5. I add only 4 lines to it:
#include ‹main.h›
#include ‹stm32f3xx_hal_gpio.h›
#include ‹stm32f3xx_hal_spi.h›
#include ‹sys/_stdint.h›

6. I compile. And I get 100 errors like: unknow type name ‘HAL_StatusTypeDef’ stm32f3xx_hal.h / L3GD20_SPI / Drivers / STM32F3xx_HAL_Driver / Inc line 863 C / C ++ Problem

7. I comment on lines 2 and 3:
#include ‹main.h›
// #include ‹stm32f3xx_hal_gpio.h›
// #include ‹stm32f3xx_hal_spi.h›
#include ‹sys/_stdint.h›

8. The project is compiled without errors.

What am I doing wrong?

I attach a log with errors and a c-file.

errors.zip (1.25 Kb)
Reads: 11286
Link
Posted by Ellissar on 2018-01-25 14:55

As usual, the problem was resolved as soon as I wrote to the forum.
I was helped by the following:

1. I deleted all 4 includes:

  1. include ‹main.h›
  2. include ‹stm32f3xx_hal_gpio.h›
  3. include ‹stm32f3xx_hal_spi.h›
  4. include ‹sys/_stdint.h›


2. And I added one #include ‹stm32f3xx_hal.h›

This was enough for the functions that I use in gyro_l3gd20.c file.

P.S. All 4 non-working #include I added using the combination CTRL + Shift + O.
I do not advise you to use this function so that there are no problems like mine.

Link