Common Problems and Fixes
Peripheral App is not reflecting latest model configuration
Problem
When the Hardware Mapping tool is open and add or delete the peripheral blocks in the model, the Hardware Mapping tool does not reflect the changes.
Possible Solution
Close the existing Hardware Mapping tool and re-open the Hardware Mapping tool. The updated changes should now be visible in the Hardware Mapping tool.
Pin information on the block is not updated
Problem
In the Hardware Mapping tool, when you configure the pin for the peripheral block and the respective block mask in the model does not reflect the changes.
Possible Solution
Go to the model and press Ctrl+D or click Update Model under Modeling tab to view the changes made in the model.
Model build failures when Trace variables enabled in virtualizer studio (VDK)
Problem
When the variables are selected for tracing in the virtualizer studio (VDK) and you encounter the following build error while building the Simulink model.
Possible Solution
The elf is locked by the VDK and deleting it is not possible. You can try any one of the following solutions:
Try to generate the code in different folder.
Rename the model.
Close and relaunch the VDK.
PWM Interrupts does not reflect in Task Map
Problem
When you try to configure the PWM peripheral and perform the following:
Set the Interrupt type to
Duty Interrupt
.Select the Duty event for channel #
Now try to map the task for Interrupt group. The PWM Interrupts does not reflect in the Interrupt Group.
Possible Solution. Try to click on the respective Channel tab for the
selected Duty event for channel #
and then try to configure the
task map for the Interrupt Group. Now you should be able to view the PWM
interrupts available in the Interrupt Group.
Build failure on changing the device series
Problem
Build failure and errors occur when you change the device series in the Hardware Mapping tool after adding peripheral blocks to the model.
Possible Solution
Before adding peripheral blocks to the model, you must set the device series after selecting the hardware board in the Hardware Mapping tool.
Issue saving Simulink models to previous MATLAB version
Problem
When you try to save a Simulink model of R2023a or later version to earlier MATLAB version, you will encounter an error message. This is due to the unification SoC and EC boards, their features are merged from R2023a. We cannot back port to a particular HSP (EC or SoC) compatible models for R2023a and later.