Understanding UART

Sure. Lets say you have a 200MHz clock. So, at idle, if your fifo is empty, you just send a 1. Let's say you have a 200MHz clock. When you have a byte (lets say its the letter A that's 01000001 in binary) at your fifo, you send a 0 as your start bit for 200,000,000/115,200 = 1736 cycles. You can just use a counter (add 1 every cycle until you get to 1736) to time how long to send the start bit. Then you send the least significant bit ( 1) for 1736 cycles and so forth until your byte is done. Then you send the end bit.

Thanks a lot for the detailed reply. I don't have any proper knowledge of the serial communication protocols but just watched two videos: 1. [video 2. [video # Point #1: Anyway, let me first clarify a point about the text from your post quoted below. >If x were an asynchronous input, for example a button press, or a UART Rx signal, AKA something that comes in unrelated to a clock, then it's async and you should synchronise it before using it: > >always\_ff @(posedge clk) x\_tmp <= x\_asyn; x\_sync <= x\_tmp; end always\_comb begin next\_state = f(x\_sync); ... I should have mentioned it earlier. I was thinking of a button press mechanism. Not sure if this protocol…