RE: [arm-gnu] C run-time initialization code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [arm-gnu] C run-time initialization code



No, this isn’t STMicro silicon.  It’s a new microcontroller based on the
M3.  And I’d like to locate the original code so that I’m not involvi*n*g
STMicro code or STMicro copyright.  My guess is that it originally came from
CodeSourcery or some place like that.



The st.com reference is assembly versions of the same code, complete with
mostly the same names.



Thanks,

Richard



*From:* Steve Loudon [mailto:steve.loudon@xxxxxxxxx]
*Sent:* Tuesday, March 09, 2010 11:25 AM
*To:* Richard Gibbs
*Cc:* arm-gnu@xxxxxxxxxxxxxxxx
*Subject:* Re: [arm-gnu] C run-time initialization code





On Mar 9, 2010, at 7:21 AM, Richard Gibbs wrote:



  I’m running freeRTOS on a new Cortex M3 processor and am looking for
sample c start-up code similar to what’s documented in the “Sourcery G++
Lite ARM EABI Sourcery G++ Lite 2009q3-68 Getting Started” documentation.
There’re various startup “c” code files for GCC for the various board
support packages that come with freeRTOS, but they’re  all subject to
copyright by the board vendor.  It looks like it all came from the same
place, as many of the variables and structures are identical.  For example,
the vector table array is named g_pfnVectors and the loop variable used for
copying initialized variables from _eText to _data and for clearing bss is
called pulDest.



Can you help me find this source code?  For freeRTOS, I need to avoid the
standard C heap functions, among other things, since freeRTOS provides its
own completely different versions of these functions.  I also need to avoid
these copyright issues.



Are you using the STM32?  If so, I would start with the Standard Peripheral
Library routines that they provide.  You can download the entire Peripheral
Library at:
http://www.st.com/stonline/products/support/micro/files/stm32f10x_stdperiph_lib.zip.
 In a directory called startup there are gcc, iar and keil assembly routines
for startup.



  Thanks,

Richard



Regards,

Steve Loudon