Jumping in on this rather late, but I've just been reminded that there's
also an issue with clashing MATLAB/Simulink toolboxes that can cause issues
with sysgen. The third comment from the bottom of this
<https://adaptivesupport.amd.com/s/question/0D52E00006vF6FOSA0/model-composer-v20212-matlab-r2021a-gets-stuck-at-initialization-stage-on-ubuntu-20041?language=en_US>
support
post has a list of known compatible toolboxes.

From what I've seen, clashes tend to be from anything involving some
library's Simulink toolbox. I imagine that under the hood these things
don't necessarily all play nicely, and it's worse with sysgen given that it
also has to interact with Vivado in the background.  Not sure that's
necessarily the case here, considering you've managed to compile the design
previously. But it may be worth mentioning in case you've recently found
yourself with a new set of toolboxes.

Even with compatible toolboxes, I've faced this issue quite a bit myself. I
have an slx file that just flat out doesn't making it past sysgen
generation at all anymore. Others will hang when just updating the design
in Simulink - I've noticed this happens when I add in new sysgen library
blocks, and it's really hit or miss as to whether it works after restarting
things.

As with Mitch, sorry I don't have a better answer either. But if anyone
ever does manage to get to the bottom of this, please let us know.

Morag

On Sat, Sep 28, 2024 at 12:24 AM Mitchell Burnett <mitch.c.burn...@gmail.com>
wrote:

> Hi Ken,I am not sure anyone understands this problem. Once upon a time, I
> thought it was a race condition between System Generator and Simulink. I
> tried to debug it by changing some of the MATLAB Java Runtime parameters
> and hooking into the JRE to watch what processes it was
> runn ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>
> <https://report.mimecastcybergraph.com?magiclink=https%3A%2F%2Fapi.services.mimecast.com%2Foauth2%2Fauthorize%3Fresponse_type%3Dcode%26client_id%3Do20nRkVXf7VUVnANkXhoOwGytEwGN0YAlyeDJn7oBTGNl2kN%26state%3DeyJhbGciOiJSU0EtT0FFUC0yNTYiLCJlbmMiOiJBMjU2R0NNIn0.IshHFYhChK_5_GNa1KcipRYFi2hPZjQMYzFsZqz2dJ71A0ZpvtDK9QX88DkarY_WgQupnLImAZTOIBo6husC24rDtnPUjc87ivp9MTWPBtXxWxhnJcWOq17hoXRrvG0zviP1AWs0lYAabDVW9W0R3eC3qoInt5Pug1ZCWSJthOiI7ptXQe4basdH9SPOQEFx7D5dR5zLAvCCYNYX7V1QZsKFVAFYIC-70_uhNnSUd2UxWAAWrrdF2WesQ007uVvItMuyhhq95904FweVxbh5yEbWg2Bwrs9zG8zqAQOh2gU65IdgaaYir4V9HjsP9js_wFBjzuCei44AP1z3-DR0eQ.9mpuRNxA70hp-UZY.OUoMJYj0SpXIQXQ3KRBkTceH2k-JXrjGIRyl0_VsL-HHvhoqanz_KDS3gFPg-CcVhn_TbjUbG5tGdkqXwRJs-mAjmWWG3UykiEfoUzj7Heic2NH1KG2xK6esjYXum15H0Q2vvmUp_QXmLgUV3Gc-J6lu2LawGXH1rfR67zi3itRAnBuMVk7b2qkPPpXBtmfKQK64B__DxKjlTazXnrOg6dL05a9eft-cTuEbomkGBt1lXox5i_7S92xvTmthSdtPZE30sT8UXwTp9zVSNZ2Hira7Xr4GI2xCHWWf3UAf9owOc997RCWmBeyD1HB-1IysLF9U15yq5jE5npuD7NvyQ5MFYSmUAL005BitZJpm1McTJbKdknL5IPaHFy4NQ5djNdo_aopSg1bBwuwlvINFdePvEzwCFC5k1XIlpFLS9Y0M8x61jThf9PQ_P1yyu5Lq8yn6QAw4347zfS63m1VWVv5WIu7lrlHpQfs-s6FkQpt8ErPwFAtU9EjdJZMvEgxR79gzLLf6eZbUWiIUJhQids9mVobZQh_JFA-DDPVadbK5fj_gHAst4Jdrb1Ps4a7jyFtCpqXvYXmcv-feTv1TqrNlXND3blvtp1BdH77fgxh8XvDijwss8ITbDgwQV9zt7mLg_GHYSI_bLW2EsuIfZMV7k1ROiRE_8pBBM9rP8IUJ8dd_mi95aj93X-xwV6wv1eNYxEvXfN0pvii8tPuL8mtcphXNvDNSoFNKw86ltfGwYhonFEfZkObW3LIqGY1fWPdXu0O7UaVXQJqWSSviPfUPTiXZXfRcAcvhNN98u7zwVDIE.4GaibfWle2sFReljE1MHGA%26redirect_uri%3Dhttps%3A%2F%2Freport.mimecastcybergraph.com%2Fcallback>
> CGBANNERINDICATOR
> Hi Ken,
>
> I am not sure anyone understands this problem. Once upon a time, I thought
> it was a race condition between System Generator and Simulink. I tried to
> debug it by changing some of the MATLAB Java Runtime parameters and hooking
> into the JRE to watch what processes it was running, and see if anything
> stood out. I didn’t have much luck then. It did look like Simulink was
> waiting for a return value. I have since chalked it up to a race condition
> and that Simulink just misses the return value. You could be right that it
> never makes it back because it silently crashes. I am not sure either how
> to look at System Generator as a process.
>
> Every time I have tried, I can hit the “cancel” button on the bottom of
> the Simulink canvas and then repeatedly spam an interrupt to in the
> terminal used to launch MATLAB and the interrupt is caught and returns
> back. Although, I have more luck at that point restarting MATLAB/Simulink
> entirely rather than starting a fresh compile. It just seems to happen
> again too often without the restart. Wish I had a better answer for you.
>
> Mitch
>
> On Sep 27, 2024, at 2:49 PM, Ken Semanov <shapkiqua...@gmail.com> wrote:
>
> This problem is not resolved by the cache cleaning.  A rumor is that this
> is caused by System Generator silently crashing, which results in the
> Compilation status popup waiting eternally for it. Does anyone know how to
> see System Generator as a process  (e.g. in  ps aux? )
> On Wednesday, September 18, 2024 at 7:38:52 PM UTC-4 Ken Semanov wrote:
>
>> This is an issue of the System Generator. Removing the cache relieves the
>> problem.
>>
>> On Wednesday, September 18, 2024 at 7:01:04 PM UTC-4 Ken Semanov wrote:
>>
>>> Anyone have troubleshooting tips for when Jasper compiles hangs at this
>>> stage?
>>>
>>> [image: Screenshot-20240918-180618.png]
>>>
>>> I have already tried the following continuously for 90 minutes on
>>> several different slx models. While these "fixes" used to work in the past,
>>> they no longer work now.
>>>
>>>    - Restart MATLAB, reload model, compile.
>>>    - Simulate the model first, save, then compile.
>>>    - Reboot the computer.
>>>    - Simulate the model for 1000 steps. Save slx. Close MATLAB, Open
>>>    MATLAB. Reopen the model. Compile
>>>    - Close model. Delete proj/proj/sysgen/ip_catalog/proj.cache/*
>>>    Reopen model. Compile.
>>>
>>> I have compiled this SLX  model many times in the past. I have moved the
>>> slx file into a fresh new directory before generating the following logs.
>>>
>>> jasper.log   at  https://bpa.st/KBYAA
>>> <https://bpa.st/KBYAA>
>>>
>>> vivado.log at https://bpa.st/ICB52
>>> <https://bpa.st/ICB52>
>>>
>>> The files generated before system generator begins to hang , at
>>> https://bpa.st/5ZT7A
>>> <https://bpa.st/5ZT7A>
>>>
>>>
> --
> 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 on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ecc53875-558a-4e89-a6de-7fd45e063950n%40lists.berkeley.edu
> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ecc53875-558a-4e89-a6de-7fd45e063950n%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 on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6D7AC189-3F38-4B94-9D35-0AB8DF06CD65%40gmail.com
> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6D7AC189-3F38-4B94-9D35-0AB8DF06CD65%40gmail.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.

-- 
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 on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TfnQPu%2BsuMjad_Eak%2BUKYVE_ZEsn4u6zHbGwBNAUgvVrw%40mail.gmail.com.

Reply via email to