Hi Marcel, I tried to log what's going on both in case of my btattach-kill-btattach workaround case, and in case i run only 'btattach -P qca' and bluetoothd is not working afterwards. You can find the logs at http://stuff.krakonos.org/files/btmonSee.tar.bz2 I'm not really able to understand the output myself :( Thank you for further comments, Libor -----Ursprüngliche Nachricht----- Von: Marcel Holtmann [mailto:marcel@xxxxxxxxxxxx] Gesendet: Mittwoch, 18. Oktober 2017 16:31 An: Libor Peltan <lpeltan@xxxxxxxxxxxx> Cc: linux-bluetooth@xxxxxxxxxxxxxxx Betreff: Re: UART baud rate to 3M within btattach Hi Libor, > Thank you Marcel, your suggestion solved my issue: > > I had to compile the kernel with CONFIG_BT_HCIUART_QCA. > I must also call following at the bootup: > > btattach -S 3000000 -P qca > sleep 1 > killall btattach > sleep 1 > btattach -S 3000000 -P h4 > bluetoothd > > ...otherwise bluetoothd doesn't work (=finds 0 adapters). > But I'm glad to have this workaround :) actually only one btattach command should be needed. If this doesn't work, we should fix hci_qca.c to support it. Since after loading the firmware and configuring the UART speed, the QCA protocol will automatically run H4. No need to kill btattach and restart it with a different protocol. Can you share "btmon -w trace.log" traces? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
