From: Raja Mallik <raja.mallik@moschip.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Thread not starting!
Date: Tue, 07 Jun 2005 04:43:00 -0000 [thread overview]
Message-ID: <1118119323.19118.6604.camel@mazda> (raw)
In-Reply-To: <1118060658.22823.21.camel@hermes>
[-- Attachment #1: Type: text/plain, Size: 2653 bytes --]
Hi Again,
following are the standard test results
The following tests taken from ecos packages and examples are OK
bin_sem0,cnt_sem0,clock0,intr0,kclock0,kflag0,kintr0,ksem0,kthread0,thread0,mutex0
All other kernel tests are failing.
All are generating same type of failures and the traces of that failures
are attached
regards
raja
On Mon, 2005-06-06 at 17:54, Gary Thomas wrote:
> On Mon, 2005-06-06 at 17:27 +0530, Raja Mallik wrote:
> > Hi again,
> >
> > We have use "default" option as template!
> >
> > these are the following packages:
> >
> > here you see the "ARM9 SCP develboard" which is a customized taken from
> > exculibar template..
> >
>
> Have you verified that the standard tests run? Since this is a
> "customized" port, you should do that first. If problems are
> experienced, then you'll know what to look at.
>
> > Packages!
> >
> > ARM common HAL
> > ARM9 SCP develboard
> > ARM9 Variant
> > c library
> > common error code support
> > Dynamic memory allocation
> > I/o sub system
> > ISO C and POSIX infrastructure
> > ISO C library date/time functions
> > ISO C library general utility functions
> > ISO C library internationaliztion
> > ISO C library non local jumps
> > ISO C library signals
> > ISO C library standard inpu/output
> > ISO C library string functions
> > ISO Environment startup/termintaion
> > Infrastructure
> > Math Library
> > Serial device drivers
> > Wall clock device framwork
> > ecos common HAL
> > eCos Kernel
> >
> >
> > regards
> > raja
> >
> >
> > On Mon, 2005-06-06 at 17:16, Gary Thomas wrote:
> > > On Mon, 2005-06-06 at 17:08 +0530, Raja Mallik wrote:
> > > > Hi again,
> > > >
> > > > Please find the tarces.txt and twothreads.c file attaced
> > > > Let me know where am I going wrong?
> > > >
> > > > regards
> > > > Raja
> > > > On Mon, 2005-06-06 at 16:14, Gary Thomas wrote:
> > > > > On Mon, 2005-06-06 at 16:01 +0530, Raja Mallik wrote:
> > > > > > hi
> > > > > >
> > > > > > I am trying to run a thread application.by calling cyg_thread_create
> > > > > > function.
> > > > > >
> > > > > > In the configtool, I have enabled "ASSERT" and while loading the
> > > > > > application to my board, I get this messages!
> > > > > >
> > > > > > I am not able understand why the thread is not getting started..
> > > > > >
> > > > > > Kindly share your views..
> > > > >
> > > > > Did you start the scheduler? Maybe you could show us your code
> > > > > instead of just this trace (it's hard to tell what you've done
> > > > > wrong, all we can see are the results)
> > >
> > > How did you configure your kernel (what template did you use)?
> >
> >
[-- Attachment #2: 1.txt --]
[-- Type: text/plain, Size: 2428 bytes --]
TRACE: mutex.cxx [ 382] void Cyg_Mutex::unlock()
{{enter
TRACE: mutex.cxx [ 447] void Cyg_Mutex::unlock()
}}return void
TRACE: mutex.cxx [ 382] void Cyg_Mutex::unlock()
{{enter
TRACE: sched.cxx [ 705] void Cyg_SchedThread::disinherit_priority()
{{enter
TRACE: sched.cxx [ 628] void Cyg_SchedThread::clear_inherited_priority
() {{enter
TRACE: sched.cxx [ 628] void Cyg_SchedThread::clear_inherited_priority
() }}RETURNING U
NSET!
TRACE: sched.cxx [ 705] void Cyg_SchedThread::disinherit_priority()
}}RETURNING UNS
ET!
TRACE: mutex.cxx [ 447] void Cyg_Mutex::unlock()
}}return void
TRACE: fputc.cxx [ 93] fputc()
}}wrote char 10
TRACE: hal_misc.c [ 211] hal_arch_default_isr()
'Interrupt: 22'
TRACE: hal_misc.c [ 188] hal_default_isr()
'Interrupt: 22, Dat
a: 0x00000000'
TRACE: hal_misc.c [ 211] hal_arch_default_isr()
'Interrupt: 22'
TRACE: hal_misc.c [ 188] hal_default_isr()
'Interrupt: 22, Dat
a: 0x00000000'
TRACE: hal_misc.c [ 211] hal_arch_default_isr()
'Interrupt: 22'
TRACE: hal_misc.c [ 188] hal_default_isr()
'Interrupt: 22, Dat
a: 0x00000000'
[-- Attachment #3: Type: text/plain, Size: 148 bytes --]
--
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:[~2005-06-07 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 10:11 AW: [ECOS] FLASH access from user program Neundorf, Alexander
2005-06-06 10:32 ` [ECOS] Thread not starting! Raja Mallik
2005-06-06 10:44 ` Gary Thomas
2005-06-06 11:40 ` Raja Mallik
2005-06-06 12:21 ` Gary Thomas
2005-06-06 12:03 ` Raja Mallik
2005-06-06 12:24 ` Gary Thomas
2005-06-07 4:43 ` Raja Mallik [this message]
2005-06-07 8:28 ` AW: [ECOS] FLASH access from user program Hans Berglund
2005-06-07 9:36 ` Hans Berglund
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=1118119323.19118.6604.camel@mazda \
--to=raja.mallik@moschip.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.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).