MSYS2 is slow on Windows 10

[mikemoy]

All you have to do in windows when using MSYS2 is slap "-jx" on the end of your make command. Where x is the number of processor cores you have. I have an 8 core system. so my make line is make -j8 flash.

[squonk11]

@mikemoy: The option -jx I know already. This was not the question.
My question is that I am not able to quit the monitor mode (incoked by 'make monitor') using "Ctrl+]" key. This keystroke is simply ignored by WSL.

[mikemoy]

@squonk11, I was replying to the OP question of "If someone have a idea of how to speed up msys2 ..."

[squonk11]

ah, o.k. Sorry for the misunderstanding.
But I am really having a problem with this right now: even starting the terminal mode (make monitor) takes sometimes several minutes until I see the first output on my screen.

[squonk11]

Now I switched to the CMake build system under Windows cmd.exe. This works tremendously fast! But I still have the problem, that I am not able to quit monitor mode by hitting "Ctrl-]". But in windows cmd.exe I have the option to exit the running script (idf.py) just by hitting "Ctrl+c". This is not the "nice" way to work but for me this is currently the solution.

[ESP_Angus]

Now I switched to the CMake build system under Windows cmd.exe. This works tremendously fast! But I still have the problem, that I am not able to quit monitor mode by hitting "Ctrl-]". But in windows cmd.exe I have the option to exit the running script (idf.py) just by hitting "Ctrl+c". This is not the "nice" way to work but for me this is currently the solution.

Great, I'm glad the CMake build system helped.

I'm not able to reproduce the Ctrl-] problem on my Windows development box. When I run "idf.py monitor", I see output as follows:

Code: Select all

Executing "C:\Python27\python.exe C:\Users\gus\dev\esp-idf\tools/idf_monitor.py -p COM6 -b 115200 C:\Users\gus\Desktop\esp-idf-v3.1.2\examples\get-started\hello_world\build\hello-world.elf -m 'C:\Python27\python.exe' 'C:\Users\gus\Desktop\esp-idf-v3.1.2\tools\idf.py' '-p' 'COM6'"...
--- idf_monitor on COM6 115200 ---

Python in this case is the standard Windows Python 2.7 install. Can you compare with the output you see from idf.py?

My guesses are:

• This is an issue with some particular Python executable version, or idf.py thinks it's running under MSYS for some reason (and does a bunch of additional winpty emulation).
• This is something with keyboard layout or language settings, where Python is seeing a different control code for Ctrl-].

[ESP_Roland]

My question is that I am not able to quit the monitor mode (incoked by 'make monitor') using "Ctrl+]" key. This keystroke is simply ignored by WSL.

Hello squonk11!

What is the IDF version you are using? I fixed a similar issue in https://github.com/espressif/esp-idf/co ... 8d36bfb1c9. Does this fix your issue?

[squonk11]

@roland:

What is the IDF version you are using?

I am using:"v3.3-beta1-136-g97eecfa1b".

I fixed a similar issue in https://github.com/espressif/esp-idf/co ... 8d36bfb1c9. Does this fix your issue?

I need to check if this also helps for me.

[squonk11]

@ESP_Angus

Code: Select all

Executing "C:\Python27\python.exe C:\Users\gus\dev\esp-idf\tools/idf_monitor.py -p COM6 -b 115200 C:\Users\gus\Desktop\esp-idf-v3.1.2\examples\get-started\hello_world\build\hello-world.elf -m 'C:\Python27\python.exe' 'C:\Users\gus\Desktop\esp-idf-v3.1.2\tools\idf.py' '-p' 'COM6'"...
--- idf_monitor on COM6 115200 ---

Python in this case is the standard Windows Python 2.7 install. Can you compare with the output you see from idf.py?

My output is:

Code: Select all

Executing "C:\Python27\python.exe C:\Users\xxxx\esp\esp-idf\tools/idf_monitor.py -p COM11 -b 115200 C:\Users\xxxx\esp\hello_world\build\hello-world.elf -m 'C:\Python27\python.exe' 'C:\Users\xxxx\esp\esp-idf\tools\idf.py' '-p' 'COM11'"...

That looks quite similar to yours, right?

[squonk11]

@roland

Hello squonk11!

I fixed a similar issue in https://github.com/espressif/esp-idf/co ... 8d36bfb1c9. Does this fix your issue?

This fix is already included in my version of "idf.py". The problem still persits. But it is not a big issue since I can terminate monitor mode by Ctrl-c.