From: Nodir Kodirov <nodir.qodirov@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: how to implement EDF scheduling in eCos
Date: Sat, 23 Jan 2010 10:08:00 -0000 [thread overview]
Message-ID: <186ad4051001230207q3ed9c6e8o2b5da1d9241ea99b@mail.gmail.com> (raw)
In-Reply-To: <186ad4051001222328p371f21a9ne00e624a15a01463@mail.gmail.com>
Back after enabling Assertion.
Last line of the assertion is:
*** ASSERT FAIL: <1> kapi.cxx [1250]
Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() Size check
failed
Seems that kernel is checking Cyg_SchedThread_Implementation class
size and as I modified it it throws error. Is it safe, if I disable
size check? Or is there any other way to overcome this problem?
Regards,
Nodir.
On 23 January 2010 16:28, Nodir Kodirov <nodir.qodirov@gmail.com> wrote:
>
> Hi John, Fabian and all,
>
> > Fabian wrote:
> > ah, sorry - the first parameter is meant to be some kind of generic
> > scheduler information parameter not necessarily a static priority. I
> > should have taken a closer look into the documentation before my first
> > comment.
>
> Me too, I thought it to be priority. Thank you for light John! I am
> following your advice.
>
> Now, I added:
>
> typedef struct
> {
> cyg_tick_count deadline;
> cyg_tick_count wcet;
> cyg_tick_count period;
> } cyg_edf_sched_info;
> typedef cyg_edf_sched_info cyg_edf_sched_info_t;
>
> to cyg/kernel/ktypes.h
> Next, I built eCos library and linked my application to it. Run on my
> x86 Advantech target board and it works fine.
>
> Next, I defined additional member variable (to be used in
> Cyg_SchedThread_Implementation class Constructor, to extract
> [deadline, wcet and period] properties from *sched_info* generic
> parameter and use it for schedule() method)
> > cyg_edf_sched_info_t *thread_edf_info;
> to Cyg_SchedThread_Implementation class, where we can define scheduler
> specific members for threads (file src/sched/edf.hxx line #252). You
> can have a look at the same place with mlqueue.hxx.
>
> But, there is problem.
> When I include thread_edf_info to Cyg_SchedThread_Implementation
> class, I can build my eCos library, link it my eCos application and
> port it to board. But, when I run eCos application in target board,
> application halts after thread creation. However, I didn't modify any
> place of neither Cyg_SchedThread_Implementation class constructor nor
> cyg_thread_create() function yet.
>
> So, my question is, can I modify Cyg_SchedThread_Implementation class
> (just adding one more class member variable)?
>
> Herein I have attached my simple eCos application source file also.
> Note: in my target board application halts before printf("Threads are
> created\n"); line.
>
> Any help is highly appreciated!
>
> Thanks,
> 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 prev parent reply other threads:[~2010-01-23 10:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <186ad4051001190626t25f15afds8720515cba54bc91@mail.gmail.com>
2010-01-20 1:25 ` [ECOS] Re: Fwd: " Nodir Kodirov
2010-01-20 15:01 ` [ECOS] " John Dallaway
2010-01-20 15:19 ` Nodir Kodirov
2010-01-21 8:41 ` John Dallaway
2010-01-21 8:58 ` Fabian Scheler
2010-01-23 7:28 ` Nodir Kodirov
2010-01-23 10:08 ` Nodir Kodirov [this message]
2010-01-23 11:23 ` John Dallaway
2010-01-24 5:42 ` Nodir Kodirov
2010-01-24 7:45 ` John Dallaway
2010-01-24 8:19 ` Nodir Kodirov
[not found] ` <186ad4051001260801n195d7543i48855912327f1fe@mail.gmail.com>
[not found] ` <186ad4051001260913pffb9d5bk5d529ffda7252c82@mail.gmail.com>
2010-01-26 17:15 ` Nodir Kodirov
2010-01-27 8:38 ` John Dallaway
2010-01-28 18:13 ` Nodir Kodirov
2010-01-28 21:29 ` John Dallaway
2010-01-31 8:57 ` Nodir Kodirov
2010-01-20 15:25 ` Fabian Scheler
2010-01-08 8:35 Nodir Kodirov
2010-01-08 8:39 ` Nodir Kodirov
2010-01-14 5:35 ` Nodir Kodirov
2010-01-14 6:48 ` Fabian Scheler
2010-01-14 6:50 ` Fabian Scheler
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=186ad4051001230207q3ed9c6e8o2b5da1d9241ea99b@mail.gmail.com \
--to=nodir.qodirov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).