Kyle Hagen

Members
  • Content Count

    9
  • Joined

  • Last visited

About Kyle Hagen

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @pedro_uno I dont suppose you can shared some insight on what was required to do this, can you? Im stuck with XSA files from Vivado and it looks like to go back to get HDF files will require me to remake the block diagram...which I really dont want to do. Since Petalinux 2017 is looking for HDF files, Id like to try a newer version. Any help is much appreciated
  2. Hello xc6lx45, Thanks for your help. To your question: I've tried with the jumper in all 3 positions, but typically we run it in SD. Actually, we have an SD card with our standalone app and a linux image which is booting and working correctly on our system (a stewart platform running inverse and forward kinematics). It's really quite wonderful the latency and performance we're getting from the Zynq. However when I try and boot that SD card on this particular Zybo, nothing happens. To recap: we have 3 Zybos in total: 2 function as expected when debugging or booting from the
  3. As an update, I got my hands on another z7-20 here and it's working as expected. The only things I can come up with here is that 1) There's physical damage to the first one which jumps to zero or 2) The onchip flash memory is different and that's causing an issue? Can anyone speak to the importance of the QSPI flash contents for a Zynq and what can be done to restore it to what it would have shipped with?
  4. Hello everyone, Im having issues getting one of our Zybos to boot. Ive tried building and running the Hello World program using Xilinx design tools 2020.1, 2019.2 and 2018.2. Something seems to go wrong in the OKToRun label, specifically at the line in boot.S commented: "/* read diagnostic register */" , the program counter jumps to 0. Jump to 0 in boot.S #ifdef CONFIG_ARM_ERRATA_743622 teq r5, #0x00200000 /* only present in r2p* */ mrceq p15, 0, r10, c15, c0, 1 /* read diagnostic register */ <<<<<<<<<<
  5. Yeah, using the correct xdc file did the trick. Humbled once again. Thanks for the promt support, Jon. It's greatly appreciated. /kyle
  6. Ugh...I think I was using the old Zybo xdc files.. Going to try with the Z7-20 version and see if this fixes it brb
  7. Hi again Jon. I started by testing each Pmod connector individually with a single constant IP block, leaving the other Pmod ports commented out in the xdc file. The results were the same. There are no circuits attached to the Pmod connectors and I suspect no current flow. Also to answer your previous question (sorry), the Zynq does not feel abnormally warm. Im a bit curious about the difference between the JB port and the others... The Zybo Z7-10 does not populate this port, while the Z7-20 (which we have here) does... could that be part of what we're seeing here?
  8. Hi Jon, thanks for the response. To test, I am using an oscilloscope to measure the voltage on the PMOD data pins. The probe is grounded to a GND via. JC,D,E show 3.3 V on all data pins JB all data pins are at around 36 mV EDIT: The constant IP blocks are all set to width 8, value 15
  9. Kyle Hagen

    Damage to PMOD JB

    Hello all, I'm having an issue with all of the digital IO on PMOD port JB. When we build a simple design that connects a constant value generator to an 8-wide output port, and use the Zybo xdc file to connect the PMOD outputs to the generator, we get no output on any of the JB logic pins. JC, JD, JE all behave as expected with their pins reading 3.3V. Is it possible to damage only those pins? Since they belong to the IO Bank 34 along with pins that we can show work, it seems strange that they would all fail together, but other pins on the IO bank wouldnt. Perhaps someone th