From: Catalin Drula <catalin.drula@imag.fr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Handling a Hardware Error event on iPAQ h5550
Date: Thu, 17 Mar 2005 15:59:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20050317T164923-411@post.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.33.0503171141200.22782-100000@redbean.intranet.gw-instruments.de
Peter Wippich <pewi <at> gw-instruments.de> writes:
> It may be much simpler trying to find the cause of the data corruption.
> Do you have hardware handshake enabled ??
> Have you tried different baud rates ??
> Do you get any errors from the UART driver (like FiFo overruns) ??
> Have you tried to modify the UART FiFo settings ??
Well, I'm over 5 weeks into finding the cause of the data corruption.
At first there were indeed overruns when receving. It turns out that
on the processor of this device (Intel XScale PXA255) there's a HWUART
(a UART with HW flow control capabilities) connected to the same lines
as the "default" UART for communicating with the BT controller
(this default UART is called BTUART). Changing to the HWUART solved the
overruns problem.
The problems now occur on the sending direction (host to controller).
There is hardware flow control although the controller never deasserts
the RTS (never tells the host to stop sending). There are no FIFO
overruns, the FIFO does not overfill or anything like that.
The speed of communication and the parameter appear to be hard coded in
the BT module as 921600, 8N1 so there's not much to do there.
In fact even with an artificial slow-down of the sending stream (down to
a few K/sec) these corrupted bytes still show. I could not correlate them
with anything else even after weeks of testing and instrumenting the
kernel. There's really not much else that I can think of that could be
wrong on the host side. I am unsure if the same problem occurs under
Windows CE on this device, but apparently it does not.
Catalin
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-03-17 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 10:23 [Bluez-devel] Handling a Hardware Error event on iPAQ h5550 Catalin Drula
2005-03-17 10:56 ` Peter Wippich
2005-03-17 11:06 ` Marcel Holtmann
2005-03-24 11:39 ` [Bluez-devel] " Catalin Drula
2005-03-24 11:46 ` Marcel Holtmann
2005-03-24 12:17 ` Catalin Drula
2005-03-24 12:35 ` Marcel Holtmann
2005-03-17 15:59 ` Catalin Drula [this message]
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=loom.20050317T164923-411@post.gmane.org \
--to=catalin.drula@imag.fr \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.