Problem

MATLAB^®returns this warning message from a call to theinfomethod:

info(dev)

## Establishing connection to hardware. This process can take several ## seconds. Warning: The device with IPAddress 192.168.3.2 is busy. The device is already owned by a block, block dialog, or System object. Stop the simulation, close the opened dialog, or call the release methods of the System Object to allow a new owner to be assigned.

This message means that the radio hardware is in use by another MATLAB or Simulink^®entity. The radio hardware can become busy when any of the following conditions occur:

Possible Solution

Release the radio hardware by stopping the simulation, closing the block mask, or calling therelease方法系统的对象.

Problem

After streaming starts, you do not receive data from the radio hardware.

Possible Solutions

Reestablish Connection.If you do not have a connection, it is possible that a bad network interface card (NIC), a bad cable, or a loss of power is causing the problem. To reestablish connectivity:

Synchronize Software with Radio Hardware

Refresh Address Resolution Protocol (ARP) Cache.You can get this message when the IP address or MAC address binding is refreshed, interfering with the transmission of data from the radio hardware to the host. To avoid the refresh issue, set a static entry in the ARP cache, that is, the table that holds the address bindings. To find the IP address and MAC address, in the block mask of the receiver, examine the hardware information section.

In the following example, the radio hardware is configured with the default IP address192.168.3.2, and the MAC address is00-0A-35-02-21-8A.

For Windows^®, with system administrator privileges enabled, execute the following in a command shell:

cmd> arp -s 192.168.3.2 00-0A-35-02-21-8A

To confirm that you got the expected outcome, examine the table and verify that the output shows astaticentry type:

cmd> arp -a 192.168.3.2 Interface: 192.168.2.8 --- 0x16 Internet Address Physical Address Type 192.168.3.2 00-0a-35-02-21-8a static

For Linux^®, withrootorsudoprivilege enabled, execute the following in a command shell (note that the MAC address delimiter is ":" instead of "-"):

sh> sudo /usr/sbin/arp -s 192.168.3.2 00:0A:35:02:21:8A

To confirm that you got the expected outcome, examine the table and verify that the output shows a static entry type, as noted by thePERMstring.

sh> sudo /usr/sbin/arp -a 192.168.3.2 ? (192.168.3.2) at 00:0a:35:02:21:8a [ether] PERM on eth3

Problem

The radio hardware is not communicating with the host computer. You might get an error similar to the following:

info(dev)

## Establishing connection to hardware. This process can take ## several seconds. Warning: Failed to create context for uri: ip:192.168.3.2 The address is not available or the last connection was not cleared properly. Make sure the device is connected. If the issue persists, click here, and try again.

Possible Solutions

Try these connection checks to see if you can identify where the communication problem is occurring.

Check Host-Hardware Ethernet Connection

Check Connection Between Radio Hardware and Operating System.Check the connection using thepingcommand and the IP address of the radio hardware.

If you get a response to thepingcommand, then your connection is successful.

If you get the messageRequest timed out, the network connection setup is incorrect. SeeConfigure Network Connection on the Hostof the guided hardware setup process.

Problem

The model is not running in real time.

Possible Solutions

Problem

A call to a function that specifies a device address returns an error that the device is not known, it cannot communicate to the radio hardware, or that it failed to find the device.

Possible Solution

Problem

During the hardware setup process, in the network connection configuration step, you don’t see the USB-to-Ethernet adapter listed in the connection list.

Possible Solution

Problem

Host blocking or antivirus software is interfering with the host computer’s ability to communicate with the radio.

Possible Solution

Problem

When usingdownloadImageto download the SD card image for a development board, the following error message appears:

### downloadImage failed ...Error attempting to connect to address '192.168.3.2'. Cannot connect to the hardware. Following error was returned while attempting to connect: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is e1:03:3c:eb:e1:cd:76:52:54:20:af:e0:f1:ed:82:66. Please contact your system administrator. Add correct host key in /home/user/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/user/.ssh/known_hosts:381 Password authentication is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Permission denied (publickey,password,keyboard-interactive).

Possible Solution

Remove all SSH host keys belonging to the IP address assigned to the development board. For example:

% ssh-keygen -R 192.168.3.2

Problem

During SDR processing on a ZedBoard™, the Zynq^®processor overheats and stops working.

Possible Solution

ZedBoard Rev B and earlier revisions must have a heat sink attached. (Rev C and later revisions have the heat sink attached already.) If your board has an FMC radio attached but no heat sink, you likely encounter this problem.

Problem

The FMCOMMS RF card tends to fall out of the slot on the Zynq development board, especially when you use a heavy antenna.

Possible Solution

Use the standoffs that come with the SDR development kit.

Problem

When you attempt to establish communication between a radio hardware and a System object or block, you get the following error message:

Tx/Rx baseband sample rates do not match.

It is likely that you are trying to send and receive radio signals at different baseband sample rates while using a single device.

Possible Solution

Make sure that the transmitter and the receiver have the same baseband sample rate. SeeTransmit and Receive On Single Devicefor more details.

Problem

When trying to receive data from the radio hardware, MATLAB or Simulink does not respond.

Possible Solution

When the data timeout property or parameter is set to the default valueInf, MATLAB or Simulink indefinitely waits for data. If you have a custom bitstream loaded onto the board, it is possible that the radio hardware does not return any samples.