• I have double checked the speed setting and it is at 115200. Have attached a few screenshots. Is there something in Linux such as a permission setting or something that could prevent Chrome from connecting? I'm running Debian version stretch (9.6).


  • One more thing to check: Settings -> Console, maybe that contains some clue.

    Here is the output from my machine (You said you have a windows machine, but may save some time)

    >>> Connecting...
    ForceThrottle option is set - set Slow Write = true
    [object Object]
    Connected [object Object]
    Got "E (544) spiram: SPI RAM enabled but initialization failed. Bailing out.\r\n"
    No Prompt found, got "\n" - issuing Ctrl-C to try and break out
    Splitting for Ctrl-C, delay 250
    Received a prompt after sending newline... good!
    >>> Sending...
    ---> "\u0010print(\"<\",\"<<\",JSON.stringify­(process.env),\">>\",\">\")\n"
    >>> Sent
    Got "< << {\"VERSION\":\"2v04\",\"GIT_COMMIT\":\"3­956264e\",\"BOARD\":\"ESP32\",\"FLASH\":­0,\"RAM\":524288,\"SERIAL\":\"3c71bf8b-f­e24\",\"CONSOLE\":\"Serial1\",\"MODULES\­":\"Flash,Storage,heatshrink,fs,net,dgra­m,tls,http,NetworkJS,Wifi,TelnetServer,c­rypto,neopixel\",\"EXPTR\":1073484860} >> >\r\n>"
    [notify_info] Found ESP32, 2v04
    Loading http://www.espruino.com/json/ESP32.json
    Board JSON loaded
    ForceThrottle option is set - set Slow Write = true
    FIRMWARE: Current 2v04, Available 2v04
    Device found {"bitrate":115200,"bufferSize":4096,"con­nectionId":1,"ctsFlowControl":false,"dat­aBits":"eight","name":"","parityBit":"no­","paused":true,"persistent":false,"rece­iveTimeout":0,"sendTimeout":0,"stopBits"­:"one"}
    [success] Connected to COM8
    >>> Connected to COM8

Avatar for AkosLukacs @AkosLukacs started