- Fri Nov 02, 2018 1:07 pm
#78995
Hello there,
I am new to the ESP8266 ecosystem. I have hooked up a fast testing setup with an ESP-07s and an FT232 usb to uart bridge. I provided enough 3V3 power supply current. When I connected the device and check the uart log, I see garbage. Thanks to this post ( viewtopic.php?t=2298 ), I was finally able to figure out what is the baud parameters for that garbage and see the output (more or less):
Interesting this is that right after this is printed out, the baud changes to 115200 (probably 8N1 no parity). The problem is that the device returns echo (so I see what I type) instead receiving an answer to my at commands. In the topic I linked, the author says that his device turned to 9600 baud after the garbage was spit (mines at 115200). I tried grounding GPIO15 but that did not help. The starting log says that I am in boot mode "(3,0)"- is that correct? I have only connected the power, uart lines and pulled up the EN line in my module. Should I provide more pull-ups or downs?
I would appreciate all help regarding this topic.
I am new to the ESP8266 ecosystem. I have hooked up a fast testing setup with an ESP-07s and an FT232 usb to uart bridge. I provided enough 3V3 power supply current. When I connected the device and check the uart log, I see garbage. Thanks to this post ( viewtopic.php?t=2298 ), I was finally able to figure out what is the baud parameters for that garbage and see the output (more or less):
Code: Select all
ets Jan 8 2013,rst cause:2, boot mode:(3,0)
load 0x40100000, len 1856, room 16
tail 0
chksum 0x63
load 0x3ffe8000, len 776, room 8
tail 0
chksum 0x02
load 0x3ffe8310, len 552, room 8
tail 0
chksum 0x79
csum 0x79
2nd boot version : 1.5
SPI Speed : 40MHz
SPI Mode : DIO
SPI Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000
rf cal sector: 1017
rf[112] : 00
rf[113] : 00
rf[114] : 01
SDK ver: 1.5.4.1(39cb9a32) compiled @ Jul 1 2016 20:04:35
phy ver: 972, pp ver: 10.1
˘hhńi×(¦)ń+ůkPx\Ŕt·Nř˘Ŕj§lInteresting this is that right after this is printed out, the baud changes to 115200 (probably 8N1 no parity). The problem is that the device returns echo (so I see what I type) instead receiving an answer to my at commands. In the topic I linked, the author says that his device turned to 9600 baud after the garbage was spit (mines at 115200). I tried grounding GPIO15 but that did not help. The starting log says that I am in boot mode "(3,0)"- is that correct? I have only connected the power, uart lines and pulled up the EN line in my module. Should I provide more pull-ups or downs?
I would appreciate all help regarding this topic.
