PSoC™ 5, 3 & 1 Forum Discussions

I've developed code that uses the recommended while((USBUART_CDCIsReady()) == 0){} before sending new data to the host.

All is working great if the host is connected and the port is open.  As soon as a close the host port, eventually the PSoC app code hangs on the while() statement shown above.

Is there a proper way to detect if the port is open to accept new data?

Len

Hi,

is there a method of storing different UDB builds in PSoC 5LP (or PSoC 4) Flash and RAM and selecting one of them for one task and another for other task ?

The pins and resources accessed by UDB blocks will be the same just UDB schematics (or Verilog code) varies ?

Thanks.

When the device is powered up (PSoC 5 in this case) windows adds it to the device list in device manager. The vendor id and product id is the default.

Once the custom driver for the device is loaded, which includes the .inf file, it is then reported in device manager with the custom VID/PID.

Is there a way to embed the a custom VID/PID in the device so that it always shows the custom VID/PID without having to install the driver/inf file first?

Hello Everyone,

I have a PSoC5LP based USB Composite Device (HID Keyboard and Mouse) that I'm working on.  One of the problems I've run into is that I require the keyboard to be functional in BIOS of the host PC.  From what I can gather, I need to create a second Keyboard HID descriptor that conforms to the Boot Interface.  Creating a new HID descriptor is no problem, but I'm not sure where in my overall Device Descriptor this new HID device should go?  Is it it's own entirely new device that requires its own endpoints?  Can I just create a new "Alternate Setting" under the keyboard interface to be used on boot?

My descriptor tree is below:

Here's what I think adding the boot keyboard should maybe look like:

Is this the right track?  Do the Boot Keyboard settings and Custom HID Keyboard settings need to use different endpoints or can they both use EP1 and the host will switch between them?  Do I need to handle this switch from the Boot Keyboard to the Custom Keyboard in firmware?  or will the USBFS component handle it for me with no intervention needed from my code?

If this were a normal keyboard, It looks like I could simply change the keyboard subclass to "Boot Interface Subclass" and call it a day, but in the OS the keyboard must support additional keycodes beyond the standard 101/104.  From my understanding extended keycodes are incompatible with the Boot Interface, so simply changing the Custom HID Keyboard to a Boot Device would probably cut those extended codes out, so that option is out.

If anyone out there has some knowledge of USB could chime in, it would be greatly appreciated.

Thanks!