Once the firmware is uploaded following command will connect to micropython on the ESP board and give you the REPL prompt :
To exit:
this was really helpful, thanks! (I was leaving off the 115200 param, and wondering why it would not connect, D'oh).
also - note that Ctrl-A, Ctrl-D is not really "exit". It is "Detach". This allows you to later re-attach via
I only noticed that when I was unable to later attempt to connect with minicom as it said
Code: Select all
minicom: cannot open /dev/ttyUSB0: Device or resource busy
although sometimes I'll get the "resource" busy message for minicom and "screen -r" says "There is no screen to be resumed." and when connecting with a new screen command, the device is unresponsive... so it is time to remove the USB and power cycle the ESP8266 to reconnect.
In my case, I'm uploading a file, then attempting to play with it interactively from my Rpi:
Code: Select all
python pyboard.py --device /dev/ttyUSB0 myI2C.py
screen /dev/ttyUSB0 115200
thus if the screen is left "detached" with Ctrl-A Ctrl D, I am unable to later then re-run the pyboard.py to upload something fresh.
As for minicom, note that the fresh install for me had "hardware control" set to "Y" which left my ESP8266 in a state of appearing to be unresponsive. See
http://www.tldp.org/HOWTO/Remote-Serial ... nicom.html for me this was Ctrl-A Z (not Ctrl-A Ctrl-Z) then press "O", and select "Serial port setup", then turn off hardware flow control. Minicom config should look like this:
Code: Select all
Welcome to minicom 2.6.1
OPTIONS: I18n
Compiled on Apr 28 2012, 19:24:31.
Port /dev/ttyUSB0
Press CTRL-A Z for help on special keys
+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : No |
>>> | G - Software Flow Control : No |
>>> | |
>>> | Change which setting? |
+-----------------------------------------------------------------------+
Software flow control *does* seem to work - only hardware control seems to be problematic. So if experiencing problems when pasting large chucks of text (e.g. via putty, as in my case) try experimenting with that setting.