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


Why does a new empty F4 project with USB-Device_Lib not build?

EDITED

When I select USB_Device_Library to be included in my new project created by STM32Cube_FW_F4_V1.11.0 (not STM32CubeMX version 4.14) for F4Discovery with HAL, I find that a Middleware folder is placed in the stm32f4discovery_hal_lib project folder preventing it build - due to unedited templates etc.

An empty project should build, or be with an instruction.txt file at the root level explaining how the use the USB_Device library so that is does build!!!!

Should I tick checkbox to exclude from build the Middleware folder , then copy only the files I need (e.g CDC class files) from middleware into my own project like in the examples of usb_device projects?

Can someone please say how middleware is supposed to be used so that I can start with something that compiles.

Hi

There is a bug. A header file created by CubeMX has wrongly capitalization.

/Middlewares/ST/STM32_USB_Device_Library/Class/CDC/Inc/USBD_CDC.h

Copy the file to one with lower case name.

If not referred to, the files in Middelware gets not compiled, at least not linked.

Dieter

Thank you Dieter, I will fix that and retry.
Bob

EDIT - I believe this bug is already fixed in in the latest STM32CubeMX version 4.14 code that is generated for the STM32 F4Discovery.