Hi, @paul_ephraim_13
I downloaded the model you gave me and tested it on the board. I notice that it was configured to toggle RGBLED0_BLUE, as it appears from the generated code.
After that, I modified the DIO block to toggle the RED color, on the RGBLED0_RED channel. Everything worked correctly, the led being red this time.
As a note, if sometimes the application is not in sync with the latest changes, try to view the generated C code, it is possible that sometimes, even if you change settings in blocks, the code remains from the previous version. I think this happened in your case.
You can view the generated code directly in Simulink, by accessing the Apps section, followed by the Embedded Coder section.
The C Code tab will open and you can access the generated code by pressing the View Code button. By clicking on a block in Simulink, you can see the generated code related to that block and thus you can see if the parameters are updated or not.
1. RGBLED0_BLUE
2. RGBLED0_RED
Additionally, you can open the generated code in text format, from the following location: model_name_ert_rtw folder -> model_name.c. In this case would be temp_2_ert_rtw -> temp_2.c
If you notice discrepancies between the model and the generated code, you can do a cleanup and delete the ert_rtw folder, where the generated code is located, and building the model again, the new code will be generated and thus make sure that it is in sync with the latest version.
Hope this helps,
Dragos
Thankyou mam for your information, but it seems that the port pins are already configured by default in the port component.
Actually, what i am going through is that when Iinitially build the simulink model into the target (s32k312), the light does glow according to the initial setup, but when i change that in the model like in the below demonstrated image(blue to red) and building it once agaiin to the target, it seems to stick around with the initial build-up.
I have also attached my model, please consider, you could also provide some manuals for the setup procedure!
Sorry to keep pstig my queries! cause i am pretty new to this area!
Hi, @paul_ephraim_13
I downloaded the model you gave me and tested it on the board. I notice that it was configured to toggle RGBLED0_BLUE, as it appears from the generated code.
After that, I modified the DIO block to toggle the RED color, on the RGBLED0_RED channel. Everything worked correctly, the led being red this time.
As a note, if sometimes the application is not in sync with the latest changes, try to view the generated C code, it is possible that sometimes, even if you change settings in blocks, the code remains from the previous version. I think this happened in your case.
You can view the generated code directly in Simulink, by accessing the Apps section, followed by the Embedded Coder section.
The C Code tab will open and you can access the generated code by pressing the View Code button. By clicking on a block in Simulink, you can see the generated code related to that block and thus you can see if the parameters are updated or not.
1. RGBLED0_BLUE
2. RGBLED0_RED
Additionally, you can open the generated code in text format, from the following location: model_name_ert_rtw folder -> model_name.c. In this case would be temp_2_ert_rtw -> temp_2.c
If you notice discrepancies between the model and the generated code, you can do a cleanup and delete the ert_rtw folder, where the generated code is located, and building the model again, the new code will be generated and thus make sure that it is in sync with the latest version.
Hope this helps,
Dragos
If you are using MBDT for S32K3 v1.5.0, besides the Pins Tool configuration, where you should configure the pins used inside the application, you would also need to ensure the same pins configuration inside the Port component.
This is because, during the initialization sequence, the Port_Init function is called. Hence, not having the pin configured there as well, won't produce your expected results.
This linkage between the Pins Tool and the Port component is mandatory, as specified by the RTD (Real-Time Drivers) implementation. MBDT uses this software drivers for ensuring hardware configuration and access from the Simulink environment.
Please check the S32K3 Release Notes document - Section 3.6 where you could find details on the correspondence between the Port component and the Pins tool (attached a snippet from the section in discussion).
Please let us know if this helps, or please provide any additional information that could help us identify the issue you are currently encountering.
Irina
