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 ]  

Broken paths when creating projects

Posted by hermannk on 2016-02-18 08:52

Using STM32CubeMX 4.13.0 I created a project from scratch for an STM32L053. To avoid redundant copies of library files I checked “Add necessary library files as references in the toolchain project conf…”. Among other (9) files, this created the file SW4STM32/${PROJ}/.project. ${PROJ} is the name of the project.

By default, STM32CubeMX sets up a repository at ${HOME}/STM32Cube/Repository, ${HOME} being the home directory of the user. Therefore, the absolute path of the repository should be taken for linking.

However, all links in the file SW4STM32/${PROJ}/.project are prefixed with PARENT-2-PROJECT_LOC. BTW, is there an official documentation for “PARENT-2-PROJECT_LOC”? Though this is reasoanble for project-local files, it is incorrect for the library files.

As a workaround I stripped off the incorrect prefixes for the library files and could import the project successfully as described in the wiki.

Reads: 5158
Link