Mario875

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. Have you tried programming directly using the JTAG interface on jumper J17? If you have that option it would be my next port of call to rule out the USB - JTAG interface. Looks like xsct can see the board, but with errors on the JTAG boundary scan. Take a look at some of these threads.... https://forums.xilinx.com/t5/Embedded-Development-Tools/Problem-of-Boundary-Scan-Chain-of-Devices/td-p/168196 https://forums.xilinx.com/t5/Embedded-Development-Tools/JTAG-chain-error-in-SDK-9-Whole-scan-chain-DR-shift-through-all/td-p/819407 https://forums.xilin
  2. The FTDI firmware should not be a problem, because it is the exact same FPGA, just a higher speed grade. All the pins for the JTAG will be the same as the original FPGA. Is it possible that the company you sent it to tried to update the FTDI firmware? I have read that the FTDI software can erase the Digilent firmware without warning when you open their software with the Digilent board connected. Maybe this happened? There is an dedicated thread about restoring FTDI firmware here... Maybe @JColvin can detail the method required to restore the FTDI firmware
  3. When you say you replaced the FPGA, do you mean you actually de-soldered the original one and soldered a new one? If so there are a couple of things to query, such as how was this done (as in what tools / method were used)? Are you sure there have been no pads lifted when the old FPGA was lifted? Are you sure the new FPGA is soldered properly with no bridges, making good contact to the pads on the board, etc? Also, I suppose the bigger question is...where did you manage to source the new FPGA? Was it from a reputable retailer or someone on Ali-Express? As I have just do
  4. Not much you can do other than edit the constraints file as Vivado is basically saying the pin you’ve selected that the LED is connected to is in a bad place for routing of the clock and could be optimised by using a more suitably placed pin on the FPGA. Unfortunately as it’s a dev board the LEDs and what not are connected to the pins chosen by digilent and you can’t change that, just add the line of text to your constraints file or chose a different LED that may be connected to somewhere Vivado prefers. Also, the solution was given to you by Vivado, there was no need to search the
  5. In the schematic, for example PMOD connector that is labelled “JA1” on the schematic linked goes to Bank 15, pin G13 on the FPGA. https://reference.digilentinc.com/_media/reference/programmable-logic/arty-a7/arty_a7_sch.pdf
  6. Mario875

    Nexys Video HDMI

    Just had a look at those Trenz Electronik SOM's and I REALLY like the idea of them! Buy a single expansion (carrier) board then simply plug in the FPGA SOM you want to develop on. Or of course you can make your own carrier board if you wanted. I have had a look at the carrier board schematic and it is using an ADV7511 (36-bit device) for converting to HDMI. However there are a few issues with it that do not address the issues on the Nexys Video such as.... GTP ports of the FPGA SOM on are routed to header pins on the carrier which are used for the CameraLink connector,
  7. Mario875

    Nexys Video HDMI

    Thanks for all the info, seems that if I want proper timings at 1080p, 60Hz, 24-bit colour I am best just using the ADV7513 (or similar). Considering the IC's are only £14 from RS Components and they are purpose built for the job, it seems going that route is first of all, less headache and second of all, likely to yield superior results. Not to mention the cost saving vs a Genesys 2! Just need to make up a custom PCB so it can interface to the FPGA via the FMC connector, not a big deal. As for the Geneys 2, I cannot justify an extra £600 over the Nexys Video, it's just not worth i
  8. Mario875

    Nexys Video HDMI

    I do think you are correct there and I have possibly assumed a 24-bit colour depth as it's generally fairly standard these days, but as they say "to assume is to make an ass out of you and me". Ideally a free to use video IP would be preferred as it would make things go a lot smoother, this is also a bit of a passion project, so budget is reasonably constrained compared to a professional project. I agree, as I've started digging into video and HDMI it seems to be a bigger and bigger rabbit hole! However that was partly what drew me into the Nexys Video. It has HDM
  9. Mario875

    Nexys Video HDMI

    Thanks for responding, however that doesn't really answer my question. Please see below responses to your answer. I am aware HDMI uses TMDS, I suppose that is my query, how does the Nexys video implement it to achieve [email protected] with 24-bit colour on their built-in demo? Genysys 2 look great, but is about double the cost and if I am not mistaken the Kintex requires a Vivado licence which I believe is included for 1 year with the Genysis 2, but then requires to be paid for, so not really an option for me due to the cost. I have just had a look at th
  10. Mario875

    Nexys Video HDMI

    Hi all, I am considering purchasing a Nexys Video dev board soon, but I have noticed the HDMI port is not connected to the GTP ports on the FPGA, just the standard IO ports. So I am wondering, can this board do 1080p 60fps with 24-bit RGB colour? According to this screen shot from the HDMI demo on the digilent website it appears that it can but I’m not sure how?? I believe the HDMI standards states 1080p 60fps with 24-bit colour (8- bits per colour) requires 4.46 Gbps. The Artix-7 standard IO is only 950 Mbps for LVDS at 2.5v, so I presume t