Unable to upload algorithm on S32K344-T172 EVB

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

Unable to upload algorithm on S32K344-T172 EVB

1,656 Views
Nikunj_Patel
Contributor I

I am trying to perform a PIL simulation using NXP S32K344-T172 EVB and Simulink R2022b MBD. I am using NXP Reference Example "s32k3xx_pil_target_s32ct.mdl" and "s32k3xx_pil_harness_s32ct.mdk" for the testing the board. Model is generating the elf file as well as bin file successfully. Also SIL is also performed. But while flashing the algorithm to hardware, I am facing the below attached 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.

0 Kudos
Reply
1 Reply

1,559 Views
georgevictor
NXP Employee
NXP Employee

Hi, @Nikunj_Patel,

Thanks for using MBDT into your projects.

I've noticed that the S32K3xx toolbox is situated in the typical MATLAB Add-Ons directory, specifically 'AppData\Roaming\MathWorks...'. Given that Windows has a maximum path length of 256 characters, and the P&E Micro programming tool within our toolbox has numerous subfolders, this could result in malfunctions for various tools, as you've experienced. In this instance, the P&E GDB Server issues an error stating that the 'Programming algorithm is not available for this device.'

My recommendation is to change your default Add-Ons path to a shorter one to avoid potential problems arising from Windows path limitations.

Please let us know if this helped you.

 

Best regards,

Victor 

0 Kudos
Reply