Please see my comments below:
1) What is the max baud rate supported by the CDC driver and the CY7C65213A? For example, max baud rate with CDC driver on Windows / Linux.
-> UART on USB-Serial can support a maximum of 3Mbps.
2) The GPIO on the CY7C65213A are non-volatile and configurable using the Cypress GUI tool. Are the API calls documented to allow us to configure the same GPIO pins using custom code?
-> The GPIOs can be configured as input/output/tristate only using the USB-Serial configuration Utility GUI . Once the GPIO's functionality is configured, the GPIO current value is set/get depending on the configuration(input/output) using the CyUSBSerial Library through a host application. Please refer to the USB-Serial API documentation in the USB-Serial SDK. An example host application to control the GPIO operation is also available in the SDK.
3) If using the 2 port device CY7C65215A, is the enumeration guaranteed to be with UART #0 to be first and UART #1 next? This important for our connector to map the proper UARTs and in sequence
-> We can assign a serial number to each USB-Serial Device. When the Serial number is assigned, the enumeration instance (COM port number and device instance path) of the each interface will be fixed. Hence the enumeration will be the same each time.
4) In reviewing this important correction:
The UARTs inside the CY7C65215A are also impacted by the same typo? Please confirm that the TXDEN is ACTIVE HIGH which is most popular with RS485 transmitter ENABLEs.
-> Yes, the TXDEN pin is active high. The datasheet discrepancy will be corrected soon in the next release.
5) Guessing these devices are PSOC based? Are the project files available to build our own version of these UARTs using the PSOC with flow control lines (8 pin) & RS485 support? Ideally to make use of the non-volatile pins to customize for our designs.
-> Yes, USB-Serial is PSOC based. We do not provide the files and the USB-Serial Device is a fixed firmware part.