This error message indicates that Simulink is unable to communicate with the Xilinx board over the Ethernet connection.
First, please go through all the steps presented in the following article:https://www.mathworks.com/matlabcentral/answers/408583-troubleshooting-connection-issues-with-xilinx-zynq-platform
Going through the above article will ensure the following:
- The Linux Image on the SD card matches your version of MATLAB.
- The jumper settings are correct and the Xilinx board boots successfully from the SD card.
- The IP settings for both the Xilinx board and host PC are correct, and you can ping the Xilinx board from the host PC.
- You can enter the "zynq" command in MATLAB without getting an error.
Once you have ensured that the Ethernet connection between the host PC and the Xilinx board is fine, please try the following troubleshooting steps:
1. Reset the 'Hardware board' setting in the interface model:
a) Open Configuration Parameters > Hardware Implementation.
b) Set 'Hardware board' to 'None'.
c) Set 'Hardware board' to 'Zedboard', then click 'Apply'.
d) Verify that the correct IP address was filled into Hardware Board Settings > Target hardware resources > Board Parameters > Device Address.
e) Run in external mode.
2. If step 1 fails, please check whether the program can be manually run on the hardware:
a) Load the model manually by entering the following command into the MATLAB Command Window:
>> h = zynq;
>> h.loadModel('gm_hdlcoder_led_blinking_interface');
where 'gm_hdlcoder_led_blinking_interface' is the name of your model.
For more info on zynq object, type "help zynq" in MATLAB.
b) From MATLAB, open a PuTTY shell:
>> h.openShell('ssh') % enter the credentials (username - 'root', password - 'root')
In the PuTTY shell, execute the following commands to run the application:
zynq> cd /tmp
zynq> ./gm_hdlcoder_led_blinking_interface
Note that in older versions of MATLAB, the executable may have an .elf extension.
c) In Simulink, select Code > External Mode Control Panel. Click 'Connect', then 'Start Real-Time Code'.
e) Check in the PUTTY window to see if the application is still running by using the "ps" Linux command:
zynq> ps
You should see the "gm_hdlcoder_led_blinking_interface" process in the list.
3. If step 2 fails, please try to do further debugging by following the steps below:
a) In your Simulink model, open the configuration parameters > Code Generation > Build Configuration > "Debug"
b) Click "Monitor & Tune" inn the model - you will see the same "Failed to connect to target error...".
c) From MATLAB, open a PuTTY shell:
>> h = zynq;
>> h.openShell('ssh') % enter the credentials (username - 'root', password - 'root')
In the PuTTY shell, execute the following commands to change the executable permissions of the app:
zynq> cd /tmp
zynq> chmod +x ./gm_hdlcoder_led_blinking_interface
zynq> ./gm_hdlcoder_led_blinking_interface
where 'gm_hdlcoder_led_blinking_interface' is the name of your model. Note that in older versions of MATLAB, the executable may have an .elf extension.
d) Run the app:you should see more informative log and errors in the shell.
zynq> ./gm_hdlcoder_led_blinking_interface
You should see a more informative log and errors in the shell now.
If the application errors out, copy the error log and send it to MathWorks Technical Support.
If the application starts and is waiting, then continue with following steps.
e) In Simulink, select Code > External Mode Control Panel. Click 'Connect', then 'Start Real-Time Code'.
f) Observe the log on the Linux shell where you started the application manually.
g) copy the error log from the PuTTY shell and send it to MathWorks Technical Support.
