-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Arduino IDE 1.6.8 - Can't open device error while uploading (No issue in 1.6.7) #4700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
On top of that, I'm getting this message when opening the serial monitor.
|
Maybe this question will be too overly obvious, but have you tried rebooting your computer? |
Yes, I did reboot my computer and it's still the same. I even tried it on other computer running the same OS (Windows 10 64-bit) and the error still exists. However, I noticed that this problem occurs intermittently and it may work for once after I've tried a few times. |
I've also noticed this happening with 1.6.8, with hardware that was fine before. |
I may be having similar issue but since it is outside IDE (1.6.8) I am not going to bore this forum with details. Unfortunately the COM "error" messages almost never say "port in use". |
My hardware programs fine with Platformio, so it's looking like a problem with the Arduino software. |
Just small add - observed several attempts to force the COM port to reset. |
Observing exactly the same problem. Uploading works fine in 1.6.7 and older, but in 1.6.8 I get regularly the error One maybe interesting extra: when I remove the MCU from the board and try again avrdude gives an unable to sync error before giving the Access denied error which seems to indicate that it can communicate at least a little with the serial driver/port, but I may be mistaken. |
Did some research. The thing is that if i click quickly "Open serial monitor" sometimes it opens. But the most time result is: " I ran process explorer and find out, that the registry key If I close this handle forcibly it will be reopened immediately. But I managed to close it and click open Serial Monitor. When Serial Monitor is opened, registry key is not being held. If I connect PuTTY to COM before opening Arduino IDE, Arduino IDE cannot open It seems some kind of bug. Maybe system requires access to this key before it can access COM port. But the key is being held by Arduino IDE permanently. PS. 1.6.7 works fine |
My last and final attempt to make 1.6.8 work on XP produced some java "touching COM" port errors. |
Hi @ozligia, are you experiencing this problem with all your boards or with one in particular? Does it use an FTDI chip as USB-to-serial converter? |
from listSerialsj library 1.0.8 the serial polling is executed using the listComPorts method (which is much more cpu intensive than the previous one) to avoid bug arduino#4700. The 3 second poll rate is needed to avoid cpu hogging
from listSerialsj library 1.0.8 the serial polling is executed using the listComPorts method (which is much more cpu intensive than the previous one) to avoid bug arduino#4700. The 3 second poll rate is needed to avoid cpu hogging
from listSerialsj library 1.0.8 the serial polling is executed using the listComPorts method (which is much more cpu intensive than the previous one) to avoid bug arduino#4700. The 3 second poll rate is needed to avoid cpu hogging
from listSerialsj library 1.0.8 the serial polling is executed using the listComPorts method (which is much more cpu intensive than the previous one) to avoid bug arduino#4700. The 3 second poll rate is needed to avoid cpu hogging
arduino-PR-4792-BUILD-534 doesn't seem to work at all on my Windows 7 system. After the splash screen it dies. Any special instructions? |
Can you launch |
Sorry for the slow reply, I was away this weekend (I removed the hash symbols):
After using
About my system: OS: Windows 7 , 64 bit Build 7601 (6.1.7601.19160) Hopes this helps. |
Solved by #4792 |
I just updated from 1.6.7 and got this error message while uploading my sketch to UNO.
FYI, I'm running on Windows 10 64bit. I don't have any issue with 1.6.7.
The text was updated successfully, but these errors were encountered: