ESP32C6 release binaries use UART on IO19 and IO10

[gworkman]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

HCI UART on IO12 and IO5 for ESP32C6, as suggested by the docs

Actual behavior (suspected bug)

sdkconfig claims UART on IO19 and IO10

I haven't been able to get HCI to work over UART yet, and I think it's because I am connected to IO5 and IO12, rather than IO19 and IO10

Error logs or terminal output

Steps to reproduce the behavior

Steps:

• Download ESP-Hosted-NG-release_v1.0.4.0.0
• file path: esp32c6/sdio+uart/sdkconfig
• lines 681/682:

  CONFIG_BT_LE_HCI_UART_TX_PIN=19
  CONFIG_BT_LE_HCI_UART_RX_PIN=10
  

Project release version

V1.0.4.0.0

System architecture

ARM 32-bit (Raspberry Pi 32-bit)

Operating system

Linux

Operating system version

Custom buildroot

Shell

other (details in Additional context)

Additional context

I have been unsuccessful in getting the driver to recognize a custom firmware when I load one that I build myself. Perhaps I am customizing it incorrectly. Updated firmware binaries would be appreciated

[mantriyogesh]

@Shreyas0-7 PTAL

[Shreyas0-7]

Hey @gworkman sorry for the discrepancy although the documentation specifies IO 5 and IO 12, the esp32c6 binaries in the release are actually configured to use IO 19 and IO 10. Thanks for pointing this out, we are pushing a new release to rectify the issue.

[gworkman]

Hi @Shreyas0-7, thanks for taking a look. When you cut the new release I'm happy to test it out and see if it resolves the issue.

Another thing I wanted to point out - after submitting the issue, I also realized that every version of the sdio+uart binaries (including ones that were downloaded from the releases and the ones that I attempted to compile myself) failed on the linux side. The logs always show esp32_sdio mmc1:0001:1: probe with driver esp32_sdio failed with error -110.

Searching other issues here suggests that is a signal integrity issue, but I don't think that is the case here. The sdio_only binary from the v1.0.4.0.0 release works fine, and the ESP32 is mounted on a PCB with trace length and impedance matching. I don't know where I am going wrong, although I haven't used my oscilloscope to debug yet. I suspect perhaps another pin configuration issue on ESP firmware side.

This is with git tag v1.0.4.0.0 and only the following changes to sdkconfig.defaults.esp32c6:

 CONFIG_BTDM_CTRL_MODE_BTDM=n

 # SPI/SDIO only
-CONFIG_BT_LE_HCI_INTERFACE_USE_RAM=y
+# CONFIG_BT_LE_HCI_INTERFACE_USE_RAM=y

 # BLE over UART:
 # Enable below config, delete sdkconfig, build/ and rebuild
-# CONFIG_BT_LE_HCI_INTERFACE_USE_UART=y
+ CONFIG_BT_LE_HCI_INTERFACE_USE_UART=y
  CONFIG_BT_LE_HCI_UART_TX_PIN=5
  CONFIG_BT_LE_HCI_UART_RX_PIN=12
  CONFIG_BT_LE_HCI_UART_FLOWCTRL=n

Followed by:

# clean the build dir
rm -rf build sdkconfig

# set the target
idf.py set-target esp32c6

# build
idf.py build