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. 2200 Machine Type And Serial Number Are Invalid Lenovo Support. I tried it on my Vista machine, and had to re-install the Windows serial port driver but all is working well on it.

I downloaded Bitminter and got it working. No serial ports found' 'No external devices detected.' This happens every time i try to start the engine.

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.

Installation Wc Broyeur Sfa. 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? Hi Jim, 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. 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 so can't guide exactly - based on Vista). First off, can you confirm the Firmware on the LPC1768 and LPC2368 mbed's are up to date (see ). Then, if you go to Device Manager, what is the version of the driver at: • Ports (COM & LPT) >mbed Serial Port - right-click Properties, Driver tab • Universal Serial Bus controllers >mbed Composite Device - right-click Properties, Driver tab I'd expect 2.0.2.0 and 1.0.0.0. If all looks in order, I'd then try un-installing both of these drivers (serial/composite), selecting to remove the software.

But then also check if you disconnect/reconnect, that an old serial driver is not recognised. How To Save Ebook From Chegg Login. If it is, remove that too using the same process.

Do this for both boards and you'll be basically back to scratch. Probably worth a reboot to ensure windows is not holding anything, then try re-installing. Please note down every step you do if possible. We haven't seen a problem yet (apart from a problem downloading the driver mentioned in ), so capturing the process may help if anyone else gets a similar result. This may come to nothing, but it'd be good to discount it.

Please report back how you get on. Well, I tried all of the above. 1) I Plugged in my LPC1768. Hi Jim, Phil suggested it could be that windows is trying to allocate it to a COM port that is already in use. That would cause it to fail with Code 10. It seems sometimes Windows gets an inconsistency in it's registration of what has already been allocated.

To see if this is the problem (and hopefully fix it), try changing the assigned COM port. • Go to Device Manager >Ports (COM & LPT) >mbed Serial Port, then right-click and select 'properties'. • Choose 'Port Settings' Tab, and click 'Advanced' • Under 'COM Port Number', try selecting a different COM port Note that windows marks some as (in use), but don't count this as exhaustive for the same reason as this problem may exist! Try changing it to a few different unused COM ports and see if this has an impact. If not, we'll dive deeper to see what windows is reporting. Simon, I had already done the un-lug/re-plug thing.