I found it. needed a 1ms delay after the tx on the windows side. Now I am getting 2k bytes through with no crashes. baud rate with 25 bytes per send is about 9600baud. Here's the working program on the windows side (esp32 side is unchanged from above): #include <stdio.h> #include <windows.h> #includ...

I also tried this on multiple devices with the same result so it is not a unit problem.

Thank you for the link. So it appears to be normal. I will need to figure out how the application will know which port to use since it varies from connection to connection. I could test both, might be able to find a register value, etc.

I am using the ESP32 to communicate with my Windows 10 PC via a Bluetooth classic SPP profile. This creates a com port in windows. I then wrote a simple program on the windows side that tests the connection through the serial port. However, after a 100 bytes or so, the connection freezes. I have to ...

I did notice that under "Bluetooth settings" in windows, one port is listed at incoming and one is listed as outgoing. but when I connect to the correct port (whichever one it is at that time), I can send and receive. how to only get one port? the "outgoing" port seems to be the one that works. but ...

When I connect the ESP32 to my PC, I see 2 com ports in windows. I searched online for an answer. Found some examples but they showed two com ports as well. One of the ports (which one changes randomly) does not work. You have to try both. The 2 ports show up in windows device manager and at the com...

It's been about a year since I posted this. Does anyone know of a working example in Windows?

printf("%.20s\n",(const char *)data); works. Thanks. It does insert occasional new lines that are not necessary:

1267

1264
1264
1264
12
64
1264
1264
1264

1267
1264
1264

1267

Good idea. I changed it to 4096. This changed the behavior although it is erratic. Sometimes now it will print ~100 readings before crashing while other times it just crashes right away. I (360) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. UART test 1264 ...

I am getting a stack overflow error when I try to display to the monitor ("make monitor") data received on UART 1 or 2. I am wondering if this is related to the the buffer sync problem (https://github.com/espressif/arduino-esp32/pull/1849) or is there something else I am missing? /* UART Echo Exampl...