From: Nodir Qodirov <nodir.qodirov@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] “Big image” of eCos initialization and work flow
Date: Thu, 25 Jun 2009 08:52:00 -0000 [thread overview]
Message-ID: <186ad4050906250151u76e9a9afmca8f57c111274d7e@mail.gmail.com> (raw)
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
HAL-to-kernel transition.
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
board) and
.extern cyg_start
call cyg_start
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,
Nodir.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-06-25 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 8:52 Nodir Qodirov [this message]
2009-06-29 16:13 ` [ECOS] " Nodir Qodirov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=186ad4050906250151u76e9a9afmca8f57c111274d7e@mail.gmail.com \
--to=nodir.qodirov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).