Qsys new component - file path keeps changing

I'm also having path problems with Qsys.

I have a QSYS SOPC system initially generated under Quartus 11.X (sp?).

There were problems with the hard PCIe core burst logic under Q11.X so when Quartus 12.0 came out I transferred to that and

everything appeared to work well.

Now I have another logic module to add to my QSYS system but it looks like Q12.0 qsys can't read Q11.X qsys files properly, it's totally

****ed up source file path names (I keep my source in a separate directory), it doesn't even select the top level file properly (even though

this is specified in the *.qsys file).

I'm going to have to start from scratch with a fairly complex system. :-(

Have you changed Quartus versions at all?

Nial

Hi!

I am facing same issues in QSYS 12.1 (SP1). File paths in Component Editor's "Synthesis Files" list change after selecting the specific source files (in my case 4 Verilog files). The wizard automatically adds additional folders in between.

e.g 3C25/fpga_src/subf/xx1.v changes to 3C25/3C25/fpga_src/subf/xx1.v

Adding another file adds another level to the first added file path: 3C25/3C25/3C25/fpga_src/subf/xx1.v

Same a GZoinker, my source files are located in a separate directory rather than the main .qsys System file.

I have also seen this behavior on earlier versions (12.0, 12.1).

Any ideas why this happens? When finishing the Component Editor, QSYS wants to access the wrong paths, which does not work since they do not exist.

Thanks!

EDIT: Workaround could be to manually edit paths in the xxx_hw.tcl file of the component. Then open again the Component Editor and continue to create the component.

It turned out that at least module name (tab1) should be identical to top level module name (tab2). Maybe either description below should be equal to module name either.

This unbelievably bad for a tool that we're supposed to be using to earn a living, you'd wonder how much

testing has been done before release?

COME ON ALTERA, THIS ISN'T GOOD ENOUGH.

Nial

I'm having the same problem too. The Qsys 'details' dialog box shows the right path, but the component editor wouldn't allow me to change the faulty path regardless how many times i try.

I solved it by deleting the tcl, and remaking the component. Not a novel workaround perhaps? but there's nothing else i can do.

--- Quote Start ---

I'm having the same problem too. The Qsys 'details' dialog box shows the right path, but the component editor wouldn't allow me to change the faulty path regardless how many times i try.

I solved it by deleting the tcl, and remaking the component. Not a novel workaround perhaps? but there's nothing else i can do.

--- Quote End ---

Qsys Component editor gave me a lot of trouble.

The workaround that I am using right now is fairly simple until they fix the bug.

I use SOPC builder component editor. It is easier than the one in Qsys. My file system looks like this (A qsys subsystem that needs to integrate a custom component )

/Qsys_subsystem_alphaQsys_subsystem_alpha.qsys

Custom_component_hdl/

custom_component_top.vhd

custom_component_hw.tcl

When you open the subsystem with Qsys it will display the custom component and you can add it to your design. the _hw.tcl file is made by SOPC builder. It works for components with multiple synth files

I was hired as a consultant to help get a company out of this kind of mess (in 11.1). They were using component editor to create their own components. Finally, since all confidence was lost in this tool, and given the statement by one of their gurus that component editor was meant to just get the user started, I decided to isolate the design from the Qsys environment by adding a bridge to export the avalon bus signals. This way the user components simply hook up to the inteface outside of Qsys. You can put a separate bridge for each user component to keep things nice. The only issue is you have to add the base addresses to your C code since it won't be done by qsys.

Good luck.

--- Quote Start ---

I was hired as a consultant to help get a company out of this kind of mess (in 11.1). They were using component editor to create their own components. Finally, since all confidence was lost in this tool, and given the statement by one of their gurus that component editor was meant to just get the user started, I decided to isolate the design from the Qsys environment by adding a bridge to export the avalon bus signals. This way the user components simply hook up to the inteface outside of Qsys. You can put a separate bridge for each user component to keep things nice. The only issue is you have to add the base addresses to your C code since it won't be done by qsys.

Good luck.

--- Quote End ---

Interesting but it will be followed by a tidy work aligning data/address of your custom component with your bus. It might be feasible for Memory Mapped connection but it is certainly tricky for Avalon-ST connections. Giving that timing adapters are "freely" provided by Qsys.

Qsys is a good tool in general (one should not focus with only one aspect that failed), not yet mature and I am sure it will be better in newer versions of Altera design tools.

I managed to incorporate a custom JPEG encoder in a Qsys subsystem. I created the (_hw.tcl) file with SOPC builder. Then I added the folder that has the RTL and TCL files under the subsystem path. Qsys recognized the tcl file and displays the component in the top left among other components. I tested it and it worked.

--- Quote Start ---

Interesting but it will be followed by a tidy work aligning data/address of your custom component with your bus. It might be feasible for Memory Mapped connection but it is certainly tricky for Avalon-ST connections. Giving that timing adapters are "freely" provided by Qsys.

Qsys is a good tool in general (one should not focus with only one aspect that failed), not yet mature and I am sure it will be better in newer versions of Altera design tools.

I managed to incorporate a custom JPEG encoder in a Qsys subsystem. I created the (_hw.tcl) file with SOPC builder. Then I added the folder that has the RTL and TCL files under the subsystem path. Qsys recognized the tcl file and displays the component in the top left among other components. I tested it and it worked.

--- Quote End ---

I've worked on a couple of SOPC systems and although I thought it was really powerful, the setbacks due to GUI issues really leaves me feeling like looking for alternatives. The last system used their Ethernet MAC. Our stuff resides outside QSYS and inside is the MAC with the necessary ST modules and signals, which eventually get exported to our modules. You're doing well by working in only the TCL and HDL files. Its is a good idea as long as you have the knowledge and keep it fresh in your mind. I have to leave this design in another companies hands and staying away from the internal workings of Qsys has been working well.

Cheers