-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed Output Behavior #22
Comments
Can you check if you run has dummy frames enabled? Also, the behavior changes slightly based on the configuration, the waveform in the wiki shows normal frame, QPSK and code rate 1/2, could you check if that's what you're running with? |
Is it possible to zoom in on the encoder's data input? I see your tvalid is toggling, maybe that's propagating to the output. We regards to the frequency change in the output after a certain point of the frame, this is introduced by the LDPC encoder due to how the tables are set. For example, for short frame, code rate 2/5, it looks like this:
The 6 first rows have 12 coefficients, while the 12 last rows have only 3. The LDPC encoder's implementation is naive, it will literally accumulate the very first bit received 12 times, then do the same with the 2nd bit, 3rd bit, etc until I think the 360th bit, after which it moves to the next row. From the 7th row onward, the encoder only needs to accumulate each bit 3 times, which makes it faster to run through 360 bits and in turn increases the output data rate. This means the actual data rate is not really dependent on the data width. There's probably smarter ways of doing this but I haven't been able to explore much! |
Hello,
I'm simulating the dvb_fpga core in the Vivado Simulator and when I compare the waveform to the ones in the Wiki, it seems that the output behavior is different. In my simulation the core starts immediately to output the encoded frame, whereas in the wiki waveform the output starts only after the input has ended and its tlast is raised.
Could you please tell me if this has changed since the wiki entry was created and if it is expected behavior now or if that is an error in my simulation design?
Thank you for your help in advance.
Vivado waveform
Waveform in the Wiki
The text was updated successfully, but these errors were encountered: