• State
  • Replies 1 reply
  • Subscribers 41 subscribers
  • Views 38 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CC3301: CC33XX BLE MTU

Pavan Nittala
Prodigy 25 points
Part Number: CC3301


Device : NXP IMX91 SOM From Boundary Devices , Ezurio

OS :  Yocto Linux Scarthgap

WiFi/BLE Module :  Sona TI351 WiFi6 + Bluetooth v5.4

FW :    summit-ti351-WW-firmware-13.24.0.20.tar.bz2 inside https://github.com/Ezurio/Connectivity_Stack_Release_Packages/releases/ 

Bluez :  v5.82

root@nitrogen91:~# hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: E8:CB:F5:80:B9:E9 ACL MTU: 255:10 SCO MTU: 0:0
UP RUNNING
RX bytes:4487 acl:44 sco:0 events:339 errors:0
TX bytes:2965 acl:44 sco:0 commands:284 errors:0
Featur[ 9288.776557] Bluetooth: hci0: unexpected cc 0x0c14 length: 1 < 249
es: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: PERIPHERAL ACCEPT
Can't read local name on hci0: Input/output error (5)

I have few Questions : 

1. Why is MTU Limited to 255 ?? On other devices , we have higher MTU of 1024

2.  Why those errors like "Cant Read Local Name" ??

 

  • 0
    Expert 1481 points

    Hi Pavan,

    The "Can't read local name" is because you are using hciconfig on a BLE only device. The error is generated because hciconfig is issuing a command that is not supported by BLE only devices.

    You shouldn't be using hciconfig at all with BlueZ 5 and modern kernels. It is deprecated, along with all the other hcixxx utilities, and has been replaced by bluetoothctl. Those older utilities interact directly with the radio, bypassing the bluetooth management interface in the kernel. It can result in synchronization problems with the bluetooth core in the kernel.

    Please use bluetoothctl, or the dbus API directly. Do not use hcitool or hciconfig.

    Dean