From: David Thornton <david@villagepublishing.com.au>
To: linux-bluetooth@vger.kernel.org
Subject: bccmds
Date: Tue, 30 Dec 2008 16:15:14 +1100 [thread overview]
Message-ID: <4959AE62.8020605@villagepublishing.com.au> (raw)
Thanks,
I looked at bccmd.c in /tools right after you posted - and hence solved
my problem.
I am, though, getting a strange error after sending an HCI inquiry command.
here are the first 15 lines of each response:
thingo: 0x04
thingo: 0x0f
thingo: 0x04
thingo: 0x00
thingo: 0x01
thingo: 0x00
thingo: 0x00
thingo: 0x00
thingo: 0x00
thingo: 0x00
that packet is normal - command status event
thingo: 0x04
thingo: 0x10
thingo: 0x01
thingo: 0x35
thingo: 0x01
thingo: 0x00
thingo: 0x00
thingo: 0x00
thingo: 0x00
thingo: 0x00
hardware error - but i cannot tell what the error code means (yes i will
check Core Spec 2.0 now :) )
thingo: 0x04
thingo: 0xff
thingo: 0x1f
thingo: 0xc3
thingo: 0x02
thingo: 0x00
thingo: 0x0f
thingo: 0x00
thingo: 0x20
thingo: 0xa7
this packet looks like a CSR manufaturer specific response (0xff) what
does that mean?
even stranger is when run again and every subsequent time before a
reboot (of bluecore) it works and gives back the correct amount of
hosts found!!!
Is it to do with some kind of baud error? Bluecore can adapt to
different baud rates just by looking at the data sent over time - but i
want to know what effect this - moreover what it mucks up.
thanks and sorry for the long email
next reply other threads:[~2008-12-30 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 5:15 David Thornton [this message]
2008-12-30 5:19 ` bccmds Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2008-12-29 22:37 BCCMDs David Thornton
2008-12-29 23:00 ` BCCMDs David Thornton
2008-12-30 1:47 ` BCCMDs 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=4959AE62.8020605@villagepublishing.com.au \
--to=david@villagepublishing.com.au \
--cc=linux-bluetooth@vger.kernel.org \
/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