Unable to connect to wifi after update

[nickthiru]

Development platform:
Processor: AMD Ryzen Threadripper 3960X 24-Core Processor 3.79 GHz
System type: 64-bit operating system, x64-based processor
OS: Windows 11

MCU: ESP32 NodeMCU

Description:
I performed an update of the Moddable SDK and the ESP32 build environment as per the instructions in the "Getting Started" guide and the "Using the Moddable SDK with ESP32" guide, respectively.

When I tried to execute the code from https://github.com/Moddable-OpenSource/iot-product-dev-book/blob/master/ch3-network/wifi-code/main.js (Screenshot 1), I'm getting an error (Screenshot 2).

When I tried to execute the http-get example from https://github.com/Moddable-OpenSource/iot-product-dev-book/tree/master/ch3-network/http-get (Screenshot 3), nothing seems to be happening (Screenshot 4).

Note: I tried running the code on two separate nodemcu units and had the same problem.

Screenshots:
1:

2: The result in xsbug after running mcconfig -d -m -p esp32/nodemcu. In the LOCALS panel, you can see that var(0) contains the password and var(1) is undefined.

3: As you can see, I didn't have to ctrl-c to exit the process either. Note: The last line from the mcrun output also has quotation marks whilst the previous ones don't.

4: The output from xsbug. When I execute mcrun, the mod doesn't seem to run; the xsbug window opens but there is no output in the console. The line in the console, from the screenshot below, is from when I installed the host in the book chapter. As you can see, there was no output from the subsequent mcrun command.

References:
1: https://github.com/Moddable-OpenSource/moddable/blob/public/documentation/Moddable%20SDK%20-%20Getting%20Started.md#win-update
2: https://github.com/Moddable-OpenSource/moddable/blob/public/documentation/devices/esp32.md#win-update

[phoddie]

Good catch. There was a change on ESP32 by @andycarle related to Wi-Fi and Ethernet to co-existence that broke these. A fix is pending. Thanks for the thorough report.

[andycarle]

Thank you for the update. I'll take a closer look at this.

[nickthiru]

@andycarle I forked and cloned the SDK. When I got to step 2 of the "Updating" section for Windows, of the "Using the Moddable SDK with ESP32" doc:

I noticed there was an error when I performed the "fetch" step:

I'm not sure if this has some "distant" bearing on the issue with mcrun.

[andycarle]

Curious, but probably not directly related. If you want to tidy that up, you could always just delete the ESP-IDF and re-clone it at the right branch.

[andycarle]

@nickthiru I was able to confirm an issue with mcrun on Windows. I have a fix in locally. You can apply the fix yourself by making a small change to tools/mcrun/nmake.esp32.mk.

Change Line 69 from:

	set "XSBUG_PORT=$(XSBUG_PORT)" && set "XSBUG_HOST=$(XSBUG_HOST)" && $(SERIAL2XSBUG) $(UPLOAD_PORT) $(DEBUGGER_SPEED) 8N1 -install $(ARCHIVE)

to:

	echo "Running serial2xsbug..." && set "XSBUG_PORT=$(XSBUG_PORT)" && set "XSBUG_HOST=$(XSBUG_HOST)" && $(SERIAL2XSBUG) $(UPLOAD_PORT) $(DEBUGGER_SPEED) 8N1 -install $(ARCHIVE)

And then try again (no need to even rebuild the Moddable SDK tools).

This is a little bit of voodoo, but I think the issue is that set has a special meaning in NMAKE and causes the rest of the line to evaluate incorrectly. Adding the echo forces everything out to the command prompt and fixes the problem.

[nickthiru]

@andycarle It's working! Explanation noted as well. Thank you very much.