From: John Dallaway <john@dallaway.org.uk>
To: Nodir Kodirov <nodir.qodirov@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: how to implement EDF scheduling in eCos
Date: Thu, 28 Jan 2010 21:29:00 -0000 [thread overview]
Message-ID: <4B6201A5.8090007@dallaway.org.uk> (raw)
In-Reply-To: <186ad4051001281013j22eae2a7gbef9b880012bd210@mail.gmail.com>
Hi Nodir
Nodir Kodirov wrote:
>> TRACE: cstartup.cxx [91] void cyg_iso_c_start() 'Resuming cyg_libc_main_thread'
>> TRACE: kapi.cxx [1238] void Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() 'Size of C struct cyg_thread != size of C++ struct Cyg_Thread'
>> ASSERT FAIL: <1> kapi.cxx [1250] Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() Size check failed
>> ASSERT FAIL: kapi.cxx [1250] Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() Size check failed
First, focus on eliminating the structure size mismatch. Whatever member
variables are added to the C++ classes must be mirrored by definitions
in kapidata.h or nothing else will make any sense. Add your changes for
EDF one at a time and ensure the structure sizes match with each change.
Second, are you sure you need to take the address of sched_info in the
following line:
>> edf_info = (cyg_edf_info_t *) &sched_info;
>> priority = (cyg_priority) edf_info->deadline;
sched_info should already be a pointer to a struct cyg_edf_info_t.
I hope this helps...
John Dallaway
eCos maintainer
--
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-28 21:29 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
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 [this message]
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=4B6201A5.8090007@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=nodir.qodirov@gmail.com \
/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).