Sysprogs forums › Forums › VisualGDB › Newlies VisualGDB with STM32Cube
Tagged: build a project with STM32Cube
- This topic has 3 replies, 2 voices, and was last updated 7 years, 11 months ago by support.
-
AuthorPosts
-
December 28, 2016 at 09:54 #9877nakornthreeParticipant
I try to build a project with STM32Cube as http://visualgdb.com/tutorials/arm/stm32/cube/. But I found it have some fail as below. Please advise me.
1>—— Build started: Project: Demo, Configuration: Debug Win32 ——
1> VisualGDB: Run “cmd.exe /c “C:\SysGCC\arm-eabi\bin\make.exe” CONFIG=Debug -j8″ in directory “C:\Projects\Demo” on local computer
1>C:\Projects\Demo\Makefile(477): warning : overriding recipe for target `Debug/system_stm32f4xx.o’
1>C:\Projects\Demo\Makefile(185): warning : ignoring old recipe for target `Debug/system_stm32f4xx.o’
1> C:\SysGCC\arm-eabi/bin/arm-eabi-g++.exe -o Debug/Demo.elf -Wl,-gc-sections –specs=nano.specs -TC:\Users\PM-NB031\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32/STM32F4xxxx/LinkerScripts/STM32F446RE_flash.lds -mcpu=cortex-m4 -mthumb -mfloat-abi=soft -Wl,–start-group Debug/system_stm32f4xx.o Debug/startup_stm32f446xx.o Debug/stm32f4xx_hal.o Debug/stm32f4xx_hal_adc.o Debug/stm32f4xx_hal_adc_ex.o Debug/stm32f4xx_hal_can.o Debug/stm32f4xx_hal_cec.o Debug/stm32f4xx_hal_cortex.o Debug/stm32f4xx_hal_crc.o Debug/stm32f4xx_hal_cryp.o Debug/stm32f4xx_hal_cryp_ex.o Debug/stm32f4xx_hal_dac.o Debug/stm32f4xx_hal_dac_ex.o Debug/stm32f4xx_hal_dcmi.o Debug/stm32f4xx_hal_dcmi_ex.o Debug/stm32f4xx_hal_dfsdm.o Debug/stm32f4xx_hal_dma.o Debug/stm32f4xx_hal_dma2d.o Debug/stm32f4xx_hal_dma_ex.o Debug/stm32f4xx_hal_dsi.o Debug/stm32f4xx_hal_eth.o Debug/stm32f4xx_hal_flash.o Debug/stm32f4xx_hal_flash_ex.o Debug/stm32f4xx_hal_flash_ramfunc.o Debug/stm32f4xx_hal_fmpi2c.o Debug/stm32f4xx_hal_fmpi2c_ex.o Debug/stm32f4xx_hal_gpio.o Debug/stm32f4xx_hal_hash.o Debug/stm32f4xx_hal_hash_ex.o Debug/stm32f4xx_hal_hcd.o Debug/stm32f4xx_hal_i2c.o Debug/stm32f4xx_hal_i2c_ex.o Debug/stm32f4xx_hal_i2s.o Debug/stm32f4xx_hal_i2s_ex.o Debug/stm32f4xx_hal_irda.o Debug/stm32f4xx_hal_iwdg.o Debug/stm32f4xx_hal_lptim.o Debug/stm32f4xx_hal_ltdc.o Debug/stm32f4xx_hal_ltdc_ex.o Debug/stm32f4xx_hal_nand.o Debug/stm32f4xx_hal_nor.o Debug/stm32f4xx_hal_pccard.o Debug/stm32f4xx_hal_pcd.o Debug/stm32f4xx_hal_pcd_ex.o Debug/stm32f4xx_hal_pwr.o Debug/stm32f4xx_hal_pwr_ex.o Debug/stm32f4xx_hal_qspi.o Debug/stm32f4xx_hal_rcc.o Debug/stm32f4xx_hal_rcc_ex.o Debug/stm32f4xx_hal_rng.o Debug/stm32f4xx_hal_rtc.o Debug/stm32f4xx_hal_rtc_ex.o Debug/stm32f4xx_hal_sai.o Debug/stm32f4xx_hal_sai_ex.o Debug/stm32f4xx_hal_sd.o Debug/stm32f4xx_hal_sdram.o Debug/stm32f4xx_hal_smartcard.o Debug/stm32f4xx_hal_spdifrx.o Debug/stm32f4xx_hal_spi.o Debug/stm32f4xx_hal_sram.o Debug/stm32f4xx_hal_tim.o Debug/stm32f4xx_hal_tim_ex.o Debug/stm32f4xx_hal_uart.o Debug/stm32f4xx_hal_usart.o Debug/stm32f4xx_hal_wwdg.o Debug/stm32f4xx_ll_fmc.o Debug/stm32f4xx_ll_fsmc.o Debug/stm32f4xx_ll_sdmmc.o Debug/stm32f4xx_ll_usb.o Debug/main.o Debug/stm32f4xx_hal_msp.o Debug/stm32f4xx_hal_timebase_TIM.o Debug/stm32f4xx_it.o Debug/system_stm32f4xx.o -Wl,–end-group
1> Debug/system_stm32f4xx.o:(.data+0x0): multiple definition of `SystemCoreClock’
1> Debug/system_stm32f4xx.o:(.data+0x0): first defined here
1> Debug/system_stm32f4xx.o:(.rodata+0x0): multiple definition of `AHBPrescTable’
1> Debug/system_stm32f4xx.o:(.rodata+0x0): first defined here
1> Debug/system_stm32f4xx.o:(.rodata+0x10): multiple definition of `APBPrescTable’
1> Debug/system_stm32f4xx.o:(.rodata+0x10): first defined here
1> Debug/system_stm32f4xx.o: In function `SystemInit’:
1> system_stm32f4xx.c:(.text.SystemInit+0x0): multiple definition of `SystemInit’
1> Debug/system_stm32f4xx.o:system_stm32f4xx.c:(.text.SystemInit+0x0): first defined here
1> Debug/system_stm32f4xx.o: In function `SystemCoreClockUpdate’:
1> system_stm32f4xx.c:(.text.SystemCoreClockUpdate+0x0): multiple definition of `SystemCoreClockUpdate’
1> Debug/system_stm32f4xx.o:system_stm32f4xx.c:(.text.SystemCoreClockUpdate+0x0): first defined here
1>collect2.exe : error : ld returned 1 exit status
1> make: *** [Debug/Demo.elf] Error 1
1> ————————————————————-
1> Command exited with code 2
1> Executable: cmd.exe
1> Arguments: /c “C:\SysGCC\arm-eabi\bin\make.exe” CONFIG=Debug -j8
1> Directory: C:\Projects\Demo
1>VisualGDB : error : Command-line action failed
1>EXEC : error : Build has failed. See the Output window for more details.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(37,5): error MSB3073: The command “”C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe” /build “C:\Projects\Demo\Demo.vcxproj” “/solution:C:\Projects\Demo\Demo.sln” “/config:Debug” “/platform:Win32″” exited with code 1.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========Thank you.
December 29, 2016 at 04:11 #9882nakornthreeParticipantI have found it. A problem are became from ,config stm32Cube with Board selector. So I ‘m config with MCU Selector that it have other problem but it can fix by delete duplicate Driver-specific files.
December 29, 2016 at 04:58 #9883nakornthreeParticipantOther problem Frame not in module??
December 30, 2016 at 00:17 #9898supportKeymasterYou can remove the VisualGDB-supplied system file and other files via VisualGDB Project Properties -> Embedded Frameworks.
Simply uncheck the “STM32 HAL” and other similar ones and those files will be removed.
The ‘frame not in module’ problem happens when your program triggers an exception outside the known sources. Please check the Call Stack window to see what could be causing it.
If you are not sure, please set a breakpoint in the Reset_Handler function and step through your code to see at which point the error occurs.
-
AuthorPosts
- You must be logged in to reply to this topic.