"Monitor Device" cannot open the serial port (IDFGH-14892)

[shiinakaze]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

turn on monitor, got a successful connection, close vscode, open vscode again, run idf.py monitor again, and see the permission error.

Actual behavior (suspected bug)

run monitor again, and see the connection error.

Error logs or terminal output

PS D:\Development\Workspace\esp32_workspace\hello_world> $env:IDF_PATH = 'C:\Users\ShiinaKaze\esp\v5.4\esp-idf';
PS D:\Development\Workspace\esp32_workspace\hello_world>  & 'C:\Users\ShiinaKaze\.espressif\python_env\idf5.4_py3.11_env\Scripts\python.exe' 'C:\Users\ShiinaKaze\esp\v5.4\esp-idf\tools\idf_monitor.py' -p COM15 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --make '''C:\Users\ShiinaKaze\.espressif\python_env\idf5.4_py3.11_env\Scripts\python.exe'' ''C:\Users\ShiinaKaze\esp\v5.4\esp-idf\tools\idf.py''' --target esp32s3 'd:\Development\Workspace\esp32_workspace\hello_world\build\hello_world.elf'

--- Warning: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM15 instead...
--- esp-idf-monitor 1.5.0 on \\.\COM15 115200
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
could not open port '\\\\.\\COM15': PermissionError(13, '鎷掔粷璁块棶銆?, None, 5)
--- Connection to \\.\COM15 failed. Available ports:
COM15

Steps to reproduce the behavior

1.open project with vscode
2.open monitor
3.got a successful connection
4.close vscode
5.open vscode again
6.run monitor again
see the permission error.

Project release version

v1.5.0

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

Windows 11

Shell

PowerShell

Additional context

I've found background occupancy

[brianignacio5]

Please consider that espressif/vscode-esp-idf-extension#1470 was opened before but the user faces the same issue when running idf.py monitor directly.

I couldn't reproduce the issue directly in my setup.

[peterdragun]

Hi @shiinakaze, unfortunately, we were not able to reproduce the issue. We tried on multiple Windows 11 machines and macOS, just to be sure. Every time port was closed without any issues as expected.

Can I ask you for more details, like the PowerShell version, which chip you used, and which port on the chip you used (UART vs. USB port)? There might be some differences based on the drivers for the UART bridge. (Even if we go to the Registry Editor, our device has a different name structure - "\Device\Sibalser0" for UART or "\Device\USBSER000" for USB. This makes me think that the drivers are different). Can you check which UART bridge are you using, that might help to narrow down the issue?

If your devkit is using a CP210x UART bridge (all Espressif official devkits have this) or you are connecting using a USB-Serial/JTAG port I would suggest installing the drivers from our documentation.

[shiinakaze]

Hi @shiinakaze, unfortunately, we were not able to reproduce the issue. We tried on multiple Windows 11 machines and macOS, just to be sure. Every time port was closed without any issues as expected.

Can I ask you for more details, like the PowerShell version, which chip you used, and which port on the chip you used (UART vs. USB port)? There might be some differences based on the drivers for the UART bridge. (Even if we go to the Registry Editor, our device has a different name structure - "\Device\Sibalser0" for UART or "\Device\USBSER000" for USB. This makes me think that the drivers are different). Can you check which UART bridge are you using, that might help to narrow down the issue?

If your devkit is using a CP210x UART bridge (all Espressif official devkits have this) or you are connecting using a USB-Serial/JTAG port I would suggest installing the drivers from our documentation.

Thank you very much for your test. The version of Windows powershell I use is 5.1.26100.2161, and the chip of USB-UART converter is CH9102. Now I have changed to CH340, and this problem is no longer there, so I guess it is the problem of CH9102 driver.

[peterdragun]

Thank you for getting back to me. In this case, I would recommend making sure that you are using the latest version of the driver for that chip. I am afraid that we are not able to do anything from the monitor side in this case, as it is not caused by the monitor itself.

[shiinakaze]

Thank you for getting back to me. In this case, I would recommend making sure that you are using the latest version of the driver for that chip. I am afraid that we are not able to do anything from the monitor side in this case, as it is not caused by the monitor itself.

ok, thanks.