This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
EB40a flash programming, interrupts and multithreading
- From: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- To: "'ecos-discuss \(E-Mail\)'" <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 10 Sep 2003 15:48:34 +0200
- Subject: [ECOS] EB40a flash programming, interrupts and multithreading
Does the scheme below put this issue to bed once and
for all?
1. move all interrupt code and data to ram
2. During flash programming, lock the scheduler
(disable other threads), leave interrupts running.
3. the above should be written such that the user can overide
the default implementation of the flash programming
pre-post sequence, e.g. to only disable certain threads, or
to do nothing(since the app is known to be entirely in ram).
Earlier discussions on this didn't end up with
a conclusion:
http://sources.redhat.com/ml/ecos-patches/2003-08/msg00041.html
Øyvind
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss