Guides · Component basics

How Should USB VID PID and Serial Numbers Be Configured for CY8C5868LTI-LP038?

Configure CY8C5868LTI-LP038 USB identity by reviewing VID permission, PID allocation, serial requirements and the identity your host actually observes.

· StockWake team · Source: Original content by StockWake. Please credit StockWake when republishing.

USB-connected-board-illustration-for-CY8C5868LTI-LP038-identity-review

To configure USB identity for the CY8C5868LTI-LP038, use an authorized Vendor ID (VID) and an appropriate Product ID (PID). Set the serial-number plan against applicable class, host, and unit-identification requirements; use this Windows 10 and Server 2016 HLK test within its listed scope. Do not simply copy a VID from a reference design—you must have the right to use it. Your descriptor plan also depends on the USBFS component version and how your host software handles device discovery.

Separate Product Identity from Unit Identity

Start with the specific decision your host application needs to make. Recognizing a product, loading the right software driver, and picking one physical board out of a stack are three different tasks. A product variant may warrant its own PID, depending on its interfaces and host software requirements. Conversely, identical units can share a PID and use distinct serial strings when the host supports unit selection.

Scroll sideways to see the whole table

Identification Goal

Field to Review

Decision to Record

Identify the vendor

idVendor

Confirm the right to use the VID.

Identify the product or variant

idProduct

Match the product plan and host software requirements.

Identify a device revision

bcdDevice

Define the release numbering policy.

Distinguish physical units

Returned serial string

Define the required uniqueness and persistence.

In the device descriptor, iSerialNumber is just an index pointing to a string descriptor—it is not the serial text itself. Two boards can point to the exact same index but return completely different serial strings. This distinction follows Microsoft's USB device descriptor field definitions.

Confirm the Right to Use the IDs

Keep your VID permission or allocation record safely stored with the product documentation. USB-IF guidance strictly prohibits using a VID without authorization. Just because you found a hex value in an example code doesn't mean you are allowed to ship a product with it. Engineering must also explicitly identify who controls PID allocation under that specific VID.

Lock Down the USBFS Project Baseline

Record the complete ordering code, board revision, firmware build, PSoC Creator version, and the USBFS component version. Add the USB class, driver package, and application matching rules. If you aren't sure which chip or firmware target you are actually using, resolve the CY8C5868LTI-LP038 and CY8C5868LTI-LP039 firmware target review first.

Note: The configuration details here use Infineon's USBFS 3.20 component datasheet (document 002-19744 Rev. *A, dated October 17, 2017). Match these details to the component installed in your specific project.

Select the Intended Product Descriptor

In USBFS 3.20, the Device Descriptor tab exposes the VID, PID, device release, and class settings. The String Descriptor tab controls your serial options. A critical warning: the documented Cypress VID 0x04B4 is for development only; the datasheet explicitly prohibits releasing products with it.

USBFS 3.20 supports several prepared device descriptor settings. USBFS_Start() selects one through its device-number argument. Remember that this argument is a descriptor index, not a PID. For runtime product selection, review the selected descriptor and the supported connection sequence. Do not treat an old descriptor-editing macro as a version-independent implementation.

Choose and Configure the Serial Source

Enable Include Serial Number String when your design actually requires a USB serial. USBFS 3.20 documents three sources. Choose one based on the unit-identification requirement you established earlier.

Scroll sideways to see the whole table

USBFS 3.20 Option

Source of the String

Release Check

User Entered Text

A design-time string

A shared firmware image can repeat it across all boards.

User Call Back

An application-supplied descriptor at runtime

Verify descriptor format, source, and initialization.

Silicon Generated Serial Number

A value generated from the silicon die ID

The component documentation does not guarantee uniqueness.

With User Call Back selected, you pass a pointer to a valid USB string descriptor to USBFS_SerialNumString(). Passing plain serial text alone will not work. The documented fallback is the default string if the function is not used or the supplied descriptor is malformed. Confirm the generated instance prefix and initialization sequence in your actual project.

Keep Allocation and Storage Explicit

Passing a descriptor pointer does not magically define serial allocation or a nonvolatile storage process. If your plan uses EEPROM or flash, you must document the storage location, the write/read procedure, and how it behaves after reflashing or board rework. Confirm that the selected hardware and firmware actually support that plan.

If uniqueness is required, define its scope and how duplicates are prevented. For an application-supplied serial source, your firmware must provide the intended USB string descriptor; an ID or UUID stored elsewhere in memory is not exposed automatically. The Silicon Generated option creates a die-ID-based serial but provides no uniqueness guarantee. Your production process must support the identity claim.

Verify What the Host Actually Sees

Use a controlled check after the firmware change. The following is a proposed verification sequence, not a report of tests performed on a board.

  1. Record the host OS, driver, application, board revision, and exact firmware build.

  2. Read the enumerated VID, PID, bcdDevice, and actual serial string. Compare them against the approved identity plan.

  3. Reconnect through the documented project procedure. Check that the expected identity remains stable.

  4. Connect the required number of units together. Confirm the application selects the intended unit and communicates with each one.

Microsoft's guidance requires the USB device descriptor to remain unchanged during a connection. A new value sitting in firmware memory alone does not prove the host has observed it. Record the actual descriptor response and application result.

If programming itself failed, resolve that earlier stage before judging USB identity. The separate CY8C5868LTI-LP038 SPC polling timeout guide addresses that programming review.

Keep the Release Record Complete

Keep the approved IDs, descriptor configuration, serial source, allocation record, build reference, and host observations together. Distinguish the observed USB identity from the physical component identity. Use top markings and full manufacturer part numbers for the latter. USB descriptors alone do not establish the chip's ordering code or authenticity.

Frequently Asked Questions

Do Identical Boards Need Different PIDs?

Not simply because they are separate units. First check whether the host needs product selection or unit selection. A serial-string plan can handle identical-unit selection. Distinct product variants may legitimately need different PIDs, subject to the product's allocation and compatibility rules.

Does Every Firmware Update Need a New PID?

No universal rule follows from a firmware change alone. Review the product identity, interface behavior, driver binding, and application expectations. bcdDevice can express a device revision, but changing it does not replace compatibility review.

Can Each Board Receive a Serial Without Recompiling the Application?

Yes, a project can use a common application with a separately provisioned serial source. USBFS 3.20 provides the User Call Back path for this. However, the project still needs an implemented allocation, storage, and readout method. The API alone does not provide those production steps.

Is the Silicon Generated Serial Guaranteed to Be Unique?

No. USBFS 3.20 explicitly gives no uniqueness guarantee for its die-ID-derived serial. If the application needs distinct unit identities, define and verify an appropriate allocation process rather than relying on that option's name.

What Should Purchasing Confirm with Engineering?

Confirm who supplies the firmware and unit serials, which approved build applies, and whether programming or rework may change the identity. Keep those requirements separate from the bare MCU ordering code. A quotation for CY8C5868LTI-LP038 does not define the finished board's USB configuration.

Finalize the Identity Plan Before Release

Release the configuration only when the product IDs are authorized, the serial method matches the unit requirement, and host observations support the intended behavior. Carry any unresolved version, provisioning, or driver questions into the engineering review. The useful output is a traceable identity plan tied to the actual build.

Related guides

Keep reading

All guides →