Dear all: I had similar error messages as Laura addressed.
I guess the error happened while Matlab was loading the "software register " in xps_library.mdl , and Matlab didn't recognize the script of "software register". I pull an instance of "software register" in a new model file, then "look under the mask", there was one input port ,out_reg, and one output port,sim_out, only, nothing in between. I browsed the script of the xps_library.mdl, it looks fine. Just somewhat the Matlab can't interpret them correctly. I tried Matlab 2012a, and 2013a. regards homin On Thu, Nov 20, 2014 at 1:04 AM, Vertatschitsch, Laura E. < lvertatschit...@cfa.harvard.edu> wrote: > Hi Dave, > > Thanks for the information. > > I'm using the sma-wideband fork of mlib_devel, and I am at commit 263df71 > from Sep 24 this year. > > Rurik checked in a design he made with a software register, and when I > attempt to edit it and double click to view the options, I get a popup > error: > -->Error evaluating 'MaskCallback' callback of swreg block (mask) > 'r2dbe_top /r2dbe/quantize_0/thresh'. -->Not enough input arguments. > -->Error evaluating 'MaskCallback' callback of swreg block (mask) > 'r2dbe_top /r2dbe/quantize_0/thresh'. -->Undefined function > 'swreg_maskcheck' for input arguments of type 'char'. -->Error evaluating > 'MaskCallback' callback of swreg block (mask) 'r2dbe_top > /r2dbe/quantize_0/thresh'. -->Undefined function 'swreg_maskcheck' for > input arguments of type 'char'. -->Error evaluating 'MaskCallback' callback > of swreg block (mask) 'r2dbe_top /r2dbe/quantize_0/thresh'. -->Undefined > function 'swreg_maskcheck' for input arguments of type 'char'. > > Ignoring the obvious names of variables in our particular design, seems > there are callback issues with swreg_maskcheck. After closing the popup, I > get to the options dialog: > Mode: one value > I/O direction: From Processor > I/O delay: 0 > Sample period: 1 > Name: gain > Bitwidth: 32 > Type: 0 > Binary Pt: 0 > X Provide sim input/output > > When attempting to hit OK even after not changing anything, I get the > following error in a popup: > -->Error in 'r2dbe_top/r2dbe/quantize_0/thresh': Initialization commands > cannot be evaluated. -->swreg block (mask) does not have a parameter named > 'numios' > > I can just close the error window and options by using the X at the top > right of the windows. > > When simulating, I get the error from the sw register we call "thresh" > saying the "Initialization commands cannot be evaluated. Caused by: swreg > block (mask) does not have a parameter named 'numios'" > > I get popup errors when trying to change any of the options, and since > pressing OK results in an error, I actually can never change this block. > > Errors are all in simulation and design - I can compile just fine. > > --Laura > > On Mon, Nov 10, 2014 at 8:01 PM, David MacMahon <dav...@astro.berkeley.edu > > wrote: > >> Hi, Laura, >> >> It looks like the software registers end up using the "fixdt" function >> when setup as "From Processor" and the mode is other than "one value". I'm >> pretty sure the "fixdt" function is from the fixed point toolbox. >> >> Does your problem happen only on software registers with more than one >> output or does it happen on all software registers? Which mlib_devel >> commit are you using? >> >> Dave >> >> On Nov 9, 2014, at 9:04 PM, Vertatschitsch, Laura E. wrote: >> >> > Hi Homin, >> > >> > I have a hunch that the new software registers may need the fixed point >> toolset to work. I can compile fine, but can't simulate and can't change >> the parameters. The fixed point toolset seems to be the main difference >> between myself and Rurik's set up, and he seems to have no issues. I'd be >> curious to see if the same is true for you. >> > >> > Laura >> > >> > On Sunday, November 9, 2014, David MacMahon <dav...@astro.berkeley.edu> >> wrote: >> > Hi, Homin, >> > >> > What bad luck did you have? One thing about the new software registers >> that might be causing you problems is that they require the inputs to be of >> the desired/requested/expected width. IOW, instead of using a "convert" >> block internally to make the user-supplied input be the expected width, the >> new software register uses an "assert" block to require that the user >> (you!) adds the appropriate convert block before the software register. I >> think this unfriendly to users, but I think that's the way it is. >> > >> > You might have to add a "bitbasher" block (or "reinterpret" and >> "convert" blocks) before the software register to make the new software >> register yellow block happy. >> > >> > HTH, >> > Dave >> > >> > On Nov 9, 2014, at 7:53 PM, Homin Jiang wrote: >> > >> > > Hi Jack: >> > > >> > > I followed your instruction, but i didn't have good luck. I am using >> latest version of mlib_devel library from ska-sa, and i guess the latest >> "software register" block has something wrong. >> > > There is a "software register_OLD" in the library, is there a command >> i can replace the "software register" by "software register_OLD" ? >> > > >> > > regards >> > > homin >> > > >> > > >> > > On Fri, Nov 7, 2014 at 7:03 PM, Jack Hickish <jackhick...@gmail.com> >> wrote: >> > > Hi Homin, >> > > >> > > As Wes says, there's a good chance you need to replace your sw >> registers with new versions from the library. For sanity, you can do this >> automatically from the matlab prompt with the command (open your model >> first so bdroot points to it): >> > > >> > > >> update_casper_blocks(bdroot, 'Tag', 'xps:sw_reg') >> > > >> > > You can update *all* casper blocks with: >> > > >> update_casper_blocks(bdroot) >> > > >> > > Cheers, >> > > Jack >> > > >> > > On Fri Nov 07 2014 at 08:30:09 Wesley New <wes...@ska.ac.za> wrote: >> > > Can you elaborate on these errors? >> > > >> > > A while ago the software registers were updated so you might have to >> replace all of the software registers in you your design with the new on >> from the library. >> > > >> > > Wesley New >> > > South African SKA Project >> > > +2721 506 7365 >> > > www.ska.ac.za >> > > >> > > >> > > >> > > On Fri, Nov 7, 2014 at 3:55 AM, Homin Jiang < >> ho...@asiaa.sinica.edu.tw> wrote: >> > > Hello: >> > > >> > > I am upgrading my system to xilinx 14.7 with Matlab 2012a and up to >> date mlib_devel library. >> > > I encountered errors by the "software register" in XPS library. Any >> one can help ? >> > > >> > > thanks >> > > homin >> > > >> > > >> > > >> > >> > >> >> >
