Re: Re: Re: [casper] timing errors

2017-06-05 Thread 门云鹏
@postgrad.manchester.ac.uk>, "casper@lists.berkeley.edu" <casper@lists.berkeley.edu> 主题: Re: Re: [casper] timing errors Hello Yunpeng, Black boxing can help speed up compile time but the place-and-route needs to run every time, so it won't really help the design meet timin

Re: Re: [casper] timing errors

2017-06-05 Thread James Smith
>> Yi He Yuan Lu 5, Hai Dian Qu, Beijing 100871, P. R. China >> >> -原始邮件- >> *发件人:*"James Smith" <jsm...@ska.ac.za> >> *发送时间:*2017-06-04 01:44:39 (星期日) >> *收件人:* "Michael D'Cruze" <michael.dcr...@postgrad.manchester.ac.uk>

Re: Re: [casper] timing errors

2017-06-05 Thread Vereese Van Tonder
9 (星期日) > *收件人:* "Michael D'Cruze" <michael.dcr...@postgrad.manchester.ac.uk> > *抄送:* "门云鹏" <yp...@pku.edu.cn>, "casper@lists.berkeley.edu" < > casper@lists.berkeley.edu> > *主题:* Re: [casper] timing errors > > > Hello Yunpeng, > > Just

Re: Re: [casper] timing errors

2017-06-03 Thread 门云鹏
"casper@lists.berkeley.edu" <casper@lists.berkeley.edu> 主题: Re: [casper] timing errors Hello Yunpeng, Just to echo what Michael and Vereese said - those tools can help you get a bit more insight into what's going on, and how badly your timing problem is, but the timing rep

Re: [casper] timing errors

2017-06-03 Thread James Smith
Hello Yunpeng, Just to echo what Michael and Vereese said - those tools can help you get a bit more insight into what's going on, and how badly your timing problem is, but the timing report should tell you how by how much you're missing timing (should be some nanosecond value). If it's just a

RE: [casper] timing errors

2017-06-03 Thread Michael D'Cruze
Hi Yunpeng, all, I recently wrote a memo which describes how you can use Xilinx SmartXplorer to help with timing issues. Have a look on the casper wiki in the Memos section: https://casper.berkeley.edu/wiki/images/f/f8/SmartXplorer_memo.pdf . It isn’t a free pass – you need to get fairly close

Re: [casper] timing errors

2017-06-03 Thread Vereese Van Tonder
Hi Yunpeng, You can use Xilinx's PlanAead tool to help with the timing errors. You can place your PFB in a "pblock" which helps with timing. I haven't worked with this in awhile but there's a tutorial on the CASPER wiki here: https://casper.berkeley.edu/wiki/Tutorial_PlanAhead I hope that helps

Re: [casper] Timing Errors ROACH2

2015-11-09 Thread Amit Bansod
Hi Ryan, I could get rid of those errors but the tool had hard time in placing with huge setup timing errors. How much utilization is good to set on p-blocks ? Currently, I had 60-70% for different components. Cheers, Amit On 05-Nov-15 9:46 AM, Ryan Monroe wrote: > Hi Amit, > > FYI, I am

Re: [casper] Timing Errors ROACH2

2015-11-09 Thread Ryan Monroe
Assuming that the pblock is not overlapping with any other pblocks, and that you have not constrained any other resources in the pblock, I have used 99% of the resources in a pblock (simply made it as small as possible). The trouble comes into play when there are resources which are not in

Re: [casper] Timing Errors ROACH2

2015-11-05 Thread Ryan Monroe
Hi Amit, FYI, I am CC'ing the CASPER list on all of these emails, so that they can be searchable for people in the future. The placements I gave you were for my personal design, and may not work for yours. When choosing pblock size, be sure to look at the pblock utilization in planahead.

Re: [casper] Timing Errors ROACH2

2015-11-04 Thread Ryan Monroe
np! the 10gbe core wasn't really intended to run at fast clock rates. Be sure to constrain it to the east-ish side of the chip, this is probably either a 1. device utilization issue (you are trying to do too much stuff on the chip), or 2. placement issue (probably this)-- the tools are

Re: [casper] Timing errors and subsystems

2014-01-30 Thread Jack Hickish
Hi Paul, I believe the placement cost table is the parameter you want to change (See http://www.xilinx.com/support/answers/35534.html). You should be able to change this and other compile parameters in xps_base/XPS_ROACH[2]_base/etc/fast_runtime.opt You might find that you get on better changing

Re: [casper] Timing errors and subsystems

2014-01-30 Thread Paul Marganian
On 01/30/2014 07:33 AM, Jack Hickish wrote: Hi Paul, I believe the placement cost table is the parameter you want to change (See http://www.xilinx.com/support/answers/35534.html). You should be able to change this and other compile parameters in xps_base/XPS_ROACH[2]_base/etc/fast_runtime.opt

Re: [casper] Timing errors and subsystems

2014-01-30 Thread Jack Hickish
I've toyed with Planahead a bit, and quickly found I was in way over my head. Could you recommend a good starting point for learning this tool? I'm sure you've found the planahead user guide, which is a bit of a documentation behemoth, but useful if you have a vague idea of what setting you're

Re: [casper] Timing errors and subsystems

2014-01-30 Thread Paul Marganian
wow. Thanks a lot Jack! Paul On 01/30/2014 10:15 AM, Jack Hickish wrote: I've toyed with Planahead a bit, and quickly found I was in way over my head. Could you recommend a good starting point for learning this tool? I'm sure you've found the planahead user guide, which is a bit of a

Re: [casper] Timing errors and subsystems

2014-01-29 Thread Paul Marganian
On 01/29/2014 01:03 PM, Paul Marganian wrote: Hi all, Should such software (simulink) features as subsystems and and gotos have any affect on the final circuit created when I build my bof file? I am compiling models on Roach I that use almost all of the available Logic Slices (~97%). That

Re: [casper] Timing errors and subsystems

2014-01-29 Thread John Ford
On 01/29/2014 01:03 PM, Paul Marganian wrote: Hi all, Should such software (simulink) features as subsystems and and gotos have any affect on the final circuit created when I build my bof file? I am compiling models on Roach I that use almost all of the available Logic Slices (~97%). That

Re: [casper] Timing errors and subsystems

2014-01-29 Thread Jack Hickish
I'm not sure what, if any, difference a subsystem will make to the mapped design (I thought none), but I believe it's the case that changing module names etc. can affect the place and route algorithm's start seed. I seem to remember seeing this mentioned in a Xilinx doc under the heading I've