public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001143] Ecos crashes when using "nop" instead of "wfi"
Date: Mon, 07 Feb 2011 08:09:00 -0000 [thread overview]
Message-ID: <20110207080920.738752F78008@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001143-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001143
Martin Blaser <martin.blaser@intefo.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.blaser@intefo.ch
--- Comment #5 from Martin Blaser <martin.blaser@intefo.ch> 2011-02-07 08:09:18 GMT ---
Hi
I'm working on our own hardware with a STM32F103ZEH6 processor and I see the
same assertion. I don't use the default configuration.
I'm having another problem, which could depend on your problem. When a thread
switch from application thread to Idle thread is executed and in this time a
IRQ occurs, the stack of the Idle thread overflows. The timing is very
important: If the IRQ comes earlier, the thread switch to idle isn't done yet
and no overflow occurs. If it comes later, the idle thread seems to have more
time to cleanup the idle stack and no overflow occurs.
Regards
Martin
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-02-07 8:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:17 [Bug 1001143] New: " bugzilla-daemon
2011-02-04 13:37 ` [Bug 1001143] " bugzilla-daemon
2011-02-04 14:22 ` bugzilla-daemon
2011-02-04 21:30 ` bugzilla-daemon
2011-02-07 7:29 ` bugzilla-daemon
2011-02-07 8:09 ` bugzilla-daemon [this message]
2011-02-07 12:21 ` bugzilla-daemon
2011-02-07 14:30 ` bugzilla-daemon
2011-03-04 10:34 ` bugzilla-daemon
2011-03-04 10:49 ` bugzilla-daemon
2011-03-04 12:51 ` bugzilla-daemon
2011-03-04 13:06 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 13:17 [Bug 1001143] New: " bugzilla-daemon
2011-02-04 13:37 ` [Bug 1001143] " bugzilla-daemon
2011-02-04 14:22 ` bugzilla-daemon
2011-02-04 21:30 ` bugzilla-daemon
2011-02-07 7:30 ` bugzilla-daemon
2011-02-07 8:09 ` bugzilla-daemon
2011-02-07 12:21 ` bugzilla-daemon
2011-02-07 14:30 ` bugzilla-daemon
2011-03-04 10:34 ` bugzilla-daemon
2011-03-04 10:49 ` bugzilla-daemon
2011-03-04 12:51 ` bugzilla-daemon
2011-03-04 13:06 ` bugzilla-daemon
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=20110207080920.738752F78008@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@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).