Hello,
I have currenlty updated my Simulink to R2023b from R2017b. In the past I have been abe to successfully build my models through the HDL workflow advisor or by script with no issues.
Since I have upgraded, to R2023b I am unable to build, as I receive the following error;
"Delay balancing unsuccessful because an extra 27 cycles of latency introduced by optimizations in the feedback loop cannot be offset using design delays for the loop latency budget"
What I do not understand is how the same Simulink project can build successfuilly with R2017b, but does not with R2023b?
I have done some breif reading and am aware of the suggestions, but I cannot help but think this is a settings related problem in the configuration parameters.
I have compared settings with a colleagues R2017b, and there are differences in relation to new settings that have been set in R2023b which do not exist in R2017b.
Can anyone confirm this could be as simple as that, or do I need to introduce latency with delay blocks?
It’s hard to understand why the model would need to chage.
I can confirm the model is using clock-rate pipelining.
RegardsHello,
I have currenlty updated my Simulink to R2023b from R2017b. In the past I have been abe to successfully build my models through the HDL workflow advisor or by script with no issues.
Since I have upgraded, to R2023b I am unable to build, as I receive the following error;
"Delay balancing unsuccessful because an extra 27 cycles of latency introduced by optimizations in the feedback loop cannot be offset using design delays for the loop latency budget"
What I do not understand is how the same Simulink project can build successfuilly with R2017b, but does not with R2023b?
I have done some breif reading and am aware of the suggestions, but I cannot help but think this is a settings related problem in the configuration parameters.
I have compared settings with a colleagues R2017b, and there are differences in relation to new settings that have been set in R2023b which do not exist in R2017b.
Can anyone confirm this could be as simple as that, or do I need to introduce latency with delay blocks?
It’s hard to understand why the model would need to chage.
I can confirm the model is using clock-rate pipelining.
Regards Hello,
I have currenlty updated my Simulink to R2023b from R2017b. In the past I have been abe to successfully build my models through the HDL workflow advisor or by script with no issues.
Since I have upgraded, to R2023b I am unable to build, as I receive the following error;
"Delay balancing unsuccessful because an extra 27 cycles of latency introduced by optimizations in the feedback loop cannot be offset using design delays for the loop latency budget"
What I do not understand is how the same Simulink project can build successfuilly with R2017b, but does not with R2023b?
I have done some breif reading and am aware of the suggestions, but I cannot help but think this is a settings related problem in the configuration parameters.
I have compared settings with a colleagues R2017b, and there are differences in relation to new settings that have been set in R2023b which do not exist in R2017b.
Can anyone confirm this could be as simple as that, or do I need to introduce latency with delay blocks?
It’s hard to understand why the model would need to chage.
I can confirm the model is using clock-rate pipelining.
Regards delay balancing MATLAB Answers — New Questions

​