issue in running PIL with TI c2000
6 views (last 30 days)
Show older comments
Hello evryone i am working with Buck boost_int32_PIL from TI F28377s/TARGET there is no error but when i started the PIL I got : The timeout of 10 seconds for receiving data from the rtiostream interface has been exceeded. There might be multiple reasons for this 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 is running. (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. Component:Simulink | Category:Modelerror Output argument "lSections" (and maybe others) not assigned during call to "coder.profile.ExecutionTime/get.Sections". Component:Simulink | Category:Modelerror
Answers (3)
maxhuangkun
on 2 Dec 2018
Hello, I also have the same problem as. Hardware setup and communication are correct.The device I use is DSP28335。My port A is GPIO63 and GPIO62. I used USB to TTL to set GPIO29 and GPIO28 to SCIA. So there should be no jumper problems, but still have this problem? I don’t know much about TI’s DSP.
1 Comment
Aradhya Sambhu Satpathy
on 28 Apr 2023
Hello everyone i am working with TI F20025c Launchpad TARGET. When I am doing the PIL simulation I got the following error: The timeout of 10 seconds for receiving data from the rtiostream interface has been exceeded. There might be multiple reasons for this 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 is running. (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. Component:Simulink | Category:Modelerror Output argument "lSections" (and maybe others) not assigned during call to "coder.profile.ExecutionTime/get.Sections". Component:Simulink | Category:Modelerror
See Also
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!