Wiki

Below is the source of this page. To edit this source as well as other pages on the wiki, you must login.
====== AD936X Quick Start Guides ======

===== AD-FMCOMMS2/3/4/5-EBZ =====

The Quick Start Guides provide a simple step by step instruction on how to do an initial system setup for the AD-FMCOMMS2/3/4/5-EBZ boards on various FPGA development boards. They will discuss how to program the bitstream, run a no-OS program or boot a Linux distribution.

==== Supported Carriers ====

The AD-FMCOMMS2/3/4/5-EBZ is, by definition a "FPGA mezzanine card" (FMC), that means it needs a carrier to plug into. The carriers we support are:

^ Board ^ FMCOMMS5 ^ FMCOMMS2/3/4 ^ Arradio ^
| [[xilinx>AC701]] |     |  √  |   |
| [[xilinx>KC705]] |     |  √  |   |
| [[xilinx>KCU105]] |     |  √  |   |
| [[xilinx>VC707]] |     |  √  |   |
| [[xilinx>ZC702]] |  √  |  √  |   |
| [[xilinx>ZC706]] |  √  |  √  |   |
| [[xilinx>ZCU102]] |  √  |  √  |   |
| [[http://zedboard.org/product/zedboard|Zed Board]] |     |  √  |   |
| [[http://zedboard.org/product/mini-itx-board| MITX045]] |     |  √  |   |
| [[https://www.arrow.com/en/products/sockit/arrow-development-tools|SoCKit]] |  |  |  √  |

==== Supported Environments ====

The supported OS are:

^ Board ^ HDL ^ Linux Software ^ No-OS Software ^ 
| [[xilinx>AC701]] |  √  |     |  √  |
| [[xilinx>KC705]] |  √  |  √  |  √  | 
| [[xilinx>KCU105]] |  √  |  √  |  √  | 
| [[xilinx>VC707]] |  √  |  √  |  √  | 
| [[xilinx>ZC702]] |  √  |  √  |  √  | 
| [[xilinx>ZC706]] |  √  |  √  |  √  | 
| [[xilinx>ZCU102]] |  √  |  √  |  √  | 
| [[http://zedboard.org/product/zedboard|Zed Board]] |  √  |  √  |   √  | 
| [[http://zedboard.org/product/mini-itx-board|MITX045]] |  √  |  √  |   √  | 




==== Hardware Setup ====

In most carriers, the AD-FMCOMMS2/3/4-EBZ board connects to the LPC connector (unless otherwise noted). The AD-FMCOMMS5-EBZ board is a dual FMC connector, and requires either FMC connectors (which can be either LPC + LPC). The carrier setup requires power, UART (115200), ethernet (Linux), HDMI (if available) and/or JTAG (no-OS) connections. A few typical setups are shown below.

=== ZC702 + FMCOMMS2 ===

Early versions of the ZC702 carriers need to work around [[xilinx>support/answers/51438.html|AR# 51438, PG signal does not assert by default]] errata.


=== ZC706 + FMCOMMS2 ===

{{:resources:eval:user-guides:ad-fmcomms2-ebz:cf_ad9361_setup.jpg?800|}}
==== SoCkit + ARRADIO ====

{{:resources:eval:user-guides:ad-fmcomms2-ebz:sockit_arradio.jpg?800|}}

=== Jumper Configuration ===

^ ^ CLOCKSEL0 ^ CLOCKSEL1 ^ BOOTSEL0 ^ BOOTSEL1 ^ BOOTSEL2 ^
|**POS**|  2-3  |  2-3  |  2-3  |  2-3  |  1-2  | 

{{:resources:eval:user-guides:ad-fmcomms2-ebz:sockit_clksel_bootsel.jpg?350|}}

^ JP2 ^
| 1.8V or 2.5V | 

{{:resources:eval:user-guides:ad-fmcomms2-ebz:sockit_jp2.jpg?200|}}

^ ^ MSEL0 ^ MSEL1 ^ MSEL2 ^ MSEL3 ^ MSEL4 ^ CODEC_SEL ^
|**POS**|  0  |  1  |  0  |  1  |  0  |  0  |

{{:resources:eval:user-guides:ad-fmcomms2-ebz:sockit_sw6.jpg?200|}}


===== ADRV936X System-On-Module =====

The ADRV936X SOMs have three selectable switches. Two are used for selecting the boot source, and one for selecting the SD card source. The selection will be based on your carrier and how you want to boot the device.

For switch S3 and S4

^ BOOT Mode      ^ S3 ^ S4 ^
| JTAG           | 0  | 0  |
| QSPI           | 0  | 1  |
| SD Card        | 1  | 1  |

For switch S1:

^ SD Card Source ^ S1 ^
| Onboard        | 0  |
| Carrier        | 1  |

For our standard evaluation system most users boot from the SD cards placed either on the SOM or carrier board. For the **ADRV1CRR-BOB** carrier or carriers without SD card slots be sure to set S1 to 0.

===== Networking =====

By default, all SD cards for the prototyping platform (not TES) are configured for DHCP networking over their Ethernet interfaces. If you want to change the networking interfaces to use static addresses, which is required for directly connected Ethernet cables without DHCP servers in the loop, a [[https://github.com/analogdevicesinc/linux_image_ADI-scripts/blob/master/enable_static_ip.sh|helper script]] is provided.

To update the IP address of the board you must be logged into the board over UART or JTAG or Ethernet.

From the development board or SOM itself run the following with the desired IP address:
<code>
enable_static_ip.sh <ip address> eth0
</code>
This will fix the IP address of the desired Ethernet adapter and prevent the onboard network manager from changing it.
Analog Devices Wiki

Page Tools
