21.1.1 standard issues resolved, where to find the details?

[AEsqu]

Hello,

The website mentions that these customer requests have been fixed in quartus prime standard 21.1.1,

Is it possible to check the details of them?

https://www.intel.com/content/www/us/en/docs/programmable/683593/21-1-1/software-issues-resolved.html

00501636

00689611

00675753

00693884

Kind Regards,

Alex.

[SyafieqS]

Hi Alex,

Is it not possible to check all of them, but I can help to show few which you are interested to

[AEsqu]

Yes,

I just would like to know what the fixes are for the 4 above,

to see if that can impact my project.

Alex.

[SyafieqS]

Understood. Let me check and get back to you for below issue.

00501636

00689611

00675753

00693884

[SyafieqS]

Hi Alex,

Apologize for the longer time to response.

00501636

- In NIOS II Library Makefile the adjust-path and adjust-path-mixed functions do not handle relative paths correctly under WIndows WSL - fixed

00689611

-Intel Arria 10/Cyclone 10 Hard IP for PCI Express, Avalon-MM mode with Avalon-MM Address Width of 32-bit. Size of address pages is missing 17 to 21 bit sizes, - fixed

00675753

- Error Message Register Unloader IP cannot be generated in Quartus 21.1 Std -fixed

00693884

Root Cause: Unsupported command in hw.tcl file for the IP;

Solution: Patch 0.08std for Quartus 21.1std removes unsupported construct from hw.tcl;

https://www.intel.com/content/www/us/en/support/programmable/articles/000090380.html

This problem is tracked down to an out-of-date TCL command in the EMR unloader IP:

quartus.21.1.0-b842-ww49\ip\altera\pgm\altera_emr_unloader\altera_emr_unloader_core2\emr_unloader_core_hw.tcl:34:    add_fileset_file $sdc_file SDC_ENTITY PATH $sdc_file

{NO_AUTO_INSTANCE_DISCOVERY NO_SDC_PROMOTION}

This command seems to be invalid in this version of Quartus. It should instead be:

add_fileset_file $sdc_file SDC PATH $sdc_file

[AEsqu]

Thank You for the information!

[SyafieqS]

I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.

p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution and give Kudos.