Forum Discussion
NIOS-V QSYS Warning Properties (associatedClock) have been set on
Hello,
I have a really basic setup of a NIOS V system, but get Warnings in QSYS (using Quartus 25.1 Standard) about Properties of associatedClock:
System:
Warning:
Warning: nios_subsystem.intel_niosv_m_0: Properties (associatedClock) have been set on interface reset - in composed mode these are ignored
Warning: nios_subsystem.intel_niosv_m_0: Properties (associatedClock,associatedReset) have been set on interface instruction_manager - in composed mode these are ignored
Warning: nios_subsystem.intel_niosv_m_0: Properties (associatedClock,associatedReset) have been set on interface data_manager - in composed mode these are ignoredQuestions:
- What is "composed mode" and how can I control it? There is no NIOS Parameter associated with it
- This appears in a basic setup simply by adding NIOS V to the system. How do I get rid of this warning?
best regards
Fabian
Hi FabianL
FabianL wrote:
Would it be possible to waive these warnings or disable these warnings on a project setting basis?
Sorry for the late reply.
We were looking for ways to waive/suppress this warnings in Quartus Std, but unfortunately none is found.Regards,
Liang Yu
4 Replies
- LiangYuG_Altera
Contributor
Hi Fabian,
What is "composed mode" and how can I control it? There is no NIOS Parameter associated with it
It is referring to use cases where you have a system (e.g., system.qsys) that contains another sub-system (e.g., nios_subsystem.qsys). It is not a NIOS parameter.
This appears in a basic setup simply by adding NIOS V to the system. How do I get rid of this warning?
You can ignore it.
The properties causing the warning are set on the inner sub-component's interface, but Quartus sees that these properties aren't being explicitly mapped or necessary for the top-level subsystem assembly.
It is safe to ignore this warning, as Quartus is simply informing you that it did not use those specific interface properties during synthesis.
We will investigate further.
Regards,
Liang Yu - FabianL
Occasional Contributor
Hi, thanks for the explanation.
Would it be possible to waive these warnings or disable these warnings on a project setting basis?
Coding Guidelines encourage us to not have any Warnings in QSYS project, so I would prefer having a way to disable these warnings explicitly.
best regards
Fabian
- LiangYuG_Altera
Contributor
Hi FabianL
FabianL wrote:
Would it be possible to waive these warnings or disable these warnings on a project setting basis?
Sorry for the late reply.
We were looking for ways to waive/suppress this warnings in Quartus Std, but unfortunately none is found.Regards,
Liang Yu - FabianL
Occasional Contributor
ok, then we have to live with these warnings.
Would be great if this could be fixed in the future. With excessive acceptable warnings in the system the important warnings tend to be overlooked.
For now your explanation allows us to deal with it. Thanks.