Assertion failed: b:\matlab\src\cgir_hdl\pir_transforms\datarateanalyzer.cpp:582:PirUtils::floatEqual(data.getRate(), outputSig->getRate())

Question

Mohammed Shameem Hussain 2017-7-16

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/348978-assertion-failed-b-matlab-src-cgir_hdl-pir_transforms-datarateanalyzer-cpp-582-pirutils-floatequa

回答： Kiran Kintali 2017-7-19

采纳的回答： Kiran Kintali

在 MATLAB Online 中打开

I am trying to convert my HDL coder project to verilog files via HDL coder workflow.

This error HDL code generation report.

Error  Assertion failed: b:\matlab\src\cgir_hdl\pir_transforms\datarateanalyzer.cpp:582:PirUtils::floatEqual(data.getRate(), outputSig->getRate())
Failed Assertion failed: b:\matlab\src\cgir_hdl\pir_transforms\datarateanalyzer.cpp:582:PirUtils::floatEqual(data.getRate(), outputSig->getRate()) 
Assertion failed:
b:\matlab\src\cgir_hdl\pir_transforms\datarateanalyzer.cpp:582:PirUtils::floatEqual(data.getRate(), outputSig->getRate())
Error in slhdlcoder.HDLCoder/makehdl
Error in downstream.DownstreamIntegrationDriver/runGenerateRTLCodeAndTestbench
Error in runGenerateRTLCodeAndTestbench
Error in Simulink.ModelAdvisor/executeCheckCallbackFct
Error in Simulink.ModelAdvisor/run
Error in Simulink.ModelAdvisor/runCheck
Error in ModelAdvisor.Node/runTaskAdvisor
Error in ModelAdvisor.Node/runToFail
Error in ModelAdvisor.Node.runtofailure
Failed Generated HDL code.

Please suggest me how to proceed. I am using Matlab 2017a.

2 个评论
显示无隐藏无

Walter Roberson 2017-7-16

This seems to be indicating that the data rate has been detected as being different from the output signal rate.

Mohammed Shameem Hussain 2017-7-17

Isn't Matlab should be able to handle data rate automatically, because I only have the freedom to enter the main clock frequency. Please correct me if I am wrong.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Kiran Kintali 2017-7-19

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/348978-assertion-failed-b-matlab-src-cgir_hdl-pir_transforms-datarateanalyzer-cpp-582-pirutils-floatequa#answer_274790

Hi, we have analyzed this issue and it looks like some of your blocks are configured with different rate inputs as you can see in the picture. This is not supported by HDLCoder.

We are investigating why you were seeing the cryptic error instead of valid error message pointing you to the incorrectly configured product block. We will fix this buggy behavior in our 17b release.

For now, can you make sure the rates are consistent in your model?

we are working with Simulink team to report this error as soon as possible (ctrl-D) during rate propagation and also update HDLCoder conformance checker to report a valid message pointing to the offending block instead of the cryptic internal error.

Hope this helps.

Thanks