Jump to content

mossygreen

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by mossygreen

  1. I have a Genesys ZU board (5ev) with a Vivado 2022.2 install and am trying to follow the steps here: https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi After I follow the steps and get to the point of doing the "Run As" procedure, Vitis downloads the bitstream and I get an error (the full trace is attached): Failed to download /home/dboles/digital_design/gen_zu_hwsw_vitis/hello/Debug/hello.elf Info: Cortex-A53 #0 (target 9) Stopped at 0x0 (Cannot resume. Cannot read 'pc'. Cannot read 'r0'. Cortex-A53 #0: EDITR not ready). I looked through this discussion: and I've validated that I have the preset.xml setting PSU__DDRC__DDR4_ADDR_MAPPING to 0. I have cloned the Digilent fork of the embeddedsw tree, checked out the genesys-zu-22.1 branch, and added it to the Vitis project as suggested. That didn't help. I did a default build of zynqmp_fsb and zynq_pmufw which generated an fsbl.elf and executable.elf in those respective areas. These may not be the right fsbl and pmu trees - I don't know how one would know. I've seen people talk about creating the platform before the application so I thought I should try that. I created a fresh Vitis project and instead of choosing "Create Application Project" I chose "Create Platform Project". In that wizard it still asks for the XSA file that I'd exported as per the Digilent tutorial. As part of the dialogs there is a place where you can have it build the fsbl and pmu so I de-selected that. After I did that, I continued with creating the platform and added the repository as suggested above. When I then created the application project and built it, I could find an fsbl.elf in the Vitis project area with a matching checksum. However, I still get the error when I try to "Run As" and run the SW on the board. The bitstream appears to download fine, but I get the write error: 17:18:24 ERROR : Memory write error at 0x0. Cortex-A53 #0: EDITR not ready Here is the trace: vitis_trace.txt I need to be able to start with a fresh Vivado 2022.2 project and follow the tutorial above. Thanks
  2. I think it was a problem with the USB device not being attached to the VM with the ZU board. Just now I connected the Nexys board and captured what the HW manager showed. When I then plugged in the ZU board I got a dialog about whether I wanted to direct the USB device to the Mac or the Linux VM. After that, the HW manager sees the device. When I set the JP3 to JTAG I can then program the device fine. Since the ZU board is new to me, and the getting started docs don't really talk about programming it via USB, I wasn't even certain it could be programmed that way. I'm up and running now.
  3. I recently got a new Genesys ZU 5EV board and have been setting up a development environment for it. The environment is Ubuntu 22.04LTS and Vivado (+Vitis, etc.) 2022.2. The environment works just fine to program a Nexys A7 board - the hardware manager sees the device and can push a bitstream to it. The ZU board appears to function. The out-of-box stuff works (although I certainly haven't exhaustively tested it). However, regardless of the jumper setting for JP3 (JTAG, USB, SD, or QSPI), the Vivado Hardware Manager doesn't see the device. I believe I have the cable drivers installed (installed as per the instructions after the Xilinx install) and have no problem with the Nexys A7 board.
×
×
  • Create New...