From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] HCI data bits corruption
Date: Wed, 08 Dec 2004 20:16:11 +0100 [thread overview]
Message-ID: <1102533371.9988.85.camel@pegasus> (raw)
In-Reply-To: <2de46576041208102112be98ee@mail.gmail.com>
Hi Manjunath,
> I am communicating between 2 d-link DBT-120 dongles. I am using the
> l2test for sending known data. I am using the DH packets to avoid FEC.
> I am measuring the link quality for various scenarios.
> I try and compare the link quality values to corresponding BER values
> as per the CSR article at your website. I use hcidump to record
> received bytes, but with link quality dropping as low as 180-170, I am
> unable to see any corrupted bits. With the l2test, the connection
> terminates even before the assigned bytes are sent with link quality
> going bad, but there is no data corruption. Could you tell me how I
> could get the corrupted data bits???I want some sort of error over air
> interface.
there might be some CSR vendor commands to get these information, but
the HCI specification has no standard way for it. However the ACL link
is per definition reliable.
> I am also looking to study the behaviour of HCI and LM firmware. Is
> this available at the Bluez or are the firmware well guarded by the
> manufacturers and not to be given to users.
The lower part of the HCI is part of the firmware. Actually the HCI
commands and events are abstractions to the LMP. You can do everything
what is written in the HCI specification and everything below that is up
to the manufacturers.
> I also wanted to know if there are any bluetooth Test development kit,
> in hardware and software as we could build a BT device. Buying a
> Trainer/Analyser is a little over budget for my project.
Sorry, but I think you need expensive hardware for this.
Regards
Marcel
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-12-08 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 18:21 [Bluez-users] HCI data bits corruption Manjunath Prabhu
2004-12-08 19:16 ` Marcel Holtmann [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=1102533371.9988.85.camel@pegasus \
--to=marcel@holtmann.org \
--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