asmi

Bytes swapping is allowed as long as it's done to entire byte groups (meaning all lines, DQ, DQS and DM). If you look closely, you will see that entire byte 0 of DDR memory chip is wired to byte 1 on Zynq, and vice versa. Bit swapping within byte is also allowed.

Can you try adding weak pullup resistors (10K) to TCK and TMS lines as recommended by the spec? I actually have pullups for all 4 JTAG signals on my designs, and I never had an issue you're describing.

CC pins are only relevant for inputs AFAIK. Besides E15/E16 are actually CC pins. TMDS uses current driver, so it can't work without termination.

It could be the same problem I had on my Genesys 2 board, as both seem to use the same PHY chip. Symptoms are identical to mine when I checked it for the last time. I was proposed a solution, but I didn't try it yet because I was occupied by other projects: You might want to give it a try to see if it works for you. Though if I my memory serves me, there are separate source files for Zynq's ARM PS and for Microblaze CPUs, even though their contents are for the most part identical.

This is really odd issue. HDMI is only supposed to provide 50 mA of current on it's +5V rail, there is no way it will be enough to power the board. In the schematics, I noticed there is a fuse oddly enough marked R134. I would try desoldering it and replacing with Schottky diode to block reverse current from flowing into the board to see if that solved the issue.

Those settings are incorrect BTW. Specifically, this file has VccAuxIO of 1.8 V while in reality it's 2.0 V, the clock period is also only 2500 ps (or 400 MHz), the board's user guide recommends 1112 ps (899.28 MHz). Clock period of 1111 ps (900.09 MHz) works best in practice though, because it allows setting input clock to exactly 200 MHz, which is what's present on the board. I get that this board is designed for people who know their way around schematics, but still - I think both MIG project file and the user guide needs to be updated. I know that we're talking about only 1 picosecond of difference, and IODELAYCTRL technically allows tolerance of ±10 MHz, but I prefer having exact values as it makes calculations easier if you use delay blocks in your custom logic elsewhere.

Memory Interface Generator, Xilinx tool/IP to generate memory controller.

It's in MIG's constraints file as part of MIG project to generate DDR3 controller.

Here they are: Many parts nowadays don't have full part number markings as there is simply not enough space on a package. Oh, and these are 4 Gbit chips, so 8 Gbits or 1 GByte total.

I can answer "yes" to the the first part, as I use HS-3 cable with 2019.2 all the time.

I wouldn't risk it as many DC-DC converters don't like when there is a voltage on their output while they are turned off. But it's up to you really.

Spec requires DNA to report current demands on each of these rails (5V, 3.3V, VIO). So I read it that you're supposed to have DNA MCU on anything you connect to SYZYGY port.

Yep. The spec recommends ATtiny44A MCU which is very cheap ($0.7 for single quantity).

Don't get me wrong - it is a great board, it's just not that good for beginners. I'm not saying it to denigrate anyone, it's just what it is. Are you sure you need UARTs for LED wall? If you use things like this: https://www.adafruit.com/product/420 they use custom serial protocol, and depending on the size of your installation, it will need to be driven at high frequency to achieve good refresh rate. There is some HDL code for it here, but the board they use is no good for you. For HDMI input - there is a fair amount of HDL code for it floating around Internet, but you will need to learn at least the basics of HDMI protocol to understand how this code works and how to adapt it to your needs. I would recommend to take a look at this, the author of this code is a frequent visitor of EEVBlog forums, so he might be able to answer some questions you will probably have.

It's always going to be a moving target for them, considering how many boards they sell, these updates will be a full time job. Users which can't figure this out are unlikely to make much progress with this board anyway. For better or for worse, Genesys is a board for people who know what they are doing as Digilent provides very limited support for it, with very few demos - I would guess because of the price this board isn't their main money maker, and - again because of price - beginners are unlikely to buy it.