public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: khoffmann@mmm.com
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Scheduler problem with MPC855T port
Date: Wed, 14 Mar 2007 08:55:00 -0000	[thread overview]
Message-ID: <20070314085536.GA29955@lunn.ch> (raw)
In-Reply-To: <OF3456E89B.91A0CA5C-ONC125729E.002820A5-C125729E.002C8185@mmm.com>

On Wed, Mar 14, 2007 at 09:06:06AM +0100, khoffmann@mmm.com wrote:
> Hello everybody,
> 
> I've got a problem with my attempts to port eCos to our MPC855T board:
> 
> I started with the FADS template (which I now know, was not the best idea) 
> and got so far that I can access my RAM, my FLASH, the UARTs and the FEC 
> (at least I can see the DHCP requests on the net).
> 
> When I compile the 'twothreads' example, I can find a bunch of threads in 
> the internal threadlist, obviously everything fine, some 'SLEEPING', some 
> 'RUNNING'.
> 
> But after each thread has  run once, the processor is only looping  throug 
> the main_idle_thread() and it's doing nothing else. The trace issues the 
> following a short time before the endless 'loop' (where the 'loop' is 
> probably triggered by an external interrupt).
> 
> TRACE: <2>[447]void Cyg_Mutex::unlock() return void
> TRACE: <2>[709]void Cyg_Alarm::initialize() enter
> TRACE: <2>[277]void Cyg_Counter::add_alarm() enter
> TRACE: <2>[277]void Cyg_Counter::add_alarm() RETURNING UNSET!
> TRACE: <2>[709]void Cyg_Alarm::initialize() RETURNING UNSET!
> TRACE: <2>[351]static void Cyg_Thread::sleep() enter
> TRACE: <2>[271]void Cyg_Scheduler_Implementation::rem_thread() enter
> TRACE: <2>[271]void Cyg_Scheduler_Implementation::rem_thread() 
> thread=0045de10
> TRACE: <2>[325]void Cyg_Scheduler_Implementation::rem_thread() return void
> TRACE: <2>[372]static void Cyg_Thread::sleep() return void
> TRACE: <2>[741]void Cyg_ThreadQueue_Implementation::enqueue() enter
> TRACE: <2>[741]void Cyg_ThreadQueue_Implementation::enqueue() 
> thread=0045de10
> TRACE: <2>[818]void Cyg_ThreadQueue_Implementation::enqueue() return void
> TRACE: <2>[119]Cyg_Thread* Cyg_Scheduler_Implementation::schedule() enter
> TRACE: <2>[192]Cyg_Thread* Cyg_Scheduler_Implementation::schedule() 
> returning thread 00419070
> TRACE: <2>[87]static void Cyg_HardwareThread::thread_entry() enter
> TRACE: <1>[1239]void idle_thread_main() enter
> TBSCR 0001, vec 15: sivec 3c000000, simask 10010000, sipend 40020000
> TBSCR 0001, vec 15: sivec 3c000000, simask 10010000, sipend 40020000
> TBSCR 0001, vec 15: sivec 3c000000, simask 10010000, sipend 40000000
> TBSCR 0001, vec 15: sivec 3c000000, simask 10010000, sipend 40020000
> TBSCR 0001, vec 15: sivec 3c000000, simask 10010000, sipend 40000000
> ... ad infinitum ...
> 
> I probably missed something, but what?


Timer tick. Run some of the kernel timer tests. I expect they will all
fail because your timer is not ticking.

     Andrew

  reply	other threads:[~2007-03-14  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14  8:06 khoffmann
2007-03-14  8:55 ` Andrew Lunn [this message]
2007-03-15  7:53   ` khoffmann
2007-03-15  8:28     ` Andrew Lunn
2007-03-15 11:15       ` Gary Thomas

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=20070314085536.GA29955@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=khoffmann@mmm.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).