From: Peter van der Linden <pjotrdenstora@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Errorhandling in BCSP protocol?
Date: Thu, 3 Feb 2005 06:03:25 -0800 (PST) [thread overview]
Message-ID: <20050203140325.25498.qmail@web52810.mail.yahoo.com> (raw)
Hi all,
I am working with an implementation that has BlueZ
running on a host processor and a CSR BlueCore02 as
Bluetooth chip. The host processor and BlueCore
communicate through BCSP protocol. The BCSP from BlueZ
regularly reports errors like:
bcsp_recv: Short BCSP packet
bcsp_recv: Checksum failed
bcsp_recv: Out-of-order packet arrived, got 1 expected
2
In these cases the BlueCore02 retransmits the BCSP
packet after a timeout.
My question: is there another mechanism than these
timeouts in BCSP protocol? Are BCSP packets that cause
these errormessages acknowledged over the BCSP link?
According to a BCSP protocol document I saw there
should e.g. be a means to send an acknowledgement with
the expected pacletnumber even when the wrong
pzcvketnumber is received. Is this implemented in
BlueZ?
I am running Linux version 2.4.18 with the latest
BlueZ package for that kernel version. The intention
is to switch to Linux 2.6, but not right now!
Regards,
Pjotr
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2005-02-03 14:03 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=20050203140325.25498.qmail@web52810.mail.yahoo.com \
--to=pjotrdenstora@yahoo.com \
--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