public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Simon Kallweit <simon.kallweit@intefo.ch>
To: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Bug in STM32 serial driver
Date: Tue, 22 Jun 2010 15:40:00 -0000	[thread overview]
Message-ID: <4C20D95C.6020101@intefo.ch> (raw)

Hi there

I discovered that high transfer loads on the UART can crash my 
application on the STM32. I wrapped up a little demo application which 
can be used to reproduce the error. See 
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000974 for details.

Can anyone with an STM3210E-EVAL board please try and see if they 
experience the same behavior? I suspect the error comes from the high 
interrupt load. Maybe the crash even results from a bug in the arch 
port. I did not yet discover where the bug comes from, but I can 
reproduce the behavior on both our custom hardware and the evaluation board.

I'd be very glad if someone else could take a look into this as well. 
Looks a bit nasty :)


Simon

                 reply	other threads:[~2010-06-22 15:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C20D95C.6020101@intefo.ch \
    --to=simon.kallweit@intefo.ch \
    --cc=ecos-devel@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).