Occasional Contributor
Occasional ContributorHello @sstrell ,
Thank you for your response and continuous support.
I do not think that relative path is an issue here because of following reasons:
(1) Please refer following image. It states we can either use absolute or relative path.
(2) Note that if we use 'user_component.ipx' file method I described in initial post, there is no issue. RTL files are generated properly when Qsys system is generated. Hence, I think file path is fine.
What do you think?
Have a Nice Day!
Kind Regards,
Bhaumik
Super ContributorHave you tried the absolute path? This may be a bug that does not follow the documentation. I've seen it happen.
Your .ipx solution is fine, but it's extra work you shouldn't have to do to make the IP visible.
Occasional ContributorHello @sstrell ,
Sorry for delayed response. And thank you for your response.
I have tried absolute path. Please have a look at following:
add_fileset_file ./sls_i2c_mstr/i2cc_wrapper.sv SYSTEM_VERILOG PATH "E:/designs/sls/i_i2cc/trunk/master/software/setup/resources/i2c_mstr/hardware/component/hdl/i2cc_wrapper.sv" TOP_LEVEL_FILE add_fileset_file ./sls_i2c_mstr/i2cc_user_define.pkg.sv SYSTEM_VERILOG PATH "E:/designs/sls/i_i2cc/trunk/master/software/setup/resources/i2c_mstr/hardware/component/hdl/i2cc_user_define.pkg.sv" add_fileset_file ./sls_i2c_mstr/i2cc_dp_ram_mf.v VERILOG PATH "E:/designs/sls/i_i2cc/trunk/master/software/setup/resources/i2c_mstr/hardware/component/hdl/i2cc_dp_ram_mf.v"
But unfortunately it didn't help.
I have attached herewith one text file which shows messages which are generated by Qsys when we refresh system. See whether this gives any clue or not.
Thank you,
Bhaumik
Occasional ContributorHas a solution to this been found? I am having the same problem. I am using Quartus Prime Standard Edition version 21.1. I am creating components using the component editor, moving them, then adding them to the IP Search Directory. They appear in the IP Catalog outside of Platform Designer, but they do not appear inside of Platform Designer.
Existing instantiations of those IP in Platform Designer before the files were moved can not find the files and will throw the error: "Component type <component_name> is not in the library"
However, it does work when you specify a search path in Platform Designer (Tools ➤ Options). I specified the folder containing subdirectories containing my _hw.tcl files. They then appear under the "Library" section of the IP Catalog in Platform Designer.
I believe this might be correct behavior as section 1.11 (Upgrading Outdated IP Components) of the Platform Designer Standard Edition User Guide (v18.1) mentions the following, "If a Platform Designer system includes IP components outside of the project directory or the directory of the .qsys file, you must add the location of these components to the Platform Designer IP Search Path (Tools ➤ Options)." However, this was not mentioned, referenced or placed conveniently in the sections talking about importing IP. The only thing listed that mention adding files to the Platform Designer IP Paths was under section 1.5.3.2. (Defining the IP Search Path with Index Files). However, even this gave an option of using Quartus Primes' or Platform Designer's IP Search Path settings. Additionally, this section was specifically about Index files, not about _hw.tcl files.
However, I could be wrong about all of this. What is the correct behavior? Must you specify the path of all IP used in Platform Designer using Platform Designer's IP Search Path. Is using Quartus Primes IP Search Path acceptable and this is a bug? Are .IPX files supposed to be specified using Quartus Primes Search Path and _hw.tcl files specified with Platform Designer's? If so, why so?
