#apertus IRC Channel Logs

I'm sorry I didn't yet write the email as I was told.

morning folks!

once you got your morning coffee/tea/mana I think apurvanandan[m] would appreciate some assistance with the code for the temperature stress test

excellent!

hi there

Bertl, Yes the issue was in FIFO logic only :) now the simpler ft601 controller is working, and I am myself amazed how much useless code has been removed. The svf size got halved too.

Mainly the buffering of data was being used due to wrong handling of clock edges

can you generate a simulation VCD of the signals invovled for current setup?

Yes, I sending the VCD in a moment

The vcd file and wlf file

The final working code

and I do not see the fifo signals in the VCD

From the testbench

how about fifo_rd_en and fifo_*emp?

That doesn't matter

yes, but you lose a cycle there

now for the real world test setup, the FIFO is now 1024 words deep?

Yes

I am at same state as two days earlier

When I stop data creation on fifo being full, I don't lose data but when I don't I lose 100 words every milion words

how much did you lose before the fifo depth change?

same*

Let me rephrase

In one case I stop data generation when FIFO gets almost full then no loss

When I stop on FIFO full condition, I lose 100 words every 200Gbits

this sounds like a bug somewhere

i.e. fifo full should be sufficient to prevent any loss if you stop data generation

I have to say that fifo takes one cycle to give new data, but the FT601_wr needs to be high just along with new data

So a cycle where no change is visible in vcd

i.e. set fifo read in one cycle and the write in the next

anyway, you have plenty of other problems, was just making a comment there

https://ibb.co/r5DD2Zf

Yes tested ok

no need to ever stop any data generation, etc

FIFO never gets full, etc

yeah, make it triple :)

FT601_wr_n is now one cycle before ie txe change on one clock, wr_n on next, data on after wr_n

apurvanandan[m]: any news on the double/triple check?

Not working :(

FIFO full condition is always required

so what was the 'no dataloss' case you reported?

ie stop writing when FIFO gets full

okay

nn

Bertl, Can I attach a counter that pause the transfer after every 256 words?

Okay

To eliminate all cases when fifo gets empty in between of transfer. So I start with around 300 words in fifo and send 256 words and then again wait for fifo to fill upto 300

Maybe I am wrong, but testing this won't hurt