Hey Peter, I'm bumping this up to the listserve.
I am unfamiliar with PAPER. Perhaps someone with that project can help. If you haven't yet, you should complete Tutorial 2 <https://casper.berkeley.edu/wiki/Tutorials> with your toolflow to learn about the 10 GbE interface and how it is controlled. I usually build an "enable" signal via a software register into my model file so that in python I can set up everything as necessary, specifically set up the 10 GbE port and give it a reset, before "enabling" data to flow into it. PAPER may have a different strategy there. Have you compiled the bitcode from a model file on your system, or have you simply downloaded the bitcode and tried to run it on a Roach2? Have you verified you are using the python software that goes with that particular bitcode? I suspect that the correct piece of python software will prevent the overflow, unless you have made changes to the model file that haven't been accommodated in software. Another thought: If you run the bitcode at a speed faster than it was intended, the 10 GbE buffer may fill as expected but the 10 GbE interface may not drain it fast enough. In other words, you may be running at a clock rate that pushes data out faster than 10 Gbps. There will be other problems with the bitcode there as you are pushing the signals past the timing limitations. If you compiled a PAPER model file but changed the FPGA rate from Simulink, then while your bitcode may function logically as expected and compile without errors, it may be trying to drive the 10 Gbps at a rate near or over 10 Gbps. You will have to adjust your model file and signals into the 10 GbE appropriately so that it does not overflow the buffer and the 10 Gbps rate on the link is not exceeded. --Laura On Mon, Oct 20, 2014 at 9:13 AM, peter <[email protected]> wrote: > Hi Laura, > This is peter from NAOC,We have a problem about the 10Gbe block on roach2. > We use the PAPER modle for a experiment,But no data comes out to send. > I find the reason is the overflow of TX,in addition,maybe it is the buffer > size caused this problem.I know a little about this overflow port,what can > I do to prevent the overflow?Do you have some good suggestions? > Thanks for your attention! > Best Regards! > peter > > >
