- Sun Jan 25, 2015 6:36 am
#8150
I can't seem to get my ESP-03 to break out of the weird 75k baudrate. The only way I can connect is by going into "flashing" mode (gpio 15, 0 both low), then I can read mac, and such. The chip runs and puts up an access point (gpio 15 low only), but refuses to communicate by UART.
- Sun Jan 25, 2015 10:53 am
#8172
Hey, I can't see anything you've done wrong so far. You might want to provide us with more details regarding your setup and procedure.
- Sun Jan 25, 2015 9:50 pm
#8219
It all started when I could not get either of my ESP-03's to respond to AT commands. I wired them up like this: CH_PD=VCC, GPIO15=GND. I could see bootloader output at 75k baud, followed by rom program output at 9600 baud. However, any input on UART was ignored. I could see an access point come up.
At this point I read that ESP-03's from factory don't respond to AT commands, so I proceeded to flash the latest firmware from Electrodragon (https://drive.google.com/folderview?id= ... sp=sharing). First, I additionally tied GPIO0 to GND, then used esptool. With esptool I could read_mac and get flash_id, but only when GPIO0 was grounded.
I flashed like this:
After flashing, and removing GPIO0 to GND link, I could see a new access point come up. The name changed slightly from before. As before, I can see bootloader output on booting at 75k baud, but I no longer see anything from the rom program. Or maybe the rom program isn't running, but then I do see the new access point, so probably it is running. Needless to say I still can't communicate over UART with the module, in fact it's even worse that before
Currently I am working on building a firmware from source using the IoT SDK to see if that will change anything...
At this point I read that ESP-03's from factory don't respond to AT commands, so I proceeded to flash the latest firmware from Electrodragon (https://drive.google.com/folderview?id= ... sp=sharing). First, I additionally tied GPIO0 to GND, then used esptool. With esptool I could read_mac and get flash_id, but only when GPIO0 was grounded.
I flashed like this:
Code: Select all
#./esptool.py write_flash 0x000000 New-AI-v0.9.5.0_AT_Firmware.binAfter flashing, and removing GPIO0 to GND link, I could see a new access point come up. The name changed slightly from before. As before, I can see bootloader output on booting at 75k baud, but I no longer see anything from the rom program. Or maybe the rom program isn't running, but then I do see the new access point, so probably it is running. Needless to say I still can't communicate over UART with the module, in fact it's even worse that before
Currently I am working on building a firmware from source using the IoT SDK to see if that will change anything...
- Mon Jan 26, 2015 9:03 am
#8245
Well, mine were already flashed with an AT firmware, I just had to choose the correct terminal settings: 9600, 8, 1, N, CR+LF. I wasn't much interested in using those commands though, so I soon flashed a NodeMCU Lua firmware, using NodeMCU's flasher, and it went seamlessly. You might want to try that path to test your setup before going the hassle of building a new firmware.
You don't mention power supply which is a frequent cause of failure. Check that yours can provide enough current. Use an external one if you can, and connect the serial adapter to Tx, Rx, and ground only.
I also found a pinout (on Pete Scargill's blog AFAIR) which I have slightly corrected:
...and I also wrote down the following notes as a foolproof setup:
To bring ESP-03 into firmware update mode from power down without having to wiggle the reset pin:
Connect GPIO0 and GPIO15 to GND, CH_PD to VCC before powering up the module. (GPIO0 can then be left floating or up.)
Then launch tool to flash a .bin file.
I remember trouble when CH_PD was pulled directly up, and adding a resistor in the 1~10k range solved it.
I hope that'll help.
esp03madness wrote:I read that ESP-03's from factory don't respond to AT commands
Well, mine were already flashed with an AT firmware, I just had to choose the correct terminal settings: 9600, 8, 1, N, CR+LF. I wasn't much interested in using those commands though, so I soon flashed a NodeMCU Lua firmware, using NodeMCU's flasher, and it went seamlessly. You might want to try that path to test your setup before going the hassle of building a new firmware.
You don't mention power supply which is a frequent cause of failure. Check that yours can provide enough current. Use an external one if you can, and connect the serial adapter to Tx, Rx, and ground only.
I also found a pinout (on Pete Scargill's blog AFAIR) which I have slightly corrected:
...and I also wrote down the following notes as a foolproof setup:
To bring ESP-03 into firmware update mode from power down without having to wiggle the reset pin:
Connect GPIO0 and GPIO15 to GND, CH_PD to VCC before powering up the module. (GPIO0 can then be left floating or up.)
Then launch tool to flash a .bin file.
I remember trouble when CH_PD was pulled directly up, and adding a resistor in the 1~10k range solved it.
I hope that'll help.
You do not have the required permissions to view the files attached to this post.
