cancel
Showing results for 
Search instead for 
Did you mean: 

Compilation problem with Atollic and STM32F100

davidouatt08
Associate II
Posted on January 23, 2013 at 18:06

Hello everybody

I use a STM32F100 micro with Atollic.

I have created a new project and imported some files I needed. The problem is that, when I compile, I get the following error:

\Debug/..\firmware\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO/startup_stm32f10x_hd_vl.s:103: undefined reference to `_sidata'

I have the same problem for _ebss, sdata, sbss...

In my linker file, I have this :

/* used by the startup to initialize data */

_sidata = .;

/* Initialized data sections goes into RAM, load LMA copy after code */

.data : AT ( _sidata )

{

. = ALIGN(4);

_sdata = .; /* create a global symbol at data start */

*(.data) /* .data sections */

*(.data*) /* .data* sections */

. = ALIGN(4);

_edata = .; /* define a global symbol at data end */

} >RAM

Does someone have the solution for that? Thanks
3 REPLIES 3
davidouatt08
Associate II
Posted on January 25, 2013 at 16:27

Hello

It's just an ''Up'' for my topic, I still dont have the solution

Thanks for any help!
Posted on January 25, 2013 at 16:55

Try cloning a working project for the VL-Discovery board. If you do have one that works, you need to understand the files, includes, define, and other meta-data settings that differ from your project settings.

Check if your F100 is in fact a HD device.

I'm not an Atollic fan, I prefer Yagarto's GNU/GCC and MAKE

I would hazard that the issue is that it's not using the linker script you think it is.
Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
davidouatt08
Associate II
Posted on January 28, 2013 at 11:23

You are right, I wasn't using the correct linker script!

Thank you clive1