Thank David, that's great to hear. Suppose the info on their site might be old or incorrect so it's good to see somebody has it working sucessfully.

-Paul

I'm building a project using the ESP32-IDF (not Arduino). It's working on a Hiletgo ESP32S driving an OLED screen and communicating via BLE. The advice on Adafruit's website seems to indicate it's tested for Arduino IDE and says "with a USB interface that lets you quickly use it with the Arduino IDE ...

I fixed the issue wiping out the esp-idf directory by redoing all the steps again. Not sure what happened, but it's working now.

I'm trying to track down a bug in the ESP code, so first I wanted to see if it's addressed already so I pulled from master. After the pull, I'm no longer able to build my project. I tried building the hello_world from the examples, and that worked. However, the bluedroid/ble examples don't compile ...

I determined I made a stupid mistake, though debugging with jlink edu mini is not working yet. The first problem is that I had the cable backwards. I picture I found showed it connected incorrectly which I now found is backwards. I see that it connects, but now it's getting timeout errors. I do see ...

I'll continue to post progress of my research in case it reveals a clue or helps somebody in the future.

I've tracked the disconnect logging back to this stack trace. This is processing a queue, which I think is created for each connection. There is an Event = 5 which is disconnect,


0x4008dcb5 ...

I'm trying to setup a debugging, but OpenOCD fails to connect and repeats the warning "Failed to receive data from device: LIBUSB_ERROR_TIMEOUT." Then I see Error: Sending data to device timed out. I'll put the full output below.

The steps I remember that I took to get here are:
1. Installed driver ...

I still have problems. I can make the gattc_multi_connect.c reproduce my problems more frequently if I comment out the following lines:


//esp_log_buffer_hex(GATTC_TAG, scan_result->scan_rst.bda, 6);
//ESP_LOGI(GATTC_TAG, "Searched Adv Data Len %d, Scan Response Len %d", scan_result->scan_rst ...

More info about #2, the messages I see with gattc_multi example are as follows.

W (8331) BT_APPL: bta_gattc_conn_cback() - cif=3 connected=0 conn_id=3 reason=0x0008
W (8331) BT_APPL: bta_gattc_conn_cback() - cif=4 connected=0 conn_id=4 reason=0x0008
W (8341) BT_APPL: bta_gattc_conn_cback() - cif=5 ...

I've switched to using the gattc_multi_connect.c example per @genedyne's advice. And that example is where the exception occurs. Glad to hear that it's been addressed. If you know of a specific patch, I would appreciate it, but I can also look and try to figure it out.

But I also run into my ...