Hi Igor,
Thanks for your quick reply and useful information.
I verified my Linux imx kernel config (/proc/configs.gz and .config) and everything seems to be activated:
• CONFIG_SERIAL_IMX=y
• CONFIG_TTY=y
• CONFIG_BT_HCIUART=y
• CONFIG_BT_HCIUART_H4=y
• CONFIG_BT_HCIUART_QCA=y
• CONFIG_BT_HCIUART_BCM=y
• CONFIG_BT=y
• CONFIG_BT_RFCOMM=y
• CONFIG_BT_RFCOMM_TTY=y
• CONFIG_BT_BNEP=y
• CONFIG_BT_BNEP_MC_FILTER=y
• CONFIG_BT_BNEP_PROTO_FILTER=y
• CONFIG_BT_HIDP=y
here is the output of dmesg:
$ dmesg | grep -i Bluetooth
Bluetooth: Core ver 2.22
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Bluetooth: HCI UART driver ver 2.3
Bluetooth: HCI UART protocol H4 registered
Bluetooth: HCI UART protocol BCSP registered
Bluetooth: HCI UART protocol ATH3K registered
Bluetooth: HCI UART protocol Three-wire (H5) registered
Bluetooth: HCI UART protocol Broadcom registered
Bluetooth: HCI UART protocol QCA registered
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
my lsmod returns the kernel module qca9377 as expected and bluez5 is included.
My mistake! Bluetooth chip is not connected to /dev/ttymxc2 but /dev/ttymxc0. Now hciattach make the setup complete.
Thanks for your help.
Regards.