Any new about the NIOS II toolchain roadmap?
In Q19.1 Std Eclipse is completely broken with Windows 10, there are a lot of video artifacts during debug that make the screen unreadable. I would like to see an updated version of Eclipse supported with the the Nios plugin.
May I know the information as below:
- Do you have follow the installation steps in chapter 2.1 as link below: https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/hb/nios2/n2sw_nii5v2gen2.pd...
- May I know the error message?
1) Yes I followed that instructions
2) There is no error message but the screen is not redrawn correctly and I can't properly see the buttons on the bottom (ex. to switch from the Debug log to the Console)
I am on a 4K monitor, using High DPI scaling override "System Enhanced"
I am trying to install the Quartus Prime Standard v19.1 and try to duplicate the defect.
Please allow me to have some time to install to test on the system.
In the meantime, could you provide me the display resolution information?
It is a 4K monitors graphic problem for Quartus Prime software in Window 10.
I had just found that the developer had known this issue and plan to solve in future.
Unfortunately, the only workaround is downscaling to 1080.
I found another bug, Eclipse is not detecting the System ID, a 0 or "Not found" is displayed when analyzing the target connection (see attached picture).
Using system-console I can read the right data at the system id MM address
Using Nios II Hardware v2 (beta) configuration seem to fix the issue (only some times). but this is very bad!
Today I even found another bug with TimeQuest. If there is an error in the SDC file and you Create the netlist from the GUI the first time you get a message, the second time everything crash!
I'm experiencing a lot of bugs with this new Q19.1 std, should Intel hire me to improve Quartus?
Adding another bug...
When creating a project with BSP in Eclipse the project doesn't reference the BSP and the intellisense is broken (show include errors, etc..)
Another bug that apply to 19.1 std (windows) as well