linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erwin Authried <eauth@softsys.co.at>
To: "bluez-users@lists.sourceforge.net" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Has anyone seen these problems with the CSR BlueCore and BlueZ before ?
Date: Thu, 17 Mar 2005 16:35:55 +0100	[thread overview]
Message-ID: <1111073754.1547.9.camel@justakiss> (raw)
In-Reply-To: <E1DBv62-0004qg-Ld@sc8-sf-mx1.sourceforge.net>

Am Don, den 17.03.2005 schrieb Han Hoekstra um 14:30:
> Hey All,
>  
> I'm developping an application on an ARM-7 based platform which is
> running Linux 2.4.18 with the latest BlueZ version for that platform.
> In this application there is a master device that can connect to up to
> 7 slaves (master and slave devices are all the same, the external
> controller determines which is master).
>  
> The application does the following, the external controller on the
> master can send a single command to the Linux application, in the
> command is an address field identifying to which slaves the command
> must be passed on. A slave will pass the command on to its external
> controller, which will respond to the command by sending a reply back
> to the Linux slave, which in turn passes it on to the Linux master and
> is then handed over to the external controller again. As soon as all
> addressed slaves have responded, the sequence is repeated.
>  
> Now to what I see happening, when I run this with 5 slaves, I don't
> see any problems for more than an hour, but when I run it with 6 or 7
> slaves, I see that the BlueCore resets itself, with 6 slaves after
> about 40 minutes and with 7 slaves already after 5 to 10 minutes. When
> I eliminate the CRC check I can run the 7 slaves configuration for up
> to about 40 minutes after it crashes.
>  
> What I think happens is that the BlueCore receives data to fast over
> the air and can not pass it on to the Linux CPU quick enough, so there
> is an internal overflow in the BlueCore.
> Communication between the BlueCore and the Linux CPU is done via BCSP
> at a speed of 921600 baud.
>  
> Has anybody seen behaviour like this before and is there something I
> can do about it ???
>  
Hi,
I had  problems with uart overruns on an embedded ARM7 system that could
be solved by optimisations in the serial driver and hci_bcsp.c. You
should take a look at /proc/tty/driver to see if you get a lot of
overrun errors. What is your cpu, how many Bogomips does the kernel
show?

Regards,
Erwin




-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2005-03-17 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 13:30 [Bluez-users] Has anyone seen these problems with the CSR BlueCore and BlueZ before ? Han Hoekstra
2005-03-17 14:02 ` Marcel Holtmann
2005-03-17 14:19   ` [Bluez-users] Has anyone seen these problems with the CSRBlueCore " Han Hoekstra
2005-03-17 14:58     ` Marcel Holtmann
2005-03-17 15:43       ` [Bluez-users] Has anyone seen these problems with theCSRBlueCore " Han Hoekstra
2005-03-17 15:35 ` Erwin Authried [this message]
2005-03-17 16:28 ` [Bluez-users] Has anyone seen these problems with the CSR BlueCore " Steven Singer
2005-03-17 16:50   ` Marcel Holtmann
2005-03-17 17:50     ` Steven Singer
2005-03-17 19:06       ` Marcel Holtmann

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=1111073754.1547.9.camel@justakiss \
    --to=eauth@softsys.co.at \
    --cc=bluez-users@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 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 NNTP newsgroup(s).