Preliminary Technical Data UG-1828
Rev. PrB | Page 275 of 277
2. If the cable is properly connected, then check if Windows OS is able to communicate over the Ethernet port with the ZYNQ
platform. Check if the IP number and open ports for the Ethernet connection used to communicate with the ZYNQ platform follow
advice described in the Hardware Operation section.
a. Run cmd.exe and then type: ping 192.168.1.10. The user should be able to see a reply from the ZYNQ platform. If no reply is
received, connection with the ZYNQ platform must be re-examined.
b. If connection with the ZYNQ platform is established but TTES still reports that hardware is not available, ensure that ports
number 22 (SSH) and 55557 (Evaluation Software) are not blocked by firewall software on the Ethernet connection used to
communicate with the ZYNQ platform. Both ports are required to be open for normal operation.
3. Check for physical damage to the EVB.
a. Look for ferrite bead E803 located on the TOP side of PCB, next to mounting hole. There is a possibility that during transit or
when in use nut used to keep PCB stand in place damaged E803. Ensure that E803 is in place with good connection. If E803 got
broken, replace it with BLM41PG600SN1L from Murata or similar.
Red LED Constantly On
1. The ZYNQ ZC706 generated power domain for IOs that control ADRV9001 over FMC interface. That power domain is called
VADJ. For proper operation voltage on that power domain should not exceed 1.89V. The SD card provided with the evaluation card
ensures that VADJ is properly set.
On an Evaluation Card, there is a red LED installed close to the FMC connector. The role of this LED is to indicate if VADJ voltage
exceeded 2.0V level. If that was the case this LED will be ON
a. When the FPGA is powered on the LED will be on for a few seconds as the SD card image readjusts the FPGA VADJ voltage to
1.8 V.
b. If this LED does not turn off then there is an issue and while the part might still operate this is exceeding the recommended
level for VADJ. This will decrease the lifetime of the part and can lead to permanent damage of the IC in the worst case.
Possible causes for this LED not turning off are connected to the SD card image.
2. Chip might still operate correctly after this issue but users should understand that VADJ exceeded recommended level. The only
way to remove uncertainty here is to change ADRV9002 on an evaluation board to the new one.
Init Calibration Fail
User may experience program failure due to init calibration. This is usually caused by Rx input is connected to the signal generator and
RF output is ON. This causes ADRV9002 to interfere with its own internal Rx calibration. User should turn off RF signal during
programming.
DLL Bug Fix
If more than one installation of the SDK exists on the computer the TES software may call an incorrect set of DLLs, causing unexpected
bugs. Knowing which set of DLLs are called is not feasible, however there is one legacy bug that was fixed in Day 11 which flags this
problem. Generate some C99 code in TES and inspect the #include’s. In the generated main.c file, the includes should look like this (as of
Day 11):
Deviations from this when using the Day 11 SDK may indicate errors. For example, consider the below examples of cases where the
includes have errors:
To Next Page
Loading...