From: "Han Hoekstra" <Han.Hoekstra@WirelessValue.nl>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Has anyone seen these problems with the CSR BlueCore and BlueZ before ?
Date: Thu, 17 Mar 2005 14:30:56 +0100 [thread overview]
Message-ID: <E1DBv62-0004qg-Ld@sc8-sf-mx1.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
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 ???
Greetings,
Han
---
Han Hoekstra
Wireless Value B.V.
Waanderweg 30a
7812 HZ Emmen
Tel: +31-591-633200
[-- Attachment #2: Type: text/html, Size: 3632 bytes --]
next reply other threads:[~2005-03-17 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 13:30 Han Hoekstra [this message]
2005-03-17 14:02 ` [Bluez-users] Has anyone seen these problems with the CSR BlueCore and BlueZ before ? 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 ` [Bluez-users] Has anyone seen these problems with the CSR BlueCore " Erwin Authried
2005-03-17 16:28 ` 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=E1DBv62-0004qg-Ld@sc8-sf-mx1.sourceforge.net \
--to=han.hoekstra@wirelessvalue.nl \
--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