Is your desire to use the on-board USB as a USBUART for serial comm?
If yes, I have provided a custom user-installable component called Term. This component can be configured as a standard UART (for example for talking to the KitProg board) or as a USBUART.
The component uses UART API calls to simplify the access to the USBUART functionality.
It is a little complicated to get started but I have included a number of documents to assist in configuring the user-installable component.
If you're interested, here is a link to the component library to access Term: Terminal Component - Simplifies UART or USBUART communication
Note: In addition, if you'd like there are a couple of other components in the library (documentation included) if you find them useful.
I do not need the uart, I only need the USB part to connect my terminal to my embedded device. I have to communicate from PC to my Infineon Iso2H823 (Isoface DO) device by usb using a PSOC5. Therefore I need a usb device on my cypress psoc5. In the past I run an HID device on my PIV32MM (worked perfect) but for I had to change to cypress devices I have to rebuild my application. (Cypress and Infineon merged and now I have to migrate all my microchip designs to Cypress) HID is my preferred profile for running a comunication on a PC does not need an driver for windows. Cypress examples do only offer keyboard or mouse for HID profile. To have an easy start I thought to use the USB UART example, removing the uart and all not needed parts and add my control code for my iso2H823 (using only the USB CDC part). But this does not work for I cannot remove the uart and the lcd parts form example code.
I just need to send and receive some strings…. PC- USB – PSOC- iso2H823
I already asked the community if an HID profile (generic) other than mouse or keyboard (just a usb hid socket offering an send and a receive method) is available form Cypress (as I used in past … microchip offers such an example code in MLA). I was told to use the mouse example and read the datasheet for USB… I am just an Psoc beginner and I can read an talk English but it is not so easy to fully understand what I have to do and which option has which result…. So it is always a try and error…. And I would be glad to avoid such a design method…. But obviously I have to go that way… ☹…
My Term component can be configured as USBUART and it will automatically use the PSoC5 on-board USB port. The component simplifies UART-type communication (such as Term_PutString(), Term_GetChar(), etc).
There is a demo program called "Term_demo" that uses Term. It's VERY simple in code structure.