Honored Contributor
Honored ContributorHello Michael,
<div class='quotetop'>QUOTE (mschnell @ Jul 11 2009, 02:18 AM) <{post_snapback}> (index.php?act=findpost&pid=23075)</div> --- Quote Start --- Supposedly, speed is not the problem but latency. Speed can't be increased, as (I believe) the UART driver is done in a quite optimum way.[/b] --- Quote End --- Indeed, its performance is remarkable. <div class='quotetop'>QUOTE </div> --- Quote Start --- Do you use the FifoedUart IPCore ? The AlteaUART needs a too low latency interrupt service, which Linux can't provide. The hardware Fifo will relax the problem.[/b] --- Quote End --- I am already using the FIFOed UART. I am making the measurements in the TX and RX pins. The message arrives and is registered correctly. My problem is the correct message takes too long to be read. Yesterday, when modifying some things about Processor type and features I noticed parameters that might be useful. However, didn't move anything to leave my OS alive but there was , for example, a parameter corresponding to the timer frequency. It says 100 Hz. But isn't this "timer" actually timer_0 (I am using a DE2)? Shouldn't it be 1 KHz since the timer is configured for every 1 ms? I don't think the problem is within the driver of the UART. The FIFOed one has proven very useful. I believe the peed that must be improved must be in the OS or in management of some sort. Regards, Francisco
