- Sun Jan 25, 2015 3:07 pm
#8200
I had my esp working at 9600baud.
I connected GPIO0 to GROUND for flashing. Powered it on, got some garbage as expected due to bootloader having some diff baud rate(and using binary?).
Wifi access point disappeared(which suggested bootmode entered). However esptool fails to connect.
Worst part is that now even if i boot without GPIO0 set to ground, I can no longer communicate with my esp at any baud rate
. I get garbage on boot(eg bootloader?), then the access point appears...but now my esp wont respond to AT commands.
Any ideas?
Does holding gpio0 on ground for too long wipe some important settings?
my firmware rev is 0018000902 + some suffix. not sure if that helps.
Update setting GPIO0 to high(VCC/CH_PD) got me back to being able to AT at 9600. Still would like to flash firmware
update 2 Solution was to find out that screen /dev/ttyAMA0 9600,leaves port open even after i kill it..So esp.py was not able to read from serial port, only write.
I connected GPIO0 to GROUND for flashing. Powered it on, got some garbage as expected due to bootloader having some diff baud rate(and using binary?).
Wifi access point disappeared(which suggested bootmode entered). However esptool fails to connect.
Worst part is that now even if i boot without GPIO0 set to ground, I can no longer communicate with my esp at any baud rate
. I get garbage on boot(eg bootloader?), then the access point appears...but now my esp wont respond to AT commands.Any ideas?
Does holding gpio0 on ground for too long wipe some important settings?
my firmware rev is 0018000902 + some suffix. not sure if that helps.
Update setting GPIO0 to high(VCC/CH_PD) got me back to being able to AT at 9600. Still would like to flash firmware
update 2 Solution was to find out that screen /dev/ttyAMA0 9600,leaves port open even after i kill it..So esp.py was not able to read from serial port, only write.
