-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serial UART Terminal misconfiguration creates apparent hang at (stack) #41
Comments
Hey there, i'm experiencing the same problem (using an ESP-01 module with a recent punyforth clone from yesterday). The flashing procedure works, so does booting, but it doesn't print the "Punyforth ready." message, and seems to hang after displaying "(stack)". I'm using minicom instead at 115200 baud, 8N1, through a PL2303 based USB-to-serial adapter. The ESP seems to function otherwise, as i can see a WiFi AP appearing with a SSID corresponding with my module's MAC address. My next step will likely be retesting the PL2303 (which is working bidirectionally since i was able to both flash and receive the boot messages), and observing the serial communication closer to see if i'm missing something. See you all back here! |
Hi, can you try this out with coolterm, using the settings from the readme.md? I remember having some problems with screen. Probably it never worked with screen or screen should be configured differently. |
Hello, i had similar problem with TeraTerm/punyforth neither with TeraTerm/other kind of forth. |
Thanks for the tip @GerardSontag, I'll investigate this. |
Switched to Windows (Virtualbox based on Free Windows 10 90-day 'Edge' tester from Microsoft). That's because Coolterm is only available as a 32-bit application on Linux, and it was looking like a world of pain to install multiarch and a whole set of i386 desktop libs just for Coolterm. Coolterm (on windows) does indeed function against the flashed punyforth on NodeMCU-M (ESP8285) following my flashing with I was then able to prove that miniterm could also connect and behave as expected if I avoided my usual --raw flag (which disables line mode), and added a new --echo flag. Connecting like this was successful from CMD.exe after installing Python3 into windows (adding it to the path). For Pip instructions try... https://vgkits.org/blog/pip3-howto/
|
And now also proven to work back on Linux... To install miniterm (after installing pip3)...
Then run it like...
|
May have spoken too soon in closing #40
After replacing with the latest esptool.py I thought the flashing process had completed but there still seems to be something wrong with the punyforth session which comes up after the flashing reports success. I tried resorting to a NodeMCUv2 device which has a CP2102 and ESP8266 with 4MB but this behaves identically.
I connected via
screen /dev/ttyUSB0 115200
and it shows(stack)
but the terminal session is non-responsive - none of the keys you press appear as echoed characters and typing the example test commandprintln: "hello"
does nothing.On closer inspection of the example terminal session you show on the main page, I should probably be seeing the phrase "Punyforth ready" which never arrives, and not just (stack).
If I stay connected to /dev/ttyUSB0 and press reset it shows the following after the boot messages...
Below is a log of the upload process in case there's anything which might help...
The text was updated successfully, but these errors were encountered: