-
Notifications
You must be signed in to change notification settings - Fork 325
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
Nothing happens on "Open" connection #74
Comments
I have the same problem with the same ESPlorer version, but with MicroPython on Windows 10 with COM6 at 115200. If I press the reset key on my WeMosD1 I see the MicroPython startup scrre on the terminal without any garble, but I still get no response at the >>> prompt. See screen below: PORT OPEN 115200 Communication with MCU..Got answer! Communication with MCU established. Can't autodetect firmware, because proper answer not received (may be unknown firmware). WebREPL daemon started on ws://192.168.4.1:8266 MicroPython v1.9.4-8-ga9a3caad0 on 2018-05-11; ESP module with ESP8266
This ESPlorer would be an ideal solution if it worked as expected. If it does not work, I will attempt to modify (if feasible) the ESPruino IDE for node.js. I think it would work fine if I got it to recongnize the proper MicroPython prompt instead of the node.js prompt. I appreciate your help and Happy Holidays. Christian |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi Anudeep.
i will be honest with you, i gave up on using ESPlorer because I never had any assistance to resolve my problem.
Nonetheless, as I said in my comment of August 18th 2018, " ESPlorer would be an ideal solution if it worked as expected."
My interest was more in using Forth with the ESP8266 (Punnyforth) and I was hoping to get ESPlorer working with Lua first and adapt it tu use Punnyforth. I never did it.
I would still like to use ESPlorer with Forth but I found a usable alternative with XShell for simple Forth fun programming.
Regarding the garbled screen problem with ESPlorer, I have the impression that it starts operation with a baud rate of 115200 but switches to a different baud rate after startup.We probably just need to find the proper baud rate to use after startup.
If you find the proper baud rate, let me know.
We need luck and patience with freeware on the Internet...
Good luck... and lots of patience.
Christian Hinse
De : Anudeep Sharma <[email protected]>
Envoyé : samedi 6 février 2021 02:49
À : 4refr0nt/ESPlorer <[email protected]>
Cc : hinsech475 <[email protected]>; Comment <[email protected]>
Objet : Re: [4refr0nt/ESPlorer] Nothing happens on "Open" connection (#74)
I'm also facing same problem with ESplorer I don't know whether is due to ESP32 or due to Esplorer because When I tried with other ESP32 also not resolved please suggest me way to get out of this error
[Screenshot (48)]<https://user-images.githubusercontent.com/66728239/107116071-fd5c4d80-6896-11eb-8065-df479fa22b1a.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#74 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJ4ICOBAODKNUQMQUAZJZHLS5UNDDANCNFSM4FQKCDHQ>.
|
Version: ESPlorer v.0.2.0-rc5
OS: Mac OS 10.13.6
Board: ESP8266 (NodeMCU-devkit with USB)
I've flashed with default firmware via nodemcu-build.com. I'm able to Connect to board through CoolTerm and also use "NodeMCU-Tool".
However when I click "Open" on ESplorer it says "Communication with MCU" and nothing happens.
Any guesses what could go wrong?
The text was updated successfully, but these errors were encountered: