- Thu Oct 26, 2017 10:36 pm
#71256
I haven't even thought to try that! I have tried flashing both the blink example for the 8266, and the check flash config, but I haven't changed the flash size from the default.
- Fri Oct 27, 2017 10:28 am
#71274
I've tried it with a few different flash configurations, including the smallest possible footprint. I've been trying to flash the blink and checkFlashConfig examples for the ESP8266, and neither is working.
- Mon Oct 30, 2017 2:02 pm
#71393
I've solved it. Turns out my FTDI adapter went bad, but in an odd way where it still appears to work, the driver still gets loaded, etc. Serial communications just doesn't work properly. Diagnosed by using it to sniff serial logging from the Nano's TX and RX pins, which I'd been able to confirm were working through the onboard CH340.
This is also not related to the counterfit chip issue where the device ID gets changed by FTDI's driver. Must've shorted something out in the clutter on my desk at some point. So many red herrings in this process!
This is also not related to the counterfit chip issue where the device ID gets changed by FTDI's driver. Must've shorted something out in the clutter on my desk at some point. So many red herrings in this process!
- Mon Oct 30, 2017 3:48 pm
#71398
Might still be FTDI's fault, rewriting the USB IDs wasn't their only way to mess with unsuspecting end users: https://hackaday.com/2016/02/01/ftdi-dr ... ips-again/
ptrsnja wrote:This is also not related to the counterfit chip issue where the device ID gets changed by FTDI's driver. Must've shorted something out in the clutter on my desk at some point. So many red herrings in this process!
Might still be FTDI's fault, rewriting the USB IDs wasn't their only way to mess with unsuspecting end users: https://hackaday.com/2016/02/01/ftdi-dr ... ips-again/
