Dear MBD-Team,
I have encountered some issues trying to run PIL on Simulink.
Here's my setting for running the software:
I have followed the video from NXP but I kept getting this error:
Error:The timeout of 10 seconds for receiving data from the rtiostream interface has been exceeded. There might be multiple reasons for this communications failure.
You should:
(a) Check that the target hardware configuration is correct, for example, check that the byte ordering is correct.
(b) Confirm that the target application is running on the target hardware.
(c) Consider the possibility of application run-time failures (e.g. divide by zero exceptions, incorrect custom code integration, etc.).
Note (c): To identify possible reasons for the run-time failure, consider using SIL, which supports signal handlers and debugging.
If you cannot find a solution, consider using the method setTimeoutRecvSecs of rtw.connectivity.RtIOStreamHostCommunicator to increase the timeout value.
Here's my setting:
Here's my testing program:
Please help identify the issues, I will continue testing and update on any progress.
Thank you!
Hello @Wei_H
From your description, the problem might come from 2 sides:
1. RAppid Bootloader - When selecting the Serial communication deployment inside the main config block, the deployment will be performed via serial communication but a bootloader needs to be executed on the board. So in this case, you have to first flash the Rappid Bootloader suitable for your board, so that when the PIL execution tries to flash the MCU, this one needs to know how to accept the binary file.
These files are located inside the MBDT tools files under tools/BootLoader/RBF_Files
Please find more details here: https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Rappid-boot-loader-for-MPC5744P/m-p/655...
This process is also described in the Release Notes, under BootLoader Setup, chapter 2.3
2. Communication pins - once you have checked step one, please check on the schematics of the board revision you have, that the serial pins connected to the OpenSDA are the ones selected inside the configuration of the main config block.
Hope this helps,
Marius
Hi Marius,
Is there a recommendation for how to accomplish this without OpenSDA? The OpenSDAv2 software and later revisions do not support the power architecture. The customer has prototyped their own board, and do not have access to the OpenSDAv1 software from PEMicro (it must be purchased).
If we select "LIN1_RX" and "LIN1_TX" then we would need to use these pins to make a UART connect to the PC, correct? Or does this imply the two connections need to go to the K20 with OpenSDA firmware?\
Thanks,
Brendan
Hi Marius,
Thank you for your quick reply.
I have loaded the bootloader from S32 Design Studio and able to download generated code from Simulink to the MPC5748G board. However, when I tried running PIL following instruction on the same board, error occurred. As for the pins, I've looked at the schematic diagram and tried serial 0 and serial 1, but neither of those worked.
Another error I encounter using an NXP example is:
------------------------------------
Error: Unable to run PIL simulation of "sim_sil_top_TC_mpc574x".
Configuration parameters for the model do not support these connectivity configurations: Texas Instruments Code Composer Studio (IDE), Texas Instruments Code Composer Studio (TCP/IP), Texas Instruments Code Composer Studio (Serial), mpc574x_pil PIL, mpc_as_pil PIL
Update configuration parameters or create a supported connectivity configuration. See Create PIL Target Connectivity Configuration.
------------------------------------
Another error I encounter using NXP example is:
Error:Unable to run PIL simulation of "sim_sil_top_TC_mpc574x".
Configuration parameters for the model do not support these connectivity configurations: Texas Instruments Code Composer Studio (IDE), Texas Instruments Code Composer Studio (TCP/IP), Texas Instruments Code Composer Studio (Serial), mpc574x_pil PIL, mpc_as_pil PIL
Update configuration parameters or create a supported connectivity configuration. See Create PIL Target Connectivity Configuration.