Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Critical Warning in Quartus 20.1.0: avoid power up to high #423

Merged
merged 4 commits into from
Oct 11, 2022

Conversation

akaeba
Copy link
Collaborator

@akaeba akaeba commented Oct 5, 2022

Avoids Critical Warning in Quartus Prime Version 20.1.0 Build 711 06/05/2020 Standard Edition

Critical Warning (18061): Ignored Power-Up Level option on the following registers
Critical Warning (18010): Register neorv32_top:neorv32_i|neorv32_cpu:neorv32_cpu_inst|neorv32_cpu_control:neorv32_cpu_control_inst|execute_engine.state[3] will power up to High
Critical Warning (18010): Register neorv32_top:neorv32_i|neorv32_cpu:neorv32_cpu_inst|neorv32_cpu_control:neorv32_cpu_control_inst|execute_engine.state[3] will power up to High

akaeba and others added 3 commits October 5, 2022 21:44
…_cpu:neorv32_cpu_inst|neorv32_cpu_control:neorv32_cpu_control_inst|execute_engine.state[3] will power up to High
@stnolting
Copy link
Owner

For the records: this issues has been discussed in #415


@akaeba thanks for contributing (and sorry for the delay)! 👍

@stnolting stnolting added HW hardware-related optimization Make things faster, smaller and more efficient labels Oct 9, 2022
@stnolting stnolting self-assigned this Oct 9, 2022
@stnolting stnolting merged commit 50bf0c5 into stnolting:main Oct 11, 2022
@akaeba akaeba deleted the avoid_power_up_high branch October 11, 2022 21:14
@akaeba
Copy link
Collaborator Author

akaeba commented Oct 11, 2022

No worry. Thanks for merge 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HW hardware-related optimization Make things faster, smaller and more efficient
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants