Hello there, I'm currently in possession of the aforementioned device, the AES-ZU7EV-1-SK-G, link: https://www.avnet.com/shop/us/products/avnet-engineering-services/aes-zu7ev-1-sk-g-3074457345634251668/
According to AVNET, its' based on the ZCU106 platform, see: https://www.xilinx.com/products/boards-and-kits/zcu106.html#hardware With that in mind, I went ahead and built a Yocto image for the 2018.2 TRD, here: https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842038/Zynq+UltraScale+MPSoC+VCU+TRD+2018.2+-+Design+Module+3 The same TRD is also mentioned here: https://www.xilinx.com/products/boards-and-kits/zcu106.html#documentation However, the image written to the SD card cannot boot on this platform, implying two possibilities: 1. The boot selection configuration on my end is wrong, or 2. The TRD referenced above is actually incompatible with the kit above. Troubleshooting steps taken: As stated in the board's documentation, one should set (MODE[0:3] = SW2[1:4]) to OFF, ON, OFF, and ON positions (Boot Mode set to SD Card, MODE[3:0] = 0x5) for SD cards. However, setting that as shown here: https://www.avnet.com/opasdata/d120001/medias/docus/190/xxxx-GSG-UltraZed-EV-Starter-Kit-v1.3.pdf results in the following: 1. The light on the SOM turns a steady, bright red. 2. The light on the carrier is also a steady bright red. Whereas with the stock settings (boot from QSPI), the light statuses for the above are blue, and a blinking red light respectively. How can I troubleshoot this further? Could the Yocto build made with the TRD above be incompatible with this design, or is this a boot medium issue? Warm regards, Dennis.
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
