-
Notifications
You must be signed in to change notification settings - Fork 236
Failed to open serial port /dev/ttyUSB0 due to error: + TypeError: Cannot read property 'close' of null #774
Comments
I will investigate with it. |
This issue has been automatically marked as stale and closed because it has not had recent activity. Please feel free to open a new issue if you would like further discussion. Thank you for your contributions. |
Hello, I am facing the same problem on Manjaro 18, running extension version 0.2.25, VSCode 1.33.1 and arduino 1.8.9. "Arduino: Upload" works perfectly, but opening the serial port causes the following error:
This is not a permission issue. I put my ttyUSB0 ad chmod 777 to troubleshoot, the problem is still here. Here's what the developer tools gave me:
The non-abreviated path is:
|
I'm having the same issue. When I try to run F1
Verify and upload run without any problems, and I can access the serial port running If I run my project with
I'm running it on
|
I have this problem too. |
@hywhuangyuwei Same problem here with no response clicking select serial port. In my case, uploading from arduino also did not work. I had to use |
Me too, just happened after VSCode updated itself to the latest June 2019 version ... I just reverted to May 2019, and the problem went away. It's clear something was broken in June 2019 version regarding this issue! |
Regarding @aboulfad comment above: See this comment here for why this fails right now: microsoft/vscode#76538 (comment) |
Fixed since Arduino extension v0.2.27, thanks @meier99 @edalongeville @pg1992 @hywhuangyuwei @Moonlight63 @aboulfad @dbaeumer . |
Thanks a lot @ArthurMa1978 ! |
the above error "Failed to open serial port COM3 due to error: + TypeError: Cannot read property 'close' of null" still persists for me. VSCode Version: 1.39.0 (insiders) Serial Monitor of Adruino IDE shows everything correctly, so this is definitely a vscode-arduino problem. |
I seem to now get this issue too after updating to the latest version of VSCode (v1.40.0). I can still compile and upload programs to my ESP32, but can't open the serial monitor anymore. Before the update I never had this problem. Opening the serial monitor still works in the Arduino IDE fortunately. |
Exactly the same issue here. It has stopped working after an upgrade to v1.40.0. |
#MeToo :) After upgrade VSCode to v1.40.0, serial monitor causes "TypeError: Cannot read property 'close' of null" (Ubuntu 18.04.3 LTS) |
Me too since upgrade VSCode to 1.40.0 |
Me too since upgrading to vscode 1.4.0 |
Same issue here, also not able to select serial port as option |
Got the same issue, but I'm mostly using the arduino devtools serial monitor since it's 2 way. @luke-shields: You can select the port by adding |
Same issue on vsc 1.4.0 on linux. Serial port selecting with a waring in verbose mode. But no error message. |
The problem is well understood and has a straightforward solution. Enumeration of serial hardware depends on native node modules which breaks whenever the node version of VS Code changes. The historical solution has been to update the extension to use the new version of node, but this just breaks again later for the same reason – which is why this issue just won't die. A permanent solution suggested by the VS Code team is to rewrite the unsupported code to use N-API, which is what they're adopting (VS Code also needs to call native modules). If you want a fix immediately, revert to 1.39.2 and disable updates. Although there may be a node update it is more worthwhile to fix the problem properly and this will take a fair amount of work. See also #918 |
The serial port issue has been fixed in the latest Arduino extension release (0.2.28). |
Perfect! Thank's.
Le ven. 15 nov. 2019 à 10:11, Dooriya Li <[email protected]> a
écrit :
… The serial port issue has been fixed in the latest Arduino extension
release (0.2.28).
Please install the latest Arduino 0.2.28 from marketplace
https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.vscode-arduino
to verify if this is resolved on your environment.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#774?email_source=notifications&email_token=AJEGKBD33KB3WKSAIEKCLRLQTZRT7A5CNFSM4GXRPYJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEEZOIQ#issuecomment-554276642>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJEGKBEO65U422FJH5G5R33QTZRT7ANCNFSM4GXRPYJQ>
.
|
I just installed 0.2.28 and I still have the issue on linux. (arduino 2:1.0.5) |
I won't insult your intelligence by asking whether you've tried rebooting. You shouldn't need to. But if you haven't, now would be a good time to rule out orphaned locks or hung processes as contributing factors. |
Sorry for late reply. I can't provide more information because I don't remember what I was doing to cause it (doh!). Consider it resolved for me. |
It has been a year, since this issue was opened and is still unsolved. |
Extension Version: 0.2.29 |
@hellyzh thanks for keeping track of this! |
@kowiste, it is due to VSCode auto upgraded to version 1.43, currently please use VSCode 1.42 as a workaround. |
Same here :( downgrade is a poor solution |
The same here! |
VSCode v1.43.0 |
I'm having the same issue here: Mac OSX 10.14.6 I also had to set my port manually through arduino.json since the port selection did not work otherwise (see #922). |
Hi, same issue for me: Mac OSX 10.15.2 |
Same issue. Honestly Microsoft, your default forced updates are almost always a problem for developers. You should rethink your choice own that when it comes to applications designed for WORK. MacOS 10.15.3 |
was having the same issue;thought I had broken something :/ |
I have the same issue. |
Yes just revert to v 1.42 previous version |
@bzeeman The problem is well understood and the workaround is public knowledge. The way to solve it is also clear. If you think it's a priority item, why don't you fork this open source project, rewrite it to use N-API and submit a PR? That would win you a lot of friends and look excellent on your resume. |
Duplicate with #980 |
Had the issue with Works again after downgrading to I simply downloaded https://update.code.visualstudio.com/1.42.1/win32-x64/stable and clicked for the install |
Hello folks, I'm running into the same problem. Unfortunately, "Arduino: Select Serial Port" doesn't do anything. I can manually update my arduino.json file to specify the port for my WiFi board as a workaround. I really don't want to downgrade my VSCode installation. But, I'll give that a shot down the road if this isn't an easy fix. VSCode v1.47.0-insiders |
Update, as of this morning, the problem has been resolved. When I fired up VSC, I didn't pay much attention but something updated and now the COMM Port selection and Serial Monitor are both working... I've checked my versions and nothing reflects an update. So, I don't know what updated. But, my serial connectivity is working... |
Issue Type: Bug
Always happens on 'Arduino: Open Serial Monitor'.
Upload of sketch (Arduino: Upload) to board via /dev/ttyUSB0 works.
Serial Monitor started via Arduino application also works fine.
Extension version: 0.2.25
VS Code version: Code 1.31.0 (7c66f58312b48ed8ca4e387ebd9ffe9605332caa, 2019-02-05T22:32:48.719Z)
OS version: Linux ia32 4.15.0-45-generic
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
surface_synchronization: enabled_on
video_decode: unavailable_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: