-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What to expect from these scripts #18
Comments
Hi @duaneellissd, This is not expected behavior. |
Liberia 2022.1 on windows |
Yes using the scripts |
Ok, I don't think the scripts are part of the problem but could you try it with the release scripts for Libero 2022.1 instead of the scripts on main as they are for Libero 2022.2. I think the issue will happen anyway but the more information we can get to try and fix it the better. |
i do not have access to every version of libero and i am not allowed to download anything i want like that (fireable offense) you i believe work for microsemi and have access to anything |
Apologies, the only reason I asked was because you said you we're using Libero 2022.1 above. |
So I saw this happen on Ubuntu, while I was running a build so I ran out of memory and got a segment fault. Libero does require a minimum of 16Gb of memory which explains why mine crashed, running multiple builds of a project. if possible could you try rebooting your machine and re-running the libero script again to see if it crashes. I'll get in contact with some people internally so see if this is expect behavior or not. |
simple solution set up about an 8gig swap space |
so I run the script, specifically I am running the script: PF_Eval_Kit_MIV_RV32_BaseDesign.tcl, with "CFG3" as the parameter.
It runs, then "POOF" - Libero closes - sort of as if the application crashed.
That is jaring and not expected.
I don't know if(A) that is expected, or (B) if something has gone horribly wrong.
Suggestions:
a) if this is intended operation, document this in the user manual.
b) think about putting popping up a dialog box of some type, ie: "SUCCESS, CLICK OK TO EXIT"
c) Write "SUCCESS" to a log file and tell your victim (ie: somebody like me) where to find the log file.
You might know where that log file is - but I sure do not.
The text was updated successfully, but these errors were encountered: