Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Logic PD support staff and engineers participate, Logic PD does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Logic PD engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Logic PD product download, please subscribe to the TDG Forum of interest.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 15 Apr 2013 02:11 PM by  steven.eckhoff@logicpd.com
Article: DM3730 T+W Measuring Bluetooth Performance
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages

steven.eckhoff@logicpd.com



Basic Member


Posts:192
Basic Member


--
15 Apr 2013 02:11 PM
    NOTE: If you would like to increase the baud rate to the Bluetooth interface see this article <!-- l -->viewtopic.php?f=52&t=16555<!-- l -->

    The DM3730 Linux BSP comes with the Bluez utilities. These utilities can be used for testing Bluetooth connections and throughput performance. In this article we will use the l2ping command to test a Bluetooth connection and its performance.

    Before being able to detect nearby Bluetooth devices, you will need to bring up the st and btwilink drivers and start the uim daemon. The following log shows the commands used to do this.
    DM-37x# modprobe st_drv
    [ 211.573455] (stk) :sysfs entries created
    [ 211.578979] (stk) : debugfs entries created
    DM-37x# /home/root/wl12xx/uim&
    [1] 715
    DM-37x# modprobe btwilink
    [ 224.370330] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
    [ 224.400146] (stc): st_register(2)
    [ 224.403808] (stc): chnl_id list empty :2
    [ 224.408325] (stk) : st_kim_start
    [ 224.517639] (stk) :ldisc_install = 1uim: Inside mainuim: Inside st_uart_configuim:install set to 1
    uim:opening /dev/ttyO1, while already open
    DM-37x# uim:cleanup
    uim: Inside set_baud_rateuim: set_baud_rate() done
    uim: Setting speed to 3000000
    uim: Inside read_command_completeuim: Command complete started
    uim: Inside read_hci_eventuim: read_hci_event
    uim: Command complete done
    uim: Speed changed to 3000000
    uim: Inside set_c
    [ 224.647735] (stc): st_tty_open ustom_baud_rateu
    [ 224.653625] (stk) : line discipline installed im: Changing baud rate to 300000
    [ 224.660766] (stk) :Logic_TIInit_10.6.15.bts0, flow control to 1
    uim: set_custom_baud_rate() done
    uim: Installed N_TI_WL Line displine

    [ 225.290771] (stc): add_channel_to_table: id 2
    [ 225.295593] (stc): st_register(3)
    [ 225.298980] (stc): add_channel_to_table: id 3
    [ 225.303741] (stc): st_register(4)
    [ 225.307128] (stc): add_channel_to_table: id 4
    [ 227.338165] (stc): remove_channel_from_table: id 2
    [ 227.343414] (stc): remove_channel_from_table: id 3
    [ 227.348480] (stc): remove_channel_from_table: id 4
    [ 227.353637] (stc): all chnl_ids unregistered
    [ 227.358703] (stk) :ldisc_install = 0uim: Inside st_u
    [ 227.366973] (stc): st_tty_close art_configuim: U
    [ 227.370544] (stc): 2 not un-registered
    [ 227.375762] (stc): 3 not un-registered
    [ 227.379730] (stc): 4 not un-registeredn-Installed N_TI_WL Line displine
    uim:cleanup

    Now, the interface needs to be brought up. The following log shows the commands used to do this.
    DM-37x# hciconfig hci0 up
    [ 1129.658325] (stc): st_register(2)
    [ 1129.661987] (stc): chnl_id list empty :2
    [ 1129.666320] (stk) : st_kim_start
    [ 1129.775634] (stk) :ldisc_install = 1uim: Inside st_uart_configuim:install set to 1
    uim: Inside set_baud_rateuim: set_baud_rate() done
    uim: Setting speed to 3000000
    uim: Inside read_command_completeuim: Command complete started
    uim: Inside read_hci_eventuim: read_hci_event
    uim: Command complete done
    uim:
    [ 1129.844909] (stc): st_tty_open Speed changed to 3000000
    uim:
    [ 1129.851318] (stk) : line discipline installed Inside set_custom_baud_rateuim:
    [ 1129.859497] (stk) :Logic_TIInit_10.6.15.btsChanging baud rate to 3000000, flow control to 1
    uim: set_custom_baud_rate() done
    uim: Installed N_TI_WL Line displine

    [ 1130.533416] (stc): add_channel_to_table: id 2
    [ 1130.538391] (stc): st_register(3)
    [ 1130.541809] (stc): add_channel_to_table: id 3
    [ 1130.546691] (stc): st_register(4)
    [ 1130.550109] (stc): add_channel_to_table: id 4

    Now you will be able to scan for nearby devices. The following log shows the commands used to scan for devices.
    DM-37x# hcitool scan
    Scanning ...
    F1:55:D4:A9:BC:04 EckhoffIsAwesome

    The following options will be used for the l2ping test.
      -t 10000 - This option sets the timeout in milliseconds (In this example 10000ms).
      -s 128 -This option sets the packet size in Bytes (In this example 128Bytes).
      -c 1 - This option specifies the number of packets to send (In this example 1 packet).


    The following is an example of the l2ping command being used on the command line to test the Bluetooth connection and throughput.
    DM-37x# l2ping -t 10000 -s 128 -c 1 00:1A:6B:44:49:45
    Ping: 00:1A:6B:44:49:45 from 1C:E2:CC:FE:CF:FB (data size 128) ...
    128 bytes from 00:1A:6B:44:49:45 id 0 time 284.73ms
    1 sent, 1 received, 0% loss

    NOTE: Currently there is a known issue with the oscillator on the SOM and we are issuing an errata to further explain the issue. If you have any question or concerns regarding the issue, please contact us at the following link http://support.logicpd.com/support/askaquestion.php
    You are not authorized to post a reply.