bmentink
bmentink
HI, I havn't had a reply to this, but would really like to see if I can use the mini-oof module ... I notice that it is used in the...
My bad, the sequence should have been send as $9a 36 **80**
Interesting, the 1st sequence pushed the incorrect data, the 2nd corrected sequence with decimal 80 instead of hex, produced the correct data .... is there a parity/8-bit issue? EDIT: Nope...
More updates on this issue: I have noticed that when I program the board including some forth which loads and runs on boot, it outputs the correct data while power...
I was looking through how the uart.v module is used and noticed it is never reset, is this the issue? instead of ``` buart _uart0 ( .clk(clk), .resetq(1'b1), .rx(uart_RXD), .tx(TXD),...
Well it "will" matter because it means that there is a chunk of code in uart.v that will never execute (code responsible for setting variables in a known state). What's...
Update: Adding the resetq to the top level of the uart module instance did not help in this case. However, there is an issue with the uart.v code. I dumped...
Remy, you are missing the point. Sure changing the constants in top of uart.v need to be changed for different baud rates, not entirely without a brain cell. (12Mhz &...
@jamesbowman I can supply it as a patch, but I won't have git "push" permissions will I ?? Or, I could just attach to this post, as it is not...
Hi Remy & James, I also apologize if I caused any offence ... was a bit frustrated :) Attached is the zip file containing a single file uart2.v ... Please...