Follow

The RX/TX way naming of nets is inherited from a previous era, when there were a clear distinction between DCE and DTE, terminals and modems. Now that all electronics systems are like matryoshka dolls of smart-ish subsystems and that it's not always clear who is "in charge" of a serial communication, shouldn't we use different names altogether to put the old way of naming things to a final rest?

How about ASI/ASO for pins and ASAB/ASBA for nets:
- Asynchronous Serial In
- Asynchronous Serial Out
- Async Serial A to B
- Async Serial B to A

ASO --> ASAB -->ASI
ASI <-- ASBA <-- ASO

Short, unambiguous, we just have to pick arbitrarily who's A and who's B amongst the two sides of a given interface.
No "crossover point", over a jumper or a connector, where the TX net *has to* become the RX net for the communication to work.

Also, no collision with the recommended new terminology for SPI oshwa.org/a-resolution-to-rede

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.