I'm running Quartus Prime Lite 16.1 on Ubuntu 16.04 and I want to start using Models-Altera, but when I click on "Tools"->"Run simulation tool"->"RTL simulation" it shows me a pop up window saying that I need to point to my license (please see the picture attached), but before running the Quartus setup installation I specifically selected the Models free version.
I had a similar problem with Signal Tap Analyzer, also requesting pointing to a licence or some similar wording. Maybe the solution applies also for the RTL simulation.
The solution that worked for me was to go to the Tools->Options->internet connectivity and enable “talkback options”.
I had found the solution here: https://mil.ufl.edu/4712/docs/SignalTap_Tutorial.pdf
Related
It's been like a month since I started using VSCode and I like it.
However, The problem is the moment I launch the program the laptop's fans start to make relatively loud sounds so I thought because there were multiple programs running at once but after trying to launch VSCode alone the problem remains untacked.
Here's what I've tried so far:
Disabled the gpu accelartion.
Disabled all the built-in extensions except the Typescript & Javascript language features extension (I didn't install any additional extensions)
Tried clean install.
Nothing worked, But when I tried to disable Typescript & Javascript language features extension the fans started to cool down. I even checked the system monitor. The reading of CPU usage for VSCode before and after disabling the mentioned extension
It jumped from 0% to 28% to 30% to 16% and keeps bouncing between 9% and 16% for as long as the application is running.
I know it seems obvious to disable this extension and I'm good to go but I need it, I mean the whole point of me using VSCode is this extension. Did anyone run into the same problem or it's only me?
P.S: I'm using Ubuntu 18.04 LTS.
So after decades of research this guy's answer solved the problem.
All you have to do is to open VSCode then File > Preferences > Settings then type the following in the search bar typescript.disableAutomaticTypeAcquisition then check the checkbox and you're good to go.
However, autocomplete is not working for some imported packages so be aware of that.
Anyway, I opened an issue long time ago if anyone wants to follow any new updates about this topic here.
Go and give this guy's answer a thumbs up or love because he deserves it.
I'm tasked with upgrading a lot of legacy models and scripts made in an older version of Matlab/Simulink and have it running smoothly in R2018b. Among other requirements I'm not allowed to have any warnings issued upon execution of .m scripts or Simulink models. This is generally tedious but straightforward to comply.
However, there is a specific warning that Matlab does not give me hints on possible sources:
Warning: MATLAB has disabled some advanced graphics rendering features by switching to software OpenGL. For more information click here.
The link opens the Matlab Help page titled Resolving Low-Level Graphics Issues, which describes issues I'm not finding (or at least not noticing)
I do note that many scripts I run create and close figures, but this is done procedurally. I haven't been able to associate this warning with some specific function or feature. I'm working on a Windows Server machine.
Does anyone have an idea of how to narrow down which kind of function os Simulink block could cause this warning?
As datenwolf and Ander point out, the first thing to try is to update your drivers. If this doesn't work, and your only problem is that you're getting the warning but your graphics still render fine, then you have two other options to try.
First, you can simply modify your OpenGL rendering preferences using opengl. The following will set your preference to 'software' and save that setting for future sessions:
opengl('save', 'software');
Alternatively, you can just try to suppress that particular warning message. After you get the warning, issue this call to the warning function:
w = warning('query', 'last');
The w.identifier field will give you the ID for the warning message, which I believe will be 'MATLAB:hg:AutoSoftwareOpenGL' in this case. You can then add the following line to your startup.m file so that this warning is suppressed every time MATLAB is opened:
warning('off', 'MATLAB:hg:AutoSoftwareOpenGL');
Install the original vendor drivers for your GPU. The drivers that are installed by Windows by default lack full OpenGL support. Download the driver package directly from the website of Intel, AMD or NVidia, depending on what GPU you have.
If you don't have GPU, for example when running in a Virtual Machine, then you can not avoid that warning, because then Matlab has no other choice than falling back on the software OpenGL implementation that it ships with.
There's nothing you can do about that, other than making sure, that the system you're running Matlab on, does have proper OpenGL support!
It took me a long time to get it, so I'll put you here in case it helps how I managed to activate openGL in Linux:
If you haven't already (it's common for other problems), rename libstdc++ library from MATLAB:
mv _YOUR_MATLAB_ROOT_FOLDER_/sys/os/glnxa64/libstdc++.so.6 _YOUR_MATLAB_ROOT_FOLDER_/sys/os/glnxa64/libstdc++.so.6.bak
Create this link: sudo ln -s /usr/lib/x86_64-linux-gnu/dri/ /usr/lib/
Run export MESA_LOADER_DRIVER_OVERRIDE=YOUR_DRI_DRIVER;matlab -desktop -nosoftwareopeng
Your DRI Driver will be a file from /usr/lib/dri, removing "_dri" (in my case was the "radeons" driver for an AMD Vega graphic card.
Run MATLAB from a terminal using: export MESA_LOADER_DRIVER_OVERRIDE=_YOUR_DRIVER_HERE_;matlab -desktop -nosoftwareopengl. YOUR_DRIVER_HERE should be your driver, radeonsi in my case.
Check openGL with info = rendererinfo
If something went wrong, you will be able to see in the terminal which library was responsible. Executing 4) and 5) I was discovering what I had to correct, you can do the same if you have another problem that has not appeared to me.
So that it always runs correctly I put export MESA_LOADER_DRIVER_OVERRIDE=YOUR_DRI_DRIVER at the beginning of the script that runs matlab (_YOUR_MATLAB_FOLDER/bin/matlab), although I suppose it can also be set as an environment variable.
I hope this has been useful to you.
I am new here but I hope you can help me to find a solution to my problem.
I have four PIGRRL Kit from Adafruit and I need to install in it Raspbian (Operating System), the PiTFT and the gamepad as shown here (https://learn.adafruit.com/pigrrl-2/software).
But, when I try to install the gamepad, the OS goes in loop and the only way to exit it is to restart everything. I have checked if there were some problems with the soldering, but the voltage machine is not showing me any problem of the kind. The problem is just on the gamepad, because at the PITFT installation step everything goes fine and works.
But when I install the gamepad it goes in loop.
I used these commands:
cd
curl -O https://raw.githubusercontent.com/adafruit/Raspberry-Pi-Installer-Scripts/master/retrogame.sh
sudo bash retrogame.sh
And then I follow the instructions for PIGRRL 2.0. But when I reboot, the OS loops.
Any idea or suggestion?
Thanks anyway!
I didn't tried retrogame, but I'm trying to use PiTFT 28 capacitive.
What I can say is that have some troubles with the display :).
In the first time I follow exactly they procedure and made my software work perfectly. But at some point in time it started to reboot after starting the software.
So I tried to start all over again, but this time I used Diet Pi and follow an alternative solution. I follow the procedure on this page: http://www.0xf8.org/2016/01/complete-rotation-support-for-the-adafruit-pitft-2-8-capacitive-touchscreen-display/
The display works, but:
1. If I use other console font, it starting immediately the font is going active.
2. The mouse don't work so well, it seems to start all the time in the left corner. So I didn't manage this part. :).
Maybe my answer can be useful in the combination of your experience.
Bafta
I found a solution. The problem for me was solved by charging the batteries. Basically, when it first reboots the OS needs more energy and with no charged batteries it went in loop.
All the best!
I'm having a problem with the built-in help/documentation within MATLAB 2013a (issue also present in 2012b).
Upon opening the help files the pages appear with no formatting, only plain text. Search results do appear correctly though.
I have found only one instance of someone else with this issue, on MATLAB central here. However, there are no responses to the author's question. The issue I'm having is exactly the same as described there.
I have tried removing the preference folder and relaunching MATLAB but this doesn't help.
I'm using Windows 8.1 and MATLAB 2013a.
Any help or suggestions on how to fix this would be very much appreciated.
Edit:
Thank you everyone for the feedback so far. I don't believe java to be the issue, I have the latest version installed (1.7.0_45) while MATLAB uses it's own version (1.6.0_17). Both of which co-exist on my machine.
Following horchler's thread led me to another semi-related bug report here. The following code is listed at the bottom of the workaround (the script attached to the workaround didn't fix anything unfortunately).
com.mathworks.mlwidgets.html.HtmlComponentFactory.setDefaultType('HTMLRENDERER');
This results in a degraded appearance of documentation pages and loss of some functionality but is still an improvement over the plain text and scrambled pages.
Hopefully from this new information we can work towards a solution!
One solution is to go back to IE-10, or to use the patch on http://www.mathworks.com/support/bugreports/989850
Which basically replaces the localnav.js at <MATLAB>/help/includes/product/scripts
The link to download!
This is an old post, but I had the same issue and have a fix (not downloading R2013b or java related). Just downgrade from IE 11 to 10: Go to System (or System & Security)->Windows Update->View Update History->Installed Updates -> Find IE11 and uninstall it. Your system should revert back to the prior installed version. This fixed the help issues.
The problem is related to Internet Explorer 11, which MATLAB uses to render its help files. I was experiencing this problem in Windows 7 and rolling back to IE 10 fixed it right up. Unfortunately, that's not an option with Windows 8.
(Running MATLAB 8.1.0.604 (R2013a), Mac OS 10.8.3)
When I use the doc command, for example, doc fwrite;, or when I click the "more help" item in the popup help bubble for a command, the documentation window opens, but MATLAB subsequently hangs (the spinning beachball appears). This lasts indefinitely, and I inevitably have to force quit MATLAB. This also happens when using the Publish option from the editor.
Anyone have any ideas for diagnosing this? I tried taking a process sample but I didn't see any info I could interpret, I think since it's in Java the relevant information is obfuscated behind the JVM.
See this post on MatlabCentral: http://www.mathworks.com/matlabcentral/answers/71718 ... and more specifically this bug report which includes a "workaround." They don't suggest what could be the cause, but you might make sure that OS X is updated and that you have the latest version of Java. If you do other work with Java or with WebKit these might cause issues.
I hope you have already solved the problem. Otherwise a solution has been found, the bug resides in the Access for Assistive devices (only for version 2012b and later). If you can turn them all off from System Preferences, do that. If you can't, type this in the command window:
com.mathworks.mlwidgets.html.HtmlComponentFactory.setBrowserProperty('JxBrowser.BrowserType','Mozilla15');
From http://www.mathworks.com/support/bugreports/870843
I had the same problem with Matlab R2014a on OS 10.10.4. For me the solution involved disabling Cinch (a window management tool I had installed). This can be done by clicking on the Cinch icon in the menu bar then Disable Cinch, or from System Preferences > Security and Privacy > Accessibility (as MarcoB detailed in his answer).
More suitable as comments (but I don't have enough rep yet):
I just updated to Java 1.8.0_73 and to Safari 9.1 and the patch horchler posted no longer works.
MarcoB's command still works for fixing the crashes. But with this, no longer retina resolution in the Doc browser (so it looks ugly).