Don't forget trying to guess if the RX label is the line they transmit out of or you transmit to.
this post was submitted on 02 Jul 2023
57 points (96.7% liked)
Programmer Humor
32600 readers
74 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Isn't it supposed to be from your device's perspective?
An RX on your side would be TX on the other.
Not always, it really depends on what the person who did the board layout or wrote the firmware thought. When I do a board/firmware I label it from the devices perspective, so the TX is where the bits I'm transmitting will be coming out of, RX is where I'm expecting your bits to be sent to. Others label it from the perspective of the device connecting to it. So TX is where you connect the line your sending bits from. To me that's wierd because, to others it's what they expect. There is no standard and the result is you end up hooking it to an oscilloscope and see which line bits are being sent from. Then you use the scope to figure out all the settings. If they don't transmit in power up then... Frustration ensures
Which is why for a lot of serial protocols nowadays they changed the labeling to MOSI/MISO instead of TX/RX
Set the baudrate to 115200, that way I should get enough garbage to be able to figure out how far off the baud rate is and if flow control is broken!