module goes away after changing baud rate
Posted: Sun Jan 10, 2016 12:52 pm
Hi,
I've got some esp-01 module. I'm trying them out by terminal, by various libraries, etc.
First I've upgraded the firmware to AT 0.9.5.2 (it seemed to be stable). It worked, I was able to connect to wifi ap, etc.
And then I needed to change baud rate to 19200. I issued an AT+IPR=19200. I changed baud rate of terminal to 19200 and sent a simple AT. I got response OK. Well, at this point everything is okay.
Then I made an AT+RST. Module rebooted and from that point I wasn't able to communicate with it. I did a lot of tries at 19200 but nothing happened. Then - accidentally - I noticed that module sends some stuff at 115200 right after it gets power. The stuff looked like this (<...trash...> means a lot of random bytes):
<...trash...>MEM CHECK FAIL!!!
ets Jan 8 2013,rst cause:4, boot mode:(3,0)
wdt reset
load 0x40100000, len 816, room 16
tail 0
chksum 0x8d
load 0x3ffe8000, len 788, room 8
tail 12
chksum 0xcf
ho 0 tail 12 room 4
load 0x3ffe8314, len 288, room 12
tail 4
chksum 0xcf
csum 0xcf
2nd boot version : 1.2
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size : 4Mbit
jump to run user1
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
....
Again, module worked well before changing baud!
With first module I thought this is a HW failure. But I can repeat all the above happening with another module....
Can anyone suggest some useful methods to get modules back to life?
I've got some esp-01 module. I'm trying them out by terminal, by various libraries, etc.
First I've upgraded the firmware to AT 0.9.5.2 (it seemed to be stable). It worked, I was able to connect to wifi ap, etc.
And then I needed to change baud rate to 19200. I issued an AT+IPR=19200. I changed baud rate of terminal to 19200 and sent a simple AT. I got response OK. Well, at this point everything is okay.
Then I made an AT+RST. Module rebooted and from that point I wasn't able to communicate with it. I did a lot of tries at 19200 but nothing happened. Then - accidentally - I noticed that module sends some stuff at 115200 right after it gets power. The stuff looked like this (<...trash...> means a lot of random bytes):
<...trash...>MEM CHECK FAIL!!!
ets Jan 8 2013,rst cause:4, boot mode:(3,0)
wdt reset
load 0x40100000, len 816, room 16
tail 0
chksum 0x8d
load 0x3ffe8000, len 788, room 8
tail 12
chksum 0xcf
ho 0 tail 12 room 4
load 0x3ffe8314, len 288, room 12
tail 4
chksum 0xcf
csum 0xcf
2nd boot version : 1.2
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size : 4Mbit
jump to run user1
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0):
epc1=0x40201884, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
....
Again, module worked well before changing baud!
With first module I thought this is a HW failure. But I can repeat all the above happening with another module....
Can anyone suggest some useful methods to get modules back to life?