You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd %MODDABLE%\examples\helloworld
mcconfig -d -m -p esp32
Then the ESP32 is flashed on COM3 and the example runs
If I use
cd %MODDABLE%\examples\piu\balls
mcconfig -d -m -p esp32/moddable_zero
then the MinGW window shows
Building xs_esp32.elf...
CC /c/Users/antho/moddable/build/tmp/esp32/moddable_zero/debug/idf/main/main.o
AR /c/Users/antho/moddable/build/tmp/esp32/moddable_zero/debug/idf/main/libmain.a
LD C:/Users/antho/moddable/build/tmp/esp32/moddable_zero/debug/idf/xs_esp32.elf
esptool.py v2.6-beta1
Flashing binaries to serial port COM8 (app at offset 0x10000 )...
esptool.py v2.6-beta1
Serial port COM8
Running SET in "Developer Command Prompt for VS 2017"
gives
My guess is that at some point when you first built this app, you had the UPLOAD_PORT set to COM8? Then the sdkconfig.h file would be generated.
Try building clean (ie. remove $MODDABLE/build/bin/esp32 and $MODDABLE/build/tmp/esp32 ), or maybe just touch $MODDABLE/build/devices/esp32/xsProj/sdkconfig.defaults then rebuild. The sdkconfig.h file should then get rebuilt, taking into account UPLOAD_PORT.
If I use
Then the ESP32 is flashed on COM3 and the example runs
If I use
then the MinGW window shows
Running SET in "Developer Command Prompt for VS 2017"
gives
Where is it getting COM8 from?
C:\Users\antho\moddable\build\tmp\esp32\moddable_zero\debug\idf\include\sdkconfig.h has
so I guess this got generated somehow?
The text was updated successfully, but these errors were encountered: