Hi, Yes, if you update blocks again, it will reset to the latest block versions I think (someone can correct me if I'm wrong), so do not update blocks after making changes.
V. Mugundhan On Thu, 14 Aug, 2025, 14:15 Bishnu Kumar Sharma, < bksha...@asiaa.sinica.edu.tw> wrote: > Hi Mugundhan vijayaraghavan, > Thank you for prompt reply. > In the New version of mlib_devel 2022a, > 'explicit_period', 'Explicit', ... in bi_real_unscr_2x_init.m in line 191, > 'explicit_period', 'Explicit', ... in bi_real_unscr_4x_init.m in line 267, > The difference is in coeff_gen_init.m > reuse_block(blk, 'en', 'xbsIndex_r4/Constant', ... > '',... > removing '',... extra line. > which I changed as you suggested also gave an error. > update_casper_blocks(bdroot), can't update fft_wideband_real block and > delete itself from the design. > File: coeff_gen_init.m Line: 585 Column: 20 Invalid expression. When > calling a function or indexing a variable, use parentheses. Otherwise, > check for mismatched delimiters. > Best Regards > Bishnu Sharma > Institute of Astronomy and Astrophysics > Academia Sinica > > > > On Thu, Aug 14, 2025 at 10:37 AM Mugundhan vijayaraghavan < > v.vaishnav151...@gmail.com> wrote: > >> Hi, >> >> I had made some brute force changes that sorts these errors and gives >> clean compilation using vivado 2023.1 and matlab 2022a. This link here has >> the details. >> >> https://github.com/casper-astro/mlib_devel/pull/219 >> >> Sincerely, >> >> V. Mugundhan >> >> >> On Thu, 14 Aug, 2025, 07:24 Bishnu Kumar Sharma, < >> bksha...@asiaa.sinica.edu.tw> wrote: >> >>> Hi Andrew, Heystack, >>> Any update about the bugs that give Failed to initialize mask. I also >>> faced a similar issue while using Vivado 2023 and MATLAB R2022a. I use a >>> naive approach, downloading each block from the Simulink library. This >>> didn't work for me. Now i copy the blocks from tutorials of zcu216 in my >>> model design. I hope this works. Please let me know how I can fix this bug. >>> Best Regards, >>> Bishnu Sharma >>> ASIAA Taiwan >>> >>> On Tuesday, January 21, 2025 at 4:38:56 PM UTC+8 Andrew Martens wrote: >>> >>>> Hi Heystek >>>> >>>> A few years ago there was a bug that might be related. Mathworks >>>> changed how the mask callbacks worked which led to one of the blocks not >>>> working properly in a similar way. I fixed it and updated the libraries. It >>>> might be that you are using a newer version of the tools, with an older >>>> version of the libraries. The tutorials probably have a newer version of >>>> the library block that works with the newer tools. >>>> >>>> To test this you could copy the block from the tutorial (that works) to >>>> your design and then simulate. >>>> >>>> If this is the problem, you need to use the fixed libraries with the >>>> newer tools as they have the fix. >>>> >>>> Regards >>>> Andrew >>>> >>>> On Mon, Jan 20, 2025 at 6:04 PM Heystek Grobler <heystek...@gmail.com> >>>> wrote: >>>> >>>>> Hey Andrew. >>>>> >>>>> >>>>> >>>>> Thank you for your reply. >>>>> >>>>> >>>>> >>>>> The PFB and FFT size that I am using is 1024 channels. >>>>> >>>>> >>>>> >>>>> I can run the tutorials without any problems. >>>>> >>>>> >>>>> >>>>> I have removed the PBF_real bock and I get the following error: >>>>> >>>>> >>>>> >>>>> Simulink:Masking:Bad_Init_Commands: Error in >>>>> 'rfsoc_zsu111_narrowband_v5/fft_wideband_real1/fft_biplex_real_4x/bi_real_unscr_4x/hilbert0/add_even_real/a_debus': >>>>> Failed to evaluate mask initialization commands. >>>>> >>>>> >>>>> >>>>> It is weird because it is the same block as in the tutorials. The >>>>> board I am targeting is the RFSoC ZCU111 and the RFSoC 4x2. >>>>> >>>>> >>>>> >>>>> Am I mussing something stupid? >>>>> >>>>> >>>>> >>>>> Thank you for the help. >>>>> >>>>> >>>>> >>>>> Heystek >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------- >>>>> Heystek Grobler >>>>> >>>>> 0832721009 >>>>> heystek...@gmail.com >>>>> >>>>> >>>>> >>>>> *From: *Andrew Martens <and...@sarao.ac.za> >>>>> *Date: *Monday, 20 January 2025 at 16:19 >>>>> *To: *cas...@lists.berkeley.edu <cas...@lists.berkeley.edu> >>>>> *Cc: *heystek...@gmail.com <heystek...@gmail.com> >>>>> *Subject: *Re: [casper] Simulation stuck >>>>> >>>>> Hi Heystek >>>>> >>>>> What size PFB are you using? Large PFBs can take many minutes to >>>>> initialise. How long are you waiting before you give up? >>>>> >>>>> >>>>> Your error could come from a number of sources. You need to simplify >>>>> things in an effort to isolate the problem. >>>>> >>>>> >>>>> Some things to try: >>>>> >>>>> - Check that you have the correct version of toolflow, mlib_devel etc. >>>>> have you run any tutorials successfully with your setup? >>>>> - Simulate the PFB in a separate, very basic design starting with just >>>>> the FFT block and a very small number of channels. Keep an eye on the >>>>> messages emitted to look for errors and warnings that might give you >>>>> clues... >>>>> >>>>> - If that works, simulate your design with just the FFT (again >>>>> starting with a small number of channels). Check that you can simulate, >>>>> even if the resulting data is rubbish. Again, look for clues in messages. >>>>> >>>>> - If that works, add the pfb_fir_real to your design but keep the >>>>> number of channels etc very small. >>>>> >>>>> >>>>> >>>>> Good luck and regards >>>>> >>>>> Andrew >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, Jan 20, 2025 at 1:47 PM Heystek Grobler <heystek...@gmail.com> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Good day everyone. >>>>> >>>>> >>>>> >>>>> I hope that you are doing well. >>>>> >>>>> >>>>> >>>>> I have a weird situation where Simulink get stuck while initialising >>>>> the simulation. The design is a narrowband spectrometer. I played around >>>>> with Simulink, and the simulation won’t initialise as soon as I add a >>>>> pfb_fir_real block and a fft_wideband_real block. If I comment out the >>>>> blocks, then the simulation initialises and runs. >>>>> >>>>> >>>>> >>>>> Has anyone stumbled across something like this? >>>>> >>>>> >>>>> >>>>> Thank you for the help. >>>>> >>>>> >>>>> >>>>> Heystek >>>>> >>>>> --------------------------------------------------------- >>>>> Heystek Grobler >>>>> >>>>> 0832721009 >>>>> heystek...@gmail.com >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "cas...@lists.berkeley.edu" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to casper+un...@lists.berkeley.edu. >>>>> To view this discussion visit >>>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/DU0P189MB249711A6177904F1B03636B3AAE72%40DU0P189MB2497.EURP189.PROD.OUTLOOK.COM >>>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/DU0P189MB249711A6177904F1B03636B3AAE72%40DU0P189MB2497.EURP189.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> >>>>> >>>>> *Disclaimer* >>>>> >>>>> The information contained in this communication from the sender is >>>>> confidential. It is intended solely for use by the recipient and others >>>>> authorized to receive it. If you are not the recipient, you are hereby >>>>> notified that any disclosure, copying, distribution or taking action in >>>>> relation of the contents of this information is strictly prohibited and >>>>> may >>>>> be unlawful. >>>>> >>>> >>>> >>>> *Disclaimer* >>>> >>>> The information contained in this communication from the sender is >>>> confidential. It is intended solely for use by the recipient and others >>>> authorized to receive it. If you are not the recipient, you are hereby >>>> notified that any disclosure, copying, distribution or taking action in >>>> relation of the contents of this information is strictly prohibited and may >>>> be unlawful. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "casper@lists.berkeley.edu" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to casper+unsubscr...@lists.berkeley.edu. >>> To view this discussion visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/3ae7009a-30a3-476b-b433-cf36d855a5den%40lists.berkeley.edu >>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/3ae7009a-30a3-476b-b433-cf36d855a5den%40lists.berkeley.edu?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "casper@lists.berkeley.edu" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to casper+unsubscr...@lists.berkeley.edu. >> To view this discussion visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAD560x%3DQRknR5nnkhVOUVAr_6s8fAxB0PUJ8FpBy0eqz_U4Z0A%40mail.gmail.com >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAD560x%3DQRknR5nnkhVOUVAr_6s8fAxB0PUJ8FpBy0eqz_U4Z0A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups " > casper@lists.berkeley.edu" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to casper+unsubscr...@lists.berkeley.edu. > To view this discussion visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACqpYn7d%3DVAXmEnuXTgmGNG0L2McC7UbNHxGBKHD-BFw64euzw%40mail.gmail.com > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACqpYn7d%3DVAXmEnuXTgmGNG0L2McC7UbNHxGBKHD-BFw64euzw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "casper@lists.berkeley.edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to casper+unsubscr...@lists.berkeley.edu. To view this discussion visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAD560xm0NP-jqov%3D3NRR3QG_4o9%3DfqYBv1Jqo_yjeUEAL1XAnw%40mail.gmail.com.
