fsm_nv_reg_TB presents a strange behavior for task_value_tb = 38. This can be seen in the graphs at page 45.
Maybe this is regular and just a glitch in how the policy reacts to the voltage trace or it is a warning for some bug in the fsm or how values are acquired by the script.
fsm_nv_reg_TBpresents a strange behavior fortask_value_tb = 38. This can be seen in the graphs at page 45. Maybe this is regular and just a glitch in how the policy reacts to the voltage trace or it is a warning for some bug in the fsm or how values are acquired by the script.