Missing "+BTDATA:" message end (terminating / CR LF) bytes.
Posted: Mon Nov 06, 2023 1:49 pm
Hello,
My device is controlled via BT and I want to send a large amount of data over Wi-Fi. When I start sending I also occasionally get BT polling bytes. Everything seems fine, but at some point two messages merge and the terminating bytes (0x0D 0x0A) are skipped. Normally it is happen at the end of the "+BTDATA:" new BT data message .
Is it normal behavior for messages to be linked/merged like this?
I have CONFIG_ESP_COEX_SW_COEXIST_ENABLE enabled (if this helps) and hardware flow control - connect CTS/RTS pins.
Version Info:
I've done a lot of tests and missing bytes are always this two (0x0D 0x0A) at the end of "+BTDATA:". I have attached image of my logs (Missing-CR-LF - log.png) and images from my uart buffer that you can see missing (0x0D 0x0A) bytes.
My device is controlled via BT and I want to send a large amount of data over Wi-Fi. When I start sending I also occasionally get BT polling bytes. Everything seems fine, but at some point two messages merge and the terminating bytes (0x0D 0x0A) are skipped. Normally it is happen at the end of the "+BTDATA:" new BT data message .
Is it normal behavior for messages to be linked/merged like this?
I have CONFIG_ESP_COEX_SW_COEXIST_ENABLE enabled (if this helps) and hardware flow control - connect CTS/RTS pins.
Version Info:
Code: Select all
AT version:3.3.0.0-dev(s-d5269eb - ESP32 - Sep 19 2023 03:00:47)
SDK version:v5.0.2-376-g24b9d38a24-dirty
compile time(34be80ff):Nov 2 2023 11:29:47
Bin version:v3.2.0.0(MY-PICO)