* [Bluez-devel] Unknown answer
@ 2004-03-28 0:42 zubiwat
2004-03-28 8:32 ` Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: zubiwat @ 2004-03-28 0:42 UTC (permalink / raw)
To: devel Bluetooth
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Hi
I'm sending these commands :
0x01 0x05 0x10 0x00
0x01 0x09 0x10 0x00
and I don't understand why I get answer like this:
04 FF 13 C2 01 00 09 00 02 00 02 68 00 00 BF 0E 00 00 00 00 00 00 04 0E 0B 01 05 10 00 C0 00 40 08 00 08 00 04 0E 0A 01 09 10 00 04 00 20 DD 09 00
Why when I'm trying to read buffer size (0x01 0x05 0x10 0x00) and read BT ADDR (0x01 0x09 0x10 0x00) I get so many events? It's strange because when I'm trying to read, device answers that it can't for example connect because of connection rejected due to security reasons (04 0E 0B 01 05 10 00 C0 00 40 08 00 08 00 ) or am I wrong?
Regards
Maciej Zubilewicz
[-- Attachment #2: Type: text/html, Size: 1608 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] Unknown answer
2004-03-28 0:42 [Bluez-devel] Unknown answer zubiwat
@ 2004-03-28 8:32 ` Marcel Holtmann
[not found] ` <001101c414a2$2d426540$fcca010a@lysydziadek>
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2004-03-28 8:32 UTC (permalink / raw)
To: zubiwat; +Cc: devel Bluetooth
Hi Maciej,
your questions are annoying me and this will be the last one I answer.
Please stop posting non BlueZ related things to our mailing lists,
because otherwise I have to ban you.
> I'm sending these commands :
> 0x01 0x05 0x10 0x00
> 0x01 0x09 0x10 0x00
>
> and I don't understand why I get answer like this:
>
> 04 FF 13 C2 01 00 09 00 02 00 02 68 00 00 BF 0E 00 00 00 00 00 00 04
> 0E 0B 01 05 10 00 C0 00 40 08 00 08 00 04 0E 0A 01 09 10 00 04 00 20
> DD 09 00
You should have taken my advise and sit down and decode your results,
because then you had seen the answers.
04 FF 13 C2 01 00 09 00 02 00 02 68 00 00 BF 0E 00 00 00 00 00 00
This is a vendor specific event. Ask your module manufacturer.
04 0E 0B 01 05 10 00 C0 00 40 08 00 08 00
And this is the result of the reading the buffer size.
04 0E 0A 01 09 10 00 04 00 20 DD 09 00
And here we have your local BD_ADDR, which is 00:09:dd:20:00:04
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] Unknown answer
[not found] ` <001101c414a2$2d426540$fcca010a@lysydziadek>
@ 2004-03-28 12:43 ` Marcel Holtmann
0 siblings, 0 replies; 3+ messages in thread
From: Marcel Holtmann @ 2004-03-28 12:43 UTC (permalink / raw)
To: zubiwat; +Cc: BlueZ Mailing List
Hi Maciej,
> Please this is the last - really. How do you decode this because 0e after 04
> means an error. After 04 shouldn't be 00 as a command succeeded. How do you
> look into specification to find out the answer?
> I swear it's the last question, because it will solve my problems.
actually your problem is reading the HCI specification. It is all there
and the HCI part is one of the easier parts of Bluetooth.
So do it step by step and take this as an example
04 0E 0A 01 09 10 00 04 00 20 DD 09 00
04 = H:4 specific and means this is a HCI event
0E 0A = HCI event header
struct hci_event_hdr {
uint8_t event;
uint8_t plen;
} __attribute__ ((packed));
0E = HCI command complete event
0A = Event len (= 10 bytes)
01 09 10 = HCI command complete event
struct hci_command_complete_evt {
uint8_t ncmd;
uint16_t opcode;
/* variable length part */
uint8_t param[0];
} __attribute__ ((packed));
01 = Number of command packets (HCI flow control)
09 10 = Command opcode (OCF & OGF)
00 04 00 20 DD 09 00 = HCI read BD_ADDR response
struct hci_read_bd_addr_rp {
uint8_t status;
bdaddr_t bdaddr;
} __attribute__ ((packed));
00 = Status (= OK)
04 00 20 DD 09 00 = BD_ADDR
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-03-28 12:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-28 0:42 [Bluez-devel] Unknown answer zubiwat
2004-03-28 8:32 ` Marcel Holtmann
[not found] ` <001101c414a2$2d426540$fcca010a@lysydziadek>
2004-03-28 12:43 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox