Software interface model on the Zynq ARM processor - MicroZed Board

5 views (last 30 days)
Hi,
I have included the MicroZed board using the steps mentioned in the 'Define and Register Custom Board and Reference Design for SoC Workflow'. When I executing the software interface model on ARM processor I get the following error, can you please suggest the possible solution.
The following error was encountered during evaluation of the External mode callback 'SetupFcn':
Attempt to reference field of non-structure array.
### Starting build procedure for model: gm_hdlcoder_led_blinking_4bit_interface
Code Generation 1
Elapsed: 1:46 min
Build process completed successfully
The following error was encountered during evaluation of the External mode callback 'PauseBeforeConnect':
Cannot connect to Zynq Hardware at IP Address "192.168.1.10".
Click here to view the troubleshooting guide and verify the IP Address settings of your hardware.
Component: Simulink | Category: N.A. warning
Attempting to establish connection with hostname '169.254.1.10' through port 17725.
Error occurred while executing External Mode MEX-file 'ext_comm':
Failed to connect to the target. Possible reasons for the failure:
a) The target is not switched on.
b) The target is not connected to your host machine.
c) The application for the model is not running on the target. You might have clicked the Stop button.
Caused by:
An error occurred attempting to open an rtIOStream. More detail may be reported in the MATLAB command window
Component: Simulink | Category: Model error
Simulation 1
6:54:36 PM Nov 1, 2016 Elapsed: 0.270 sec
Unable to connect to the 'Xilinx Zynq ZC702 evaluation kit' target for 'gm_hdlcoder_led_blinking_4bit_interface'.
Component: Simulink | Category: Model error

Answers (1)

Walter Roberson
Walter Roberson on 1 Nov 2016
I see
Cannot connect to Zynq Hardware at IP Address "192.168.1.10".
and
Attempting to establish connection with hostname '169.254.1.10' through port 17725.
That hints to me of the possibility that your device starts out without an IP address and sends a DHCP request but that you have no DHCP server, so the device creates an IP address in the "self-assigned" range (which all start with 169.254)
If my suspicion is correct then you either need to find a way to tell the device to use 192.168.1.10 or else you need to set up a DHCP server on the network interface that you are connecting the device to. If you are using MS Windows, then one way to do that is to configure the interface for Ethernet Sharing.
  2 Comments
Anirudh  Acharya
Anirudh Acharya on 2 Nov 2016
Hi Walter,
I did try changing the IP address (zynq>ifconfig eth0 169.254.1.10)and make a successful connection. When I make a run, I get an error on the console (please see the attachment: error.png).
Error while opening: dev/mwipcore
DEV_OPEN_FAILURE: No such file or directory
The diagnostic viewer gives the following message without any errors:
10:04:25 AM Nov 2, 2016 Elapsed: 17 sec
### Starting build procedure for model: gm_hdlcoder_led_blinking_4bit_interface
Code Generation 1
Elapsed: 7 sec
### Generating code into build folder: C:\Users\anirudhb\Documents\MATLAB\LED\gm_hdlcoder_led_blinking_4bit_interface_ert_rtw
### Generated code for 'gm_hdlcoder_led_blinking_4bit_interface' is up to date because no structural, parameter or code replacement library changes were found.
### Evaluating PostCodeGenCommand specified in the model
### Using toolchain: Xilinx Software Development Kit (SDK) v2013.4 | gmake (64-bit Windows)
### 'C:\Users\anirudhb\Documents\MATLAB\LED\gm_hdlcoder_led_blinking_4bit_interface_ert_rtw\gm_hdlcoder_led_blinking_4bit_interface.mk' is up to date
### Using toolchain: Xilinx Software Development Kit (SDK) v2013.4 | gmake (64-bit Windows)
### 'C:\Users\anirudhb\Documents\MATLAB\LED\gm_hdlcoder_led_blinking_4bit_interface_ert_rtw\gm_hdlcoder_led_blinking_4bit_interface.mk' is up to date
### Building 'gm_hdlcoder_led_blinking_4bit_interface': C:\PROGRA~1\MATLAB\R2015a\bin\win64\gmake -f gm_hdlcoder_led_blinking_4bit_interface.mk all
"### Successfully generated all binary outputs."
"### Invoking postbuild tool "Download" ..."
C:/MATLAB/SUPPOR~1/R2015a/XILINX~1/toolbox/target/SUPPOR~1/zynq/@SLCUS~1/../download.bat "C:\Program Files\MATLAB\R2015a/toolbox/idelink/foundation/hostapps" root root 169.254.1.10 /tmp ../gm_hdlcoder_led_blinking_4bit_interface
Connection successful
gm_hdlcoder_led_blinking_ | 4 kB | 4.0 kB/s | ETA: 00:00:13 | 6%
gm_hdlcoder_led_blinking_ | 59 kB | 59.6 kB/s | ETA: 00:00:00 | 100%
"### Done invoking postbuild tool."
### Successful completion of build procedure for model: gm_hdlcoder_led_blinking_4bit_interface
Build process completed successfully
Walter Roberson
Walter Roberson on 4 Nov 2016
I cannot really tell from the window decorations where the routine is being run -- though "No such file or directory" is more typical of Unix error messages than of Windows error messages.
The information I find is that /dev/mwipcore should be mapped to the IP core at the Linux level. I cannot tell at the moment, though, who is responsible for that. I see a hint it would be done by the image that was stored onto the SD card at the time you installed the Zynq software into MATLAB.

Sign in to comment.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!