Could not apply model's TargetPlatform settings in Task 1.1 of the HDL Workflow Advisor

Hello,

I am currently working on converting a Simulink model to an NI FPGA Bitfile. Recently, I updated LabVIEW from the 2023 version to the 2024 version. Consequently, I also updated the HDL NI FPGA Support Package add-ons to match the new version of LabVIEW.

After updating, I was able to open the HDL Workflow Advisor successfully the first time I tried with the Simulink model. However, when I attempted to open the HDL Workflow Advisor again with the same model, I encountered the following error:

Could not apply model's TargetPlatform settings in Task 1.1 of the HDL Workflow Advisor for the following reason:Dot indexing is not supported for variables of this type. Default setting is applied instead.If you are using the HDL Workflow Command Line Interface, consider making these changes in the HDL Workflow Advisor and using 'Export to Script...' to automatically generate the appropriate 'hdlset_param' commands.

Could anyone assist me in resolving this issue?

Thank you.

Answer 1

[Anshuman]

Hello Madhusudan,

This type of error often arises due to compatibility issues or changes in the software environment. Here are some steps you can take to troubleshoot the issue:

1. Ensure that all your software versions are compatible. This includes MATLAB, Simulink, the HDL Coder, and the NI FPGA Support Package.
2. Try clearing the cache and resetting the environment. Use the 'restoredefaultpath' command in MATLAB to reset the path. Additionally, clear any temporary files or settings related to the HDL Workflow Advisor.
3. Since the error mentions issues with applying the model's 'TargetPlatform' settings, try manually reapplying these settings. Open the HDL Workflow Advisor and reconfigure the target platform settings manually.
4. As suggested by the error message, try using the "Export to Script" feature in the HDL Workflow Advisor. This will generate a script with the appropriate 'hdlset_param' commands. You can then run this script to apply the settings programmatically, which might resolve the issue.

Hope it helps!