Ok, that is what I presumed.

Thanks!

Franco


-------- Original Message --------
Subject: Re: [casper] Warnings with new mlib_devel
From: Jonathon Kocz
To: [email protected]
CC:


Hi Franco,

It's probably the Matlab 2013a version that's causing the warning. If you switch to 2013b it should go away.

(As you found from your simple model, you can ignore the warning and stick with 2013a, but if you're opening a model with an FFT or similar, it can take a *long* time to get through all the warnings). 

Hope this helps,
Jonathon

On 2 January 2018 at 06:51, Franco Curotto <[email protected]> wrote:
Dear all,

I'm doing a fresh install of mlib_devel for ROACH and ROACH2 programming. I cloned the repository from github.com/casper-astro/mlib_devel, and switched to roach2 branch. I setup the startsg.local for my version of Xilinx ISE (14.7) and Matlab (2013a), but when I start Matlab I get a bunch of warnings like this:

Warning: xps_library.mdl, line 31617: line does not have a parameter named 'ZOrder'
> In load_system at 21
  In startup at 24
  In matlabrc at 188

I compiled a simple model for testing and it worked, but I'm wonder if those warnings are important, or is normal behavior. Should I switch to another mlib_devel/Matlab/Xilinx version?

Thanks,

Franco Curotto

--
You received this message because you are subscribed to the Google Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]ley.edu.
To post to this group, send email to [email protected].

--
You received this message because you are subscribed to the Google Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].

--
You received this message because you are subscribed to the Google Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].

Reply via email to