Zile,
Instructions for testing Bluetooth speeds can be found here:

viewtopic.php?f=52&t=16554

Zile,

Here are the instructions for increasing the baud rate to the Bluetooth interface.

Posted By richh on 16 Apr 2013 8:33 AM
Zile,
Instructions for testing Bluetooth speeds can be found here:

viewtopic.php?f=52&t=16554

Hi Richh, thank you for reply. As I can see from your post, tested speed is 128Bytes in 284ms, which is around 4000 bps. That is too slow.

Posted By steven.eckhoff on 16 Apr 2013 8:54 AM
Zile,

Here are the instructions for increasing the baud rate to the Bluetooth interface.

Hi Steven, thank you for reply. Sorry, but I can't see your instructions for increasing speed over bluetooth. Did you attach it?

Zile,

I apologize. Here is the link viewtopic.php?f=52&t=16555

Hi Steven,

Thank you. Meanwhile, I have found same this and changed. It works fine. I should produce more tests, but I can see that bluetooth port is opened at 3Mbps.

Did you test speed on UART above 921600bps? What is the maximum speed? I suppose 3.692Mbps (48MHz(UART clock) / 13 (divisor)), based on DM3730 TRM http://www.ti.com/lit/ug/sprugn4r/sprugn4r.pdf
Figure 19-31 and Table 19-30. Also based on this figure and table for speeds 1Mbps and 1.5Mbps I changed following 2 lines in
LogicPD_Linux_BSP_2.3-2/rpm/BUILD/linux-3.0/drivers/tty/serial/omap-serial

-if (baud > OMAP_MODE13X_SPEED && baud != 3000000)
+if (baud > OMAP_MODE13X_SPEED && baud != 3000000 && baud != 1500000 && baud != 1000000)
divisor = 13;
else
divisor = 16;

-if (baud > 230400 && baud != 3000000)
+if (baud > 230400 && baud != 3000000 && baud != 1500000 && baud != 1000000)
serial_out(up, UART_OMAP_MDR1, UART_OMAP_MDR1_13X_MODE);
else
serial_out(up, UART_OMAP_MDR1, UART_OMAP_MDR1_16X_MODE);

I will test 1Mbps, 1.5Mbps and 3.692Mbps.

Hello,

So I tried to stream data at 3Mbps over the bluetooth and there are problems. I am not able to send data and after some time error pops out
[ 1488.113708] hci_link_tx_to: hci0 link tx timeout
[ 1488.118774] hci_link_tx_to: hci0 killing stalled connection 00:1B:10:00:01:48

Also, I did tests per viewtopic.php?f=52&t=16554. Results are very disappointing.

DM-37x# l2ping -t 10000 -s 128 -c 1 00:1B:10:00:01:48
Ping: 00:1B:10:00:01:48 from 1C:E2:CC:FE:D3:8F (data size 128) ...
0 bytes from 00:1B:10:00:01:48 id 0 time 10864.26ms
1 sent, 1 received, 0% loss
DM-37x# l2ping -t 10000 -s 128 -c 1 00:1B:10:00:01:48
Ping: 00:1B:10:00:01:48 from 1C:E2:CC:FE:D3:8F (data size 128) ...
0 bytes from 00:1B:10:00:01:48 id 0 time 3253.23ms
1 sent, 1 received, 0% loss
DM-37x# l2ping -t 10000 -s 128 -c 1 00:1B:10:00:01:48
Ping: 00:1B:10:00:01:48 from 1C:E2:CC:FE:D3:8F (data size 128) ...
0 bytes from 00:1B:10:00:01:48 id 0 time 2044.50ms
1 sent, 1 received, 0% loss
DM-37x# l2ping -t 10000 -s 128 -c 1 00:1B:10:00:01:48
Ping: 00:1B:10:00:01:48 from 1C:E2:CC:FE:D3:8F (data size 128) ...
0 bytes from 00:1B:10:00:01:48 id 0 time 50295.18ms
1 sent, 1 received, 0% loss

My PN is 1021711 REV C. So obviously this is because limitations L0002 in Errata document for Torpedo Wireless SOM.

Regards,
Dragan

Zile,
That is correct. With the fix in place, the Bluetooth speeds are significantly improved.

Hi Steven, this link seems to be dead. Could you re-post please?

Thanks!

Here is a link to an older post about how to change the baud rate.

http://support.logicpd.co...aft/106/Default.aspx

We've updated our BSP several times since it was originally posted. I'll try to find some Bluetooth testing results and see what I can find for throughput.

adam

Hi Adam, thanks for your reply.

I have checked the baud rate- set to 3000000.

I observe a much slower data rate when egressing data from the DM3730 (200 kbit/s) than when sending data to the DM3730 (1.6 Mbit/s). Trying to diagnose- any suggestions?

There was an issue with the clocking on the BT modules in previous revisions of the hardware.

Description:
The clock path, TCXO_P, feeding U17 (D7002) has added phase noise. This causes degraded performance (lower throughput and/or poor connection) for both transmit and receive on the Bluetooth interface. IMPORTANT NOTE: The 802.11b/g/n (2.4 GHz) and GPS interfaces are not impacted by this issue.

I did some research and it looks like we had released an errata due to slow BT connections and poor BT connections. Can you look at your module's part number and compare it to this Errata notice? http://support.logicpd.co...id=0&EntryId=652 I need to know if you have an affected part number.

-adam

if the link does not work, you may need to log into the support site to download the files.

Thanks. Our model number is SOMDM3730-31, so I don't believe that is covered by the errata notice. The significant thing is that the problem is asymmetric- I am investigating how the module selects master/slave roles and packet types for egress/receive. Manually forcing these parameters using hciconfig has no effect.

Can you tell me which version of the BSP you are using? The latest release is 2.4-3 we have made some improvements to the BT over time.

adam

Our latest BSP has an option to compile in newer verisons of BlueZ.

If you have been using 2.4-3 already, you'll need to do distclean,

./ltib -b -m distclean

Then rerun ltib with different defconfig options.


./ltib -b --preconfig config/platform/omap_logic/defconfig.new-bluez


This should compile in some newer Bluetooth options. Give that a try, and let me know how it goes. As an FYI, I will be out of the office from Dec 24-Jan 7 and returning on Jan 8.

adam