This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
scheduler lock is not zero in idle thread
- From: Jürgen Lambrecht <J dot Lambrecht at televic dot com>
- To: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 10 Aug 2006 16:01:46 +0200
- Subject: [ECOS] scheduler lock is not zero in idle thread
Hello,
on my ARM7 platform, I use the bitmap scheduler. Sometimes (after
letting the application run for a day), there comes an assert:
"Scheduler lock not zero". That assert comes I think from the idle
thread (idle_thread_main).
Can this be caused because 2 threads have the same priority (not allowed
with the bitmap scheduler)?
Anyhow, I would like to use the bitmap scheduler because its a simple
deterministic scheduler, but I have problems with all the threads (and
their priorities) hidden in ecos. (for example the network thread, tftp
server thread, jffst garbage collect thread....)
Is there an easy way to see all used threads and their priorities?
Now, I search through ecos.ecc.
Kind regards,
--
Jürgen Lambrecht
Development Engineer
Televic Transport Systems
http://www.televic.com
Televic NV / SA (main office)
Leo Bekaertlaan 1
B-8870 Izegem
Tel: +32 (0)51 303045
Fax: +32 (0)51 310670
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss