This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with keil microvision 5 and STM32L Discovery

I have a problem with the configuration of Keil microvision 5 with the STM32L Discovery Development board. I set up a template project according to the tutorial present in this page fabioangeletti.altervista.org/.../ that is however for a different version of STM32 board (STM32F0 Discovery).
When I click on the build all button, I receive a lot of error messages. Following is a part of the errors list (176 in total). Any suggestion on how to fix it? Thanks in advance.

.\obj\Project.axf: Error: L6200E: Symbol DAC_IRQHandler multiply defined (by startup_stm32l1xx_md.o and startup_stm32l1xx_hd.o).
.\obj\Project.axf: Error: L6200E: Symbol DAC_IRQHandler multiply defined (by startup_stm32l1xx_mdp.o and startup_stm32l1xx_hd.o).
.\obj\Project.axf: Error: L6200E: Symbol DAC_IRQHandler multiply defined (by startup_stm32l1xx_xl.o and startup_stm32l1xx_hd.o).
.\obj\Project.axf: Error: L6200E: Symbol DMA1_Channel1_IRQHandler multiply defined (by startup_stm32l1xx_md.o and startup_stm32l1xx_hd.o).
.\obj\Project.axf: Error: L6200E: Symbol DMA1_Channel1_IRQHandler multiply defined (by startup_stm32l1xx_mdp.o and startup_stm32l1xx_hd.o).
.\obj\Project.axf: Error: L6200E: Symbol DMA1_Channel1_IRQHandler multiply defined (by startup_stm32l1xx_xl.o and startup_stm32l1xx_hd.o).

Not enough information to list image symbols.
Not enough information to list the image map.
Finished: 2 information, 0 warning and 176 error messages.
".\obj\Project.axf" - 176 Error(s), 0 Warning(s).
Target not created

Parents Reply Children
  • I don't think the problem is compatibility with my development board.
    The compiler gives these error messages after clicking buil all. No programming operation was performed. However the files were downloaded from the ST web site for my development board.

  • I don't think the problem is compatibility with my development board.
    It quite certainly is, for at least one of those source files. Those files might both work for that board, but they appear to be for different CPUs that can be mounted on it.

    But you missed Per's main point, which was about having only one of those files in the build.

    The compiler gives these error messages after clicking buil all.
    Strictly speaking, no. It's the linker that gave those messages. There's a difference worth knowing about.