I need RFCOMM as well. The last I was told the RFCOMM protocol doesn't work. It is due in one of the early 3.0 releases. So, no, there is no example.

I'm looking at the i2s example (i2s_example_main.c from 2.0 rc1) and am really confused by something. The setup_triangle_sine_waves function creates what looks like 1 wave form of 100 Hz data (10 msec) and sends it to the i2s via i2s_write_bytes. The main loop then delays for 5000 msec. I don't unde...

Thanks - and it sounds like a good plan.

In terms of requirements, I need the ability to define address bits and dummy bits on a per message basis not on a per device basis. I'm assuming that the parallel operation (DIO, QIO) starts with the data field and that command, address, and dummy fields are all on a single wire. Another option wou...

I'm trying to access a Micron SPI NAND Flash Memory chip via the SPI library (spi_master). The library looks like it was designed for a protocol where all messages have the same format, i.e. same command bits, address bits and dummy bits for each message. When you set up a device, that's where those...

For those reading this thread, JTAG Debugging on a custom board isn't appreciably different than on the WROOM dev kit board. My issue was that GPIO0 was shorted to ground because a part was installed incorrectly. GPIO 0 is a strapping pin, that if held low, causes the ESP32 to try to download the pr...

I'm somewhat confused by the documentation on strapping pins. I think there's a mistake. Rev 1.5 of ESP32 Datasheet section 2.4 discusses them. It says there are 5 while Rev 2.2 of the Technical Reference Manual shows 6 bits used in the GPIO_STRAPPING register. The ESP32 Datasheet also has MTDO doin...

I realized I had never flashed the bootloader.bin or partitions_singleapp.bin to the custom board and thought that might be the problem. The dev kit had those components downloaded via the USB port prior to my JTAG debugging. I flashed: bootloader.bin to 0x1000 partitions_singleapp.bin to 0x8000 No ...

I'm trying to debug a custom board through JTAG (using Tiao Tumpa debugger). I'm able to do 4-line JTAG flash and debugging on the dev kit board which uses the ESP-WROOM-32 module. The custom board uses the same module and appears also to flash successfully. Both boards have the same openocd logs wh...

No. AFAICT, the RFCOMM aspect of the BT library does not work. See this thread: https://www.esp32.com/viewtopic.php?f=18&t=1928&p=9328&hilit=rfcomm#p9328 After reading that, it made sense why the RFCOMM directories weren't included in the library build - they don't work. I followed up asking when th...