- Make sure to use ESP32 wrover kit. If you are using a different ESP32 module, please check SDIO pull up requirements
- Recheck jumper cable connections. Try to use cables that are smaller in length(less than 10 cm should work).
- Make sure that driver module is loaded.
$ sudo lsmod | grep esp32
esp32 28672 0
- Check if host could perform sdio level enumeration. Assuming ESP32 gets detected as mmc1, execute following and check the output.
$ sudo cat /sys/devices/platform/soc/fe300000.mmc/mmc_host/mmc1/mmc1\:0001/mmc1\:0001\:1/uevent
SDIO_CLASS=00
SDIO_ID=6666:2222
MODALIAS=sdio:c00v6666d2222
- In case issue persists, collect and send following logs to Espressif support.
- dmesg log on host
- Output of above mentioned commands
- ESP console log
Network interfaces are by default in down state. Execute ifconfig -a
to see those.
In case issue persists, collect and send following logs to Espressif support.
- dmesg log on host
- Output of above mentioned commands
- ESP console log
- Check ESP console log for wlan disconnect event. For reconnection, execute provided python script.
- Execute
route -n
command on host and verify that appropriate routes are configured. - In case issue persists, collect and send following logs to Espressif support.
- dmesg log on host
- Output of above mentioned commands
- ESP console log
- WLAN air capture log
- Make sure that bluetooth is not blocked on host
$ sudo rfkill list
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
- Execute
hciconfig
command to ensure that device is detected and initialized properly - User permissions
$ sudo usermod -G bluetooth -a pi
- Reinstall bluetooth software
$ sudo apt remove bluez bluez-firmware pi-bluetooth
$ sudo apt install bluez bluez-firmware pi-bluetooth
- Restart bluetooth service
$ sudo systemctl restart bluetooth
$ sudo systemctl status bluetooth
- In case issue persists, collect and send following logs to Espressif support.
- dmesg log on host
- Output of above mentioned commands
- ESP console log
- hcidump log (
hcidump -X -t
)