Closed teburd closed 5 years ago
@bfrog can you try https://github.com/zephyrproject-rtos/zephyr/pull/18573 ?
will do
@bfrog it's merged now, so you can test the latest master
quickly tested on reel board with configuration below, seems to work, IMHO configuration problem
CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_SMP=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_GATT_DIS=y
CONFIG_BT_GATT_DIS_PNP=n
CONFIG_BT_GATT_BAS=y
CONFIG_BT_GATT_HRS=y
CONFIG_BT_DEVICE_NAME="Zephyr Heartrate Sensor"
CONFIG_BT_DEVICE_APPEARANCE=833
CONFIG_GPIO=y
CONFIG_USB=y
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Zephyr USB console sample"
CONFIG_USB_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_LINE_CTRL=y
CONFIG_UART_CONSOLE_ON_DEV_NAME="CDC_ACM_0"
CONFIG_USB_UART_DTR_WAIT=n
[00:00:00.000,976] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.000,976] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 0
[00:00:00.001,708] <inf> bt_hci_core: Identity: c8:e9:b4:3c:df:40 (random)
[00:00:00.001,739] <inf> bt_hci_core: HCI: version 5.1 (0x0a) revision 0x0000, manufacturer 01
[00:00:00.001,739] <inf> bt_hci_core: LMP: version 5.1 (0x0a) subver 0xffff
[00:00:00.001,739] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.001,861] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.005,798] <inf> usb_cdc_acm: USB device suspended
[00:00:00.101,806] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.110,351] <inf> usb_cdc_acm: USB device resumed
[00:00:00.110,443] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.210,479] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.238,067] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.290,863] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.338,134] <wrn> usb_cdc_acm: Device not configured, drop 1 bytes
[00:00:00.389,099] <inf> usb_cdc_acm: USB device configured
@bfrog
When I go to debug I see this loop never exits
Please use CONFIG_USB_UART_DTR_WAIT=n or press a key in your terminal client.
Describe the bug Using USB CDC console with bluetooth, seems to result in an endless loop in the USB CDC code.
I'm looking to try the peripheral_hr sample using usb console. So I added the prj.conf settings from the subsys/usb/console/prj.conf to the peripheral_hr/prj.conf and attempted to run it.
This results in the following message from linux
When I go to debug I see this loop never exits
To Reproduce Add prj.conf settings from the usb console sample to the peripheral_hr sample, try to run.
Expected behavior I expected usb and bluetooth to be working.
Impact Showstopper, my custom board based on this setup doesn't have a easily accessible uart
Environment (please complete the following information):
Additional context nrf52840 pca10056