Hi Chao-Te,

Can you try replacing the fft and the pfb_fir blocks, making sure to set the
parameters the same?  Then try rerunning it.  Sometimes this resolves the
problem.  If you get the same error, try running the initialization scripts
by hand.  You can see how the script is called by right clicking on the
block -> view mask, then go to the 'initialization' tab.  From the matlab
prompt, just enter in the call, replacing the variables with the actual
values (ex. fft_init(gcb,'FFTSize',12,...etc.) ).  This should give you more
verbose output.

Mark


On Mon, May 3, 2010 at 4:17 AM, Chao-Te Li <c...@asiaa.sinica.edu.tw> wrote:

> Hi Mark,
>
> I got some errors as follows when I tried to specify the parameters
> for fft or pfb (although I have updated the ISE 10.1 to SP3) -
>
>
> #############################
> ##      System Update      ##
> #############################
> Error using ==> set_param
> Error in 'r_spec_2048_r103/pfb_fir_real': Initialization commands cannot be
> evaluated.  MATLAB error message: Error using ==> set_param
> Error in 'r_spec_2048_r103/pfb_fir_real/pol1_in1_last_tap': Initialization
> commands cannot be evaluated.  MATLAB error message: Error using ==>
> get_param
> Invalid Simulink object name:
> r_spec_2048_r103/pfb_fir_real/pol1_in1_last_tap/pfb_real_add_tree.
> #############################
> ##      System Update      ##
> #############################
> Error using ==> set_param
> Error in 'r_spec_2048_r103/pfb_fir_real': Initialization commands cannot be
> evaluated.  MATLAB error message: Error using ==> set_param
> Error in 'r_spec_2048_r103/pfb_fir_real/pol1_in1_last_tap': Initialization
> commands cannot be evaluated.  MATLAB error message: Error using ==>
> get_param
> Invalid Simulink object name:
> r_spec_2048_r103/pfb_fir_real/pol1_in1_last_tap/pfb_real_add_tree.
> Warning: Block diagram 'r_spec_2048_r103' contains one or more
> parameterized
> library links.  To find the
> parameterized links use the Model Advisor.  The diagram has been saved but
> may not behave as you intended.
> Warning: Block diagram 'r_spec_2048_r103' contains one or more disabled
> library links.  To find the disabled
> links use the Model Advisor.  The diagram has been saved but may not
> contain
> what you intended.
>
>
> ----------------------------------------------------------------------------
>
> any suggestion?
>
> Chao-Te
>
> --
> Open WebMail Project (http://openwebmail.org)
>
>
> ---------- Original Message -----------
> From: Mark Wagner <mwag...@eecs.berkeley.edu>
> To: Chao-Te Li <c...@asiaa.sinica.edu.tw>
> Cc: casper@lists.berkeley.edu
> Sent: Sun, 2 May 2010 22:59:34 -0700
> Subject: Re: [casper] casper Digest, Vol 30, Issue 1
>
> > Hi Chao-Te,
> >
> > The 100% utilization of DSP48's seems to be your problem.  I would
> > try using slices instead. In the fft and pfb paramater box, you can
> > do this by checking 'specify multiplier use' and then entering in a
> > vector that specifies the multipliers you want to use. I think you
> > want 'behavioral,' so if you have a 2^7 fft, you would enter in: [2
> > 2 2 2 2 2 2].
> >
> > Mark
> >
> > On Sun, May 2, 2010 at 10:12 PM, Chao-Te Li <c...@asiaa.sinichink
> > that unless you dig deep into the design, you're nota.edu.tw> wrote:
> >
> > > Hi Mark,
> > >
> > > Thanks for the help.
> > > I copy the utility summary from MATLAB as follows -
> > >
> > > Device Utilization Summary:
> > >
> > >   Number of BUFGs                           3 out of 32      9%
> > >   Number of DCM_ADVs                        1 out of 12      8%
> > >   Number of DSP48Es                        64 out of 64    100%
> > >   Number of ILOGICs                        65 out of 800     8%
> > >   Number of External IOBs                  97 out of 640    15%
> > >      Number of LOCed IOBs                  97 out of 97    100%
> > >
> > >   Number of External IOBMs                  1 out of 320     1%
> > >      Number of LOCed IOBMs                  1 out of 1     100%
> > >
> > >   Number of External IOBSs                  1 out of 320     1%
> > >      Number of LOCed IOBSs                  1 out of 1     100%
> > >
> > >   Number of OLOGICs                         5 out of 800     1%
> > >   Number of RAMB18X2s                      50 out of 148    33%
> > >   Number of RAMB36_EXPs                    14 out of 148     9%
> > >   Number of Slice Registers             21382 out of 69120  30%
> > >      Number used as Flip Flops          21382
> > >      Number used as Latches                 0
> > >      Number used as LatchThrus              0
> > >
> > >   Number of Slice LUTS                  21127 out of 69120  30%
> > >   Number of Slice LUT-Flip Flop pairs   27717 out of 69120  40%
> > >
> > > ------------------------------------------------------------------
> > >
> > > The model does use up all the DSP48Es (and some other devices).
> > > But they are at most 100%. So it's ok in terms of resources?
> > >
> > > Regards,
> > > Chao-Te
> > >
> > >
> > > --
> > > Open WebMail Project (http://openwebmail.org)
> > >
> > >
> > > ---------- Original Message -----------
> > > From: Mark Wagner <mwag...@eecs.berkeley.edu>
> > > To: Chao-Te Li <c...@asiaa.sinica.edu.tw>
> > > Cc: casper@lists.berkeley.edu
> > > Sent: Sun, 2 May 2010 21:48:48 -0700
> > > Subject: Re: [casper] casper Digest, Vol 30, Issue 1
> > >
> > > > Hi Chao-Te,
> > > >
> > > > To answer you question, the xps executable should be in the EDK
> > > directory.
> > > >  For instance, ours is located here:
> > > >
> > > > /opt/Xilinx/11.1/EDK/bin/lin64/xps
> > > >
> > > > I haven't directly used xps on windows, but I think it should be
> > > something
> > > > like this:
> > > >
> > > > C:\Xilinx\10.1\EDK\bin\nt\xps.exe
> > > >
> > > > >From the XPS_ROACH_base directory on linux I run the command:
> > > >
> > > > $xps -nw system.xmp
> > > >
> > > > Although, before you try to remove this error, I would check to see
> > > > what the utilization report looks like and if you actually have the
> > > > resources to build the design.  You can find this report in:
> > > >
> > > > <model_directory>/XPS_ROACH_base/implementation/system_map.mrp
> > > >
> > > > The example spectrometer was designed for the sx95t and may not fit
> > > > on the lx110t (which doesn't have very many dsp48's).
> > > >
> > > > Mark
> > > >
> > > > On Sun, May 2, 2010 at 9:12 PM, Chao-Te Li
> > > > <c...@asiaa.sinica.edu.tw> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I was compiling the wideband spectrometer from the 2009 tutorials.
> > > > > http://casper.berkeley.edu/wiki/Tutorials
> > > > >
> > > > > It was compilted well with ROACH:sx95t. but when I chose
> > > > > ROACH:lx110t, I got the following error message and suggestion -
> > > > >
> > > > >
> > > > > xilperl D:/Xilinx/EDK/data/fpga_impl/observe_par.pl -error yes
> > > > > implementation/system.par
> > > > > Analyzing implementation/system.par
> > > > >
> > > > >
> > >
> > >
>
> *****************************************************************************
> > > > > ***
> > > > > ERROR: 1 constraint not met.
> > > > >
> > > > > PAR could not meet all timing constraints. A bitstream will not be
> > > > > generated.
> > > > >
> > > > > To disable the PAR timing check:
> > > > >
> > > > > 1> Disable the "Treat timing closure failure as error" option from
> the
> > > > > Project Options dialog in XPS.
> > > > >
> > > > > OR
> > > > >
> > > > > 2> Type following at the XPS prompt:
> > > > > XPS% xset enable_par_timing_error 0
> > > > >
> > > > >
> > > > >
> --------------------------------------------------------------------
> > > > >
> > > > >
> > > > > How do I do to bring up the XPS or its prompt?
> > > > > Thanks.
> > > > >
> > > > >
> > > > > --
> > > > > Open WebMail Project (http://openwebmail.org)
> > > > >
> > > > >
> > > > > ---------- Original Message -----------
> > > > > From: casper-requ...@lists.berkeley.edu
> > > > > To: casper@lists.berkeley.edu
> > > > > Sent: Sat, 01 May 2010 12:55:16 -0700
> > > > > Subject: casper Digest, Vol 30, Issue 1
> > > > >
> > > > > > Send casper mailing list submissions to
> > > > > >       casper@lists.berkeley.edu
> > > > > >
> > > > > > To subscribe or unsubscribe via the World Wide Web, visit
> > > > > >
> > > > >
> > > > >
> https://calmail.berkeley.edu/manage/list/listinfo/cas...@lists.berkel
> > > > > ey.edu
> > > > > >
> > > > > > or, via email, send a message with subject or body 'help' to
> > > > > >       casper-requ...@lists.berkeley.edu
> > > > > >
> > > > > > You can reach the person managing the list at
> > > > > >       casper-ow...@lists.berkeley.edu
> > > > > >
> > > > > > When replying, please edit your Subject line so it is more
> specific
> > > > > > than "Re: Contents of casper digest..."
> > > > > >
> > > > > > Today's Topics:
> > > > > >
> > > > > >    1. Re: 'The Great Debate: Are We Alone?' (Tonight) (dana
> whitlow)
> > > > > >
> > > > > >
> > > ----------------------------------------------------------------------
> > > > > >
> > > > > > Message: 1
> > > > > > Date: Fri, 30 Apr 2010 17:15:22 -0400
> > > > > > From: dana whitlow <dwhit...@naic.edu>
> > > > > > Subject: Re: [casper] 'The Great Debate: Are We Alone?' (Tonight)
> > > > > > To: melvyn wright <melvyn.wri...@gmail.com>
> > > > > > Cc: casper@lists.berkeley.edu
> > > > > > Message-ID: <4bdb486a.2040...@naic.edu>
> > > > > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > > > > >
> > > > > > Good idea- we'll just hook that right up.  Let's see now- should
> it
> > > > > > be 430 MHz or 2380 MHz?
> > > > > >
> > > > > > Dana
> > > > > >
> > > > > > melvyn wright wrote:
> > > > > > > On Fri, Apr 30, 2010 at 12:13 PM, David Hawkins
> > > <d...@ovro.caltech.edu>
> > > > > wrote:
> > > > > > >
> > > > > > >>> will the debate be recorded, and available later for humans
> or
> > > for
> > > > > LGMs ?
> > > > > > >>>
> > > > > > >> Shouldn't we be blasting it out into space for the LGMs
> > > > > > >> to listen to live?
> > > > > > >>
> > > > > > >> :)
> > > > > > >>
> > > > > > >
> > > > > > > not according to
> > > > > > >
> > > http://www.csmonitor.com/USA/Politics/DC-Decoder/2010/0430/Stephen-
> > > > > Hawking-alien-warning-Could-we-talk-to-them
> > > > > > >
> > > > > > > :-(
> > > > > > >
> > > > > > > M.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > End of casper Digest, Vol 30, Issue 1
> > > > > > *************************************
> > > > > ------- End of Original Message -------
> > > > >
> > > > >
> > > > >
> > > ------- End of Original Message -------
> > >
> > >
> ------- End of Original Message -------
>
>

Reply via email to