For USBUART a device driver is needed that physically connects to the USB-port and emulates a serial port to be accessed forom the OS. Cypress provides a driver for that although windows already has got one. Neither of those will run under Linux or any other OS. I would suggest you to google for "usb uart driver linux" and see if you can find something that works.
Try this app note and see if it helps you. AN82072
I tried the same thing with the CY8CKIT-059, trying to use a LINUX serial terminal program to connect to the USBUART interface with the same USB vendor ID / product ID as above. I found that it is possible to issue a modprobe command as root to get the USB device to be attached to a driver and a /dev/ttyUSBx device permitting the use of the device with terminal programs. This is what I found:
modprobe usbserial vendor=0x04B4 product=0xF139
minicom –baudrate 9600 –8bit –device /dev/ttyUSB1
#minicom –baudrate 9600 –8bit –device /dev/ttyUSB0
USB1 was the one that ended up passing target serial data to my minicom. I don’t know what USB0 is for.
You probably must also turn off hardware flow control in the terminal program in order to be able to transmit data from the PC to the USBUART.
I know this post is old but figured I would update it for those finding this page from search results.
I originally used cyc15's technique with usbserial. However, this allowed me to only use the attached CY8CKIT-059 devices and not other serial devices needing the usbserial module simultaneously. I discovered that if I updated the kitprog firmware to version 2.16, Ubuntu 16.04 LTS with kernel 4.4 successfully recognizes the device using the cdc-acm driver. I can now use minicom as normal on /dev/ttyACM0.
<<This is not Linux related, but it's the closest thread I could find for my issue>>
For my latest task, I want to use the Kitprog USB-UART Bridge as a debugging aide. But when I connect a terminal (tried both PuTTY and 232Analyzer) to the Kitprog COM port (COM3 in my Windows), it's flooded with non-stop incoming data. At 9600 they're all zeroes, but a 115K, there's more variety (but it's not really the spice of life...). It happens with the PSoC 5's Tx/Rx connected to nothing, and it and it happens with a blank project loaded on the board (no hardware modules, no code). Before I realized it was seemingly unrelated to the PSoC 4, I tried a couple of different project approaches, including the example in the CY8CKIT-042 Kit Guide, but had the same problem with all and there was no sign of characters coming across from the PSOC 4 (which I thought might somehow be intermingled with all the spurious characters).
I did find the Community Support Page: CY8CKIT-042: Buffer Overflow of USB-UART Bridge - KBA87869, but I'm using the most recent firmware on the programmer.
Firmware Version: 2.17
IDE: PSoC Created 3.3
OS: Windows 10
@Dave (1-28 ???)
I observe the continous flooding nonsens data are sent as long as the UART is not initialized and the pins are floating.
I would suggest you to check your kit's schematic for the correct Rx/Tx pins. Did you snap-off the Kitprog and re-connect it with wires?
On my machines the com-port is a two digit com-number, check by plugging and removing the Kit while watching the device manager.
Update: I installed the latest version of Creator on a different machine (running Windows 7) and it works fine. Will try updating my version on my main machine next.
Thanks for the input. It's good to know about the uninitialized state. Further on the Creator 4.0 update, it fixed the problem on my main (Win 10) machine. No other changes to hardware or project.
Hi,i have the same problem you mentioned in the first post.Can you please elaborate on your solution?
user.warn kernel: cdc_acm: probe of 1-1.1:1.2 failed with error -22