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

vol_cntr1_pa_val in fsm_nv_reg_db false triggers #9

Open
simoneruffini opened this issue Oct 27, 2020 · 0 comments
Open

vol_cntr1_pa_val in fsm_nv_reg_db false triggers #9

simoneruffini opened this issue Oct 27, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@simoneruffini
Copy link
Owner

The volatile counter power approximator triggers improperly during runtime (only for fsmn_nv_reg_DB policy). This causes miscalculation of the power approximation visible in the report.

The bug is caused by the fact that:
1)vol_cntr1_pa_val triggers when fsm_nv_reg_state = do_operation_s
2) When the machine is in hazard state (voltage trace level below hazard threshold level) a data save is performed. But after that the machine goes back to do_operation_s even if the system is still in hazard.

Possible solution
Add an additional state to fsm_nv_reg_DB that precedes do_operation_s and that is in charge to check the voltage level against defined thresholds. This state will then direct the fsm to the right operation and will be the sink for all of them after completion.

@simoneruffini simoneruffini added the bug Something isn't working label Oct 27, 2020
@simoneruffini simoneruffini self-assigned this Oct 27, 2020
@simoneruffini simoneruffini changed the title vol_cntr1_pa_val in fsm_nv_reg_db false triggers vol_cntr1_pa_val in fsm_nv_reg_db false triggers Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants