×

SparkFun Electronics will be closed in observance of memorial day on Monday, May 29th. We will resume normal business hours on Tuesday, May 30th. Any orders placed after 2pm Mountain Time on Friday, May 26th will process and ship out on Tuesday, May 30th.

avatar

Christopher Baker

Member Since: June 18, 2007

Country: United States

Profile

Websites

http://christopherbaker.net

  • Yeah, I tried all of those things. I’ve tried it with the latest stable esp8266 Arduino, and the latest esptool-ck (which happens to be the same one that is included with the esp8266 Arduino).

    I’ve now tried it with 4 or 5 boards and both using Arduino and manually and get the same output:

    esptool-ck  -vvv -cd ck -cb 115200 -cp /dev/cu.usbserial-DA01R6ZH -ca 0x00000 -cf /var/folders/l9/mgv_83hx22g9lrmsx1cnwg4w0000gn/T/build3564637723258270712.tmp/ESP8266_Standalone.cpp.bin
    esptool v0.4.6 - (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-DA01R6ZH
        setting address from 0x00000000 to 0x00000000
        espcomm_upload_file
        stat /var/folders/l9/mgv_83hx22g9lrmsx1cnwg4w0000gn/T/build3564637723258270712.tmp/ESP8266_Standalone.cpp.bin success
    opening port /dev/cu.usbserial-DA01R6ZH at 115200
        tcgetattr
        tcsetattr
        serial open
    opening bootloader
    resetting board
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    resetting board
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    resetting board
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    trying to connect
        setting character timeout 0
        done
        setting character timeout 1
        done
        espcomm_send_command: sending command header
        espcomm_send_command: sending command payload
            espcomm_send_command: didn't receive command response
    warning: espcomm_sync failed
    error: espcomm_open failed
    

    We have a workshop with 25 of these tomorrow morning and we’re kind of up a creek without a paddle at the moment. I’ve contacted the support team several times over the last few days via email on via the web form with no response.

  • For what it’s worth, if I manually take GPIO0 to ground on startup, it will enter bootloader mode and I can program it via the integrated FTDI/USB cable.

    Is this normal or should the integrated FTDI/USB be taking GPIO0 low automatically w/DTS … ?

  • Hi there, just received the new WRL-13711 board and am unable to upload a program using Arduino or the standard esptool / espressif sdk. I have been working with the older WRL-13231 (and generic ESP8266s) and am able to upload programs using an FTDI breakout.

    So here’s what I know:

    • The FTDI device shows up and I can connect to whatever program was shipped with the unit (confirmed with CoolTerm, screen, etc).
    • When uploading there are three groups of three blinks on the RX led of the WRL-13711. This is the same pattern I see when initiating an upload on the WRL-13231, so I believe the FTDI is communicating correctly.
    • I’ve tested several USB cables in an attempt to confirm that isn’t the problem. Each exhibits the same blinks.
    • In the past when the esptool failed, I powered off the device, unplugged and replugged the usb, and tried slower communication speeds and the WRL-13231 would eventually accept a program. No combination of speeds, unplugging and replugging, power-cycling, etc has worked thus far.
    • I’ve tested this on two units so far and both seem to have the same problem. I’ve got 20+ other units that I could test, but imagine it’s probably the same issue.
    • To my eye, the blink pattern and fail looks like the situation that happens when the board is not put into bootloader mode. On the WRL-13231 this was done via DTR – not sure how it’s working on the DEV board, but haven’t looked at it too closely yet. Perhaps the board is not going into bootloader mode successfully? Anyway I scoured the hookup guide (of course … it’s quite possible that I missed it), but I didn’t find any special instructions for manually placing the device in bootloader mode.

    Thanks! Christopher

No public wish lists :(