Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
resources:eval:ad4630-24-eval-board:ad4630-24-developer-guide [08 Sep 2022 22:27] – [Basic HW and SW Architecture] Jim Cattresources:eval:ad4630-24-eval-board:ad4630-24-developer-guide [26 Jan 2023 09:42] (current) – replaced the obsolete ADI Kuiper Linux page link Joyce Velasco
Line 41: Line 41:
     * **LibIIO subsystem** - a library of IIO functions that are used to create custom device drivers that run within the Linux system (see **[[:resources:tools-software:linux-software:libiio|LibIIO]]** for more details). These drivers have already been generated for the AD463x/AD4030x and incorporated in the uImage file.     * **LibIIO subsystem** - a library of IIO functions that are used to create custom device drivers that run within the Linux system (see **[[:resources:tools-software:linux-software:libiio|LibIIO]]** for more details). These drivers have already been generated for the AD463x/AD4030x and incorporated in the uImage file.
     * **IIOD** - An IIO daemon that exposes IIO devices over a network connection to a remote host.     * **IIOD** - An IIO daemon that exposes IIO devices over a network connection to a remote host.
-    (More information on the general Kuiper Linux distribution can be found at **[[:resources:tools-software:linux-software:embedded_arm_images|ADI Kuiper Linux]]**)+    (More information on the general Kuiper Linux distribution can be found at **[[:resources:tools-software:linux-software:kuiper-linux |ADI Kuiper Linux]]**
   * **Device tree file** that describes the attributes of the AD4630/AD4030 configuration. The attributes of the ADC node in the device tree set the clocking mode (SPI or Echo), data rate (single or dual edge), output data format (see data sheet), and number of active lanes per channel (1, 2, or 4). During boot, the system loads the device.dtb file contained in the boot directory. If the operating configuration of the ADC needs to be changed, the device tree must be updated with the new ADC attributes. Instructions for changing the operating configuration of the ADC and HDL are provided in a later section of this guide.     * **Device tree file** that describes the attributes of the AD4630/AD4030 configuration. The attributes of the ADC node in the device tree set the clocking mode (SPI or Echo), data rate (single or dual edge), output data format (see data sheet), and number of active lanes per channel (1, 2, or 4). During boot, the system loads the device.dtb file contained in the boot directory. If the operating configuration of the ADC needs to be changed, the device tree must be updated with the new ADC attributes. Instructions for changing the operating configuration of the ADC and HDL are provided in a later section of this guide.  
   * **BOOT.BIN** files that are used to configure the FPGA. The default boot.bin file in the boot directory will correspond to a specific interface operating mode, distinguished by clocking mode (SPI vs. Echo), number of active lanes per channel (1, 2, or 4), and data rate (SDR vs. DDR). **The boot.bin must be synchronized to the ADC attributes in the device tree**. Unique boot.bin files have been pre-generated and stored on the SD card for several different configurations. Table 2 lists the available configurations (boot.bin files) that correspond to clocking modes, lanes, data rate mode. These files are available on the SD card in sub-directories that are labeled according to the configuration. This simplifies the HDL architecture and avoids the introduction of bugs due to unnecessary complexity.   * **BOOT.BIN** files that are used to configure the FPGA. The default boot.bin file in the boot directory will correspond to a specific interface operating mode, distinguished by clocking mode (SPI vs. Echo), number of active lanes per channel (1, 2, or 4), and data rate (SDR vs. DDR). **The boot.bin must be synchronized to the ADC attributes in the device tree**. Unique boot.bin files have been pre-generated and stored on the SD card for several different configurations. Table 2 lists the available configurations (boot.bin files) that correspond to clocking modes, lanes, data rate mode. These files are available on the SD card in sub-directories that are labeled according to the configuration. This simplifies the HDL architecture and avoids the introduction of bugs due to unnecessary complexity.
resources/eval/ad4630-24-eval-board/ad4630-24-developer-guide.txt · Last modified: 26 Jan 2023 09:42 by Joyce Velasco