On Mon, Mar 3, 2014 at 3:41 PM, Andreas Fritiofson <andreas.fritiof...@gmail.com> wrote: > > > > On Mon, Mar 3, 2014 at 2:17 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: >> >> On Sun, Mar 2, 2014 at 11:13 PM, Andreas Fritiofson >> <andreas.fritiof...@gmail.com> wrote: >> > I haven't tried this myself or even heard someone suggest it before, but >> > I think you could actually make use of another misfeature of Windows. I >> > don't know why or how but sometimes I have to reinstall the drivers for a >> > device when it's plugged into another port. I guess this depends on the >> > driver >> > inf file because it only happens for some devices (typically my own virtual >> > com-port devices, which is highly annoying). >> >> Usually that means your device does not have a unique serial number. >> If the device has a unique serial number, Windows will not need to >> re-install the driver for your device. > > That might explain it, good to know, thanks! Will start adding serial > numbers to all firmwares, I guess. Actually, the *same* serial number for > all devices sounds like the best option to reduce the Windows driver > hassle... :P >
You can not do that, using the same serial number is worse than without serial number. The USB Specification allows either no serial number or *unique* serial number. If you inserted two device with the same serial number into a Windows system, it may crash the OS as per one Microsoft guy. Ref: http://blogs.msdn.com/b/oldnewthing/archive/2004/11/10/255047.aspx Having unique serial number sometimes create problems for the test guy under Windows. But there is trick for that. Ref: IgnoreHWSerNum registry setting http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm http://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspx http://www.microchip.com/forums/m543480-print.aspx -- Xiaofan ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
