Cannot Access Serial Port Error
Contents |
from GoogleSign inHidden fieldsSearch for groups or messages
serial port, COM1: Donate $1 now to see this question answered quickly Sponsored questions offer a monetary incentive to answerers to produce quality responses. Be intelligently matched with 5 likely answerers who will https://www.daniweb.com/hardware-and-software/microsoft-windows/threads/243355/cannot-access-serial-port-com1 be alerted to help. 2Contributors 4Replies 7Views 6 YearsDiscussion Span 6 Years Ago Last Post by johnpote 0 6 Years Ago I cannot access the serial port, COM1:. I used to be https://developer.mbed.org/forum/mbed/post/2037/ able to but now any app, such as Hyperterminal, that tries to open COM1: puts up a small info window that says "Unable to open COM1. Please check your port settings." Any serial port idea what might be causing this? According to Device Manager the port is working correctly. I'm wondering if another auto started app that I don't know about has opened the port. Is there any way to find out what apps have opened the serial ports on the PC? I'm running Win XP home with all service packs and updates. Any help really appreciated. John cannot access serial johnpote 5 posts since Sep 2007 Community Member windows-nt-2000-xp 0 donaldw 33 6 Years Ago It'd be pretty tough to chase down who's using it. You could try uninstalling it and restarting the machine to let it reinstall. 0 Discussion Starter johnpote 6 Years Ago Thanks for the idea. I found that Device Manager showed a Standard 19200 baud modem was using COM1:. I first disabled it then uninstalled it (including re-boots) but this made no difference. Finally uninstalled the COM1: device, re-booted (which found the 'new' device and installed it) and all is now working. The help is appreciated. John 0 donaldw 33 6 Years Ago Weird. Maybe the modem got confused, I would think it would want COM3 rather than COM1. The uninstall-reboot-install new device cycle seldom fails :) Don't forget to mark your thread "solved" if you're all squared away. 0 Discussion Starter johnpote 6 Years Ago Wierd indeed, on the other hand we are talking about win xp. Got to admit though it's better than its predecessors. Thanks again. John This question has already been answered. Start a new discussion instead. Message Insert Code Snippet Alt+I Code
driver problem Topic last updated 08 Nov 2010, by bert van kokswijk. 17 replies Jim Harris # 25 Nov 2009 . Edited: 01 Dec 2009 I originally started developing with the LPC2368 beta unit on a Windows XP machine. All was working fine with the Windows serial port driver. When the new (current) driver was released, I started using that and it wored fine. I then added a Vista machine to my office. I then loaded the new drivers onto the Vista machine and all worked fine. Recently, I received my LPC1768 mbed. I tried it on my Vista machine, and had to re-install the Windows serial port driver but all is working well on it. Now, either board works fine on this machine. I then tried to run the LPC1768 on my XP machine, and again found I had to re-load the Windows Serial Port Driver. When I did, Windows reported that there was a problem and could not start the serial port driver. I tried re-installing it several times, both from the website as well as from a local drive copy. Finally, I went back to my LPC2368 mbed. Re-installed drivers, and everything works fine. Going back to the LPC1768, it fails. It always says the driver could not start. I have uninstalled, re-installed, etc., but to no avail. Again, everything works fine on my Vista machine, just not on my XP machine, and only with the LPC1768 board...the LPC2368 works fine. Any clues as to what might be the issue? Thanks. Jim Simon Ford # 25 Nov 2009 . Edited: 25 Nov 2009 Hi Jim, Jim Harris wrote: Recently, I received my LPC1768 mbed. I tried it on my Vista machine, and had to re-install the Windows serial port driver but all is working well on it. Now, either board works fine on this machine. Glad this is working at least. To clarify, this behaviour is expected. Windows registers each different mbed as a separate device, hence the need to install again. Jim Harris wrote: I then tried to run the LPC1768 on my XP machine, and again found I had to re-load the Windows Serial Port Driver. When I did, Windows reported that there was a problem and could not start the serial port driver. I wonder if this is some hangover from the old driver getting picked up when you put in a new device. However, we tested this all very thoroughly, including re-installing and upgrading, so it feels like a strange interaction/history thing. I'll have a chat with Phil (our USB guru) tomorrow, and see what he recommends. But in the mean time you could look at the following: (Note, I don't have an XP machine with me s