ASSERT_WARN(1 8), in lc_task.c in serial output when using ESP32 Bluetooth Classic in Master Mode

[alastaira]

Board

ESP32 DevKit v1 (ESP-WROOM-32)

Device Description

ESP DevKit v1

Hardware Configuration

No other hardware connected

Version

v1.0.6

IDE Name

Arduino IDE 1.8.15

Operating System

Windows 10

Flash frequency

80MHz

PSRAM enabled

no

Upload speed

921600

Description

Using Bluetooth Classic in Master mode on the ESP32 to connect to an HC-06 slave that is transmitting data.
The ESP32 pairs successfully to the device, including the required Bluetooth pairing PIN code, and data is received correctly.

However, when printing the received data to the serial output of the ESP32, an additional message is periodically printed in the output (every few seconds) - "ASSERT_WARN(1 8), in lc_task.c at line 1394", as shown below:

I think this error is possibly related to the issues described at:

• bt spp connection shift system time (IDFGH-3121) esp-idf#5140
• >ASSERT_WARN(1 8), in lc_task.c at line 5054ASSERT_WARN(1 8), in lc_task.c at line 5054 PowerBroker2/ELMduino#43
  Those reference different line numbers (but also relate to earlier versions of the ESP32 codebase), but otherwise describe similar scenarios related to Bluetooth connections. However, neither issue referenced has been closed with a solution.

Sketch

#include "BluetoothSerial.h"

uint8_t address[6] = {0x98, 0xDA, 0x20, 0x03, 0xA5, 0x24};
char *pin = "1234";

BluetoothSerial SerialBT;

void setup() {
  Serial.begin(115200);
  SerialBT.begin("ESP32", true);
  SerialBT.setPin(pin);
  SerialBT.connect(address);
}

void loop() {
  if(SerialBT.available()) {  
    Serial.print(SerialBT.read());
  }
}

Debug Message

12365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536
ASSERT_WARN(1 8), in lc_task.c at line 1394
1236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536
ASSERT_WARN(1 8), in lc_task.c at line 1394
12366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536123654858485857485848125361236651565845494958455348585748125361236548584858574858481253612366515658454949584553485857481253612365485848585748584812536123665156584549495845534858574812536
ASSERT_WARN(1 8), in lc_task.c at line 1394

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[zvikaf]

Got the same error, But to my surprise it happens only if i connect to an HC-06 that is connected to arduino nano.
connecting the HC-06 with FTDI to the USB stops the error ...
Nothing was changed in the ESP32 program.
Did some checks, disconnected the TX RX lines at the HC-06.. had still errors..
moved the dongle closer to the ESP .. and all is gone, suspect either power problem or noisy reception :-)
and now it's back ... have no idea what was changed

[alastaira]

Curious. In my case, the HC-06 is connected to an STM32F103 chip, but I've no reason to think there's any issue with the power supply.

[zvikaf]

my HC-06 connects to NANO, tried two HC-06 boards, tried also with external 5V supply, made no difference.
This error is only up when the ESP32 is connected on SPP... anyway is has no affect on my code as I do not use the serial (just for debug) and the OLED screen used, works fine, also checked range and found no effect (yet) :-)

[magicmicros]

Same problem here, communicating with an ANT BMS (not sure that module is on that).
Usually get the ASSERT shortly after a 140 byte block have been received, but sometimes it occurs in the middle of the block.

[VojtechBartoska]

Hello, can you please retest this on v2.0.3-rc1?

[magicmicros]

Sadly, still the same.
My error message is "ASSERT_WARN(1 8), in lc_task.c at line 1409".
I'm connecting to an ANT BMS, using SPP.
Simple comms, sending 6 bytes, receiving 140 bytes, repeated every second.
The ASSERT doesn't always show up, but comes every 4-5 blocks or so.

[magicmicros]

Maybe I should add that I'm on an old WROOM module.
Chip is ESP32-D0WD (revision 1)

[VojtechBartoska]

Ok, thanks for testing. I'm adding this to our Roadmap and we will test it. :)