Changing the channel on the Dio block does not change the generated code.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Changing the channel on the Dio block does not change the generated code.

Jump to solution
840 Views
Automan
Contributor I

I am using the s32k3xx_dio_s32ct example have found that if you change the Channel i any of the Dio blocks that the generated code continues to use the original channel. I tried deleting and re-adding a Dio block and connecting to a different channel sometimes works, but not always.

0 Kudos
Reply
1 Solution
819 Views
robertv
NXP Employee
NXP Employee

Hello @Automan ,

The behavior you are describing is happening because changing the Channel/Pin inside the Dio mask is not causing Simulink to regenerate the code. We are looking into ways to improve this specific scenario and make it as hassle-free as possible.

For now, the best course of action in your specific use case, and to always get consistent results, would be to delete the "modelName_ert_rtw" folder and the "modelName.slxc" file before building the model. Doing so will trigger the code generation and update the executable based on the current state of the model. This should not be needed if the model is changed in a more significant way, like adding blocks, changing signals and/or connections, etc. 

Regards,
Robert V

View solution in original post

0 Kudos
Reply
3 Replies
820 Views
robertv
NXP Employee
NXP Employee

Hello @Automan ,

The behavior you are describing is happening because changing the Channel/Pin inside the Dio mask is not causing Simulink to regenerate the code. We are looking into ways to improve this specific scenario and make it as hassle-free as possible.

For now, the best course of action in your specific use case, and to always get consistent results, would be to delete the "modelName_ert_rtw" folder and the "modelName.slxc" file before building the model. Doing so will trigger the code generation and update the executable based on the current state of the model. This should not be needed if the model is changed in a more significant way, like adding blocks, changing signals and/or connections, etc. 

Regards,
Robert V

0 Kudos
Reply
806 Views
Automan
Contributor I
Hi Robert,
Is there a list somewhere that shows the current issues and workarounds for the MBDT version 1.6.0?
0 Kudos
Reply
792 Views
robertv
NXP Employee
NXP Employee

Hello @Automan ,

On every release, we update the list of limitations and known issues. This list can be found inside the readme.txt file located in the root of the Toolbox.

Regards,
Robert V

0 Kudos
Reply