Forum Discussion

roeekalinsky's avatar
roeekalinsky
Icon for Contributor rankContributor
2 years ago
Solved

Bug: Import of QDB file partition fails in Quartus Pro versions that use DNI

Quartus Pro versions that use DNI fail when trying to import a partition from a QDB file.

The error observed, which doesn't occur with non-DNI versions, is as follows:

Error (20045): Can't find the stub file for /"example_core/". File: example_wrapper.vhd Line: 21

I'm providing a simple design example that demonstrates the issue (zip file attached).

Build the example using any DNI version of Quartus Pro to see it fail, and build it using any non-DNI version of Quartus Pro to see it not fail.

See the README.txt in the zip file for further detail.

Thanks,

-Roee

Hdl
  • roeekalinsky's avatar
    roeekalinsky
    2 years ago

    Hi @SyafieqS .

    Testing with the newly released Quartus Pro 24.1, I can confirm that it fixes the original issue of this thread. Error (20045) no longer appears, and a stub file is no longer required.

    As for the other two incidentally related issues that came up in this thread:

    I can confirm that the erroneously produced Warning (21610) has also been fixed. With 24.1 this warning no longer appears.

    However, the erroneously produced Critical Warning (24035) has not been fixed. These still appear with 24.1. And this is apparently a separate issue that's independent of the stub file issues. With 24.1 it can be observed that these warnings are generated whether or not a stub file is used.

    As the original issue of this thread has been addressed in 24.1, let's close out this thread at this point. I will start a new thread to deal with the Critical Warning (24035) issue.

    Thanks,

    -Roee

18 Replies

Show More
  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    2 years ago

    Roee,

    Noted and thanks for the feedback.

    I am getting this issue to developer.

    Seem the scope is bigger that I expected.

    Anyway please stay tune and let me know if there is any more valuable feedback regarding dni.

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    2 years ago

    Hi Roee,


    Update from developer:


    I'm seeing these critical warnings in both DNI and classic mode, so they suggest actual potential issues with the PR partitions:


    Critical Warning (24035): The exported partition, "example_wrapper_level1_partition", has 2 ports being driven by the same source, "clk", outside it. Up to 10 such ports are listed below. Multiple ports sharing a source external to the partition may lead to routing conflicts in compiles that reuse this partition in another context.

    Info (24036): example_wrapper_level1_i|example_core_i|clk.

    Info (24036): example_wrapper_level1_i|clk.

    Critical Warning (24035): The exported partition, "example_wrapper_level1_partition", has 2 ports being driven by the same source, "i1", outside it. Up to 10 such ports are listed below. Multiple ports sharing a source external to the partition may lead to routing conflicts in compiles that reuse this partition in another context.

    Info (24036): example_wrapper_level1_i|example_core_i|i1.

    Info (24036): example_wrapper_level1_i|i1.

    Critical Warning (24035): The exported partition, "example_wrapper_level1_partition", has 2 ports being driven by the same source, "i0", outside it. Up to 10 such ports are listed below. Multiple ports sharing a source external to the partition may lead to routing conflicts in compiles that reuse this partition in another context.

    Info (24036): example_wrapper_level1_i|example_core_i|i0.

    Info (24036): example_wrapper_level1_i|i0.

    This one only happens in DNI mode:


    Warning (21610): Output port "o" in instance "example_wrapper_level1_i|example_core_i" of entity "example_core" does not have a driver. Connecting to the default value "gnd".


    This warning should not be produced, This will be removed. It is otherwise innocent.


    I compared the atom netlists after synthesis between DNI and classic and they are the same. I checked both 23.3 and 23.4.


    Roee this should work fine. We do have extensive tests for partial reconfig in DNI mode, we were only missing the case where the design is VHDL and there is not stub.




    • roeekalinsky's avatar
      roeekalinsky
      Icon for Contributor rankContributor
      2 years ago

      Hi @SyafieqS ,

      Re: "I'm seeing these critical warnings in both DNI and classic mode":

      In what Quartus versions did you observe this?

      I'm not seeing these warnings in Quartus 23.2 and earlier. I only see them in 23.3 and 23.4.

      So is there still a classic mode in 23.3 and 23.4?

      And are these warnings then just a separate bug that was introduced in 23.3 and 23.4 that's independent of DNI?

      I'm just trying to understand the exact scope of each of these seemingly related issues.

      And will all these issues that we've uncovered be fixed in 24.1? Removing the need for the stub, as well as removing the bogus warnings?

      Thanks,
      -Roee

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    2 years ago

    Hi Roee,


    These critical warnings are newly introduced design rules for bottom-up compile. They are new in 23.3/23.4


    These are intentionally created and are supposed to help the customer in preventing issues with their design.


    Yes all these issue discovered will be fixed in 24.1 and the plan has been submitted.


  • roeekalinsky's avatar
    roeekalinsky
    Icon for Contributor rankContributor
    2 years ago

    Hi @SyafieqS .

    Testing with the newly released Quartus Pro 24.1, I can confirm that it fixes the original issue of this thread. Error (20045) no longer appears, and a stub file is no longer required.

    As for the other two incidentally related issues that came up in this thread:

    I can confirm that the erroneously produced Warning (21610) has also been fixed. With 24.1 this warning no longer appears.

    However, the erroneously produced Critical Warning (24035) has not been fixed. These still appear with 24.1. And this is apparently a separate issue that's independent of the stub file issues. With 24.1 it can be observed that these warnings are generated whether or not a stub file is used.

    As the original issue of this thread has been addressed in 24.1, let's close out this thread at this point. I will start a new thread to deal with the Critical Warning (24035) issue.

    Thanks,

    -Roee