BT issue: Assert_warn and no serial connection possible, but pairs

[Shane87F3Ng]

Make your question, not a Statement, inclusive. Include all pertinent information:

----------------------------- Remove above -----------------------------

Hardware:

Board: WEMOS LOLIN D32 PRO V2.0.0
Core Installation version: ?1.0.0? ?1.0.1-rc4? ?1.0.1? ?1.0.1-git? ?1.0.2? ?1.0.3?
IDE name: Arduino IDE?
Flash Frequency: 80Mhz
PSRAM enabled: no
Upload Speed: 115200
Computer OS: Windows 10 + Mac OSX

Description:

I cannot connect to the serial COM-port as soon as i use the 5.1 Bluetooth adapter. I can pair the esp32, but nothing more and the message/warning below occures. If i use a BT4.0 dongle, anything works fine without warning etc. and the connection is stable. Data transfer is possible with BT4.0, but i need to use the new adapter because of multiconnect.

How can is solve this? What does the warning actually mean?

Best regards

Sketch: (leave the backquotes for code formatting)

//Change the code below by your sketch

#include "BluetoothSerial.h"

#if !defined(CONFIG_BT_ENABLED) || !defined(CONFIG_BLUEDROID_ENABLED)
#error Bluetooth is not enabled! Please run `make menuconfig` to and enable it
#endif

BluetoothSerial SerialBT;

void setup() {
  Serial.begin(115200);
  SerialBT.begin("ESP32test"); //Bluetooth device name
  Serial.println("The device started, now you can pair it with bluetooth!");
}

void loop() {
  if (Serial.available()) {
    SerialBT.write(Serial.read());
  }
  if (SerialBT.available()) {
    Serial.write(SerialBT.read());
  }
  delay(20);
}

### Debug Messages:
[I][BluetoothSerial.cpp:539] _init_bt(): device name set
The device started, now you can pair it with bluetooth!
[I][BluetoothSerial.cpp:228] esp_spp_cb(): ESP_SPP_INIT_EVT
[I][BluetoothSerial.cpp:231] esp_spp_cb(): ESP_SPP_INIT_EVT: slave: start
[I][BluetoothSerial.cpp:315] esp_spp_cb(): ESP_SPP_START_EVT
ASSERT_WARN(103 23), in lc_task.c at line 8775ASSERT_WARN(103 24), in lc_task.c at line 8775

[societyofrobots]

Try NimBLE.

This is what I use:
https://github.com/h2zero/NimBLE-Arduino/tree/master/examples/Refactored_original_examples/BLE_uart

[Shane87F3Ng]

Try NimBLE.

This is what I use:
https://github.com/h2zero/NimBLE-Arduino/tree/master/examples/Refactored_original_examples/BLE_uart

Thanks for your reply!
As i try to use BT-serial, i think it is not possible with BLE? Thought i have to use BT-classic?

[societyofrobots]

I use NimBLE for passing serial.

Use this to declare it a serial port:
pAdvertising->addServiceUUID((uint16_t)0x1101);

before you start advertising:
BLEDevice::startAdvertising();

[Metaln00b]

Same problem here with 1.0.6:
No connection possible. Using 1.0.4 no problem.

02:22:10.444 -> ets Jun  8 2016 00:22:57
02:22:10.444 -> 
02:22:10.444 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
02:22:10.492 -> flash read err, 1000
02:22:10.492 -> ets_main.c 371 
02:22:10.828 -> ets Jun  8 2016 00:22:57
02:22:10.828 -> 
02:22:10.828 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
02:22:10.828 -> configsip: 0, SPIWP:0xee
02:22:10.828 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
02:22:10.828 -> mode:DIO, clock div:1
02:22:10.876 -> load:0x3fff0018,len:4
02:22:10.876 -> load:0x3fff001c,len:1044
02:22:10.876 -> load:0x40078000,len:10124
02:22:10.876 -> load:0x40080400,len:5856
02:22:10.876 -> entry 0x400806a8
02:22:11.161 -> Setup
02:22:11.161 -> [D][ESP32-BT.ino:66] ledc_init(): ledc_channel_config returned 0
02:22:11.209 -> [D][ESP32-BT.ino:75] ledc_init(): ledc_timer_set: divider: 0x3d090 duty_resolution: 10
02:22:11.209 -> 
02:22:11.209 -> [D][ESP32-BT.ino:66] ledc_init(): ledc_channel_config returned 0
02:22:11.209 -> [D][ESP32-BT.ino:75] ledc_init(): ledc_timer_set: divider: 0x3d090 duty_resolution: 10
02:22:11.209 -> 
02:22:12.692 -> [I][BluetoothSerial.cpp:571] _init_bt(): device name set
02:22:12.692 -> [I][BluetoothSerial.cpp:243] esp_spp_cb(): ESP_SPP_INIT_EVT
02:22:12.692 -> [I][BluetoothSerial.cpp:246] esp_spp_cb(): ESP_SPP_INIT_EVT: slave: start
02:22:12.692 -> [I][BluetoothSerial.cpp:347] esp_spp_cb(): ESP_SPP_START_EVT

ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
...

[Shane87F3Ng]

Same problem here with 1.0.6:
No connection possible. Using 1.0.4 no problem.

02:22:10.444 -> ets Jun  8 2016 00:22:57
02:22:10.444 -> 
02:22:10.444 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
02:22:10.492 -> flash read err, 1000
02:22:10.492 -> ets_main.c 371 
02:22:10.828 -> ets Jun  8 2016 00:22:57
02:22:10.828 -> 
02:22:10.828 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
02:22:10.828 -> configsip: 0, SPIWP:0xee
02:22:10.828 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
02:22:10.828 -> mode:DIO, clock div:1
02:22:10.876 -> load:0x3fff0018,len:4
02:22:10.876 -> load:0x3fff001c,len:1044
02:22:10.876 -> load:0x40078000,len:10124
02:22:10.876 -> load:0x40080400,len:5856
02:22:10.876 -> entry 0x400806a8
02:22:11.161 -> Setup
02:22:11.161 -> [D][ESP32-BT.ino:66] ledc_init(): ledc_channel_config returned 0
02:22:11.209 -> [D][ESP32-BT.ino:75] ledc_init(): ledc_timer_set: divider: 0x3d090 duty_resolution: 10
02:22:11.209 -> 
02:22:11.209 -> [D][ESP32-BT.ino:66] ledc_init(): ledc_channel_config returned 0
02:22:11.209 -> [D][ESP32-BT.ino:75] ledc_init(): ledc_timer_set: divider: 0x3d090 duty_resolution: 10
02:22:11.209 -> 
02:22:12.692 -> [I][BluetoothSerial.cpp:571] _init_bt(): device name set
02:22:12.692 -> [I][BluetoothSerial.cpp:243] esp_spp_cb(): ESP_SPP_INIT_EVT
02:22:12.692 -> [I][BluetoothSerial.cpp:246] esp_spp_cb(): ESP_SPP_INIT_EVT: slave: start
02:22:12.692 -> [I][BluetoothSerial.cpp:347] esp_spp_cb(): ESP_SPP_START_EVT

ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
ASSERT_WARN(103 24), in lc_task.c at line 877
...

Yes, 1.0.4 is doing the trick, so it seems there is a problem with the newer versions

[stale]

[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[Shane87F3Ng]

Will this issued bei focused in a future update? Maybe in 2.0.0 ?

[stale]

[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future.

[stale]

[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.