Build problems with Cube Tutorial

[RolfSt]

Hi,

I’m getting the following build problem:

Warning        overriding recipe for target `Debug/system_stm32f4xx.o’    CubeDemo    C:\projects\CubeDemo\CubeDemo\Makefile    473
Warning        ignoring old recipe for target `Debug/system_stm32f4xx.o’    CubeDemo    C:\projects\CubeDemo\CubeDemo\Makefile    185
Error        ld returned 1 exit status    CubeDemo    C:\projects\CubeDemo\CubeDemo\collect2.exe    1
Error        Command-line action failed    CubeDemo    C:\projects\CubeDemo\CubeDemo\VisualGDB    1
Error        Build has failed. See the Output window for more details.    CubeDemo    C:\projects\CubeDemo\CubeDemo\EXEC    1
Error    MSB3073    The command “”C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe” /build “C:\projects\CubeDemo\CubeDemo\CubeDemo.vcxproj” “/solution:C:\projects\CubeDemo\CubeDemo.sln” “/config:Debug” “/platform:Win32″” exited with code 1.    CubeDemo    C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets    41

The only difference to the tutorial is, that I selected my Nucleo STM32F446RET6 as target. I’m using VS community 2015 with update 3.

This error occurs in step 16 of tutorial.

[support]

Hi,

Please check the Output window of Visual Studio for details on the error. It should explain why the link fails.

[HorizonBreak]

Hey there.

Had the same problem. Look at your output window for the build. Mine was failing due to multiple definitions of SystemClockUpdate, a result of including STM32F1xx_hal.c (or something like it) twice. I removed the one that STM32CubeMX generated, retaining the version that was included with the HAL package, and my build worked.

Find the function that has multiple definitions, and remove one of the sources of that definition, preferably from the included CubeMX sources. Good luck!

[RolfSt]

Thanx a lot for quick response,

@HorizonBreak: the same cause, I had only to remove – in my case – system_stm32f4xx.c and tutorial worked as described.

[support]

Hi,

Good to know it works. BTW, VisualGDB should normally recognize and display the ‘multiple definition’ errors properly. If you believe this does not happen and those errors are only visible in the Output window, please feel free to post the Output window contents here and we will update our message parser to display them properly.

[Author]

Posts