- Fri Mar 31, 2017 12:37 am
#64433
That obviously is an issue with the com port, the driver, the cable or the device itself. ESPlorer can't detect NodeMCU because it can't communicate with your device. However, you said you were able to flash new firmware, right? That would suggest that communication can be established with the device.
- Tue Apr 04, 2017 4:07 am
#64593
Hi Marcel,
I wonder if the problem StarkJarvis is experiencing is the same one I had when I first tried to use cloud-built firmware. In that case, simply changing the baud from 9600 to 115200 in ESPlorer fixed the problem.
Of course, this may not be the case here, but since Stark does not say what firmware he used, how he flashed it on the chip (with what software, what command, etc), I may well be wrong - but his description did remind me of the issue I had.
I wonder if the problem StarkJarvis is experiencing is the same one I had when I first tried to use cloud-built firmware. In that case, simply changing the baud from 9600 to 115200 in ESPlorer fixed the problem.
Of course, this may not be the case here, but since Stark does not say what firmware he used, how he flashed it on the chip (with what software, what command, etc), I may well be wrong - but his description did remind me of the issue I had.
- Thu Apr 13, 2017 5:51 am
#64904
I also have the same problem as the OP. I tried all baud rate available in esplorer but the console still shows
Communication with MCU..
for ever. Please help.
Communication with MCU..
for ever. Please help.
