Hi Miguel,

Sorry you're having so much trouble.

1. This is just a warning you're getting and doesn't hav any effect on the
functionality of the toolflow, but you can comment out:

Browser(2).Library = 'testbench_lib';
Browser(2).Name    = 'Testbench Blockset';

in mlib_devel/gavrt_library/slblocks.m, and you should stop getting that
warning.

2.  I think this is because you are opening up the model file with a newer
library than what it was originally created with.  But I think you solved
this already by deleting the block and pulling from the library you're
opening the model file with.

3.  If you look at this posedge, I think it's not being loaded correctly.
 If you try deleteing and replacing the posedge (tut2/pkt_sim/posedge) like
you did in 2, it should fix the problem.

4. I'm not sure what the issue is here, but try ctrl-D, which will update
the design and propagate the data types and hopefully it will give a more
telling error.

Best,
Mark


On Tue, Apr 5, 2011 at 1:43 AM, <[email protected]> wrote:

>   Hi Griffin,
> Thank you so much!!
>
> About the first option
> centos 5.3 / Xilinx ISE 11.4 / Matlab 2009b
> Are  Casper Libraries compatibles with? I mean, don’t are they build for
> Ise 10.1?
>
>
> My problems?  Ok let’s go step by step:
>
> 1) Each time I open simulink:
> Warning: Could not find library ‘testbench_lib’ o speciefied in
> ‘C:\codigos\mlib_devel\gavrt_library\slblocks.m’
>
> 2) The first time i open a model all the yellow blocks are “bad link” and
> matlab welcomes me with a lot of warnigs like:
> “Warning: "tut1/counter_value" is a parameterized link. To view, discard,
> or propagate the changes for this link,
> use the "Link Options" menu item.”
> With the tutorial 2 I also get four warnings like,
> “Warning: casper_library_misc.mdl, line 5905: block_diagram does not have a
> parameter named 'BlockName'”.
> And others warning about a parameter "SID” (I can remember a discussion
> about SID in the casper list)
> Anyway, then I pick up an element from BEE_XPS System Blockset (i can see
> this library in the simulink library browser) , put it in the model and the
> yellow blocks became ok.
>
> 3) When I tried to run ‘bee_xps’ with ‘tut2.mdl’ i get the same warnings
> plus the following error:
> Error using ==> gen_xps_files at 199
> Failed to find 'Misc/pulse_ext/posedge' in library 'casper_library'
> referenced by 'tut2/pkt_sim/posedge'.
>
> 4) With tutorial3 after “bee_xps” the thing are getting worse... I received
> around fifty errors like (i only copy two of them but i have a .txt file if
> someone is interested in):
> “Error using ==> gen_xps_files at 199
> --> Error reported by S-function 'sysgen' in 'r_spec_2048_r105/Concat1':
> An internal error occurred in the Xilinx Blockset Library.
>
> Please report this error to Xilinx (http://support.xilinx.com), in as much
> detail as possible. You may also find immediate help in the Answers Database
> and other online resources at http://support.xilinx.com.
>
> Since it is possible that this internal error resulted from an unhandled
> usage error in your design, we advise you to carefully check the usage of
> the block reporting the internal error. If errors persist, we recommend that
> you restart MATLAB.”
>
> “--> Error in 'r_spec_2048_r105/sync_cnt': Initialization commands cannot
> be evaluated.  MATLAB error message: Error using ==> register_mask at 48
> Error evaluating 'MoveFcn' callback of Xilinx Gateway Out Block block
> (mask) 'r_spec_2048_r105/sync_cnt/r_spec_2048_r105_sync_cnt_user_data_in'.
> Error using ==> xlBlockMoveCallback at 53
> Error reported by S-function 'sysgen' in
> 'r_spec_2048_r105/sync_cnt/r_spec_2048_r105_sync_cnt_user_data_in':
> An internal error occurred in the Xilinx Blockset Library.
>
> Please report this error to Xilinx (http://support.xilinx.com), in as much
> detail as possible. You may also find immediate help in the Answers Database
> and other online resources at http://support.xilinx.com.
>
> Since it is possible that this internal error resulted from an unhandled
> usage error in your design, we advise you to carefully check the usage of
> the block reporting the internal error. If errors persist, we recommend that
> you restart MATLAB.”
>
>
>
> I download the models from Casper web so i assume they will be ok. This is
> the reason why i was wondering if i have the correct setup. I readed
> http://www.xilinx.com/support/answers/17966.htm  and chose, Windows XP 32
> bits, Matlab R2008a, ISE 10.1.3. Theoretically... it should be valid
> but........
>
> Miguel.
>
>
>  **
> **
> *From:* Griffin Foster <[email protected]>
>  *Sent:* Monday, April 04, 2011 6:38 PM
> *To:* [email protected]
> *Cc:* [email protected]
> *Subject:* Re: [casper] Roach: Getting Started Enviroment 2011
>
> Hi Miguel,
>
> We are using a windows and linux setup which is:
>
> centos 5.3 / Xilinx ISE 11.4 / Matlab 2009b
> windows XP / Xilinx ISE 10.1 / Matlab 2007b
>
> the main git repo is at: git://casper.berkeley.edu/mlib_devel.git
>
> What kind of errors are you getting?
>
> -Griff
>
> On Mon, Apr 4, 2011 at 4:45 PM, <[email protected]> wrote:
>
>>   Hi all,
>> My name is Miguel. I started to work with Casper enviroment a couple of
>> months ago. I’m trying to comunicate severals Roach through a swicth.
>> I readed on the web that the best choice was: Windows XP, System Generator
>> 10.1 and Matlab 2008a (as Xilinxs said, it was compatible) but i started to
>> get (a lot of) warnings and errors.
>>
>> I would like to be sure, because I still have a terrible mess with
>> Linux/Windows, Matlab, System generator versions supported to work with
>> Casper libraries, the respository (isn’t a link to git repository on the
>> web, is it?) and i’m driving insane.
>>
>> It would be very helpfull  if someone could resume one/two different
>> options:
>>
>> 1) Which O.S must I install?
>> 2) Which System Generator Version must i install?
>> 3) Which Matlab version must i use?
>>
>> I mean, could anyone tell me for example :
>> “RED HAT 5, System Genereator 12.6, Matlab 2011”  or
>> “ubuntu 9.7, System Generator 10.1, Matlab 2009a”
>>
>> they both work ok.
>>
>> Thanks.
>> Miguel.
>>
>
>

Reply via email to