The ESP8089 driver's "reset on module unload/reboot" function doesn't seem to work. The problem is - after a ZeroPhone is rebooted through software, ESP8266 is no longer recognized as a network card, even though:
GPIO0 is connected to the CH_PD GPIO of the Pi Zero
GPIO0 seems to be successfully toggled on the first boot, just not on following reboots
modprobe -r esp8089 does nothing, the module doesn't show up in lsmod and attempting to remove the module fails. I didn't get the kernel logs from the ZeroPhone yet, but I will as soon as I have the opportunity. Also, as a side effect, "Shutdown" and "Reboot" functions become inaccessible in ZPUI for some reason. I didn't delve further because of lack of USB_UART with me, but it might as well be a kernel panic or something like it.
Also, a peek into dmesg (through ZPUI) shows some mmc1 (the SDIO bus used for ESP) errors. I'm guessing the driver doesn't reset the ESP for some reason - which it should (at least from my understanding of the source code)
The ESP8089 driver's "reset on module unload/reboot" function doesn't seem to work. The problem is - after a ZeroPhone is rebooted through software, ESP8266 is no longer recognized as a network card, even though:
modprobe -r esp8089does nothing, the module doesn't show up inlsmodand attempting to remove the module fails. I didn't get the kernel logs from the ZeroPhone yet, but I will as soon as I have the opportunity. Also, as a side effect, "Shutdown" and "Reboot" functions become inaccessible in ZPUI for some reason. I didn't delve further because of lack of USB_UART with me, but it might as well be a kernel panic or something like it.Also, a peek into dmesg (through ZPUI) shows some mmc1 (the SDIO bus used for ESP) errors. I'm guessing the driver doesn't reset the ESP for some reason - which it should (at least from my understanding of the source code)
Links: