Re: Startup code
- From: "Jet Morgan" <jm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 11:24:41 +0100
"Meindert Sprang" <mhsprang@xxxxxxxxxxxxxxxxxxx> wrote in message
news:11c4t1rcaohggba@xxxxxxxxxxxxxxxxxxxxx
> 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.
That is still startup code, even if written in C.
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.
The compiler vendor will not typically know how the processor
is connected to the other devices, such as memory bus widths,
clock timings etc. That's why YOU (the designer) has to write it.
There seems to be this perception that startup code is specifically
assembler. It *could* be written that way but I've always
written my startup code in a combination of C and assembler.
Richard [in PE12]
.
- Follow-Ups:
- Re: Startup code
- From: Chris Hills
- Re: Startup code
- From: Meindert Sprang
- Re: Startup code
- References:
- Startup code
- From: ravikumar . n
- Re: Startup code
- From: Jet Morgan
- Re: Startup code
- From: Meindert Sprang
- Startup code
- Prev by Date: Re: Startup code
- Next by Date: Re: CLIL source code from book "Firmware demystified"
- Previous by thread: Re: Startup code
- Next by thread: Re: Startup code
- Index(es):
Relevant Pages
|