It seems that the problem with the bad links was caused by me not opening the 
libraries on startup. I updated my startup.m script and everything is fine, 
except that I still have to remove the link to the Casper library to get the 
FFT block to compile.

-Nevada

On Mar 12, 2010, at 4:44 AM, John Ford wrote:

>> Is it still necessary in 11.x/RHEL to load/open the CASPER library
>> before opening a model containing library blocks?
> 
> Yes, Henry, it is.  We have a startup.m that opens/loads the user's
> libraries and starts sysgen.
> 
> Here it is.
> 
> Yes, Master<1005> more startup.m
> addpath('/export/home/tokra/scratch/casper/mlib_devel_10_1/xps_library');
> addpath('/export/home/tokra/scratch/casper/mlib_devel_10_1/casper_library');
> addpath('/export/home/tokra/scratch/casper/mlib_devel_10_1/gavrt_library');
> sysgen_startup
> system_dependent('RemoteCWDPolicy','reload')
> system_dependent('RemotePathPolicy','reload')
> load_system('casper_library');
> load_system('gavrt_library');
> Yes, Master<1006>
> 
> Then of course there are all the environment variable to set.  We also
> have a script for that:
> 
> Yes, Master<1006> more Startsg.sh
> #!/bin/bash
> source /export/home/tokra/Xilinx/11.1/settings64.sh
> export MATLAB=/opt/matlab
> export XILINX=/export/home/tokra/Xilinx/11.1/ISE
> export XILINX_EDK=/export/home/tokra/Xilinx/11.1/EDK
> export PLATFORM=lin64
> export XILINX_DSP=/export/home/tokra/Xilinx/11.1/DSP_Tools/${PLATFORM}
> export
> BEE2_XPS_LIB_PATH=/export/home/tokra/scratch/casper/mlib_devel_10_1/xps_l
> ib
> export MLIB_ROOT=/export/home/tokra/scratch/casper/mlib_devel_10_1
> export PATH=${XILINX}/bin/${PLATFORM}:${XILINX_EDK}/bin/${PLATFORM}:${PATH}
> export
> LD_LIBRARY_PATH=${XILINX}/bin/${PLATFORM}:${XILINX}/lib/${PLATFORM}:${XIL
> INX_DSP}/sysgen/lib:${LD_LIBRARY_PATH}
> export LMC_HOME=${XILINX}/smartmodel/${PLATFORM}/installed_lin
> export PATH=${LMC_HOME}/bin:${XILINX_DSP}/common/bin:${PATH}
> export INSTALLMLLOC=/opt/matlab
> export TEMP=/tmp/
> export TMP=/tmp/
> $MATLAB/bin/matlab
> 
> 
> John
> 
> 
>> 
>> Thanks,
>> Henry
>> 
>> On 3/11/2010 11:46 PM, Nevada Sanchez wrote:
>>> I've tried deleting and replacing (even creating an entirely new model)
>>> with no luck. I managed to fix it be destroying the link of the FFT
>>> module back to the Casper library and all is well now. Except that I
>>> don't think I should have to do that.
>>> 
>>> Anyway, I've been having another annoyance that may be related to this
>>> problem. Every time I open a model, all of the casper and xps blocks
>>> have bad links until I drag one of the blocks from their respective
>>> libraries into the file. The libraries are in the path and they show up
>>> in the library browser. Any ideas on what might be going wrong here?
>>> 
>>> If it helps, we're running Xilinx tools version 11.4, with the latest
>>> snapshot of the casper repository on RHEL 5.
>>> 
>>> -Nevada
>>> 
>>> On Mar 4, 2010, at 2:18 AM, Mark Wagner wrote:
>>> 
>>>> Hi Nevada,
>>>> 
>>>> If all your casper libraries are linked and updated, the first thing I
>>>> would try is deleting the fft and replacing it with a new one from the
>>>> library, then recompiling.
>>>> 
>>>> Or try running the fft mask script from the matlab command line and
>>>> see if you get any other telling errors.
>>>> 
>>>> Mark
>>>> 
>>>> 
>>>> On Wed, Mar 3, 2010 at 11:10 PM, Nevada Sanchez <nev...@mit.edu
>>>> <mailto:nev...@mit.edu>> wrote:
>>>> 
>>>>    I have a rather simples model that takes a signal stored in ram
>>>>    and FFT's it. However, I'm having some problems getting it to
>>>>    compile. I get the following errors whenever I run 'Update
>>>> Diagram':
>>>> 
>>>>    + Block error: twiddle: Simulink: The LinkStatus can be set only
>>>>    for a linked block.
>>>>    + Block error: twiddle: Simulink: Error in
>>>>    
>>>> 'sysgen_scratch/fft/fft_biplex0/biplex_core/fft_stage_3/butterfly_direct/twiddle':
>>>>    Initialization commands cannot be evaluated.
>>>> 
>>>>    Could somebody help me out with this?
>>>> 
>>>>    -Nevada
>>>> 
>>>> 
>>> 
>> 
> 
> 
> 


Reply via email to