public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Stephenson <pws@csr.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Test Mode
Date: Wed, 01 Dec 2004 10:28:34 +0000	[thread overview]
Message-ID: <200412011028.iB1ASZIk030820@news01.csr.com> (raw)
In-Reply-To: <1101882666.18840.23.camel@pegasus>

> The LMP specification speaks about the Test Mode and Methodology
> saying that Adaptive power control, adaptive freq hopping scenarios
> can be imitated provided the respective LMP PDU's are sent.
> 
> How do I make the HCI commands initiate these LMP PDU's? The HCI
> specification have only the "Test Enable" and "Read and Write
> Loopback"  test commands but other no commands which will result in
> inititating the LM to the testing modes. How do i conduct these
> adaptive tests?

It's quite deliberate that the only thing you can do with a production
device is put it into test mode as a slave
(HCI_Enable_Device_Under_Test_Mode), requiring all test instructions to
be sent from the master.  To do the test end you need a specialist
tester.  These tend to be expensive since they're aimed at manufacturers
doing a lot of testing.

You can use local and remote loopback without any extra hardware
support, however.  They are completely separate from the test modes you
are talking about.

Since the features aren't available over HCI, you need to ask somewhere
else.  However, if you're looking for a cheap way of using the Bluetooth
test modes you're probably out of luck.  Most manufacturers (including
us) provide some simplified but non-standard test commands you can run
between two modules for RF testing and characterisation.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
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

  reply	other threads:[~2004-12-01 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 18:23 [Bluez-users] Test Mode Manjunath Prabhu
2004-12-01  6:31 ` Marcel Holtmann
2004-12-01 10:28   ` Peter Stephenson [this message]
2004-12-01 12:27     ` Manjunath Prabhu
2004-12-01 12:41       ` Peter Stephenson
2004-12-06 14:36     ` Manjunath Prabhu
2004-12-06 14:51       ` Peter Stephenson
2004-12-06 15:05         ` Manjunath Prabhu
2004-12-06 15:41           ` Steven Singer
2004-12-07  7:41             ` Manjunath Prabhu
  -- strict thread matches above, loose matches on Subject: below --
2004-11-30 13:52 Manjunath Prabhu
2004-11-30 14:43 ` Marcel Holtmann
2004-11-30 14:59   ` Manjunath Prabhu

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=200412011028.iB1ASZIk030820@news01.csr.com \
    --to=pws@csr.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