SLAA457B September 2013 – October 2018 MSP430F5500 , MSP430F5501 , MSP430F5502 , MSP430F5503 , MSP430F5504 , MSP430F5505 , MSP430F5506 , MSP430F5507 , MSP430F5508 , MSP430F5509 , MSP430F5510 , MSP430F5513 , MSP430F5514 , MSP430F5515 , MSP430F5517 , MSP430F5519 , MSP430F5521 , MSP430F5522 , MSP430F5524 , MSP430F5525 , MSP430F5526 , MSP430F5527 , MSP430F5528 , MSP430F5529 , MSP430F5630 , MSP430F5631 , MSP430F5632 , MSP430F5633 , MSP430F5634 , MSP430F5635 , MSP430F5636 , MSP430F5637 , MSP430F5638 , MSP430F5658 , MSP430F5659 , MSP430F6630 , MSP430F6631 , MSP430F6632 , MSP430F6633 , MSP430F6634 , MSP430F6635 , MSP430F6636 , MSP430F6637 , MSP430F6638 , MSP430F6658 , MSP430F6659 , MSP430FG6425 , MSP430FG6426 , MSP430FG6625 , MSP430FG6626
Having a unique VID and PID pair on a USB device is important to prevent conflicts. A given USB host stores information about the USB device's driver requirements after its first encounter with a given VID and PID. It must be able to assume that any subsequent devices with the same VID and PID require the exact same host driver setup. Therefore, once released to market, a product's VID and PID should not be changed.
During development, however, the VID and PID might sometimes need to change as the developer arrives at the final USB descriptor set. The developer must prevent conflicts on the host machine being used. This can be done either by using a new PID value any time the USB descriptors change; or the original PID can be used, but the device must be uninstalled off the system and re-installed. See the USB API Programmer's Guide in the USB Developers Package, for more information.