-
Notifications
You must be signed in to change notification settings - Fork 236
0.3.3 No serial output when extension indicated it's connected. #1130
Comments
Well this is embarrassing. I opened this and previous issues based on VSCode and the Arduino 0.3.3-rc and 0.3.3 not having any serial output when connected to a controller. When using the Arduion IDE and this controller I got the expected serial output but not from the VSCode & Arduino Extension. Today plugged in a Adafruit Huzzah32 controller and began getting expected serial output with VSCode and Arduino 0.3.3 extension. I have two controllers (Arduino Portenta) that exhibit this problem. The serial output from then works on my computer with Arduino IDE and Putty but not VSCode & Arduino 0.3.3 extension. Now I'm not sure this is a VSCode or Extension problem. |
@adiazulay In and effort to mitigate this I have gone to VS Code Insiders so yes I would like to try anything and report my findings. |
@adiazulay I was unable to test this as I couldn't figure out how to obtain the updated extension. |
@boskoe sorry for the delay, here is the rc with fix in it |
@adiazulay |
@adiazulay |
It appears that 0.3.4-rc2 has resolved the serial problem I reported with the Arduino Portenta. |
Connect to a COM port connected to a microcontroller that is serial printing once a second. Nothing is shown in the Output screen other than port connection status. Independent monitoring of the COM port with Putty shows the output from the
microcontroller.
[Edit]
Connecting to COM port does not change status Icon as I reported in #1125. Pressing F1 then Arduino: Close Serial Monitor results in:
[Starting] Opening the serial port - COM4
[Error] Failed to open the serial port - COM4
[Error]Error: Writing to COM port (GetOverlappedResult): Operation aborted
[Done] Closed the serial port
[Edit]
Works as expected on macOS Big Sur 11.0.1, MacBook Pro 2019
Version: 1.50.1 (user setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z (2 wks ago)
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041
The text was updated successfully, but these errors were encountered: