PaSw,
... My RX and TX terminals are connected to a bufoe component controlled by the TX_EN, this all works fine for the UDB UART, but the issue is that the UART SCB has fixed RX and TX connections and it won't allow me to route to a single bidirectional pin.
You are correct. On the PSoC6s (and later PSoC4s) Cypress elected to reduce the GPIO functionality of the Digital Routing 'Fabric'. options. From my research, I cannot find a way for a GPIO to be assigned to be Bidirectional or as a Input and Output pin with Output enable.
Unless someone can show how a GPIO pin can be configured as listed above, you have to assign a separate pin for Input and for an Output as open drain and physically connect the pins together outside the IC.
The TopDesign allows for a "BiDirectional" and a Input/Output with OE, but I have yet to get either of these GPIO configurations to route and build. It these GPIO types are not allowed, Infineon should remove them from the component catalog for the PSoC6.
I have two solutions that do route.
Solution #1
This solution has the advantage of eliminating the Tx_oe control from the UART. However, it basically requires a pullup on the GPIO. I configured the Rx input as an digital input with Pullup. This eliminated an external pullup resistor.
The potential downside is the data rate. Since the Tx output is open drain, it pulls low strongly but an inactive high is a float. The the float high is dependent on the value of the pullup resistor. A lower value a faster float high.
Solution #2
This solution theoretically could have faster data rates since the external transceiver IC can switch the driver off and the receiver on faster.
The downside is that it requires the Tx_oe signal through a GPIO to control the transceiver direction.
As I mentioned earlier I have an identical setup to the first post in the thread I originally linked, and the same problem they had. According to that thread their problem was resolved but the actual resolution is not provided. I posted this to try and clarify what their resolution is as it is apparently possible (or else that thread is mislabeled as resolved).
It was my "solution" that was apparently selected as "solved" on the thread you posted. However, sometimes solutions are accepted by the forum moderator and not the original person posting. Therefore it is not clear which idea in the discussion that was adopted and working.
The solutions I list above do build/route. Due to the internal architecture of the PSoC6, it is much more limited than what is available on the PSoC5.
PaSw,
Attached is a modified App Note project that defines a Tx_Enable pin to control an external Bi-directional transceiver.
This Tx_Enable pin is enabled in the component configuration under the "Advanced" tab.
Then you also have to declare the PSoC GPIO pin to use for this signal in the "DWR/Pins" window.
I hope this helps.
PaSw,
... My RX and TX terminals are connected to a bufoe component controlled by the TX_EN, this all works fine for the UDB UART, but the issue is that the UART SCB has fixed RX and TX connections and it won't allow me to route to a single bidirectional pin.
You are correct. On the PSoC6s (and later PSoC4s) Cypress elected to reduce the GPIO functionality of the Digital Routing 'Fabric'. options. From my research, I cannot find a way for a GPIO to be assigned to be Bidirectional or as a Input and Output pin with Output enable.
Unless someone can show how a GPIO pin can be configured as listed above, you have to assign a separate pin for Input and for an Output as open drain and physically connect the pins together outside the IC.
The TopDesign allows for a "BiDirectional" and a Input/Output with OE, but I have yet to get either of these GPIO configurations to route and build. It these GPIO types are not allowed, Infineon should remove them from the component catalog for the PSoC6.
I have two solutions that do route.
Solution #1
This solution has the advantage of eliminating the Tx_oe control from the UART. However, it basically requires a pullup on the GPIO. I configured the Rx input as an digital input with Pullup. This eliminated an external pullup resistor.
The potential downside is the data rate. Since the Tx output is open drain, it pulls low strongly but an inactive high is a float. The the float high is dependent on the value of the pullup resistor. A lower value a faster float high.
Solution #2
This solution theoretically could have faster data rates since the external transceiver IC can switch the driver off and the receiver on faster.
The downside is that it requires the Tx_oe signal through a GPIO to control the transceiver direction.
As I mentioned earlier I have an identical setup to the first post in the thread I originally linked, and the same problem they had. According to that thread their problem was resolved but the actual resolution is not provided. I posted this to try and clarify what their resolution is as it is apparently possible (or else that thread is mislabeled as resolved).
It was my "solution" that was apparently selected as "solved" on the thread you posted. However, sometimes solutions are accepted by the forum moderator and not the original person posting. Therefore it is not clear which idea in the discussion that was adopted and working.
The solutions I list above do build/route. Due to the internal architecture of the PSoC6, it is much more limited than what is available on the PSoC5.
