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


Trouble trying to debug test application with System Workbench for stm32

I haven’t been able to figure out how to get this IDE working. I’m stuck trying to start a debugging session for an example code generated on STM32 Cube MX.

I’m using windows 8.1 on a x64 machine with a Stm32f4 Discovery board, but I also have a Stm32f411 Nucleo with equal results.

I’ve followed the instructions on the http://www.openstm32.org/Importing+a+STCubeMX+generated+project?structure=DocumentationQuestion page. The thing is that I still can´t manage to get this thing to debug or compile my test project.
I´ve already installed the updates with the Help>> Check for updates… as recommended on the installation page.
I installed all the updates from “fr.ac6… “
I’m getting the following error message:


Error Capture

The text is:
Error in final launch sequence
Failed to execute MI command:
symbol-file C:\Users\Mauricio\stm32\workspace\DiscoveryTest01\Src\main.c

Error message from debugger back end:
`C:\Users\Mauricio\stm32\workspace\DiscoveryTest01\Src\main.c’: can’t read symbols: File format not recognized.
`C:\Users\Mauricio\stm32\workspace\DiscoveryTest01\Src\main.c’: can’t read symbols: File format not recognized.

I’m also getting this warning in the problems tab on eclipse:
Description Resource Path Location Type
Invalid project path: Include path not found (C:\Users\Mauricio\stm32\workspace\DiscoveryTest01\SW4STM32\DiscoveryTest01 Configuration\Debug). DiscoveryTest01 Configuration pathentry Path Entry Problem

Does anyone know how to solve this problem? I still haven’t been able to figure it out.
Thanks and regards.

France

Hello,

You said you were not able to compile your project; what are the errors when compiling (you can have the details in the console view). If you generate the code from CubeMX and import it as explained it should compile out of the box

Of course there is no interest in trying to debug if it does not compile correctly.

Bernard


I get the following message when building the project:

21:05:51 **** Build of configuration Debug for project DiscoveryTest01 Configuration ****
make all
Building file: C:/Users/Mauricio/stm32/workspace/DiscoveryTest01/SW4STM32/syscalls.c
Invoking: MCU GCC Compiler
%cd%
arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32F407xx -I../../../Inc -I../../../Drivers/STM32F4xx_HAL_Driver/Inc -I../../../Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -I../../../Drivers/CMSIS/Include -I../../../Drivers/CMSIS/Device/ST/STM32F4xx/Include -g3 -Wall -fmessage-length=0 -ffunction-sections -c -MMD -MP -MF”user/syscalls.d” -MT”user/syscalls.d” -o “user/syscalls.o” “C:/Users/Mauricio/stm32/workspace/DiscoveryTest01/SW4STM32/syscalls.c”
make: *** user/syscalls.o Error -1073741502

21:05:59 Build Finished (took 8s.469ms)


Seems like I´m not getting any love here. T-T Guess I´ll look for a different IDE....
France

Hi,

I’m afraid you are running in a Windows 8 incompatibility; Currently System Workbench was only validated against Windows 7, not Windows 8 or 8.1.

I know that there may be at least a problem with the STLink driver provided by ST; System Workbench try to install the Windows-7 version of the driver, while Windows-8 need a different one. You should probably download it directly from the ST website and install it manually; we are working on a solution with ST so that the proper driver will be installed automatically on Windows 8.

Regarding the compilation problem, I really don’t understand the problem you have. Is the
%cd%
stance you mention effectively present in your console?

It should be the directory in which syscalls.o will be generated... The makefile contains a
echo %cd%
sequence that is here just to inform you of where the output will be placed; it seems that Windows 8 cmd.exe command processor does not expand it correctly; however that should not cause any problem, and the compiler call below seems correct, but obviously the compiler fails generating the output file.


Could you open a command line and go to C:/Users/Mauricio/stm32/workspace/Configuration Test01/Debug/user then try to copy paste the compiler call to see what the result is; you should obviously prefix arm-none-eabi-gcc by the correct directory (in folder plugins\fr.ac6.mcu.externaltools.arm-none.win32_1.1.0.201503101257\tools\compiler\bin where you installed System Workbench) as this directory is not in PATH.

Bernard


 

Newest Forum Posts

  1. reservation car service Seattle by Jamesprede, 2025-05-01 10:06
  2. Last day: drone bonus by Danielrug, 2025-04-19 16:55
  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. Insightful Perspectives on This Subject by davidsycle, 2025-03-04 05:45
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  10. Build a project in "release" mode by tang, 2025-02-20 10:36

Last-Modified Blogs