Post Go back to editing

ZCU102 & AD9174 boot couldn't reach opt_post_running_stage.

Thread Summary

The user encountered issues with the AD9174 DAC on ZCU102 where the JESD FSM did not reach the opt_post_running_stage state, preventing the DAC from outputting data. The solution involved adding the 'adi,dual-link = <1>' property to the devicetree and ensuring the Constant IP was correctly connected to the DAC data input port. The DAC output amplitude was also found to be very low, likely due to the evaluation board's output circuit, which the user will investigate further.
AI Generated Content
Product Number: ZCU102, AD9174-FMC-EBZ

Hi all,

I used following HW & SW setups and found that FSM state reached link_running and Linux boot sequence completed apparently successfully with neither moving on to opt_post_running_stage nor rolling back to previous state. Is this correct procedure? In my understanding, TXEN, etc. are not set in the boot sequence without reaching opt_post_running_stage since ad9172_finalize_setup() is not called.

.

ZCU102 & AD9174-FMC-EBZ as HW.

"$HDL_DIR/projects\dac_fmc_ebz\zcu102/make" to create system_top.xsa (JESD mode 4 as default settings)

"./build_zynqmp_boot_bin.sh ./system_top.xsa ./u-boot.elf download" to create BOOT.bin.

"./build_zynqmp_kernel_image.sh ./linux-adi/ xilinx/zynqmp-zcu102-rev10-ad9172-fmc-ebz-mode4.dtb /opt/pkg/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-" to create Image and dtb.

Note: dtsi, dts, and $HDL_DIR/projects\dac_fmc_ebz\common\config.tcl are not changed from default.

Parents Reply Children