importing a partition

--- Quote Start ---

I am sub-compiling and logic locking a module. The source files are all called using relative paths.

When I run the top level compile I get an error in the assembler stage indicating that it cannot find the relative paths of the sub-compiled module.

The build still runs and generates the correct rbf file, but the sof file is not generated.

Since the sub-compile and the top-level compile are in different folders, the sub-compile relative paths would not make sense in the top-level directory.

In the top-level .qsf I provided the relative paths to the sub-compile source files, but it still seems to be using relative paths from the sub-compiled build.

Hopefully this make sense .. anyone know how to get around this.

thanks

--- Quote End ---

Hi flipper,

I do not understand what you are trying to achieve. As far as I know you can't generated sof-files for the Toplevel and the Sublevel , combine them and programm the FPGA. I never heard of that.

Of course you can run the Subdesign in a separate project. You have to define a design partition and a LockLock region. After succesful P&R you have to export the design as design partition. In the Toplevel project you have to define your sublevel design also as design partition. I have a small example project attached.

Kind regards

GPK

I am only trying to generate a SOF file for the top level.

In the assembler step, I see an error indicating that it cannot find a couple files.

The files use relatives paths from the subcompile directory. Since I am building the top level in a separate directory these relative paths generate errors.

It looks as if when importing the partition, some of the paths are used in the top_level compile instead of just using the .qxp

thanks

--- Quote Start ---

I am only trying to generate a SOF file for the top level.

In the assembler step, I see an error indicating that it cannot find a couple files.

The files use relatives paths from the subcompile directory. Since I am building the top level in a separate directory these relative paths generate errors.

It looks as if when importing the partition, some of the paths are used in the top_level compile instead of just using the .qxp

thanks

--- Quote End ---

Hi Flipper,

how did you import the partition ?

Kind regards

GPK

Are the files in the error message related to encrypted IP source files? In 8.1 and lower, Quartus II would look for the source encrypted IP files to find the license info for the IP. The license info would be required to generate a .sof, since IP doesn't support programming unless it is licensed.

In 9.0 the search for Ip source files shouldn't happen, so you could try in recently-released version 9.0 if you think this might be the problem...

--- Quote Start ---

Are the files in the error message related to encrypted IP source files? In 8.1 and lower, Quartus II would look for the source encrypted IP files to find the license info for the IP. The license info would be required to generate a .sof, since IP doesn't support programming unless it is licensed.

In 9.0 the search for Ip source files shouldn't happen, so you could try in recently-released version 9.0 if you think this might be the problem...

--- Quote End ---

Yes, the sub-compiled partition is encrypted source files. I'll run it on 9.0 ans see if teh problem persists.

thanks

--- Quote Start ---

Yes, the sub-compiled partition is encrypted source files. I'll run it on 9.0 ans see if teh problem persists.

thanks

--- Quote End ---

I had the same problem with 9.0

Here is the response from Quartus tech support

////

Proper license information is required to compile encrypted IP cores. The license assignment is imported in to the top-level project when a design is imported as a .qxp file. However, the license assignment contains an absolute path to the licensed IP source files. Therefore, the .qxp file works correctly only if imported into a top-level project on the same computer as the lower-level project, or the IP files are installed in the same directory path location on both computers.

To avoid this problem, you can include this partition in the top-level project instead of importing it, because IP cores generally do not require additional changes by a designer in the project team. You can set the partition that contains the core to Post-Fit after the first compilation to reduce future compilation times, because the partition will not be changing in any subsequent compilation. You can also set the partition to Empty to exclude the IP core from the database until you are ready "

/////

Instead of the suggested workaround, I just edited our automated build scripts to copy the files to the path that Quartus is looking for and removed them after.

--- Quote Start ---

I had the same problem with 9.0

--- Quote End ---

Did you re-generate the QXP with 9.0 or simply try to use it with 9.0? If you generate a QXP with 9.0, you shouldn't need the original encrypted IP files to use it.

Your're right. I had just re-ran the top-level build with 9.0.

I re-generated the qxp with 9.0 and it works fine.

Thanks to everyone for the help