Community
cancel
Showing results for 
Search instead for 
Did you mean: 
dns13
Novice
516 Views

alftp components missing in altera_mf_components on Quartus 20.1

I've recently updated from 18.1 Lite to 20.1 Lite and now my build is failing as all altfp components are missing in the declaration file.

I haven't found anything about deprecation of this use. Do I need to compile this megafunctions by myself or can I define them in every file? Is there another workaround?

What's the recommended way to use those megafunctions? I like the use with a USE statement more than generating every megafunction, this way I have all informations I need in the corresponding *.vhd-file instead of an extra folder with compiled megafunctions I need to update and keep an eye of breaking things when multiple IPs are using the same compiled megafunction.

Thanks for your help

Jan

16 Replies
502 Views

Hi Jan,


Could you share the design for investigation?


Thanks.

Best regards,

KhaiY


dns13
Novice
500 Views

Hi KhaiY,

I've attached a component (and the used component "st_driver") that's failing compilation on 20.1 with "Error (10482): VHDL error at measure_trigger_time.vhd(75): object "altfp_div" is used but not declared". It worked completely fine with 18.1 as it is.

When I check the library file under "<quartus install dir>/libraries/vhdl/altera_mf/altera_mf_components.vhd" all altfp_* declarations are missing - they are present in the 18.1 version of this file. I could do the component declaration in each file for my own, but I think that's not how it's supposed to be.

Thanks
Jan

dns13
Novice
485 Views

The issue seems to lay deeper:

  • Just creating a new library with all the altfp_* component declarations from 18.1 failed with component not found
  • Then I tried to use the megafunction compiler to create the used megafunctions. This worked for altfp_div, but alftp_convert just creates an empty *.qip file with not even opening the MegaWizard, failed with "Error (14736): Error: Wizard "ALTFP_CONVERT" cannot be launched."
  • Reinstalling Quartus 20.1 did not help
479 Views

Hi,


Could you share the design.qar that includes the Quartus project/settings file, qip/qsys, etc? To generate the QAR file, click on Project > Archive Project > Archive.


Thanks.

Best regards,

KhaiY


dns13
Novice
469 Views

Hi KhaiY,

I've created a test project and archived it as my main project is kind of huge and includes internas.

Thanks,

Jan

461 Views

Hi Jan,


I can reproduce the error here and I will file a case to our engineering team for investigation.


Thanks

Best regards,

KhaiY


dns13
Novice
459 Views

Hi KhaiY,

thanks.

Greetings

Jan

434 Views

Hi Jan,


I received the reply from the team, you may create altera_fp_function in version 18.1 and use that instance in version 20.1. In v18.1, a qip file is also generated which will list all the generated files you need to include in your v20.1 project.


Thanks.

Best regards,

KhaiY


421 Views

Hi,

We do not receive any response from you to the previous question/reply/answer that I have provided. This thread will be transitioned 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

Best regards,

KhaiY


JHill1
Novice
322 Views

JHill1
Novice
314 Views

My use case is that my VHDL component's port has a fixed fractional width generic which cascades to a generic passed to the alt_fpconvert VHDL component's port. So my complaint is that functionality that worked in the past, and is described in the 2020 version of the manual, no longer works, and we are wedged by Intel when trying to migrate our code base in-between versions. This generics passing down functionality isn't supported by the wizard, assuming of course that the wizard was even working in 20 and or 19, which it isn't.

Furthermore, what is really frustrating is such problems with the FP library exist, and users are documenting them, but they continue to persist year after year.

JHill1
Novice
306 Views

One possibility is that the floating point IP VHDL component declarations are included in the "pro" quartus and not in the "standard" 19 and 20 quartus I have installed? The per-mutated mix of language, compiler, and device features in the new three tier licensing _is_ a little bit complicated. So perhaps the floating point IP are available only on select recent device families along with full VHDL 2008 fixed/floating point library support included in quartus "pro"?

JHill1
Novice
294 Views

 

Searching in the 19.1 and 20.1 "standard" I do see some snippets indicating that support for some of the altfp_xxxx ip might be at least partially embedded therein.

./quartus/libraries/megafunctions/xml_info/altfp_convert_wiz_map.xml:5: <WIZARD_MAP NAME="ALTFP_CONVERT" WIZARD_NAME="ALTFP_CONVERT" MODULE_NAME="altfp_convert" >

 

JHill1
Novice
290 Views

And this is the error in quartus when we try to run the wizard.

Info (14738): Fatal Error: The file altfp_convert_info.xml does not exist or cannot be read
Error (14736): Error: Wizard "ALTFP_CONVERT" cannot be launched.

JHill1
Novice
288 Views

$ ls /ade/fpga/altera/19.1/quartus/libraries/megafunctions/xml_info/altfp*info.xml
ls: cannot access /ade/fpga/altera/19.1/quartus/libraries/megafunctions/xml_info/altfp*info.xml: No such file or directory
$ ls /ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp*info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_abs_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_add_sub_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_atan_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_compare_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_convert_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_div_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_exp_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_inv_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_inv_sqrt_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_log_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_matrix_inv_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_matrix_mult_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_mult_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_sincos_info.xml
/ade/fpga/altera/17.1/quartus/libraries/megafunctions/xml_info/altfp_sqrt_info.xml

TomMiddleton
Beginner
148 Views

Is there any resolution to this other than use the ones from 18.1? I've found I cannot even open the MegaWizard for the IP that won't upgrade (ALTFP_MULT and ALTFP_CONVERT) that bails out without notice only leaving an "iplauncher_debug.log" file with the line "Fatal Error: The file altfp_mult_info.xml does not exist or cannot be read" It isn't clear from your answers, is this just an Intel " is not going to fix" thing?

Reply