When using the HDL Workflow Advisor, why do I get errors in Task 1.2 that mention "Dot indexing is not support for variables of this type"?

I am using  a Zynq ZC706 and FMCOMMS2/3, and following this example that can be found when I run the following command on MATLAB R2018a: 

web(fullfile(docroot, 'supportpkg/xilinxzynqbasedradio/examples/hw-sw-co-design-qpsk-transmit-and-receive-using-analog-devices-ad9361-ad9364.html'))

I have replaced some of the example's block with my own.

When I reach Task 1.2 of the HDL Workflow Advisor,  this error appeared:

Could not apply model's setting to the Target Interface Table in Task 1.2 of the HDL Workflow Advisor for the following reason:

Dot indexing is not supported for variables of this type.

Default or last valid setting is applied instead.

How do I find the root cause of this issue and fix it?

Answer 1

[MathWorks Support Team]

The root cause of the issue are the commented-through blocks in the DUT model. If you right-click on the DUT block and select HDL Code -> Check Subsystem Compatibility, the HDL Code Generation Check report indicates that 5 blocks are commented-through, which is apparently not supported by HDL Coder. For example check this report error:

The 'sim_05092019_1100/DUT1/cross_correlator (RAM short)/LTE/slice/abs^2' block is commented through. HDL code generation is not supported for blocks that are commented through.

If you remove these blocks and replace them with a connecting line, Task 1.2 completes successfully. I would suggest that you try this (best to make a backup copy of the model), then proceeds through the remainder of the HDL Workflow Advisor.

The above conclusions are the result of running the HDL Model Checker;

web(fullfile(docroot, 'hdlcoder/hdl-model-checker.html'))

Specifically this check:

web(fullfile(docroot, 'hdlcoder/ug/check-for-ports-and-subsystems.html'))

Please follow the below link to search for the required information regarding the current release:

https://www.mathworks.com/help/

Answer 2

[Kiran Kintali]

Thanks for identifying the root cause of the issue. It is worth improving the error message. I do not see a model. Can you create an enhancement request with reproduction steps?