If you enter a "ps -ef" in your telnet session, you should see a line like this:
There is the bsa_server process running with several options...
So if you enter "/mtd_cmmlib/BT_LIB/bsa_server -help", you find out that there are several debugging options and the ability to create a .snoop file which you can open in wireshark...
Found out, you should first kill the current active bsa_server process and immediatly fire up your own with enabled debugging options and logging of all bluetooth traffic into a btlog.snoop file, which can be opendend in wireshark afterwards.
First do a "ps -a" to get the current pid of the bsa_server process:
Afterwards fireup the following to see everything about blouetooth in your terminal an to log into a snoop file. Substitute my pid (11454) with your own!!!
Voila!! A new instance of the bsa_server process is running and logging all the detailed contents...
But i do not have neither a official Samsung A2DP Device, nor a A2DP Headphone or something like that....
Code:
ttyS1 00:00:00 /mtd_cmmlib/BT_LIB/bsa_server -all=0 -diag=0 -hci=0 -l2c=0 -app=0 -btm=0 -sdp=0 -rfc=0 -gap=0 -a2d=0 -avdt=0 -avrc=0 -mca=0 -u /mtd_rwarea/
There is the bsa_server process running with several options...
So if you enter "/mtd_cmmlib/BT_LIB/bsa_server -help", you find out that there are several debugging options and the ability to create a .snoop file which you can open in wireshark...
Code:
root@tv:/mtd_rwcommon # /mtd_cmmlib/BT_LIB/bsa_server -help
BSA_trace 1@23h:59m:35s:347ms: Starting Bluetooth Daemon
BSA_trace 2@23h:59m:35s:348ms: BSA version:BSA_MI_01.00.05.00.29-eng3
BSA_trace 3@23h:59m:35s:348ms: BSA server version info:Eng2 + security update
DESCRIPTION:
bsa_server supports:
- if UART HCI is used, forcing the UART device to use
- if tracing is enabled, configuring tracing levels for the various
protocols and profiles of the Bluetooth stack and application.
The use of the option on the command line without any number will
result in the maximum trace level of 5 (DEBUG) for the layer.
Otherwise, the tracing level is set to the number specified.
The possible levels are the following:
NONE 0 No trace messages to be generated
ERROR 1 Error condition trace messages
WARNING 2 Warning condition trace messages
API 3 API traces
EVENT 4 Debug messages for events
DEBUG 5 Full debug messages
USAGE: bsa_server [OPTION]...
-help get option help information
-b file specify the BT Snoop file to save serial packets
-d device set the hci device interface (e.g. /dev/ttyHS0)
-u path prefix all the socket names with a path
-p patchfile force the patchfile to use
-all=# set trace level to # for all layers
-diag=# set DIAG trace level to #
-hci=# set HCI trace level to #
-l2c=# set L2CAP trace level to #
-app=# set APPL trace level to #
-btm=# set BTM trace level to #
-sdp=# set SDP trace level to #
-rfc=# set RFCOMM trace level to #
-gap=# set GAP trace level to #
-a2d=# set A2DP trace level to #
-avdt=# set AVDT trace level to #
-avct=# set AVCT trace level to #
-avrc=# set AVRC trace level to #
-mca=# set MCA trace level to #
EXAMPLES:
Example: bsa_server -d /dev/com10
This command would force the HCI to use /dev/com10
Example: bsa_server -d /dev/com10 -hci -l2c -app -a2d
This command would establish the following trace setting:
HCI layer = 5 (DEBUG)
L2CAP layer = 5 (DEBUG)
APPL layer = 5 (DEBUG)
A2DP layer = 5 (DEBUG)
Example: bsa_server -hci=0 -l2c=4 -app -a2d=3
This command would establish the following trace setting:
HCI layer = 0 (NONE)
L2CAP layer = 4 (EVENT)
APPL layer = 5 (DEBUG)
A2DP layer = 3 (API)
Found out, you should first kill the current active bsa_server process and immediatly fire up your own with enabled debugging options and logging of all bluetooth traffic into a btlog.snoop file, which can be opendend in wireshark afterwards.
First do a "ps -a" to get the current pid of the bsa_server process:
Code:
11454 ttyS1 00:00:00 bsa_serverAfterwards fireup the following to see everything about blouetooth in your terminal an to log into a snoop file. Substitute my pid (11454) with your own!!!
Code:
kill -9 11454 && /mtd_cmmlib/BT_LIB/bsa_server -all=5 -diag=5 -hci=5 -l2c=5 -app=5 -btm=5 -sdp=5 -rfc=5 -gap=5 -a2d=5 -avdt=5 -avrc=5 -mca=5 -u /mtd_rwarea/ -b /mtd_rwcommon/bt_test/btlog.snoopVoila!! A new instance of the bsa_server process is running and logging all the detailed contents...
But i do not have neither a official Samsung A2DP Device, nor a A2DP Headphone or something like that....
Statistics: Posted by hudd0 — Sun Mar 06, 2016 1:10 am — Replies 29 — Views 13189