So you're a Noob? Post your questions here until you graduate! Don't be shy.

User avatar
By Fed
#58633 I am trying to program an ESP8266 using OSX 10.11 (El Capitan).

I have tried to connect to it via FTDI, as well as via PL2303. In both cases, I can see the serial connection in terminal, and if I connect the ESP8266's Rx to Tx and use the Serial Monitor in Arduino IDE, my typed text is echoed as expected. This suggests the FTDI and PL2303 are working (am I correct in assuming this?)

As soon as I connect the ESP8266 to the FTDI or PL2303, the serial connections disappear. If I then disconnect the ESP 8266, the connection reappears after 2-10 seconds. The connection to the connected ESP8266 returns sporadically, whereupon I have been able to use the Serial Monitor (in Arduino IDE) to send commands to the ESP8266. Specifically, I have had the following result for AT+RST:


AT+RST
OK

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: 8Mbit(512KB+512KB)
jump to run user1 @ 1000

don't use rtc men data


This does not look like what would be expected. I have searched high and low, but have only found 2 occasions where people have asked for help about this same issue. In both cases, the OP noted that they have resolved the issue, but did not post how.

I know it sound ridiculous, but I have spent over 10 hours on this, without resolution. I have checked the connections, examined the soldering on the FTDI and PL2303, reinstalled OSX drivers several times, etc.

When the ESP8266 is connected to the FTDI or PL2303, if I connect the reset pin to ground, the serial connection appears again. Once I remove the reset pin from the ground, it disappears again. The blue led on the ESP8266 flashes twice when I do this.

Any help would be greatly appreciated. I cannot move forward with my project (an alarm system that will email me when triggered) without this component.
User avatar
By RichardS
#58671 Again so I hope we can get you some help... OSX has been a pain for a lot of people as most things have been done in Windows and Linux.... let see if other OSX people can pipe in here...

RichardS
User avatar
By Fed
#58692 I figured it out. I did not set up an external 3.3v supply, and the FTDI USB could not suply the required current. Once I did set up the external supply, all worked well.

I then tried to upload a sketch via Arduino IDE, and I got:

Sketch uses 222,141 bytes (51%) of program storage space. Maximum is 434,160 bytes.
Global variables use 31,508 bytes (38%) of dynamic memory, leaving 50,412 bytes for local variables. Maximum is 81,920 bytes.
/Users/fed/Library/Arduino15/packages/esp8266/tools/esptool/0.4.9/esptool -vv -cd ck -cb 115200 -cp /dev/cu.usbserial-A50285BI -ca 0x00000 -cf /var/folders/lb/5zdjdm6153jcx_5nq32tt7gw0000gn/T/build630bdedc97ed411bfadf0f4a1e3b906f.tmp/Blink.ino.bin
esptool v0.4.9 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
setting board to ck
setting baudrate from 115200 to 115200
setting port from /dev/tty.usbserial to /dev/cu.usbserial-A50285BI
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
espcomm_upload_mem
opening port /dev/cu.usbserial-A50285BI at 115200
tcgetattr
tcsetattr
serial open
opening bootloader
resetting board
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
resetting board
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
resetting board
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
trying to connect
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
warning: espcomm_sync failed
error: espcomm_open failed
error: espcomm_upload_mem failed



Now, when I connect and then disconnect the ESP reset pin to ground, the blue LED flashes once, not twice as it used to. In the Serial Monitor, I see:

ets_main.c
ets Jan 8 2013,rst cause:2, boot mode:(1,7)


When I connect GPIO0 to ground, and then connect/disconnect reset to ground, I see:

ets Jan 8 2013,rst cause:2, boot mode:(3,7)


Have I totally messed up the ESP? If not, how can I fix it?

Thanks in advance.
User avatar
By Fed
#58733 Here is some more testimg results. It seems I can connect ans receive data, but nonly id data. Any idea what is occuring here?

Clinic:~ fed$ esptool.py --baud 115200 --port /dev/tty.usbserial-A50285BI flash_id
esptool.py v1.3-dev
Connecting...
Manufacturer: e0
Device: 4014

Clinic:~ fed$ esptool.py --baud 115200 --port /dev/tty.usbserial-A50285BI chip_id
esptool.py v1.3-dev
Connecting...
Chip ID: 0x001eb645

Clinic:~ fed$ esptool.py --baud 115200 --port /dev/tty.usbserial-A50285BI read_mac
esptool.py v1.3-dev
Connecting...
MAC: 5c:cf:7f:1e:b6:45

Clinic:~ fed$ esptool.py --baud 115200 --port /dev/tty.usbserial-A50285BI erase_flash
esptool.py v1.3-dev
Connecting...
Running Cesanta flasher stub...
A fatal error occurred: Timed out waiting for packet header