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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel