Email or username:

Password:

Forgot your password?
7 comments
Lukas

@leah The only cursed experience I had with UART was when implementing a soft UART transmitter, didn't leave enough time between two bytes and sometimes the receiver and the protocol decoder in my scope got confused about the byte boundaries. Adding a couple bits of idle time between two bytes fixed it.

Trammell Hudson

@karotte @leah sometimes serial stop bits are necessary for the physical UART mechanism

Marcus Müller

@karotte @leah in practice: many of the very established UART controller IP cores simply have state machine bugs – Cadence, things that ended up in FTDI converters, Zynqs, …
UART also is extremely cursed in concept, with the idea that sample something happening on a physically noisy channel and then go ahead with nothing but at most a single parity bit and act as if it's reliable – and that although you're not even sure where the symbol transitions happened. UART is very very cursed.

kleines Filmröllchen

@leah @karotte UART is less of a standard than SPI or I2C so it is definitely cursed

Leah Neukirchen

@filmroellchen @karotte it's a fine standard that almost noone implements

Domi.UwUException | this nickname is now extra long to prove a point, hi linus yes ~~it runs netware

@leah @filmroellchen @karotte it’s modified RS-232, with the only important change being lower voltage levels and a lot of removed pins

i’d argue that it’s at least based on a standard ^^

Go Up