Sysprogs forums › Forums › VisualGDB › Using STM32CubeMX Project Wizard for STM32L053R8T
This topic contains 4 replies, has 2 voices, and was last updated by PeterU 1 week, 1 day ago.
-
AuthorPosts
-
February 23, 2021 at 14:17 #29971
VisualGDBÂ version5.5R4, STM32CubeMX version 6.1.1
Using STM32CubeMX Project Wizard I have been able to create a project for an STM32F030RCT device.
Following the same steps if I try and create a project for a STM32L053R8T device. When I click finish (the final step of the project creation wizard), error messages are displayed in the Log window the fist error message is:
— Configuring done
CMake Error at C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:43 (add_library):
Cannot find source file:There are no source files viewable in the “Solution Explorer” of the created project.
When I navigate to the project folder with window explorer the .c and .h files for the project have been generated/copied to the folder.
February 23, 2021 at 15:28 #29972Hi,
It looks like you have attached an incomplete configuration log. Please make sure you copy the entire log from the VisualGDB Build window (you can use the “Copy All” context menu command). It should provide more context on the error.
February 23, 2021 at 23:54 #29977Configuration log:
C++12345678910111213141516171819202122232425262728293031323334353637383940414243Running CMake: C:\Users\Daniel\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G "Ninja" -DCMAKE_BUILD_TYPE=DEBUG -DTOOLCHAIN_ROOT=c:/sysgcc/arm-eabi -DCMAKE_MAKE_PROGRAM="C:/Program Files (x86)/Sysprogs/VisualGDB/ninja.exe" -DCMAKE_TOOLCHAIN_FILE=C:\Working\stmTest\EmbeddedProject1/build/VisualGDB/Debug/toolchain.cmake -DPLATFORM=VisualGDB -DLOCALAPPDATA=C:/Users/Daniel/AppData/Local-- The C compiler identification is GNU 9.2.1-- The CXX compiler identification is GNU 9.2.1-- The ASM compiler identification is GNU-- Found assembler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe-- Check for working C compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-gcc.exe-- Check for working C compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-gcc.exe -- works-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Detecting C compile features-- Detecting C compile features - done-- Check for working CXX compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe-- Check for working CXX compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe -- works-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Detecting CXX compile features-- Detecting CXX compile features - doneGenerated C:/Working/stmTest/EmbeddedProject1/build/VisualGDB/Debug/BSP.cmake.-- Configuring doneCMake Error at C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:43 (add_library):Cannot find source file:C:/Working/stmTest/EmbeddedProject1/Drivers/STM32L0xx_HAL_Driver/Inc/stm32l0xx_hal_dma_ex.hTried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm.hpp .hxx .in .txxCall Stack (most recent call first):C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:306 (create_bsp_library)CMakeLists.txt:5 (find_bsp)CMake Error at C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:43 (add_library):No SOURCES given to target: BSPCall Stack (most recent call first):C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:306 (create_bsp_library)CMakeLists.txt:5 (find_bsp)CMake Generate step failed. Build files cannot be regenerated correctly.System.Exception: CMake exited with code 1at za.a(l a)========== Project Configuration Summary ==========EmbeddedProject1 configured in 00:05========== Configuration: 1 Succeeded, 0 Failed, 0 Skipped ==========-
This reply was modified 1 week, 2 days ago by
support. Reason: formatting
February 24, 2021 at 10:00 #29981Thanks, this looks like the .gpdsc file generated by the STM32CubeMX tool is referencing a header file that doesn’t exist. This is a bug in the STM32CubeMX tool that is likely specific to a certain device family/package. Please consider reporting it to ST. You can also work around it by simply creating the missing file.
We have also updated VisualGDB to automatically skip the missing files (VisualGDB-5.6.1.4029.msi), however it may lead to unbuildable projects that would require manual adjustment in case STM32CubeMX skips important files.
February 24, 2021 at 12:01 #29983Thanks for solving this issue downloaded and tried the new version of VisualGDB and can now generate the project; was also able to build the project as the missing header file is not reference in any of the source code files.
Have now reported the issue to ST
-
This reply was modified 1 week, 2 days ago by
-
AuthorPosts
You must be logged in to reply to this topic.