1 of 1 people found this helpful
Please note that Kitprog acts as a USB-UART bridge to the target device as shown below:
So, on the slaves if you snap off the Kitprog and want UART for debugging purposes, then follow these steps:
#1: You can program the target using the 5 pin M/F headers
#2: You must unpopulate R22, R23 to isolate UART_TX and UART_RX lines of the Kitprog from the target
#3: Connect the FTDI (USB to Serial converter) on these pins to observe the serial output
Using the Kitprog on the slaves for UART seems like a better option. So, you could consider connecting it back.
The signals coming in to the target from the Kitprog are shown below:
The link to the schematic can be found here: https://www.cypress.com/file/443786/download
Thank you. This is an enormous help. It will take me a while to process it all but I think it is what I need to know.
One more question if I may.
On your advice, I had another look at the USB (micro) on the target end. I adapted the Code Example and made that work. Is it possible for the USBFS_UART to generate an interrupt on one or more characters received?
There are ISRs for each endpoints inside the file USBUART_episr.c. You can add your code in the OUT EP. When host is sending data to device OUT EP ISR will be triggered. Please consider creating a new thread if you have more queries regarding this.