Hi Steve

Are you preloading the libraries?

The missing XPS block error might be because your libraries did not load. Newwer simulink versions seem to only load libraries as they are required. Unless the library is loaded (eg, by "expanding" it in the Simulink library browser) before trying to open your model and run the scripts, the links might be broken.

You can automate this process (to happen on Matlab startup) by adding the following commands into your startup.m:

addpath([getenv('MLIB_ROOT'), '\xps_library']);
load_system([getenv('MLIB_ROOT'), '\xps_library\xps_library.mdl']);
addpath([getenv('MLIB_ROOT'), '\casper_library']);
load_system([getenv('MLIB_ROOT'), '\casper_library \casper_library.mdl']);
addpath([getenv('MLIB_ROOT'), '\gavrt_library']);
load_system([getenv('MLIB_ROOT'), '\gavrt_library\gavrt_library.mdl'])

Jason

On 14 Mar 2010, at 07:54, Steve Maher wrote:

Hi,

I'm moving forward but have hit a snag.

To move forward I have done the following:
        • Added new version to switch in bee_xps.m
• Moved all Casper libraries to path without spaces after getting complaints I have now loaded all the libraries (XSG, Casper) into simulink, created the tutorial model in Simulink, started bee_xps, but I'm getting errors when running the XSG generator ("Run XPS" in BEE XPS 1.1).

The problems are in gen_xps_files.m. I started working through them but I'm wondering if there's something systemic, so I'm posting to the group. NOTE: I'm including a graphic with most of the details of my description - hopefully it goes through.

Strangely, the script doesn't recognize I'm on windows, even though system('ver') returns "Microsoft Windows XP [Version 5.1.2600]". I modified the code to force the windows assertion (system_os = 'windows';) after the OS detection code, but I still get the following error around line 200:

 set_param(sys,'SimulationCommand','update');

The error is

Failed to find 'XSG core config' in library 'xps_library' referenced by 'testborph/XSG core config'.

The value of 'sys' is "testborph".

I'm including mlib_devel_10_1/ [casper_library,gavrt_library,xps_library, xps_lib] in my path.

Any tips?

Thank,
Steve


On Fri, Mar 12, 2010 at 12:41 PM, Jason Manley <[email protected]> wrote:
I haven't yet tried 11.5 myself (nor has anyone at CASPER Berkeley),
but 11.4 works so it should be compatible. Just add the 11.5.2275 case
to the switch statement in bee_xps.m and let us know how if you have
any further problems.

Jason

On 12 Mar 2010, at 06:28, Jack Hickish wrote:

> Hi Steve,
>
> Is 11.5 actually unsupported, or is it just a case statement that
> needs adding to the bee_xps.m file. I remember Griffin had a similar
> problem when he set up our first 11.4 machine -- he just added the
> last case in that switch. (Detailed here 
http://casper.berkeley.edu/wiki/Xilinx_ISE_11.4_Setup)
>
> Cheers,
>
> Jack
>
>
>
> On Fri, Mar 12, 2010 at 2:12 PM, Steve Maher
> <[email protected]> wrote:
> More n00b issues ..
>
> Now I'm having trouble making Xilinx and Casper libraries happy
> (compatible).  The "latest" download of Xilinx/XSG appears to be
> 11.1, and then an upgrade will load version 11.5.2275 (even though
> it says it will upgrade to 11.4).  I see in xps_library/bee_xps.m
> that neither 11.1 nor 11.5 are supported (and I get fatal errors as
> expected)
>
> I'm having trouble finding versions 11.3/11.4 on Xilinx website, but
> I think I can find version 10.1.  Maybe I'll just try 10.1..
>
> Steve
>
>
> bee_xps.m
>     switch xsg
>         case {'8.2.02'}
>             set(handles.xsg_version,'String','8.2');
>         case {'9.1.01'}
>             set(handles.xsg_version,'String','9.1');
>         case {'10.1.1.1182'}
>             set(handles.xsg_version,'String','10.1');
>         case {'10.1.2.1250'}
>             set(handles.xsg_version,'String','10.1');
>         case {'10.1.3.1386'}
>             set(handles.xsg_version,'String','10.1');
>         case {'11.3.2055'}
>             set(handles.xsg_version,'String','11.3');
>         case {'11.4.2254'}
>             set(handles.xsg_version,'String','11.4');
>
>
> On Wed, Mar 10, 2010 at 5:05 PM, Steve Maher
> <[email protected]> wrote:
> You were right.  One little piece of the install failed because of
> Windows Logo requirements.
>
> I moved from that pesky XP64 machine to an XP32 machine and the
> install went better, although apparently the latest Xilinx (11.5)
> doesn't like the latest Matlab (2010a) so I had to downgrade Matlab
> to 2009b.
>
> Thanks,
> Steve
>
>
> On Wed, Mar 10, 2010 at 12:35 PM, Jason Manley <[email protected]
> > wrote:
> You might want to take a look at 
http://casper.berkeley.edu/wiki/MSSGE_Toolflow
>  and also http://casper.berkeley.edu/wiki/MSSGE_Toolflow_Setup
>
> If you do not have any of the Xilinx blocks in your simulink library,
> then installation of System Generator probably didn't complete. Once
> you've installed sysgen, the libraries should show up automatically.
> Be sure to install matlab before you install the xilinx tools.
>
> Jason
>
> On 10 Mar 2010, at 09:26, Steve Maher wrote:
>
> > Hi,
> >
> > Beginner question ..
> >
> > I'm brand new to Matlab/Simulink and Xilinx.  I have the Casper
> > libraries ready for use in Simulink but can't seem to find the right
> > documentation to integrate Xilinx blocksets.
> >
> > I've installed Xilinx ISI Design Suite 11 but don't know if that's
> > the right software (can't find any .m files) and if so, how to hook
> > it into Simulink.
> >
> > Any pointers are appreciated.
> >
> > Thanks,
> > Steve
>
>
>
>


<Capture.PNG>


Reply via email to