This is the mail archive of the
mailing list for the eCos project.
“Big image” of eCos initialization and work flow
- From: Nodir Qodirov <nodir dot qodirov at gmail dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Thu, 25 Jun 2009 17:51:54 +0900
- Subject: [ECOS] “Big image” of eCos initialization and work flow
Good time of day!
I am trying to understand initialization of eCos kernel (e.g. when/how
scheduler, clock, interrupt, mutex, messageBox is getting init) and
system’s work flow during rum time. Hence, I can create "Big image" of
eCos init and work flow. Just to make my eCos development better,
while after it will be easier to know where to do modification, in
order to get some specific functionality.
When I have read book of J.Massa “Embedded software development with
eCos” there was told that – kernel (scheduler, clock, interrupt …)
gets fully initialized before cyg_start() method call which serves as
I found from some posts in discussion-list that "_start" in vectors.S
file is the point where we’ll come just after power reset (I have i386
in the same file is point where we’ll start execute kernel. So I have
looked lines between this 2 calls (from “_start” to “cyg_start”), but
I couldn’t find source code for kernel (scheduler, clock, interrupt …)
initialization. I have looked to other external function call as well,
which are in other files. I think there should be such line of codes
(for init), but I’m having difficulties with finding them…
Is there any hint, to find init source code lines?
And to better understand general execution flow of eCos after
cyg_start function call?
Thanking in advance,
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss