[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] sending data and access violation in l2cap




this means that your hardware has got no free outbuffers (acl_num, if using ericsson P9A module this is not uncommon...) and that you simply leave the data in the btmem buffers for later transmission. As soon as the module informs about new free outbuffers (number of completed packets event) the queued packets are sent. However, due to bugs in ericsson baseband this might never occur...

the l2cap->frame is a pointer in the newly subscribed tx buf which points at the start of the l2cap frame i.e the hci header is "stripped". It is set when you cast the tx_buffer to a l2cap_buf in :
l2cap_buf = (l2cap_tx_buf *)(tx->data). See header files for the details.

What version of the stack are you using ? 
Is the return value checked after the subscribe_bt_buf() i.e are you sure that there was enough memory in btmem ?

brgds
Mattias Ågren, 
AXIS Communications AB

-----Original Message-----
From: Walter [mailto:Walter.van.Berkel@xxxxxxx.nl]
Sent: den 22 november 2000 14:00
To: Blue tooth list
Subject: [bluetooth-dev] sending data and access violation in l2cap


Hello..
I've got 2 questions again.. Hoping someone could help me...
first:
in function hci_send_data I get output:
hci_send_data : leave in queue, buffers 93, acl_num 0

Question: which queue is this and when are bytes send!?

second: in l2cap.c in function l2cap_connect_req
I get an access violation at this line:
 cmd = (sig_cmd*)(l2cap_buf->frame + L2CAP_HDRSIZE);
There seems to be something wrong with l2cap_buf because the value in it
couldn't be examined.
Could you explain where l2cap_buf->frame gets its value..

THnx again..

W.


-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com