From: Iris Lindner <ilindner@logopak.de>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] FLASH API v.2 and interrupts
Date: Fri, 02 Oct 2009 10:35:00 -0000 [thread overview]
Message-ID: <200910021236.44312.ilindner@logopak.de> (raw)
Hi everyone,
(Please excuse if I have overlooked a solution to our problem in mailing lists
for example.)
we have the following problem with our system (using redboot romram mode):
We can't properly harmonize flash operations and interrupt handling. There are
regularly frames coming in on CAN bus (lifesign signals of the nodes) which
have to be treated.
We use Version 1 eCos FLASH API (chip: Spansion S29GL256P) and get terrible
crashes (including completely empty flash afterwards) when interrupts are NOT
disabled and flash is programmed for example when meanwhile CAN bus traffic
is increased.
If we disable interrupts on device driver level (HAL_[DISABLE|
RESTORE]_INTERRUPTS()) flash operations all work fine
but CAN frames get lost and the task goes offline (-> whole machine no longer
able to work).
Could Version 2 of eCos FLASH API solve the problem? (It is interrupt safe
now, isn't it?)
Do you need more information about our system/configuration (I'm not sure
about what details are useful to know)?
Thank you very much in advance for your help, I'm looking forward to any
comment!
Kind regards,
Iris Lindner
--
Iris Lindner
Software Development
Industrial Print and Apply Labelling
www.Logopak.com
--
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 reply other threads:[~2009-10-02 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 10:35 Iris Lindner [this message]
2009-10-02 10:50 ` [ECOS] IDE failed to identify unit 0 - wrote: a0, read: 7f Jim Bradleigh
2009-10-02 14:06 ` [ECOS] Debugging Redboot Jim Bradleigh
2009-10-07 16:20 ` Bart Veer
2009-10-02 11:13 ` [ECOS] FLASH API v.2 and interrupts Stanislav Meduna
2009-10-07 16:55 ` Bart Veer
2009-10-07 17:30 ` Paul D. DeRocco
2009-10-07 18:46 ` Bart Veer
2009-10-08 11:22 ` Iris Lindner
2009-10-08 13:50 ` Bart Veer
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=200910021236.44312.ilindner@logopak.de \
--to=ilindner@logopak.de \
--cc=ecos-discuss@ecos.sourceware.org \
/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).