The terminal window shows the following:
It is displaying garbage because the blink program outputs at 115200. If I stop that monitor and type "idf.py -p COM18 monitor" at the prompt, it will start at 115200 and display the correct readable output.PS C:\Users\myname\Documents\Projects\wifi_audio_sync\code\esp32\idf5.0\blink> set IDF_PATH=C:\Users\myname\esp\esp-idf
PS C:\Users\myname\Documents\Projects\wifi_audio_sync\code\esp32\idf5.0\blink> C:\Users\myname\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe C:\Users\myname\esp\esp-idf\tools\idf_monitor.py -p COM18 -b 460800 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 c:\Users\myname\Documents\Projects\wifi_audio_sync\code\esp32\idf5.0\blink\build\blink.elf
--- WARNING: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM18 instead...
--- idf_monitor on \\.\COM18 460800 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
xx�xxxx��x��x��x��x�x�xx�������x��xx�������x�����������x�x�xxx��x�x�x��x�xx�x���������������x�x�x��x�x�x���x��xx��xxxxx�x��x�x�xx�x�x�x�x���x��x��xxx�xx�xx�xxxx�x�xx�x�xx�x�x�xxx�xx�x��xxx�xxxx����xxxxx��xx�x�x�xxx��x��x�xx��x�x�xxxx��x��x�x��x�x�x�x�xx�x���x����xxxx���x��x�xxx�x���x��������x�x�x�xx�x���x�������x�������x�xxx�x���xxxx�x�x�x�xx�x���x�������xx����x�xxx�x���x���x���x��xx�x�x�x�x�x��x�������x��x�
Why do I usually get the window that indicates that powershell terminated?
Why does idf_monitor start at 460800 baud? I don't see 460800 anywhere in the project directory and it starts properly if I don't specify the baud rate?
I should also say that this was working about a month ago. I don't know what has changed during that time.
I hope someone can help with this issue.