Re: Startup code
- From: "Meindert Sprang" <mhsprang@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 12:13:13 +0200
"Jet Morgan" <jm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:d9trqi$rgb$1@xxxxxxxxxxxxxxxxxxxxxxx
> "startup code" is a fragment of program that gets the "environment"
> ready for use by (typically) a higher level language: setting
> up chip-selects, bus widths, processor options, stack pointers
> (all the stuff that doesn't really fit in to the way e.g. C works).
>
> Startup code will be specific to the particular processor that
> you are using, and will be specific to the way the processor
> is connected to the other devices in your design. You have to write it.
I'd like to disagree with this. In all compilers I used so far, the startup
code only set's up the very basic things like the stack pointer, code and
data segments dependig on the CPU used and initializing all variables and
constants. The rest, like further processor and peripheral initialisation is
done in user written C functions. And so far, I have never written start up
code, I could always use the start up code supplied by the compiler vendor,
which is automatically chosed and configured by most IDE's.
My experience anyway,
Meindert
.
- Follow-Ups:
- Re: Startup code
- From: Bob Stephens
- Re: Startup code
- From: Jet Morgan
- Re: Startup code
- References:
- Startup code
- From: ravikumar . n
- Re: Startup code
- From: Jet Morgan
- Startup code
- Prev by Date: Re: Startup code
- Next by Date: Re: Startup code
- Previous by thread: Re: Startup code
- Next by thread: Re: Startup code
- Index(es):